StarlingX Developers:

 

In the past 2 weeks we’ve had many days of build failures.  A full timeline is below but the majority of the issues were associated with delivery of a large number of commits for 2 large features.  And having this done just days after build layering was enabled for the project.  Looking through the variety of failures, the Build Team identified the following recommendations to prevent similar issues in the future.  These recommendations are for both the developers as well as the Cores.

 

Recommendations for Developers:

  1. Every developer must do a final build before removing WFL -1 from their commit. 
  2. For larger features or any commits that introduce or change an rpm, the developer build must be done in clean workspace and clean ‘output’ directories. This includes starting with a clean mirror download from CENGN.  Address any failures seen in your build when using a clean workspace.  Identify any mirror updates required and see [3] for how to handle.
  3. Any changes to lst files need to be handled separate from rest of code/feature as follows:
  4. Community needs to move over to use the layered build approach for their developer builds.  This is the production way of building and will save developer build times for most commits.

 

Recommendations for Cores:

  1. Ensure large features have followed the above guidelines before allowing the code to merge.

 

If there are any other suggestions please provide your input.  Thank-you.

 

StarlingX Build Team

 

----------------------------------------

----- Timeline of failures --------

 

April 28

 

April 29

 

April 30

 

May 1-3

 

May 4

 

May 5

 

[1] https://review.opendev.org/#/c/725214/

[2] https://review.opendev.org/#/c/724951/

[3] https://review.opendev.org/#/c/724955/

[4] https://review.opendev.org/#/c/725379/

[5] https://review.opendev.org/#/c/725371/

[6] https://review.opendev.org/#/c/725447/