|
matias blanco opened 2 years ago
|
||||
|
I think you have to use build promotion. That means you open the scans_pre build and then trigger the next build from there. See: https://medium.com/nerd-for-tech/build-promotion-with-onedev-ce6c275aa1b8 |
||||
|
Robin Shen changed state to 'Closed' 2 years ago
|
||||
|
|
It is by design that triggering from commits view will initiate a new pipeline. As @jbauer mentioned, build promotion should be used if you want to trigger downstream jobs of certain build. Or you can trigger downstream jobs from build pipeline view: |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
Not Found
|
Issue Votes (0)
Watchers (4)
Hi,
When I configure pipelines, some jobs should be manual (in this case the latest 2 jobs), so I configure it in these jobs only the "Job Dependencies", without trigger rules after jobs dependency terminate successfully.
so, when a commit it's pushed, the 3 first builds are triggered.
But when I want to trigger the manuals, like "deploy_dev", all the previous builds jobs are triggered again
Automatic jobs finished:
Redirect after triggered "deploy_dev"
This jobs are listed in build sections:
Here we can see all jobs related to this commit, and the duplication of the previous jobs: