-
Bug
-
Resolution: Fixed
-
Critical
-
None
When used with the GitHub Organization Plugin (most used pipeline plugin that auto-creates jobs for github repositories and branches) you will get a meaningless radiator view.
This happens because radiator view assumes that the build name is the branch name, which means that you will get something like the attached screenshot, full of boxes with names of the branches but that are missing the named of the repository which is even more important than the branch name.
Here is an exampe of url of such a job https://ci.example.com/job/github-orgname/view/radiator/job/repo-name/job/master/66/
[JENKINS-36320] Radiator jobs names meaningless when used with GitHub Organization Folder Plugin
| Workflow | Original: JNJira [ 173019 ] | New: JNJira + In-Review [ 184884 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Summary | Original: Radiator jobs names are meaningless when used with GitHub Organisation Plugin | New: Radiator jobs names are meaningless when used with GitHub Organization Folder Plugin |
| Summary | Original: Radiator jobs names are meaningless when used with GitHub Organization Folder Plugin | New: Radiator jobs names meaningless when used with Pipeline Multibranch Plugin |
| Summary | Original: Radiator jobs names meaningless when used with Pipeline Multibranch Plugin | New: Radiator jobs names meaningless when used with GitHub Organization Folder Plugin |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |