[BUILD-507] Define the three Jenkins jobs in the same repository thanks to some Job DSL Created: 26/Aug/21 Updated: 15/Nov/21 Resolved: 15/Nov/21 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Epic Link: | Release automation |
| Description |
|
In our current Jenkins pattern, there is one branch per repository. This is why we have three repositories for the project:
However, the last two jobs really belong to the same project. They should be in the same repository, and some Job DSL should create all the jobs in the repository. |
| Comments |
| Comment by Maxime Michel [ 15/Nov/21 ] |
|
Using Bitbucket labels instead. That way the multiple jobs are grouped together in some way. |