[Starlingx-discuss] Role of zuul in build failures related to PLATFORM_RELEASE

Scott Little scott.little at windriver.com
Wed May 27 15:02:17 UTC 2020


The two updates in question:

utilities: https://review.opendev.org/#/c/730108/

ansible-playbooks:  https://review.opendev.org/#/c/730113/


730113 depends in 730108

730108 was WF-1 to prevent merge until 730113 was reviewd

730113 received it's +2/+1 ... Zuul didn't merge because 730108 was not 
merged.

730108 is given it's WF+1 late Friday and merged.

Expected behavior was for 730113 to 'wake up' within zuul and merge.

It did not, and the builds produced unusable loads until the issue was 
noticed on Monday.  730113 had to be given a new WF+1 to wake it up and 
merge.







More information about the Starlingx-discuss mailing list