Adding in support for making any extension pipeline a "nightly" publishing pipeline#8740
Open
richardpark-msft wants to merge 1 commit into
Open
Adding in support for making any extension pipeline a "nightly" publishing pipeline#8740richardpark-msft wants to merge 1 commit into
richardpark-msft wants to merge 1 commit into
Conversation
…Jurek. Yes _the_ Daniel Jurek.
So the important stuff:
- We know it's a "nightly" build because it's scheduled. That's it.
- We don't push GitHub releases for nightlies (it's a lot of clutter).
They only get pushed to our blob storage account.
- Nightlies have their own branch for the registry ('nightly') and their
own registry (cli/azd/extensions/registry.nightly.json).
So to enable this for an extension, just add a nightly publish schedule.
richardpark-msft
requested review from
JeffreyCA,
RickWinter,
danieljurek,
hemarina,
tg-msft and
vhvb1989
as code owners
🔗 Linked Issue RequiredThanks for the contribution! Please link a GitHub issue to this PR by adding |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds “nightly” publishing support for azd extensions by treating scheduled Azure DevOps runs as nightly builds: publish artifacts to an always-latest storage folder, update a dedicated nightly registry on a separate nightly branch, and avoid creating GitHub Releases to prevent clutter.
Changes:
- Add scheduled-run (“nightly”) version suffixing (
-nightly.<buildId>/.nightly.<buildId>) and a registry normalization script for artifact URL rewriting. - Update extension pipeline templates to support nightly publishing semantics (storage-only publish + direct push to
nightlybranch registry). - Document the nightly registry and add Go tests that pin semver upgrade/promotion behavior for nightly versions.
Show a summary per file
| File | Description |
|---|---|
| eng/scripts/Update-NightlyExtensionRegistry.ps1 | Normalizes azd x publish --artifacts output by rewriting local artifact paths to the public storage URL and pruning to the latest nightly entry. |
| eng/scripts/Set-ExtensionVersionVariable.ps1 | Appends semver-valid nightly prerelease suffixes on scheduled runs using the pipeline build id. |
| eng/pipelines/templates/steps/publish-extension.yml | Adds a switch to skip GitHub release creation for nightlies and forces storage uploads to overwrite the nightly folder contents. |
| eng/pipelines/templates/stages/sign-extension.yml | Enables signing for scheduled (nightly) extension builds in addition to CI/manual builds. |
| eng/pipelines/templates/stages/release-azd-extension.yml | Extends release/sign stages to run for scheduled builds (nightlies) as well as manual builds. |
| eng/pipelines/templates/stages/publish-extension.yml | Implements nightly publish flow: storage-only publish and direct-push updates to cli/azd/extensions/registry.nightly.json on the nightly branch with retry-on-conflict. |
| cli/azd/pkg/extensions/nightly_versioning_test.go | Adds tests that pin semver ordering + upgrade/promotion behavior for nightly version formats. |
| cli/azd/docs/extensions/extension-resolution-and-versioning.md | Documents the nightly registry URL/source, retention model, and upgrade/promotion semantics. |
| cli/azd/docs/extensions/extension-framework.md | Adds a short “nightly registry” opt-in section pointing to the detailed versioning doc. |
Copilot's findings
- Files reviewed: 9/9 changed files
- Comments generated: 1
Collaborator
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
vhvb1989
reviewed
Jun 20, 2026
Comment on lines
+89
to
+94
| ```bash | ||
| # Add a new extension source name 'nightly' to your `azd` configuration. | ||
| azd extension source add -n nightly -t url -l "https://raw.githubusercontent.com/Azure/azure-dev/nightly/cli/azd/extensions/registry.nightly.json" | ||
| ``` | ||
|
|
||
| See the [Nightly Extension Registry](./extension-resolution-and-versioning.md#nightly-extension-registry) section for version semantics, promotion behavior, and caveats. |
Member
There was a problem hiding this comment.
What if we make this concept a little more 1st class? Something like azd extension enable-nightly (the name doesn't matter to me).
This would help to worry less about the url and make it simpler. At the end, only 1st party extensions would be listed in the nightly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Most of this comes from the discussion I had with Daniel Jurek. Yes the Daniel Jurek.
Basically:
To enable this for an extension, just add a nightly publish trigger in Azure DevOps (not as part of the YAML itself). I've tested this with a few builds, and even did an upgrade after the extension was pushed:
Here's the latest build of the azd-demo that produced a nightly build: dev.azure.com, publishing microsoft.azd.demo as a nightly build
First part of the work for #8729