Make deployment to 'tested' run asynchrnously with the '*-tester' jobs
General
Additional Info
General
Additional Info
Description
Activity
Show:
Barak Korren February 5, 2018 at 8:20 AM
fix patch merged
Barak Korren January 15, 2018 at 7:24 AM
This is not as simple as it seemed initially. We need to ensure the deployment to 'tested' completes before we can run the next build of the 'tester' job, otherwise components verified by a previous run of the 'tester' job will not be available for the next run.
We can still make the deployment happen in parallel with the time the 'tester' job spends waiting for artifacts to be built, we will need to make the tester job wait for the 'deploy' job to finish at the same time it waits for the build jobs.
Fixed
Details
Details
Assignee
Barak Korren
Barak Korren(Deactivated)Reporter
Barak Korren
Barak Korren(Deactivated)Blocked By
Blocking on code review
Components
Priority
High
Created January 10, 2018 at 11:09 AM
Updated February 28, 2018 at 3:33 PM
Resolved February 5, 2018 at 8:20 AM
The 'deploy-to_*_tested' job is triggered by the '*-change-queue-tester' job which then waits for it to finish.
Since the 'tested' repo can get big, the 'deploy-to_*_tested' job can end up taking a long time. This in turn means the next run of the '*-change-queue-tester' job gets delayed by a long time.
We should change things so that the '*-change-queue-tester' job no longer waits for the 'deploy-to_*_tested' job to finish