Release Automation Process #9555
Merged
Conversation
This file contains 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
offtherailz
force-pushed
the
release_automation
branch
from
9327042 to
12d895c
Compare
11 tasks
offtherailz
commented
Nov 16, 2023
offtherailz
commented
Jan 30, 2024
tdipisa
reviewed
Feb 7, 2024
There was a problem hiding this comment.
@MV88 this PR is ready for the final review the only missing part is the one generating the docker image for which we can continue using the jenkins for the moment. That part for the docker image will be included later with a dedicated PR.
We need someone familiar with the release process like you are for reviewing this and finally merge.
MV88
requested changes
Feb 14, 2024
There was a problem hiding this comment.
some comments here and there. maybe we can talk a bit @offtherailz ?
there is a wrong link inside release_steps.md which is the mapfish print link check if here
it points to http_proxy (line 18)
| Here a flow chart that describes the process: | ||
|
|
||
| ```mermaid | ||
| flowchart TD |
Co-authored-by: Matteo V. <[email protected]>
tdipisa
approved these changes
Mar 4, 2024
|
@offtherailz please backport to stable branch. Thanks |
ElenaGallo
added
the
BackportNeeded
|
the commit 39e9019 looks to be present in 2024.01.xx commits list
For some reason |
offtherailz
removed
the
BackportNeeded
offtherailz
added a commit
to offtherailz/MapStore2
that referenced
this pull request
Apr 10, 2024
* Add actions * Updated workflows for deprecations and security * Fixed changelog stuff * renamed release workflow file * Fixed concurrency * Separated release steps * Update for uniformity the scripts. Fixed wrong java modules set * Fixed wrong version system in binary * Fixed version update script * Updated documentation. Last fixes * Removed file committed in error * Improved docs * Improved docs * Improved docs * Minor fixes to doc * Fixed release procedure missing paragraph * Update procedure for linking latest stable doc * Update release_steps.md * Update .github/ISSUE_TEMPLATE/release_steps.md * Apply suggestions from code review Co-authored-by: Matteo V. <[email protected]> --------- Co-authored-by: Matteo V. <[email protected]>
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
This PR introduces release procedure automations for:
At the moment, we still rely on jenkins for :
While we rely on github actions to build and publish artifacts (If we want to use the artifacts from jenkins, we can still re-upload them)
We can later automate docker stuff and updates to MapStoreExtension repository accordingly to finalize the automation
(the following examples are on my fork, of course the final operations have to be applied to the real repository)
Cut release branch
Lunching the Cut release branch workflow from github
screencast-github.com-2023.10.04-11_41_42.webm
At the end the branch will be created with the version fixed accordingly, and a PR will be sent to the master branch with the versions updates.
screencast-github.com-2023.10.04-12_23_55.webm
Prepare Release
The release process will
This process have to be executed on the release branch (a check protect it to accidentally exceute on master).
Create release
This action creates effectively the relase. This has been separated from prepare-release in order to be able to lunch them separately (e.g. if something went wrong, we can fix and generate only the release).
After execution succeed, the release will be ready. You can run manually in draft with the binaries attached (only docker part missing).
You can in the meanwhile:
Post release
After the release, you can trigger the post release process to restore snapshots and increase package.json versions on the release branch.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#9001
What is the new behavior?
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information