Projects onedev server Issues #901
#901  Manual jobs should continue insted of triggering dependencies job again
Closed
matias blanco opened 1 month ago

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.

imagen_2.png

so, when a commit it's pushed, the 3 first builds are triggered.

imagen.png

But when I want to trigger the manuals, like "deploy_dev", all the previous builds jobs are triggered again

Automatic jobs finished:
imagen_3.png

Redirect after triggered "deploy_dev"
imagen_4.png

This jobs are listed in build sections:
imagen_5.png

Here we can see all jobs related to this commit, and the duplication of the previous jobs:
imagen_6.png

jbauer commented 1 month 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' 1 month ago
Previous Value Current Value
Open
Closed
Robin Shen commented 1 month 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:

https://faun.pub/understanding-onedev-pipeline-db0bb0e54aa7

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
Seen Builds
Issue Votes (0)
Watchers (4)
Reference
issue onedev/server#901
Please wait...
Page is in error, reload to recover