Create AzDO pipeline for JDK updates and enhance version detection - #156
Merged
Conversation
…attach to AzDO run
…ders during version-bump commits
…ion handling and commit clarity
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
2 participants
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.
Summary
Follow-up to #153, which introduced
versions.jsonas the single source of truth and the version-scraping script. This PR replaces the GitHub Actions updater from #153 with an Azure DevOps pipeline that actually opens the version-bump PR..devops/update-versions.ymlrunsscripts/update-versions.shto refreshversions.jsonfrom the upstream sources (Microsoft Build of OpenJDK download page + Adoptium API) on a Tue/Thu schedule, then commits the change on a clean branch offmainand opens a PR. Two new scripts keep the logic out of the pipeline YAML:summarize-version-changes.sh(renders a readablevendor major: old -> newsummary) andopen-version-pr.sh(creates/refreshes the PR).Why Azure DevOps instead of GitHub Actions
The GitHub Actions workflow from #153 could refresh
versions.jsonbut couldn't open a PR: the defaultGITHUB_TOKENis blocked from creating pull requests by org policy, and the usual workaround — a dedicated GitHub App — requires the OSPO /microsoft/github-operationsapproval process rather than being self-service. The Azure DevOps pipeline authenticates through the existingGithub-Java-EngineeringGitHub App service connection which already has the proper access to push the branch and open the PR with no new credentials or approvals.Changes
.devops/update-versions.yml(scheduled AzDO pipeline, with a dry-run vs create-pull-request mode).scripts/summarize-version-changes.shandscripts/open-version-pr.sh..github/workflows/update-jdk-versions.yml.Tests