[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Robert Watkins commented on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
The env.JOB_NAME still has escaped characters. Example usage in my pipelines:
def notifySuccessful() {
hipchatSend color: 'GREEN', credentialId: 'HipChat', message: "${env.JOB_NAME.replace('%2F', '/')} ${env.BRANCH_NAME} ${env.BUILD_NUMBER} Successful", notify: true, room: 'Build Server Messages', sendAs: 'Jenkins', server: '', v2enabled: false
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. The file system hasn't used % for some time (since Jesse's fixes in 2016) - but it also can't be mapped back to the branch name. The way I've been using to get the branch name (e.g. to publish artefacts to S3 in a branch-specific folder) is to use `env.BRANCH_NAME` This works for me - I don't really care where on disk my build is located, but I do care where I'm going to put it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title
Robert Watkins commented on JENKINS-41425
Re: Refreshing page with / in job name results in 404
Okay, so changing this, in my nginx jenkins.conf file:
location /jenkins/ {
proxy_pass http://jenkins:8080/jenkins/;
...
}
to this:
location /jenkins/ {
proxy_pass http://jenkins:8080;
...
}
worked. Hmm - going back through the history of my config file, this is what I actually had at the start of my Jenkins/Nginx config. But then I wanted to run Jenkins on a subpath so I could put another web app (Sonatype Nexus) on the same server - and that's when I screwed it up. Weird.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Michael Neale mine are attached above. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 I can confirm that the https://ci.blueocean.io/blue/organizations/jenkins/folders%2Ftest/activity link works fine for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Vivek Panday I've created my jobs and folders through the UI, plus via the BitBucket Branch Source Plugin. Both exhibit the problem I described - at least when going through the nginx proxy. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 I've added the nginx config files from my Docker setup, for reference. Basically, I run nginx in front on port 80 and 443 (with 80 -> 443), proxying requests for /jenkins to the http://jenkins:8080/ address. Normally, I don't expose the Jenkins port directly, but I've got it exposed for now, and when I access it directly over HTTP, things work. When I go via HTTPS through the reverse-proxy, it doesn't. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins updated an issue Jenkins / JENKINS-41425 Refreshing page with / in job name results in 404 Change By: Robert Watkins Attachment: jenkins.conf Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins updated an issue Jenkins / JENKINS-41425 Refreshing page with / in job name results in 404 Change By: Robert Watkins Attachment: nginx.conf Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 I haven't yet had a chance to try the PR, but I do have more information to share. I set up a local copy of Jenkins, and tried to reproduce the behaviour - and I could not. I then configured an nginx reverse-proxy in front of it, the same as I have in my production version - and the problem came back. I then exposed the port I run Jenkins on in my production Docker container. Accessing Jenkins directly, and I don't see the problems I described above. When I go via the reverse proxy, I do. I suspect it's an issue with how the URL rewriting works. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 I'll need to set up a dev build first, but sure - I'll do that tomorrow. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins edited a comment on JENKINS-41425 Re: Refreshing page with / in job name results in 404 [~tfennelly] - I'm using Safari 10.0.3 (macOS Sierra).[~michaelneale] In both Chrome and Safari, I can navigate within the Blue Ocean UI just fine. However, as soon as I get to a page that uses an escaped /, I can't refresh it without getting a 404 due to the %2F becoming unescaped. This is a problem, especially on the build pages that auto-refresh.In Chrome, I can manually enter the URL (with %2F), and refresh it fine (until I navigate away from the page). In Safari, I can't even do that.The issue seems to be that Blue Ocean needs the %2F, but browser browsers won't reliably supply it - partly because the HTTP spec says they shouldn't . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Tom FENNELLY - I'm using Safari 10.0.3 (macOS Sierra). Michael Neale In both Chrome and Safari, I can navigate within the Blue Ocean UI just fine. However, as soon as I get to a page that uses an escaped /, I can't refresh it without getting a 404 due to the %2F becoming unescaped. This is a problem, especially on the build pages that auto-refresh. In Chrome, I can manually enter the URL (with %2F), and refresh it fine (until I navigate away from the page). In Safari, I can't even do that. The issue seems to be that Blue Ocean needs the %2F, but browser won't reliably supply it - partly because the HTTP spec says they shouldn't. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Also, the Safari-specifc behaviour was that refreshing the page, after putting in the %2F, would unescape the URL, resulting in a 404 again. Firefox and Chrome would still fail going to the page - but they refreshed correctly (that is, they didn't unescape the URL). Interestingly, the current version of Chrome (56.0.2924.87) is working when I type the %2F in the URL by hand and refresh the page - but if I follow a link from the page, and then refresh it, it unescapes the URL again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins edited a comment on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Sure.0) Install Folders Plugin (probably got this already)1) Create a Folder - e.g. 'Foo'2) Create an ad hoc job in that folder - e.g 'Bar'3) Go to the job page in the regular UI - https:///job/Foo/job/Bar/ 4) Push the 'Open in Blue Ocean' button. This will take you to https:///blue/organizations/jenkins/Foo/Bar, and you get a 404.5) Replace 'Foo/Bar' with 'Foo%2FBar' and see the page resolve.If you want, I can give you access to my Jenkins instance. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Sure. 0) Install Folders Plugin (probably got this already) 1) Create a Folder - e.g. 'Foo' 2) Create an ad hoc job in that folder - e.g 'Bar' 3) Go to the job page in the regular UI 4) Push the 'Open in Blue Ocean' button. This will take you to https:///blue/organizations/jenkins/Foo/Bar, and you get a 404. 5) Replace 'Foo/Bar' with 'Foo%2FBar' and see the page resolve. If you want, I can give you access to my Jenkins instance. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 The / in the job name is because BitBucket leverages the Folders plugin, creating a folder for the project/repository, and then creating jobs inside that. As I mentioned above, it's the Folder part that does it, not the BitBucket part - I can reproduce it with a manual job placed in a manually created folder. I suspect the Github Organisation Folder has the same issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 FYI: Still occurring in 1.0.0-b23. Not sure when this is meant to be released. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 This has been occurring for some time, but it's still occurring with 1.0.0-b19. (This also happens with jobs in a folder, not just for BitBucket Branch Source jobs) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 Note that you can navigate around the BlueOcean UI just fine in Safari - it's refreshing that doesn't work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 404s on navigation from the classic UI to the BlueOcean UI also happen in current versions of Chrome & Firefox. However, once the URL is manually corrected, they refresh and maintain the escaped URL. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Robert Watkins created an issue Jenkins / JENKINS-41425 Refreshing page with / in job name results in 404 Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/25 1:34 PM Environment: BlueOcean 1.0.0-b19, Jenkins v2.32.1, Safari 10.0.3 Priority: Minor Reporter: Robert Watkins When accessing a job or branch that has '/' in the name, it needs to be escaped using %2F. However, in Safari, when the page refreshes, the escapes are removed, and the URL just has a / in it. And you then get a 404 page. Similarly, when navigating from the regular Jenkins UI to the Blue Ocean UI in Safari, you get a 404 page and the job & branch names aren't escaped. Steps to reproduce: create a job with / in the name open the page in the Blue Ocean UI, using Safari, with the escaped URL. refresh the page see a 404 page. We get / in the job name because we use the BitBucket Branch Source Plugin (v1.9), so our jobs are in folders, and the job name ends up being /. On top of that, we use a pattern of story/_ for our branches, so there's another /
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore You may (heck, probably do) need that if you're hosting a Jenkins server for use by others. You don't need that if you're hosting it for yourself - your chances of conflict are infinitesimal, and you can solve them if you get them. So putting up with a lot of hassle to work around this problem isn't worth it for most installations. (Though the simple escaping of the branch name was tolerable enough) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore It still sounds like what you need is to escape/transform/mangle the job name only when it comes to writing to the filesystem, though. Yes, transforming the job name is probably the easiest way to do that without changing the existing plugins, but it has serious knock-on impacts. You seem to have a choice: (optionally) transform the job name, then fix every plugin that really needs access to the untransformed job name, or keep the job name as specified by the user, and only mangle it when needing to build a filesystem path. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore Michael Neale Yes, after restoring from the backup (which I took as advised in the upgrade notes), I'm working fine again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins edited a comment on JENKINS-41124 Re: Can't get a human readable job name anymore Is there a reason we can't have an _option_ (disabled by default) to leave the job & branch name the way the user specified it? Because a lot of those problems aren't problems for a lot of users, a lot of the time, and can be worked around by selection of job repository & branch name. Whilst mangling the job name can not be.I understand that in environments like CloudBees that this will be a problem - but in a standard self-hosted development environment, we would be extremely unlikely to encounter these issues.\[Also, I believe you're unnecessarily conflating the Job name with the workspace name - the Job name isn't part of any filespace other than the web URL (and HTML escaping works fine for that)]I've rolled back now, so I can't easily check, but from my recollection the env.JOB_DISPLAY_NAME didn't have the unmangled version - I did a dump of all of the environment properties, and not one was unmangled except for the BRANCH_NAME property. It's possible that the JOB_DISPLAY_NAME wasn't set yet, as I did the dump at the start of the job; I'll double-check that tonight. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore Is there a reason we can't have an option (disabled by default) to leave the job & branch name the way the user specified it? Because a lot of those problems aren't problems for a lot of users, a lot of the time, and can be worked around by selection of job & branch name. Whilst mangling the job name can not be. I understand that in environments like CloudBees that this will be a problem - but in a standard self-hosted development environment, we would be extremely unlikely to encounter these issues. [Also, I believe you're unnecessarily conflating the Job name with the workspace name - the Job name isn't part of any filespace other than the web URL (and HTML escaping works fine for that)] I've rolled back now, so I can't easily check, but from my recollection the env.JOB_DISPLAY_NAME didn't have the unmangled version - I did a dump of all of the environment properties, and not one was unmangled except for the BRANCH_NAME property. It's possible that the JOB_DISPLAY_NAME wasn't set yet, as I did the dump at the start of the job; I'll double-check that tonight. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore The S3BucketPublisher, BTW, uses run.getParent().getFullName(); to determine the prefix. If I can get an unmangled job name, I can do my own S3 uploads, but if I want to keep using this plugin, I need a way to make the parent's full name to be unmangled. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore What about the job name? Is there a way to get an unmangled form of that? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore I know the mangling of the paths is there to ensure uniqueness - but it's causing problems for me like crazy. An option to disable it would help a lot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins updated an issue Jenkins / JENKINS-41124 Can't get a human readable job name anymore Change By: Robert Watkins Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore This is also breaking my use of the S3BucketPublisher - It used to publish to S3 with a path prefix of (using the above) 'Foo/Bar/feature%2FBaz'. It now publishes with 'Foo/Bar.qxyz123/feature-KEY.abcd12345ghij-Baz'. I could probably live with the suffix on the project name (though that sucks, it is at least consistent), but the mangling of the branch name is horrible, as it's non-deterministic. At this point, I'm about to rollback to my backup and stick with the v1.0 version; notification templates were painful, but this is a problem that completely breaks my ops infrastructure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins updated an issue Jenkins / JENKINS-41124 Can't get a human readable job name anymore Change By: Robert Watkins Comment: Ack! I just realised something more important - I can't find related projects to do things such as copy artefacts from upstream builds, because the repository name itself now has a suffix. I'll be raising another bug for that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore Ack! I just realised something more important - I can't find related projects to do things such as copy artefacts from upstream builds, because the repository name itself now has a suffix. I'll be raising another bug for that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title Robert Watkins commented on JENKINS-41124 Re: Can't get a human readable job name anymore Probably similar to JENKINS-41104 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41124) Can't get a human readable job name anymore
Title: Message Title
Robert Watkins created an issue
Jenkins / JENKINS-41124
Can't get a human readable job name anymore
Issue Type:
Bug
Assignee:
Antonio Muñiz
Components:
bitbucket-branch-source-plugin
Created:
2017/Jan/17 10:28 AM
Environment:
Jenkins 2.32.1, Bitbucket Branch Source Plugin 2.0.0
Priority:
Major
Reporter:
Robert Watkins
Since the SCM 2.0 release, I can't find a way, in a pipeline, to get a human-readable job & branch name. For example, if I had a BitBucket team called 'Foo', a repository called 'Bar' and a branch 'feature/KEY-Baz', it used to be possible to get a nearly human readable branch - env.BRANCH_NAME would be 'Foo/Bar%2FKEY-Baz', which was easy enough to escape to a human readable form. Now, however, it's a shortened form, with numbers in it - something like 'Foo/Bar.qxyz123/feature-KEY.abcd12345ghij-Baz'. And there appears to be no way to get the human readable version. This has broken all of my build notification templates. Here's my 'build started' notification, for example:
hipchatSend color: 'YELLOW', credentialId: 'HipChat', message: "${env.JOB_NAME.replace('%2F', '/')} ${env.BUILD_NUMBER} Started", notify: true, room: 'Build Server Messages', sendAs: 'Jenkins', server: '', v2enabled: false
[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Robert Watkins commented on JENKINS-39407 Re: Use system default Maven, Maven Settings if not specified That's pretty much the behaviour I would expect. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title Robert Watkins commented on JENKINS-39407 Re: Use system default Maven, Maven Settings if not specified Well, it's stock by default unless you, as the Jenkins administrator, change the Jenkins global maven config. As a Jenkins administrator, I must say that if I change the global maven config, I expect it to be used by default. If I didn't want it to be used by default, I wouldn't have made it the global maven config. Basically, what I'm looking for here is parity-of-behaviour with the freestyle plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39407) Use system default Maven, Maven Settings if not specified
Title: Message Title
Robert Watkins created an issue
Jenkins / JENKINS-39407
Use system default Maven, Maven Settings if not specified
Issue Type:
Improvement
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2016/Nov/01 2:05 PM
Priority:
Minor
Reporter:
Robert Watkins
Currently, when you use the ``withMaven`` step, you need to specify the Maven installation. Furthermore, if you've configured, using the Managed Files and Global Tools Configuration, a maven settings.xml, you need to specify an ugly ID for that. For example: withMaven(maven: 'Maven 3.3', mavenSettingsConfig: 'ecbd05c9-e03e-4ccb-9aa1-242f9f1a423c') { sh "mvn clean verify -B" } It would be good if these could both be defaulted - at least, the mavenSettingsConfig, which doesn't have to be specified with the freestyle Maven Builder.
Add Comment
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. You could just use a UUID. The canonical form is 36 characters long, and you can express one in Base32 in just 16 characters. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. bq. This is using SHA-256 encoded in Base32So optionally use SHA-256 encoded in [RFC-4648|https://en.wikipedia.org/wiki/Base64#RFC_4648]-flavoured Base64 - it'll be half the length. Hmm. No, you'll have potential problems with case-insensitive file systems. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. bq. This is using SHA-256 encoded in Base32So use SHA-256 encoded in [ RFC-4648 |https://en.wikipedia.org/wiki/Base64#RFC_4648] -flavoured Base64 - it'll be half the length. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. This is using SHA-256 encoded in Base32 So use SHA-256 encoded in RFC-4648-flavoured Base64 - it'll be half the length. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
