[FOLIO-2885] SPIKE: consider improvements to the release process Created: 19/Nov/20 Updated: 16/Mar/21 Resolved: 16/Mar/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | DevOps Sprint 109, DevOps Sprint 107, DevOps Sprint 108, DevOps Sprint 106 | ||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||
| Description |
|
Consider what can be done to improve the process of making individual module releases. This is especially problematic for bugfix releases where POs would like see individual bugfixes released and deployed (e.g to the bugfest env) as soon as they are ready, while development teams (and devops) prefer that multiple bugfixes are bundled into a single release to minimize the preparation (and deployment) overhead. During the DevOps Team standup we have discussed the following improvement ideas:
|
| Comments |
| Comment by Zak Burke [ 09/Dec/20 ] |
|
Notes:
Questions:
|
| Comment by Julian Ladisch [ 10/Dec/20 ] |
|
I suggest to use semantic versioning instead of release branches like b5.6-honeysuckle and b5.6-iris.
These artifacts are not automatically deployed to bugfest where the current version is mod-foo-5.6.7 or mod-foo-5.6.7-SNAPSHOT:
|
| Comment by Julian Ladisch [ 10/Dec/20 ] |
We should consider using GitHub Actions to build, test and publish artifacts. GitHub Actions are generally available since March 2020. GitHub Action Minutes are free for public repositories. Merging a pull request or publishing a release can trigger an action: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/migrating-from-jenkins-to-github-actions |
| Comment by John Malconian [ 10/Dec/20 ] |
|
Lots of good ideas and suggestions here. I think there is potential for better Jira/CI/CD integration. I am also interested in taking a look at Github Actions to eventually replace or at least offload Jenkins. |
| Comment by Marc Johnson [ 11/Dec/20 ] |
I did not know that teams did this, it doesn't seem to fit with the current release guidance. That said, I wouldn't expect (with RAML Module Builder and stripes upgrades each release) that many modules would retain the same version across official distributions.
This seems like a particularly awkward anti-pattern. There should not be more than one definition of a module version. |
| Comment by Jakub Skoczen [ 14/Jan/21 ] |
|
Julian Ladisch Marc Johnson Using branches like b5.8-iris is NOT aligned with our release guidelines. Who is doing that? |
| Comment by Julian Ladisch [ 14/Jan/21 ] |
|
This has been proposed in the first post, see above:
|
| Comment by Marc Johnson [ 14/Jan/21 ] |
Who / what is this comment a response to? Is it to Jakub Skoczen question about who is using a branch like b5.8-iris? |