• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • blueocean-plugin
    • 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.

          [JENKINS-51636] No pipeline when branch name contains space

          Vivek Pandey added a comment -

          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?

          Vivek Pandey added a comment - 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?

          Tom Wtb added a comment -

          Do you have an idea of when this will be fixed?

          Tom Wtb added a comment - Do you have an idea of when this will be fixed?

          James Mitchell added a comment - - edited

          I'm also having similar issues, using Perforce for the underlying version control system, using spaces not @, it appears the string is being encoded twice 'Hello World' becomes 'Hello%2520World" with %25 being '%' and '%20' being the space.

           

          NOTE: This only occurs on the branch, not the other parts of the string (e.g. job name)

          James Mitchell added a comment - - edited I'm also having similar issues, using Perforce for the underlying version control system, using spaces not @ , it appears the string is being encoded twice 'Hello World' becomes 'Hello%2520World" with %25 being '%' and '%20' being the space.   NOTE: This only occurs on the branch, not the other parts of the string (e.g. job name)

          Tom Wtb added a comment -

          Any news on this? This bug prevents us from using the BlueOceans plugin.

          Tom Wtb added a comment - Any news on this? This bug prevents us from using the BlueOceans plugin.

          Liran P added a comment -

          Nothing new?
          It's still reproduced with the latest version of Jenkins / BlueOcean / Pipeline Multibranch Plugin, and prevents us from using BlueOcean as well.

          Whitespaces are a valid character in hg branches and we have to support that.
          I will try to look into it this weekend.

          Liran P added a comment - Nothing new? It's still reproduced with the latest version of Jenkins / BlueOcean / Pipeline Multibranch Plugin, and prevents us from using BlueOcean as well. Whitespaces are a valid character in hg branches and we have to support that. I will try to look into it this weekend.

            Unassigned Unassigned
            tomwtb Tom Wtb
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: