You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having problems with getting Release-IT to orchestrate releases in GitLab pipeline. I have followed the GitLab pipeline recipe and this may be a case of just needing more documentation on how Release-IT is expecting to handle the release.
What I have done is to create a MR from the main branch to the release branch. When I merge the MR into release I have a CI job that run to handle the release. The following is the job definition:
The version to be released is correctly determined
The change log is generated, commited to the release branch and pushed back to GitLab
The version tag is created and pushed back to GitLab
GitLab release is created with artifacts uploaded
What seems not to work:
The change log commit set does not get applied to main branch. This may be a bit out of the scope of Release-IT and may be able to be done with a git checkout main; git rebase release after the run of Release-IT.
The packages for the release get generated before Release-IT executes so the package names do not have the updated version strings added to the name. So I got package names like aamm_20231007-release-5bfa0be_all.ipk instead of aamm_0.2.0_all.ipk.
GitLab release does not get the change log
Given the point about the incorrect package names, it seems that Release-IT needs to be run in 2 stages so that the version information can be generated, paused for the build to be created with the version information and then resumed to create the GitLab release and upload the build artifacts.
For completeness, the following is the Release-It configuration that is being used:
I am having problems with getting Release-IT to orchestrate releases in GitLab pipeline. I have followed the GitLab pipeline recipe and this may be a case of just needing more documentation on how Release-IT is expecting to handle the release.
What I have done is to create a MR from the
main
branch to therelease
branch. When I merge the MR intorelease
I have a CI job that run to handle the release. The following is the job definition:This sort of works and sort of does not work.
What works:
release
branch and pushed back to GitLabWhat seems not to work:
main
branch. This may be a bit out of the scope of Release-IT and may be able to be done with agit checkout main; git rebase release
after the run of Release-IT.aamm_20231007-release-5bfa0be_all.ipk
instead ofaamm_0.2.0_all.ipk
.Given the point about the incorrect package names, it seems that Release-IT needs to be run in 2 stages so that the version information can be generated, paused for the build to be created with the version information and then resumed to create the GitLab release and upload the build artifacts.
For completeness, the following is the Release-It configuration that is being used:
Any suggestions or corrections to my assumptions would appreciated.
The text was updated successfully, but these errors were encountered: