-
We are currently researching the deployment strategy for AL-Go but are a bit confused as to how it works in real life. Our process is as follows:
Very basic and what most partners probably follow. Freddy describes the process in AL-Go as follows:
This is where we are confused. Because after we publish to the FAT environment we obviously continue developing new features that are pushed into main Freddys next step is to create a release of the latest build version from main, but if we developed new features in the meantime that means we are now publishing features that have never been tested in FAT. So, the process actually looks like
So, our understanding would be
First of all, I want to know if this process is correct or if we are simply misunderstanding something? Secondly, we wanted to try our workflow with creating a prerelease but we are not really sure what version to use in the release. For example for the prerelease we defined the version to be 26.0.0 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @Mkublbock Thanks for sharing your experience when working will AL-Go for GitHub. Your feedback is greatly appreciated!
Correct. This is indeed the assumed process. "Create release" action utilizes GitHub releases. Once you have a pre-release, you don't need to create a new release, you can change the pre-release manually to a release by unsetting the "Set as a pre-release" check. |
Beta Was this translation helpful? Give feedback.
Hi @Mkublbock
Thanks for sharing your experience when working will AL-Go for GitHub. Your feedback is greatly appreciated!
Correct. This is indeed the assumed process.
"Create release" action utilizes GitHub releases. Once you have a pre-release, you don't need to create a new release, you can change the pre-release manually to a release by unsetting the "Set as a pre-release" check.