Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

post-merge build-artifacts jobs can run out of order

Description

Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel.
The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order.

To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available.

Activity

Show:

Barak Korren June 24, 2018 at 8:26 AM

This issue is not relevant for STDCI V2 as all post-merge actions happen within the same job. So closing Wontfix

Barak Korren July 3, 2017 at 3:49 PM

yes. for when using build-artifats as a yum repo with the latestStableBuild link.

Eyal Edri July 3, 2017 at 3:04 PM

is this still relevant after the deployment of the new logic of deploy rpms?

Won't Fix

Details

Assignee

Reporter

Priority

Created March 12, 2017 at 12:28 PM
Updated September 2, 2018 at 3:51 PM
Resolved June 24, 2018 at 8:26 AM

Flag notifications