It's quite rare to have to trigger a pipeline manually once it's 100% setup. But sometimes you need an emergency build or need to change a variable just to make an experimental build (like, changing endpoints for a beta testing build which you don't want to accidentally make permanent by forgetting to remove it).
It would be nice to, as admin of the repo, when manually triggering a pipeline, to be able to overwrite a variable for experimental purposes.
What do you guys think?
PS: I know I can just declare a pipeline for a specific branch and do ifs and elses to read different variables, but it's just too much manual work when all you want to make sure is that the new keys or tokens for a remote service are already operational before replacing the old ones in the pipeline, no? :-)
Any thoughts are welcome and I hope this becomes a feature at least for admins triggering manually the pipelines so we can do experimental builds with lower risk of leaving something behind.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events