[JIRA] (JENKINS-32933) No TestNG results should mark build as Failure
Title: Message Title Sameer Jethvani commented on JENKINS-32933 Re: No TestNG results should mark build as Failure This is something related to this JENKINS-20985 You have to update config of jenkins job such 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-32933) No TestNG results should mark build as Failure
Title: Message Title Sameer Jethvani updated an issue Jenkins / JENKINS-32933 No TestNG results should mark build as Failure Change By: Sameer Jethvani Attachment: Config_Update_Solved_This_Error.png 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-36661) Preserve formatting on input box in stage view
Title: Message Title Dirk Hagener commented on JENKINS-36661 Re: Preserve formatting on input box in stage view Thanks for the quick solution. Our DevOps will appreciate it. When will it be released? With the next weekly update? 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-34587) better supoort for "tip" changelogs
Title: Message Title Justinas Urbanavicius closed an issue as Fixed fixed in v1.55 Jenkins / JENKINS-34587 better supoort for "tip" changelogs Change By: Justinas Urbanavicius Status: Open Closed Resolution: Fixed 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-34587) better supoort for "tip" changelogs
Title: Message Title Justinas Urbanavicius commented on JENKINS-34587 Re: better supoort for "tip" changelogs yes it's appears to be fixed in the latest version 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-36675) REGRESSION: unable to launch any multibranch jobs
Title: Message Title Michael Neale commented on JENKINS-36675 Re: REGRESSION: unable to launch any multibranch jobs Jobs can't be run from within folders either (but that was probably the case before anyway). 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-36645) Getting Invalid id : Process leaked file descriptors.
Title: Message Title Vishnu Yadav commented on JENKINS-36645 Re: Getting Invalid id : Process leaked file descriptors. Thanks for responding Mark!!! Yes, it was failing in all jobs in 1.642.3. Seems it was issue with that version. I upgraded jenkins to 2.7.1 yesterday and it seems working fine now. 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-36676) PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing)
Title: Message Title Michael Neale assigned an issue to Cliff Meyers Jenkins / JENKINS-36676 PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing) Change By: Michael Neale Assignee: Cliff Meyers 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-36676) PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36676 PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing) Change By: Michael Neale Priority: Critical Major 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-36677) No support for parallel builds
Title: Message Title apgray updated an issue Jenkins / JENKINS-36677 No support for parallel builds Change By: apgray Issue Type: Improvement Bug 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-36677) No support for parallel builds
Title: Message Title
apgray updated an issue
Jenkins / JENKINS-36677
No support for parallel builds
Change By:
apgray
If I set "Execute concurrent builds if necessary" checkbox on to ON, I get the below exception. It would appear to me the TFS plugin does not support parallel builds on Windows. {code:java}FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.ItemNotMappedException: There is no working folder mapping for D:\Jenkins\jobs\MasterBranch\jobs\TheTPS\jobs\TPS\workspace@2.java.lang.RuntimeException: com.microsoft.tfs.core.clients.versioncontrol.exceptions.ItemNotMappedException: There is no working folder mapping for D:\Jenkins\jobs\MasterBranch\jobs\TheTPS\jobs\TPS\workspace@2. at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Project.getFiles(Project.java:177) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:54) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:221) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Caused by: com.microsoft.tfs.core.clients.versioncontrol.exceptions.ItemNotMappedException: There is no working folder mapping for D:\Jenkins\jobs\MasterBranch\jobs\TheTPS\jobs\TPS\workspace@2. at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.getLocalWorkspace(VersionControlClient.java:737) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.getWorkspace(VersionControlClient.java:2154) at hudson.plugins.tfs.model.MockableVersionControlClient.getWorkspace(MockableVersionControlClient.java:93) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:57) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:17) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:106) ... 11 more{code}
[JIRA] (JENKINS-36677) No support for parallel builds
Title: Message Title apgray created an issue Jenkins / JENKINS-36677 No support for parallel builds Issue Type: Improvement Assignee: redsolo Components: tfs-plugin Created: 2016/Jul/14 3:55 AM Environment: Windows 2012 R2 Jenkins 2.13 tfs-plugin 4.0.0 Labels: tfs-plugin Priority: Major Reporter: apgray If I set "Execute concurrent builds if necessary" checkbox on I get the below exception.It would appear to me the TFS plugin does not support parallel builds on Windows. FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.ItemNotMappedException: There is no working folder mapping for D:\Jenkins\jobs\MasterBranch\jobs\TheTPS\jobs\TPS\workspace@2. java.lang.RuntimeException: com.microsoft.tfs.core.clients.versioncontrol.exceptions.ItemNotMappedException: There is no working folder mapping for D:\Jenkins\jobs\MasterBranch\jobs\TheTPS\jobs\TPS\workspace@2. at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Project.getFiles(Project.java:177) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:54) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:221) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.jav
[JIRA] (JENKINS-36670) FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Title: Message Title Alex Earl commented on JENKINS-36670 Re: FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty I'm not sure who the maintainer of the plugin is. You may want to hop on IRC and ask there. Have you recently upgraded any plugins? 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-36674) Tests are not being reported
Title: Message Title Michael Neale commented on JENKINS-36674 Re: Tests are not being reported encodeURIComponent(branchName) needed somewhere... 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-36676) PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing)
Title: Message Title Michael Neale commented on JENKINS-36676 Re: PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing) This may be best done by reviewing how all URIs are handled that are returned from the api (as discussed between Cliff Meyers and Vivek Pandey but I just wanted to flag this). encodeURIcomponents needed 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-36676) PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-36676 PullRequest.jsx needs to cope with branch names that are non alpha (eg feature/thing) Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/14 3:35 AM Priority: Critical Reporter: Michael Neale Similar to Branches.jsx - an encodeURIComponent is needed for the branch name. Basicaslly pull requests should be brought up to scratch with Branches.jsx Ideally they share a lot of the same code where possible. Add Comment
[JIRA] (JENKINS-36675) REGRESSION: unable to launch any multibranch jobs
Title: Message Title Michael Neale started work on JENKINS-36675 Change By: Michael Neale Status: Open In Progress 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-36675) REGRESSION: unable to launch any multibranch jobs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36675 REGRESSION: unable to launch any multibranch jobs Change By: Michael Neale Sprint: 1.0-m11 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-36675) REGRESSION: unable to launch any multibranch jobs
Title: Message Title Michael Neale commented on JENKINS-36675 Re: REGRESSION: unable to launch any multibranch jobs Cliff Meyers Vivek Pandey this is actually 3 fixes: 1) The actual regression that was stopping running even "master" branch 2) I added an encoding call to ensure it can run branches like "feature/blah" 3) I changed the blue message enricher to correctly encode the branch name so that SSE would pick it up correctly. The 1st one was really a regression 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-36670) FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Title: Message Title madhukar kasireddy updated an issue Jenkins / JENKINS-36670 FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty Change By: madhukar kasireddy Priority: Minor 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-36670) FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Title: Message Title
madhukar kasireddy updated an issue
Jenkins / JENKINS-36670
FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Change By:
madhukar kasireddy
Environment:
Jenkins ver 1.638OS Centosmailer plugin 1.17 Git plugin 2.2.9Git lab plugin 1.1.3
I have several free style projects and i am seeing this error from last couple of days *Randomly* . Please find below the error trace . I did not come across any working solution anywhere . Please help !! Started by an SCM changeBuilding on master in workspace /home/cmsbuild/Workspace/middletier > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/bin/git config remote.origin.url g...@gitlab.ins.risk.regn.net:cmd/middletier.git # timeout=10Fetching upstream changes from g...@gitlab.ins.risk.regn.net:cmd/middletier.git > /usr/bin/git --version # timeout=10using GIT_SSH to set credentials > /usr/bin/git -c core.askpass=true fetch --tags --progress g...@gitlab.ins.risk.regn.net:cmd/middletier.git +refs/heads/*:refs/remotes/origin/* > /usr/bin/git rev-parse refs/remotes/origin/test_CI^{commit} # timeout=10 > /usr/bin/git rev-parse refs/remotes/origin/origin/test_CI^{commit} # timeout=10Checking out Revision a2fa4a0cfae39d50d51d01d46190891f879b6d8a (refs/remotes/origin/test_CI) > /usr/bin/git config core.sparsecheckout # timeout=10 > /usr/bin/git checkout -f a2fa4a0cfae39d50d51d01d46190891f879b6d8a > /usr/bin/git rev-list 2b4d0c33e20ba201fd0896b75223555f005dde98 # timeout=10FATAL: hudson/tasks/Mailer$UserPropertyjava.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:77) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:71) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:48) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:29) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:927) at hudson.model.AbstractBuild.access$600(AbstractBuild.java:104) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:619) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.lang.ClassNotFoundException: hudson.tasks.Mailer$UserProperty at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(A
[JIRA] (JENKINS-36563) Git plugin does not fetch branch to merge to when merge before build is used
Title: Message Title Mark Waite commented on JENKINS-36563 Re: Git plugin does not fetch branch to merge to when merge before build is used One work around with the current plugins is to switch from using the non-default refspec you're currently using +refs/heads/feature/my-feature-branch to the default refspec that your merge process seems to assume is needed. At minimum, the refspecs need to include both the source branch and the target branch. You can include multiple refspecs in the repository definition by separating them with spaces. Or, you can clear the refspec field so that it will use the default refspec. The refspec is retained from the initial clone, so changing the refspec will require that you wipe the workspace. 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-36670) FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Title: Message Title madhukar kasireddy commented on JENKINS-36670 Re: FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty Alex Earl I saw a you responding a similar bug , so i thought you might have an idea . Is there a chance that you can assign it to the right person pls 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-36675) REGRESSION: unable to launch any multibranch jobs
Title: Message Title Michael Neale commented on JENKINS-36675 Re: REGRESSION: unable to launch any multibranch jobs PR for this: https://github.com/jenkinsci/blueocean-plugin/pull/346 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-36675) REGRESSION: unable to launch any multibranch jobs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36675 REGRESSION: unable to launch any multibranch jobs Change By: Michael Neale Summary: REGRESSION: unable to launch any multibranch 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-36675) REGRESSION: unable to launch multibranch jobs
Title: Message Title Michael Neale commented on JENKINS-36675 Re: REGRESSION: unable to launch multibranch jobs Related to https://issues.jenkins-ci.org/browse/JENKINS-36615 but this also breaks any old branch name. 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-36675) REGRESSION: unable to launch multibranch jobs
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-36675 REGRESSION: unable to launch multibranch jobs Issue Type: Bug Assignee: Cliff Meyers Components: blueocean-plugin Created: 2016/Jul/14 3:07 AM Priority: Critical Reporter: Michael Neale A recent change, in an attempt to fix encoding problems for opening branches with / in the name, resulted in being unable to launch any type of multi branch. Change: https://github.com/jenkinsci/blueocean-plugin/commit/11e065f7b8e67065e1ef6a447c2a9d9f34fac2e3 The destructuring variable was assigned to "branchName" but "name" was still used in the argument to the RunPipeline component. I have a PR incoming for this, but also found that it needs to encode the already "once encoded" form again, for Jenkins to work. An encode call was needed on the branchName. I then discovered that SSE events were coming back only once encoded. Jenkins, both classic URIs and API requires a "double encoding" for branch names, so I had to change the backend code to emit a message that would encode it correctly. Confused? I also note that the PullRequest.jsx will be in a similar state, so that needs to be corrected. Like Cliff Meyers points out, these really should be combined, and use some other way to get links rather than assembling them each time which seems to be error prone.
[JIRA] (JENKINS-36674) Tests are not being reported
Title: Message Title James Dumay assigned an issue to Cliff Meyers Jenkins / JENKINS-36674 Tests are not being reported Change By: James Dumay Assignee: Cliff Meyers 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-36674) Tests are not being reported
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36674 Tests are not being reported Cliff Meyers I had Vivek Pandey verify that this is a URL encoding problem for the branch name. https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/jenkins-design-language/branches/topic%252Fadd-test-reports/runs/2/testReport/result/ works just fine. 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-36640) Result modal never transitions from running to success/fail
Title: Message Title James Dumay commented on JENKINS-36640 Re: Result modal never transitions from running to success/fail Thorsten Scherler I tried this today and I got a similar problem where the state did not transition but there was an 404 in the console trying to fetch the log of the last node. 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-36674) Tests are not being reported
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36674 Tests are not being reported Change By: James Dumay Priority: Minor 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-36674) Tests are not being reported
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36674 Tests are not being reported Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/14 2:43 AM Priority: Minor Reporter: James Dumay No tests are displayed here: https://ci.blueocean.io/blue/organizations/jenkins/jenkins-design-language/detail/topic%2Fadd-test-reports/2/tests/ However there are JUnit tests on the job in classic: https://ci.blueocean.io/job/jenkins-design-language/job/topic%252Fadd-test-reports/lastCompletedBuild/testReport/PhantomJS_2_1_1_(Linux_0_0_0)/ At closer inspection it looks like the REST URL 404s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/jenkins-design-language/branches/topic%2Fadd-test-reports/runs/2/testReport/result Add Comment
[JIRA] (JENKINS-27163) Matrix builds do not have escaped path names
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-27163 Matrix builds do not have escaped path names Change By: Gavin Mogan Summary: Workspace import error Matrix builds do not have escaped path names 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-31447) Support for Jenkins Workflow plugin?
Title: Message Title Gavin Mogan commented on JENKINS-31447 Re: Support for Jenkins Workflow plugin? Jan Molak We have support for this https://wiki.saucelabs.com/pages/viewpage.action?pageId=63479539 has some details. 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-31447) Support for Jenkins Workflow plugin?
Title: Message Title Gavin Mogan closed an issue as Fixed Jenkins / JENKINS-31447 Support for Jenkins Workflow plugin? Change By: Gavin Mogan Status: Resolved Closed 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-31447) Support for Jenkins Workflow plugin?
Title: Message Title Gavin Mogan resolved as Fixed Jenkins / JENKINS-31447 Support for Jenkins Workflow plugin? Change By: Gavin Mogan Status: Open Resolved Resolution: Fixed 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-31447) Support for Jenkins Workflow plugin?
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-31447 Support for Jenkins Workflow plugin? Change By: Gavin Mogan Assignee: Kohsuke Kawaguchi Gavin Mogan 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-32728) NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-32728 NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName) Change By: Gavin Mogan Assignee: Jack Moxon Gavin Mogan 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-35986) Sauce Labs results section is displayed on Job main page when Sauce Labs is not enabled in the job configuration
Title: Message Title Gavin Mogan commented on JENKINS-35986 Re: Sauce Labs results section is displayed on Job main page when Sauce Labs is not enabled in the job configuration Hi Taras Kurdyna, This will be fixed in the next version. I'll let you know when its out. 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-35986) Sauce Labs results section is displayed on Job main page when Sauce Labs is not enabled in the job configuration
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-35986 Sauce Labs results section is displayed on Job main page when Sauce Labs is not enabled in the job configuration Change By: Gavin Mogan Assignee: Jack Moxon Gavin Mogan 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title James Dumay commented on JENKINS-36652 Re: Archive tests in Blue Ocean and Acceptance Test pipelines Michael Neale looks like the ATH uses surefire - we should be getting reports for this. 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title James Dumay reopened an issue Jenkins / JENKINS-36652 Archive tests in Blue Ocean and Acceptance Test pipelines Change By: James Dumay Resolution: Fixed Status: Closed Reopened 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title Michael Neale commented on JENKINS-36652 Re: Archive tests in Blue Ocean and Acceptance Test pipelines not sure - it may be able to output the xml, but not sure. Nightwatch? In any case it can be added to it until the code is merged with master. 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-36509) 'Active Choices Reactive Reference Parameter' type variable is empty
Title: Message Title Ioannis Moutsatsos resolved as Fixed This is the expected behavior as described on https://wiki.jenkins-ci.org/display/JENKINS/Active+Choices+Plugin. Read instructions on how to pass parameters to the build there please. Jenkins / JENKINS-36509 'Active Choices Reactive Reference Parameter' type variable is empty Change By: Ioannis Moutsatsos Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-36640) Result modal never transitions from running to success/fail
Title: Message Title James Dumay commented on JENKINS-36640 Re: Result modal never transitions from running to success/fail Thorsten Scherler did you try this on blueocean.io's Jenkins Design Language pipeline? 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title James Dumay commented on JENKINS-36652 Re: Archive tests in Blue Ocean and Acceptance Test pipelines Michael Neale interesting - what test runner does the ATH use? 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-36509) 'Active Choices Reactive Reference Parameter' type variable is empty
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-36509
Re: 'Active Choices Reactive Reference Parameter' type variable is empty
The Groovy script must return valid HTML in the form:
return "value\" value=\"${reactRefParam}\" class=\"setting-input\" type=\"text\">"
where *reactRefParam *is the value calcuclated by the script that you want to use as parameter. In addition, under 'Advanced' options check the 'Omit Value Field'. Make sure you read the documentation on the Active-Choices https://wiki.jenkins-ci.org/display/JENKINS/Active+Choices+Plugin wiki page documenting these techniques under 'Passing Reactive Reference Values to the build' (Scenatio 1, 2)
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-36645) Getting Invalid id : Process leaked file descriptors.
Title: Message Title Mark Waite commented on JENKINS-36645 Re: Getting Invalid id : Process leaked file descriptors. I can't duplicate the problem you're reporting. You'll need to provide more information before anyone can be of much help. Does it fail like this on every job, or just one job? If you install a new Jenkins instance does it fail in the same way with that job? Does it fail this way with a newer version of Jenkins (since 1.642.3 is now 4 months old and has been superseded by 1.651.3 and 2.7.1 as long term support releases)? In general, you'll get better results asking for help from the user mailing list rather than from a bug report. There are many more people who read the mailing list than read bug reports for specific plugins. 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-36645) Getting Invalid id : Process leaked file descriptors.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-36645 Getting Invalid id : Process leaked file descriptors. Change By: Mark Waite Assignee: Mark Waite 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-31924) GitSCMSource should offer extensions
Title: Message Title Mark Waite resolved as Fixed Included in git plugin 2.5.2, released July 2016 Jenkins / JENKINS-31924 GitSCMSource should offer extensions Change By: Mark Waite Status: Open Resolved Resolution: Fixed 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-33958) RepoScm changelog hang when used with pipeline
Title: Message Title Makson Lee resolved as Fixed Jenkins / JENKINS-33958 RepoScm changelog hang when used with pipeline Change By: Makson Lee Status: Open Resolved Resolution: Fixed 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-36673) Cannot Call Pipeline Library Function
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-36673 Cannot Call Pipeline Library Function Change By: Mark Bidewell Priority: Minor Major 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-33958) RepoScm changelog hang when used with pipeline
Title: Message Title Makson Lee assigned an issue to Makson Lee Jenkins / JENKINS-33958 RepoScm changelog hang when used with pipeline Change By: Makson Lee Assignee: Makson Lee 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-36673) Cannot Call Pipeline Library Function
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-36673 Cannot Call Pipeline Library Function Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jul/14 1:13 AM Environment: Jenkins 1.651.3 and 2.7.1 Priority: Minor Reporter: Mark Bidewell I updated to the latest Pipeline plugins. I had some library functions taking closures created using the directions here: https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md Prior to the update the scripts worked perfectly. after updating I get the error: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: static Maven.svnRelease() is applicable for argument types: (org.jenkinsci.plugins.workflow.cps.CpsClosure2) values: [org.jenkinsci.plugins.workflow.cps.CpsClosure2@3a07d220] Possible solutions: svnRelease(groovy.lang.Closure) at groovy.lang.MetaClassImpl.invokeStaticMissingMethod(MetaClassImpl.java:1367) at groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1353) at org.codehaus.groovy.runtime.callsite.StaticMetaClassSite.call(StaticMetaClassSite.java:50) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at WorkflowScript.run(WorkflowScript:1) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.N
[JIRA] (JENKINS-36644) Tag action is not working in pipeline job
Title: Message Title Makson Lee resolved as Fixed Jenkins / JENKINS-36644 Tag action is not working in pipeline job Change By: Makson Lee Status: Open Resolved Resolution: Fixed 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-27860) Build does not stop if it is marked as Failure
Title: Message Title Chee Yee commented on JENKINS-27860 Re: Build does not stop if it is marked as Failure I have the same issue. I have a Post-Build step that run xUnit on Junit xml and expect it to stop the Job if there are any error, but It carries on to execute the steps that follow and upload my artifact to Artifactory. 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-36644) Tag action is not working in pipeline job
Title: Message Title Makson Lee assigned an issue to Makson Lee Jenkins / JENKINS-36644 Tag action is not working in pipeline job Change By: Makson Lee Assignee: Makson Lee 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title Michael Neale commented on JENKINS-36652 Re: Archive tests in Blue Ocean and Acceptance Test pipelines they show up in classic - at least for blue ocean junit tests. Neither the js tests nor the ATH output things in the junit xml format though, so they won't be included. 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title James Dumay commented on JENKINS-36652 Re: Archive tests in Blue Ocean and Acceptance Test pipelines Do we? They aren't showing up on any of the runs.. 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-33776) Cannot start from preview rpm
Title: Message Title Daniel Beck commented on JENKINS-33776 Re: Cannot start from preview rpm This was marked resolved because we fixed it. I'm currently trying to get information on the release process, maybe something went wrong there (specifically, master branch of https://github.com/jenkinsci/packaging used rather than the jenkins-2.0 branch). 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title Michael Neale closed an issue as Fixed Jenkins / JENKINS-36652 Archive tests in Blue Ocean and Acceptance Test pipelines Change By: Michael Neale Status: Open Closed Resolution: Fixed 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-36652) Archive tests in Blue Ocean and Acceptance Test pipelines
Title: Message Title Michael Neale commented on JENKINS-36652 Re: Archive tests in Blue Ocean and Acceptance Test pipelines We already archive test results from it. 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-36650) Why do acceptance tests not run for branches?
Title: Message Title Michael Neale commented on JENKINS-36650 Re: Why do acceptance tests not run for branches? The second option doens't make sense and wouldn't solve it - it would just mean there are lots of branches of the ATH code. 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-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Title: Message Title Ben Jones commented on JENKINS-5853 Re: Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key I apologize for bringing such an old topic back up, but I encountered an issue related to this today. The problem I see is that jobs being run on an EC2 slave are able to obtain root privileges on that slave. This may be just fine for some setups, but it obviously has the potential to introduce quite a bit of irritation and chaos (or worse) as well. To prevent this, I would like to have the master connect to an ec2 slave using the configured remote user, but with a key separate from that which the instance was launched with. Using a base Ubuntu image as an example, I'm currently restricted to using 'ubuntu' as the remote user and connecting with the key the instance was launched with. Instead I would like to connect as 'jenkins' with some other key entirely (the assumption is that I created this user appropriately via user data, pre-baked ami, etc.). I could just generate an authorized_keys entry for that user by generating a public key from the private key, which I suppose is just fine, but it doesn't seem like an intuitive solution. 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-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title Mark Waite commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches Git client plugin 1.18.1 is quite old. Is there a reason you went backwards that far rather than trying the pre-release mentioned earlier? 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-36668) LinkResolver returns null for Pipeline job
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36668 LinkResolver returns null for Pipeline job Change By: James Dumay Sprint: 1.0-m11 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-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches Hi, We hit the same issue during one of our builds, wanted to add that we were able to downgrade the git client plugin back to 1.8.1 to bypass the issue. Not sure how to go back and search each commit that happened for a new line in our case the culprit commit is not the most recent, so we would need to go back and update ones that happened several commits ago... not sure how to do that yet 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-33776) Cannot start from preview rpm
Title: Message Title Matthew Sexton commented on JENKINS-33776 Re: Cannot start from preview rpm toby cabot - I agree that this needs to be remedied from a base install. Have you tried installing with the latest version (2.13) to test? There's nothing that points to that being removed or changed for the RPM, but it never hurts to try. Since there is a workaround in place (and since it's marked as resolved) it's not a high priority for the devs. 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-36619) Close of modal leads to a 404 on a folder project
Title: Message Title James Dumay commented on JENKINS-36619 Re: Close of modal leads to a 404 on a folder project Cliff Meyers Thorsten Scherler I think we want to introduce a more nuanced way of doing it after pagination goes in. the behaviour is great when the run is below the fold, but when its not it just causes an unnecessary jump - may be best to kill this feature for the time being. 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-36671) Support to copy Jobs (not only AbstractProject)
Title: Message Title ikedam resolved as Not A Defect I found that jobcopy-builder already supports TopLevelItem for JENKINS-24515. Jenkins / JENKINS-36671 Support to copy Jobs (not only AbstractProject) Change By: ikedam Status: Open Resolved Resolution: Not A Defect 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://
[JIRA] (JENKINS-36654) promoted-builds-plugin does not compile against 1.651.3
Title: Message Title Oleg Nenashev commented on JENKINS-36654 Re: promoted-builds-plugin does not compile against 1.651.3 Raul Arabaolaza Many Jenkins plugins are affected by this API change. We could fix a particular plugin, but I'm not sure what you're trying to achieve. Is it for the Plugin Compatibility Tester? 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-36672) Support runtime authorizations
Title: Message Title ikedam created an issue Jenkins / JENKINS-36672 Support runtime authorizations Issue Type: Improvement Assignee: ikedam Components: jobcopy-builder-plugin Created: 2016/Jul/13 10:48 PM Priority: Major Reporter: ikedam Should support QueueItemAuthenticator introduced in 1.532 and perform access permission checks for jobs to copy from. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36671) Support to copy Jobs (not only AbstractProject)
Title: Message Title
ikedam created an issue
Jenkins / JENKINS-36671
Support to copy Jobs (not only AbstractProject)
Issue Type:
Improvement
Assignee:
ikedam
Components:
jobcopy-builder-plugin
Created:
2016/Jul/13 10:47 PM
Priority:
Minor
Reporter:
ikedam
It should be applicable to {{Job}}s (e.g. pipelines).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36660 Acceptance tests for nested project and funky branch name regressions Change By: James Dumay Priority: Major Critical Sprint: 1.0-m11 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-36670) FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Title: Message Title Alex Earl assigned an issue to Unassigned Not sure why this was assigned to me. Jenkins / JENKINS-36670 FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty Change By: Alex Earl Assignee: Alex Earl 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-36276) "Activity" table is not scrolled to position after closing Run Details for a branch with special characters in name
Title: Message Title James Dumay commented on JENKINS-36276 Re: "Activity" table is not scrolled to position after closing Run Details for a branch with special characters in name Axe the feature please 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-33776) Cannot start from preview rpm
Title: Message Title
toby cabot edited a comment on JENKINS-33776
Re: Cannot start from preview rpm
Hi, I think this might still be an issue. My chef tests started failing recently - they spin up a Centos 7 VM, install Jenkins (currently jenkins-2.7.1-1.1.noarch) from the http://pkg.jenkins-ci.org/redhat-stable repo, and then tries to start it. The /etc/sysconfig/jenkins config file included in the rpm has a line that tries to run AJP on port 8009: {noformat} ## Type:integer(0:65535)## Default: 8009## ServiceRestart: jenkins## Ajp13 Port Jenkins is listening on.# Set to -1 to disable#JENKINS_AJP_PORT="8009" {noformat} This causes jenkins to fail at startup as described by https://issues.jenkins-ci.org/browse/JENKINS-33776?focusedCommentId=255250&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-255250It would be better if the /etc/sysconfig/jenkins file included in the rpm didn't try to configure AJP so jenkins would run right out of the box without requiring the users to modify it.
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-33776) Cannot start from preview rpm
Title: Message Title toby cabot commented on JENKINS-33776 Re: Cannot start from preview rpm Hi, I think this might still be an issue. My chef tests started failing recently - they spin up a Centos 7 VM, install Jenkins (currently jenkins-2.7.1-1.1.noarch) from the http://pkg.jenkins-ci.org/redhat-stable repo, and then tries to start it. The /etc/sysconfig/jenkins config file included in the rpm has a line that tries to run AJP on port 8009: Type: integer(0:65535) Default: 8009 ServiceRestart: jenkins # Ajp13 Port Jenkins is listening on. Set to -1 to disable # JENKINS_AJP_PORT="8009" This causes jenkins to fail at startup as described by https://issues.jenkins-ci.org/browse/JENKINS-33776?focusedCommentId=255250&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-255250 It would be better if the /etc/sysconfig/jenkins file included in the rpm didn't try to configure AJP so jenkins would run right out of the box without requiring the users to modify it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36670) FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Title: Message Title
madhukar kasireddy created an issue
Jenkins / JENKINS-36670
FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty
Issue Type:
Bug
Assignee:
Alex Earl
Components:
mailer-plugin
Created:
2016/Jul/13 9:41 PM
Environment:
Jenkins ver 1.638 OS Centos mailer plugin 1.17
Priority:
Minor
Reporter:
madhukar kasireddy
I have several free style projects and i am seeing this error from last couple of days Randomly . Please find below the error trace . I did not come across any working solution anywhere . Please help !! Started by an SCM change Building on master in workspace /home/cmsbuild/Workspace/middletier > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > /usr/bin/git config remote.origin.url g...@gitlab.ins.risk.regn.net:cmd/middletier.git # timeout=10 Fetching upstream changes from g...@gitlab.ins.risk.regn.net:cmd/middletier.git > /usr/bin/git --version # timeout=10 using GIT_SSH to set credentials > /usr/bin/git -c core.askpass=true fetch --tags --progress g...@gitlab.ins.risk.regn.net:cmd/middletier.git +refs/heads/:refs/remotes/origin/ > /usr/bin/git rev-parse refs/remotes/origin/test_CI^ {commit} # timeout=10 > /usr/bin/git rev-parse refs/remotes/origin/origin/test_CI^{commit} # timeout=10 Checking out Revision a2fa4a0cfae39d50d51d01d46190891f879b6d8a (refs/remotes/origin/test_CI) > /usr/bin/git config core.sparsecheckout # timeout=10 > /usr/bin/git checkout -f a2fa4a0cfae39d50d51d01d46190891f879b6d8a > /usr/bin/git rev-list 2b4d0c33e20ba201fd0896b75223555f005dde98 # timeout=10 FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty at hudson.plugins.git.GitChangeLogParser.parseCommit(
[JIRA] (JENKINS-36476) Default value for Password Parameter is not extracted for users without Configure Permission
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36476 Default value for Password Parameter is not extracted for users without Configure Permission Change By: Jesse Glick Labels: lts-candidate parameter password regression security 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-36669) Jenkins Remote API does not show details for pipeline jobs
Title: Message Title
jim jaeger created an issue
Jenkins / JENKINS-36669
Jenkins Remote API does not show details for pipeline jobs
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline-stage-view-plugin, remoting
Created:
2016/Jul/13 9:21 PM
Environment:
Jenkins 2.0
Labels:
rest pipeline
Priority:
Major
Reporter:
jim jaeger
Problem description: We use the Jenkins remote REST API for example /api/json?tree=views[name,jobs[name,description,color,url,lastBuild[number,duration,timestamp,result]]] to get metadata of all existing jobs. Now we start using the Pipeline features only the folder of GIT organization of the pipeline is listed as job in the response { "description" : "", "name" : "squad-example", "url" : "http://hostname:portl/job/squad-example/" } , but not the nested jobs of each folder. Our assumption was that the jobs are listed as other jobs because in the UI it show the fullname squad-example/gitrepo/master. We found a REST api from the plugin Pipeline+Stage+View+Plugin to get metadata for each pipeline nested job if the name is known but there is not the detailed entry in the usual remote api. The plugin rest api we can only use when we know the specific path to the job and the usual remote api does give a link to it. How we can proceed the get the data?
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Jonathan Strootman commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Me as well. You can't pass a parameter into the `Branch specifier` field of the pipeline SCM section, can you? I tried, unsuccessfully. 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-36668) LinkResolver returns null for Pipeline job
Title: Message Title Vivek Pandey edited a comment on JENKINS-36668 Re: LinkResolver returns null for Pipeline job [~cliffmeyers] There was a pipeline factory in test that had correct implementation of resolve() method vs in PipelineImpl.FactoryImpl.resolve() and so was hiding the bug in PipelineImpl.FactoryImpl.resolve() and tests were passing. This would have failed for any freestyle or pipeline job but not multi branch ones. More tests have been added and fix has been made. PR https://github.com/jenkinsci/blueocean-plugin/pull/345 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-36668) LinkResolver returns null for Pipeline job
Title: Message Title Vivek Pandey commented on JENKINS-36668 Re: LinkResolver returns null for Pipeline job There was a pipeline factory in test that had correct implementation of resolve() method vs in PipelineImpl.FactoryImpl.resolve() and so was hiding the bug in PipelineImpl.FactoryImpl.resolve() and tests were passing. This would have failed for any freestyle or pipeline job but not multi branch ones. More tests have been added and fix has been made. 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-34367) Add support for empty sendTo field for extendedEmail plugin
Title: Message Title
Alexander Komarov edited a comment on JENKINS-34367
Re: Add support for empty sendTo field for extendedEmail plugin
Another way to demonstrate undesirable behavior is to use the sandbox (http://job-dsl.herokuapp.com/){code:java}freeStyleJob('ci') { description 'Build and test the app.'publishers{ extendedEmail {recipientList 'gene...@something.com'triggers {success {//only send to success@ , not to generic@recipientList 'succ...@something.com'sendTo {}}}} }}{code} This code should generate an empty recipientProviders block, but it produces this instead: {code:java}{code}As a result, success email is sent to both generic@ and success@. As a workaround I am setting the most unlikely sendTo option (*failingTestSuspects()* in my case as this is a Success trigger) and that displaces the default.
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-36638) SSE events not coming through to the client
Title: Message Title Cliff Meyers commented on JENKINS-36638 Re: SSE events not coming through to the client Tom FENNELLY I believe you are back tomorrow? I can touch base w/ you then as to what I am working on. JENKINS-33615 has some bugs and regressions dealing with nested jobs and branch names with special chars in them. That may effectively resolve this bug. 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-31738) Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view
Title: Message Title Manuel Recena Soto closed an issue as Fixed Jenkins / JENKINS-31738 Non-deterministic behavior in PrioritySorterPluginTest#match_jobs_by_view Change By: Manuel Recena Soto Status: In Progress Closed Resolution: Fixed 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-36668) LinkResolver returns null for Pipeline job
Title: Message Title Vivek Pandey started work on JENKINS-36668 Change By: Vivek Pandey Status: Open In Progress 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-24679) Executor_Number variable doesn't align with the build executor status
Title: Message Title Timothy Duch commented on JENKINS-24679 Re: Executor_Number variable doesn't align with the “build executor status” From what I can see, this is still happening, and I consider it a bug (from the perspective of the documentation: https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project) "This is the number you see in the "build executor status", except that the number starts from 0, not 1". You can see in the images above that Build #7 has EXECUTOR_NUMBER 0, whilst on the UI under the build executor status, build #7 is running on what I would expect to be EXECUTOR_NUMBER 1 (#2 - 1 = 1). 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-36668) LinkResolver returns null for Pipeline job
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-36668 LinkResolver returns null for Pipeline job Change By: Cliff Meyers Issue Type: Task Bug 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-34005) Make WorkflowJob.triggers into a JobProperty
Title: Message Title Andrew Bayer started work on JENKINS-34005 Change By: Andrew Bayer Status: Open In Progress 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-34005) Make WorkflowJob.triggers into a JobProperty
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-34005 Make WorkflowJob.triggers into a JobProperty Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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-34005) Make WorkflowJob.triggers into a JobProperty
Title: Message Title Andrew Bayer commented on JENKINS-34005 Re: Make WorkflowJob.triggers into a JobProperty Initial PR work up at https://github.com/jenkinsci/workflow-job-plugin/pull/9 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-36668) LinkResolver returns null for Pipeline job
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-36668 LinkResolver returns null for Pipeline job Change By: Cliff Meyers Priority: Minor Blocker 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-36668) LinkResolver returns null for Pipeline job
Title: Message Title Cliff Meyers created an issue Jenkins / JENKINS-36668 LinkResolver returns null for Pipeline job Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Jul/13 8:36 PM Priority: Minor Reporter: Cliff Meyers While attempting to integrate changes to BlueMessageEnricher as suggested in JENKINS-36286, I found that LinkResolver.resolve returns null when an instance of WorkflowJob is passed to it. Add Comment This message was sent by Atlassian JIRA (v7.
[JIRA] (JENKINS-33263) Detecting mercurial changes doesn't work for "concurrent builds"
Title: Message Title Rick Oosterholt commented on JENKINS-33263 Re: Detecting mercurial changes doesn't work for "concurrent builds" Really? General aspects are able to run concurrent builds and haven scm changes. Not when combining there are no changes anymore. Might be hard to fix, but no reason to mark it as 'not a defect' IMHO 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-36476) Default value for Password Parameter is not extracted for users without Configure Permission
Title: Message Title Jesse Glick commented on JENKINS-36476 Re: Default value for Password Parameter is not extracted for users without Configure Permission I think the problem is that PasswordParameterDefinition/index.jelly uses f:password, which blocks passwords for users lacking Item.CONFIGURE as part of the fix of SECURITY-266. But that defense was intended for form fragments shown in a job configuration screen. When you define a PasswordParameterDefinition.defaultValue, you actually expect that the secret will be exposed to anyone with Item.BUILD. Or perhaps you do not necessarily wish to show them the secret, but wish them to be allowed to use it in the context of a build. 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-36476) Default value for Password Parameter is not extracted for users without Configure Permission
Title: Message Title Jesse Glick started work on JENKINS-36476 Change By: Jesse Glick Status: Open In Progress 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-36476) Default value for Password Parameter is not extracted for users without Configure Permission
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-36476 Default value for Password Parameter is not extracted for users without Configure Permission Change By: Jesse Glick Assignee: Jesse Glick 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-36615) Unable to run multibranch pipeline with '/' the name
Title: Message Title Cliff Meyers commented on JENKINS-36615 Re: Unable to run multibranch pipeline with '/' the name Tom FENNELLY thanks. I talked to Vivek and am going to make this change locally for now to try to unblock myself. 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.
