[FOLIO-2965] build platforms from master and release branches, instead of snapshot and master Created: 15/Jan/21 Updated: 01/Mar/21 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | TBD |
| Reporter: | Zak Burke | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | FOLIO DevOps |
| Description |
| Comments |
| Comment by Jakub Skoczen [ 18/Jan/21 ] |
|
Zak Burke John Malconian I agree this is confusing, the master branch should track the snapshot {{master} artifacts from individual master branches. As far as the "release" branch goes – it probably makes more sense to have names releases – r1, r2, .. etc. |
| Comment by Zak Burke [ 01/Mar/21 ] |
|
Alternatively, could we change the default branches of these repos to snapshot? That would shift the burden of changing the checked-out branch to our renovate scripts, and it would reduce the developer-impact for folks who are running platforms locally. It might be just as much effort, however, and folks might still raise PRs against the wrong branches ... so maybe it's not worth the effort. Dunno; I'm just thinking through options. |