haha - this is not the first time i18n has bitten URLs. Although in this case the extra space is incorrect (but Blue Ocean just happens to use that in the URL whereas classic does not).
On Monday, July 25, 2016 at 4:45:18 PM UTC+10, Ivan Meredith wrote: > > Hi there, > > It is because your Jenkins instance is in spanish!. > > There is this bit of code > https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/rest/OrganizationImpl.java#L40 > > And a quick grep > > ivan@MacBook-Pro ~/w/jenkins/core/src/main/resources/jenkins/model > (master)$ grep -R -E 'Hudson.DisplayName=.* $' . > ./Messages_es.properties:Hudson.DisplayName=Jenkins > > I created PR https://github.com/jenkinsci/jenkins/pull/2471 to fix it in > Jenkins, > > and also JENKINS-36907 > <https://issues.jenkins-ci.org/browse/JENKINS-36907> to track it in Blue > Ocean. > > Switching your language should fix this.I imagine this will be changed in > Blue Ocean quickly too. > > On Thursday, July 21, 2016 at 8:31:43 PM UTC+12, 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/a7d1fd6d-c341-40ba-a4d3-5952e11e8b6e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
