Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Have a main off switch for async release publishing
See original GitHub issueLet’s say there is major outage on AzDo release pipelines and we are one day ahead of shipping and we need packages to be published. Today, the backup plan would be to go to each repo and change _PublishUsingPipelines to false. This would take time between making the change and getting it merged, etc.
We should have a config-like file in eng/common so all repos get it where we define whether we should use the things defined in the YAML or we should override what the YAML defines and just go the “previous” way.
/cc: @JohnTortugo @mmitche
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Won’t that just change how Arcade publishes?
I thought the idea was a kill switch for the feature for emergencies that we could change in Arcade, and then flow to all repos.
If we change it in the template to always be false, we ensure that no repo specific configuration will override it.
I’m closing this since eventually we’ll move all repos to stages and everything (build + publishing) will happen in the same pipeline