-
Notifications
You must be signed in to change notification settings - Fork 82
-
Notifications
You must be signed in to change notification settings - Fork 82
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
rewire-pipeline
Command Switches YAML Triggers
#1237
Comments
Also seeing similar behavior. |
Wondering if this is the intended functionality & assumption that YAML pipelines would be using |
I tested out adding the
|
I would expect it to still be overridden, but does a PR to github repo automatically kick off ADO pipeline? EDIT: Oh nevermind, that should be default. |
Description
After running the
rewire-pipeline
against an ADO YAML pipeline, the pipeline options/triggers have been changed unexpectedly. Curling the definition content it looks like therewire-pipeline
command removes the pipeline definitiontriggers
object and instead populates it withoptions
(mine didn't have options before anyway). After manually unchecking theOverride the YAML continuous integration trigger from here
checkbox and curling the definition, thetriggers
object is repopulated.After Running Command:
After Manually Reverting/Unchecking:
Reproduction Steps
Run the
rewire-pipeline
command against an ADO YAML pipeline without any explicit pipeline definition trigger overrides. After running the command, edit the pipeline in ADO and navigate to the triggers. Notice theOverride the YAML continuous integration trigger from here
checkbox is checked.The text was updated successfully, but these errors were encountered: