Feature #2745
Orchestration
| Status: | In Progress | Start date: | 11/16/2017 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: | J. Moringen | % Done: | 50% | ||
| Category: | Template | ||||
| Target version: | - |
Description
Hi Jan,
please have a look at branch wip-orchestration that tackles various issues with your latest improvements to orchestration (and consider it for rebasing into master).
1. I moved more code to the common folder.
2. In ci-deploy, but probably also in other modes, you should disable all jobs before building to disable auto-triggering by job dependencies.
3. Trigger build of downstream jobs also if upstream is only UNSTABLE.
4. Cancel jobs scheduled by orchestration, if orchestration is cancelled. That's an easy way for the user to cancel all the dozens of jobs together with orchestration.
History
#1 Updated by J. Moringen over 6 years ago
- Category set to Template
- Status changed from New to In Progress
- Assignee set to J. Moringen
#2 Updated by J. Moringen over 6 years ago
- % Done changed from 0 to 30
#3 Updated by J. Moringen over 6 years ago
- % Done changed from 30 to 50
In ci-deploy, but probably also in other modes, you should disable all jobs before building to disable auto-triggering by job dependencies.
This should already be the case for modes in which it makes sense, i.e. ci and ci-deploy. The current workflow should be:
- Generate jobs
- All jobs start out disabled when newly generated
- Existing jobs are not re-disabled
- Run "initial orchestration" job
- Builds all jobs in dependency order
- Enables jobs in the process
- Rely on SCM trigger
#4 Updated by R. Haschke over 6 years ago
In toolkit and citk mode, it's important to re-disable all jobs before when running orchestration.
#5 Updated by J. Moringen over 6 years ago
In toolkit and citk mode, it's important to re-disable all jobs before when running orchestration.
How so? These modes don't configure SCM triggers so jobs shouldn't start randomly.
#6 Updated by R. Haschke over 6 years ago
They don't configure SCM triggers by default. However, one may do that anyway.