-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger a merged build per pipeline rather than step #6
Comments
Additionally documents checkout vs trigger modes, closing #6
Additionally documents checkout vs trigger modes, closing #6
Additionally documents checkout vs trigger modes, closing #6
Additionally documents checkout vs trigger modes, closing #6
I'm interested in using this plugin over our home-grown solution, however we would need this functionality before switching. We currently pin the commit that will be merged into the PR as an artifact/metadata so that there's a consistent merge for all of the different steps, even if new commits are added to the target branch. |
The plugin can do what's in this bug, it's just about avoiding duplicate builds on:
The idea was to set metadata to make sure it's only triggered once. Regardless if you have multiple steps. Is that what you're after? |
Not really-- our issue comes from if you have steps that don't start for a while in a build, or if you retry a step, you can get into a state where the merge ref from master isn't the same across all steps since each step performs the merge into the pr branch independently. Maybe I'm misunderstanding how it works? |
If the build pipeline has multiple steps, then multiple merge builds will be triggered. There should be only merged build triggered.
The text was updated successfully, but these errors were encountered: