-
Bug
-
Resolution: Unresolved
-
Critical
-
newest version of jenkins & blueocean plugin
1.6.0-beta-3
- Core 2.107.3
- 5787c97
-
-
Blue Ocean - Candidates, Blue Ocean - 1.6 - beta 4
Would like to report an issue that is very similar to JENKINS-48027, that is still not fixed in the latest beta build (1.6.0-beta-3). The pipeline doesn't show up, and one of the requests returns a 404 error.
Apparently the issue not only occurs when there is an "@" in the branch name, but also when it contains a space.
Not sure if it's relevant, but we are using SVN instead of GIT.
- duplicates
-
JENKINS-49818 Unable to open multibranch pipeline projects where the branch name contains a space
-
- Closed
-
[JENKINS-51636] No pipeline when branch name contains space
Epic Link | New: JENKINS-35761 [ 171656 ] |
Assignee | New: ivan wang [ ivan ] |
Assignee | Original: ivan wang [ ivan ] | New: Vivek Pandey [ vivek ] |
Sprint | Original: Blue Ocean - 1.6 - beta 4 [ 561 ] | New: Blue Ocean - Candidates, Blue Ocean - 1.6 - beta 4 [ 441, 561 ] |
Link |
New:
This issue duplicates |
I think encoding of job name across jenkins data model and front end is broken. imeredith we discussed in past to have uniform encoding/decoding at front end and backend and even some other approaches. Do you know whatever happened with that or that '@' encoding issue as well?