[FOLIO-3387] Detect common mistakes with module configuration early in CI stages Created: 13/Jan/22 Updated: 05/May/23 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | David Crossley | Assignee: | David Crossley |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 135, DevOps Sprint 136, DevOps Sprint 137, Kitfox: sprint 165, DevOps sprint 132, DevOps Sprint 133, DevOps Sprint 134 |
| Development Team: | FOLIO DevOps |
| Description |
|
Some mistakes with module configuration will cause disruption for subsequent build systems, and so hinder further services and development, and cost devops time. Detect such during the early phases of a module project repository branch build continuous integration. Some grief situations and some notes:
|
| Comments |
| Comment by Marc Johnson [ 13/Jan/22 ] |
Given that our mainline builds are used to seed our pre-release artefacts, I like the idea of failing mainline builds that are not considered a pre-release. |