[CIMAN-1] job-template names should use {project-name} Created: 22/Mar/19 Updated: 16/Apr/19 Resolved: 16/Apr/19 |
|
| Status: | Done |
| Project: | CI-Management |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | High |
| Reporter: | Eric Ball | Assignee: | Milin Jaiswal |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The difference between {project} and {project-name} is that {project} is used for git, and can therefore support slashes. {project-name} needs to replace all slashes with dashes, and should be used for job naming. Jenkins interprets slashes as requiring job folders, which we do not use. This was not previously detected due to the lack of subprojects. However, since there are now quite a few subprojects that will likely start using shared jobs soon, it is important to get this fixed soon. |
| Comments |
| Comment by Milin Jaiswal [ 16/Apr/19 ] |
|
The changes have been made and merged through https://gerrit.akraino.org/r/#/c/545/. |