feat(ci): [TASK] Add release workflow support for parallel J (#34637)#34664
Open
feat(ci): [TASK] Add release workflow support for parallel J (#34637)#34664
Conversation
Add support for building multiple Java versions in parallel during releases and create new manual deployment workflow with safety checks. New workflows: - cicd_7-release-java-variant.yml: Automatic parallel Java variant builds - Triggers on release branch creation - Runtime -Dchangelist override for Maven versioning - Skips one-time operations (javadocs, plugins, labels, SBOM) - Supports multiple Java versions (e.g., Java 25 + Java 21) - cicd_8-manual-deploy.yml: On-demand Docker image deployment - Deploy from any branch/tag/commit - Safety checks prevent artifact collision - Separate environment (GitHub UI) and version (artifacts) inputs - Artifact suffix default prevents Maven/Artifactory namespace collision - Replaces legacy-release_publish-dotcms-docker-image.yml Modified workflows: - Add Java version override and artifact suffix support - Runtime -Dchangelist override in release phase - Dual suffix handling (dash for Maven, underscore for Docker) - Conditional operations for Java variants Deprecation notices: - Legacy workflows marked deprecated with migration paths - LEGACY_WORKFLOW_MIGRATION.md documents transition plan - 3 workflows identified safe to delete (no usage 9+ months) Architecture: - Primary and variant workflows run in parallel from same release branch - Distinct namespaced artifacts prevent collisions - Modular phases ensure consistency Issue: #34637 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
8 tasks
8 tasks
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.
Description
Add support for parallel Java version builds during releases with automatic workflow triggering and new manual deployment workflow with safety checks.
Changes
Architecture
Both primary and variant workflows run in parallel from the same release branch and commit, ensuring identical source code. The variant workflow uses runtime Maven property precedence to override -Dchangelist without creating separate branches.
Testing
Changes
Testing
Closes #34637
Issue: [TASK] Add release workflow support for parallel J