|
Daniel Gollings opened 2 years ago
|
||||
|
What do you mean by "pipline job" and "commit job" here? For a pull request, it will show all jobs configured with trigger "pull request open/update", and the commit these jobs fired off is the current merge commit (target branch and source branch) of the pull request. |
||||
|
|
commit build job is the one inline with a commit pipeline build job -> I meant PR build job, is the one displayed on the right in a PR I think the issue there was the conflicting triggers mentioned in issue #863 |
||||
|
|
I see. Commit job is different from PR job. When you push a commit to source branch of a pull request, the commit job runs against head commit of the source branch if you have a trigger to run job upon branch update, and PR job runs against merged commit of source branch and target branch if you have a trigger to run job upon pull request open or update. If you observe odd behavior, please try to reproduce it and let me know the steps. |
||||
|
|
Daniel Gollings changed state to 'Closed' 2 years ago
|
||||
|
|
I've since figured out the difference, thanks |
| Type |
Question
|
| Priority |
Normal
|
| Assignee |
I have four PRs open, two with online 'commit build jobs' and two with a 'pipeline build job' view on the right (one of the PRs has both styles)
What causes it to display a commit vs PR build job?