Adding in first pass with copilot at doing nightly builds.#8726
Adding in first pass with copilot at doing nightly builds.#8726richardpark-msft wants to merge 1 commit into
Conversation
- Run the individual release pipelines in a loop, from one orchestration job (release-ext-foundry-nightly.yml), There's a staged suffix variable that only gets set when we're doing this kind of aggregate job, so the stages all have unique names. (normally it's blank) - Use a simple versioning standard - whatever the <version> for the plugin + .nightly.buildnumber. - No signing, just FYI. This is similar to what we get for dev builds today - there's also no docs about it, which makes me wonder if signing isn't needed, or if it's annoying and we need to include instructions about how to allow our unsigned binaries. Also, added in some tests just to make sure that our nightly versions, beta versions and normal stable versions all compare okay against each other.
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
Also, added in some tests just to make sure that our nightly versions, beta versions and normal stable versions all compare okay against each other.