Hi Javier,
Hmm, certainly sounds like something is up. How did you install Blue Ocean?
If you built it from source could you try to install it from the experimental
update center <https://jenkins.io/blog/2016/07/19/blue-ocean-update/> and
try again?
We are performing weekly binary releases on the path to the beta release
and you may have a snapshot where some key things (such as path encoding)
was not working correctly.
Sorry for not responding sooner as I've been traveling for work.
On Thursday, July 21, 2016 at 6:31:43 PM UTC+10, Javier Martín Caro BEEVA
wrote:
>
> Hi there!
>
> We have set up jenkins blue ocean behind a nginx reverse proxy and
> configured successfully the prefix in the url to <URL>/jenkins. Despite of
> this, when we access to the blue ocean ui in <URL>/jenkins/blue and try to
> access some pipeline, a 422 (unprocessable entity error) is displayed in
> the browser debugging console and a white screen is shown.
>
> The URL in the browser is like the following (note the encoded space):
>
> https://<URL>/jenkins/blue/organizations/*jenkins%20*/<pipeline>/activity
>
>
>
> When we call the blue ocean API for organizations the following
> information is shown (https://<URL>/jenkins/blue/rest/organizations/):
>
>
> [{"_class":"io.jenkins.blueocean.service.embedded.rest.OrganizationImpl","_links":{"pipelines":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>
> /pipelines/"},"self":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>
> /"},"user":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>
> /user/"},"users":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
> /users/"}},"name":"jenkins "}]
>
>
> Note the white space in the organizations href after /jenkins /pipelines.
>
>
> If we call to
> https://<URL>/jenkins/blue/rest/organizations/jenkins/pipelines/<pipeline>/runs/
> the following message is shown:
>
>
> {
>
> "message" : "Organization jenkins not found",
>
> "code" : 422,
>
> "errors" : [ ]
>
> }
>
>
> But if we force the organization to be jenkins%20
> (https://<URL>/jenkins/blue/rest/organizations/jenkins%20/pipelines/<pipeline>/runs/)
> the information is displayed correctly.
>
>
> Can someone help us to configure the proper name for the organization? We
> thought it was the jenkins url in the settings page but this is set to
> https://<URL>/jenkins/.
>
>
> Old UI is working properly for all pipelines, folder organizations and
> bitbucket team jobs.
>
>
> Thank you and regards!
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/42213fb6-7543-422a-84cc-b87892956ea4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
