[JIRA] (JENKINS-38949) Respect included/excluded regions in git
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-38949 Respect included/excluded regions in git Change By: Tomas Bjerre Assignee: Paul Wellner Bou Tomas Bjerre 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-38164) Group changelog entries by Jenkins build numbers
Title: Message Title Tomas Bjerre commented on JENKINS-38164 Re: Group changelog entries by Jenkins build numbers Here is an example that recursively gets the older builds: https://stackoverflow.com/questions/38084806/how-to-get-the-changes-since-the-last-successful-build-in-jenkins-pipeline Here is an example that gets the changesets of builds: https://support.cloudbees.com/hc/en-us/articles/217630098-How-to-access-Changelogs-in-a-Pipeline-Job- Using that in combination with this plugin should solve this. def changelogString = gitChangelog returnType: 'STRING', from: [type: 'COMMIT', value: 'commit hash here'], to: [type: 'COMMIT', value: 'next build commit hash here'], template: """ the template... """ println changelogString 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-38164) Group changelog entries by Jenkins build numbers
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-38164 Group changelog entries by Jenkins build numbers Change By: Tomas Bjerre Assignee: Paul Wellner Bou Tomas Bjerre 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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title Tomas Bjerre closed an issue as Won't Fix Jenkins / JENKINS-43362 Allow for setting how commit hashes should be abbreviated Change By: Tomas Bjerre Status: Open Closed Resolution: Won't Fix 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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title
Tomas Bjerre edited a comment on JENKINS-43362
Re: Allow for setting how commit hashes should be abbreviated
The problem here is to find out how to do that with JGit... I can't find it in any docs.But what one can do for now is to use one of these attributes on the commit instance: * {{hash}} * {{hashFull}} {{}} [https://github.com/tomasbjerre/git-changelog-lib]I'll close this one and you can open an issue in the lib if this is still something that you need.
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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title
Tomas Bjerre commented on JENKINS-43362
Re: Allow for setting how commit hashes should be abbreviated
The problem here is to find out how to do that with JGit... I can't find it in any docs. But what one can do for now is to use one of these attributes on the commit instance:
hash
hashFull{{}}
https://github.com/tomasbjerre/git-changelog-lib I'll close this one and you can open an issue in the lib if this is still something that you need.
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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-43362 Allow for setting how commit hashes should be abbreviated Change By: Tomas Bjerre Assignee: Paul Wellner Bou Tomas Bjerre 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-50878) Move 'Upstream Build' and 'Downstream job' on top of Maven report
Title: Message Title dan tran commented on JENKINS-50878 Re: Move 'Upstream Build' and 'Downstream job' on top of Maven report expand/collapse is a much better solution 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-49076) Cannot set custom PATH inside docker container
Title: Message Title
Steven Clark edited a comment on JENKINS-49076
Re: Cannot set custom PATH inside docker container
I believe this may be the root cause as well with the failures I'm seeing within a declarative pipeline. Running this PATH from the env command is the normal value and not the value within my pipeline . This only seems to break when the agent is a docker {code:java}pipeline { agent { docker { image 'debian:stretch' } } environment { PATH = "/opt/test/bin:/usr/bin/:/bin" } stages { stage('Example') { steps { sh 'env' } } }}{code}
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-49076) Cannot set custom PATH inside docker container
Title: Message Title
Steven Clark commented on JENKINS-49076
Re: Cannot set custom PATH inside docker container
I believe this may be the root cause as well with the failures I'm seeing within a declarative pipeline. Running this PATH from the env command is the normal value.
pipeline {
agent {
docker {
image 'debian:stretch'
}
}
environment {
PATH = "/opt/test/bin:/usr/bin/:/bin"
}
stages {
stage('Example') {
steps {
sh 'env'
}
}
}
}
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-50558) Valgrind plugin results error
Title: Message Title
Marshall Galbraith updated an issue
Jenkins / JENKINS-50558
Valgrind plugin results error
Change By:
Marshall Galbraith
Valgrind report pages have stopped working as of today. I recently installed the latest pipeline plugin upgrads, but I don't know if that is related. The valgrind xml files appear to be processes without warnings or errors in the console log.I get the following "Ooops" page when trying to view results: {code:java} org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/valgrind/WEB-INF/lib/valgrind.jar!/org/jenkinsci/plugins/valgrind/ValgrindResult/index.jelly:13:57: No page found 'sidepanel.jelly' for class org.jenkinsci.plugins.valgrind.ValgrindResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:140) at org.kohsuke.stapler.IndexViewDispatcher.dispatch(IndexViewDispatcher.java:30) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Matt Gaspar commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume I didn't see your comment before I posted, but yeah, the workflows.xml are the files from the workflow folder for the build. There was only 45-47 available in there. I did see that this particular one failed despite the console output saying SUCCESS near the bottom. Regardless, this was a build that already ran and completed and shouldn't have reran after a restart of Jenkins. 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Matt Gaspar commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Sam Van Oort I've attached the build.xml for one of the builds that shows SUCCESS (at least in the console) but appears to want to replay after a Jenkins restart. I also attached workflows.xml which is the concatenated files from the workflow directory of the same build. I haven't found any other useful logs associated with this build beyond the exception in my last comment. build.xml workflows.xml 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Matt Gaspar Your data shows that we did indeed fail at some point in the loading of the heads/start nodes/flownodes, and switched to the fallback directory. Under your build workflow folder, please could you upload the file 40.xml through 47.xml – or any that are present, in any case? Perhaps as a single matt-flownodes.xml? I also see that, paradoxically, we show persistedClean = false, for the execution (it thinks that we did not cleanly save data), and completed is false too (may be a result of preceding issues and showing as the build being incomplete). Thanks! I think both of those issues should be covered by fixes I've done now. 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Matt Gaspar updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Matt Gaspar Attachment: workflows.xml 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Matt Gaspar updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Matt Gaspar Attachment: build.xml 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Matt Gaspar Thanks, do you have the build.xml and the flowNodeStorage.xml or the XML files in the workflow subdirectory of the build? I have something that feels like it's 80% of the way there to resolve this cluster of issues – it addresses most of the things noted by Mike Kozell – but it has one known issue still to resolve with shutdown-time persistence. I would like to identify why YOUR build is not showing as already-complete though – all signs point to something going wrong with loading the FlowExecution information, pointing to it looking as if it is incomplete. Do you have any other log messages associated with this build, also? 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-45509) Xcode 9 requires provisioning profile to be specified when using manual code signing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45509 Re: Xcode 9 requires provisioning profile to be specified when using manual code signing Code changed in jenkins User: Kazuhide Takahashi Path: src/main/java/au/com/rayh/ProvisioningProfile.java src/main/java/au/com/rayh/XCodeBuilder.java src/main/resources/au/com/rayh/Messages.properties src/main/resources/au/com/rayh/XCodeBuilder/config.jelly http://jenkins-ci.org/commit/xcode-plugin/5d4f52127cccbe60a52121083f70f9dc29e7e73b Log: Merge pull request #86 from lampietti/xcode9 add xcode9 new signing support JENKINS-45509 Compare: https://github.com/jenkinsci/xcode-plugin/compare/7172a7c67279...5d4f52127ccc 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-45190) Xcode plugin 2.0.0 no longer zips dSYMs as in previous versions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45190 Re: Xcode plugin 2.0.0 no longer zips dSYMs as in previous versions Code changed in jenkins User: Kazuhide Takahashi Path: src/main/java/au/com/rayh/AppFileFilter.java src/main/java/au/com/rayh/DSymFileFilter.java src/main/java/au/com/rayh/XCodeBuilder.java http://jenkins-ci.org/commit/xcode-plugin/7172a7c67279adc2120958209158fe55bb4b22ac Log: Merge pull request #85 from lampietti/dSYM fix dSYMs generation JENKINS-45190 Compare: https://github.com/jenkinsci/xcode-plugin/compare/3937e54f3c0a...7172a7c67279 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-50921) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title
eerik aljas updated an issue
Jenkins / JENKINS-50921
Team Foundation Sercer plugin error: workspace is already mapped
Change By:
eerik aljas
When using the TFS-plugin in combination with the Matrix plugin the first build of the project worked fine. But every new build of the same project throws this error:{code:java}Creating workspace 'Hudson-iTrak(multi-browser)-MASTER' owned by 'ealjas'...Mapping '$/QA/iTrak/iTrak12' to local folder 'C:\wrkspc\iTrak(multi-browser)' in workspace 'Hudson-iTrak(multi-browser)-MASTER'...FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER.com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER. at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:229) at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:176) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1014) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:950) at hudson.plugins.tfs.model.MockableVersionControlClient.createWorkspace(MockableVersionControlClient.java:114) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:81) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:24) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233)Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Workspaces.newWorkspace(Workspaces.java:109) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:144) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:59) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:352) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code} There exists a I have had no success with the workaround for this problem by
[JIRA] (JENKINS-50921) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title eerik aljas updated an issue Jenkins / JENKINS-50921 Team Foundation Sercer plugin error: workspace is already mapped Change By: eerik aljas Environment: Jenkins 2. 89 107 . 3 1 TFS-plugin 5. 126 133 .0matrix-plugin 1. 12 13 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-50921) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title
eerik aljas updated an issue
Jenkins / JENKINS-50921
Team Foundation Sercer plugin error: workspace is already mapped
Change By:
eerik aljas
When using the TFS-plugin in combination with the Matrix plugin the first build of the projekt project worked fine. But every new build of the same projekt project throws this error:{code:java} Creating workspace 'Hudson-iTrak(multi-browser)-MASTER' owned by 'ealjas'...Mapping '$/QA/iTrak/iTrak12' to local folder 'C:\wrkspc\iTrak(multi-browser)' in workspace 'Hudson-iTrak(multi-browser)-MASTER'... FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path D C :\ jenkins wrkspc \ workspace iTrak(multi-browser) \ All_Targets SELENIUM_DRIVER \ target\KDF Windows_10chromelatest is already mapped in workspace Hudson- target SELENIUM_DRIVER = KDF Windows_10chromelatest - KP0025_VisualStudio_VM;24865124 MASTER.com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi - d1ea browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson - 4545 SELENIUM_DRIVER=Windows_10chromelatest - 8285-2de5a102bff6 MASTER . at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:229) at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:176) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1014) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:950) at hudson.plugins.tfs.model.MockableVersionControlClient.createWorkspace(MockableVersionControlClient.java:114) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:81) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:24) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233)Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Workspaces.newWorkspace(Workspaces.java:109) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:144) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:59) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:352) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) at
[JIRA] (JENKINS-49619) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title
eerik aljas updated an issue
Jenkins / JENKINS-49619
Team Foundation Sercer plugin error: workspace is already mapped
Change By:
eerik aljas
Comment:
I am using plugin version [5.133.0|http://auto-hub:8080/pluginManager/plugin/tfs/thirdPartyLicenses] and also experienced it on 5.126.0{code:java}// Mapping '$/QA/iTrak/iTrak12' to local folder 'C:\wrkspc\iTrak(multi-browser)' in workspace 'Hudson-iTrak(multi-browser)-MASTER'...FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER.com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER. at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:229) at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:176) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1014) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:950) at hudson.plugins.tfs.model.MockableVersionControlClient.createWorkspace(MockableVersionControlClient.java:114) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:81) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:24) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233)Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Workspaces.newWorkspace(Workspaces.java:109) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:144) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:59) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:352) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code}
[JIRA] (JENKINS-50921) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title eerik aljas created an issue Jenkins / JENKINS-50921 Team Foundation Sercer plugin error: workspace is already mapped Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2018-04-20 22:15 Environment: Jenkins 2.89.3 TFS-plugin 5.126.0 matrix-plugin 1.12 Priority: Major Reporter: eerik aljas When using the TFS-plugin in combination with the Matrix plugin the first build of the projekt worked fine. But every new build of the same projekt throws this error: FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path D:\jenkins\workspace\All_Targets\target\KDF is already mapped in workspace Hudson-target=KDF-KP0025_VisualStudio_VM;24865124-d1ea-4545-8285-2de5a102bff6. There exists a workaround for this problem by deleting the workspace manually before building the project. But a solution would be desirable.
[JIRA] (JENKINS-49635) Permit VirtualFile to serve external file contents
Title: Message Title Jesse Glick updated JENKINS-49635 Jenkins / JENKINS-49635 Permit VirtualFile to serve external file contents Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed 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-26810) File attribute/symlink support in VirtualFile
Title: Message Title Jesse Glick updated JENKINS-26810 Jenkins / JENKINS-26810 File attribute/symlink support in VirtualFile Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed 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-26810) File attribute/symlink support in VirtualFile
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26810 Re: File attribute/symlink support in VirtualFile Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/util/VirtualFile.java core/src/test/java/jenkins/util/VirtualFileTest.java http://jenkins-ci.org/commit/jenkins/8e603a5986079f7137a571e6ce1c2d9d971a772d Log: JENKINS-26810 Added VirtualFile.mode. 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-49635) Permit VirtualFile to serve external file contents
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49635 Re: Permit VirtualFile to serve external file contents Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/DirectoryBrowserSupport.java core/src/main/java/jenkins/util/VirtualFile.java test/src/test/java/hudson/model/DirectoryBrowserSupportTest.java http://jenkins-ci.org/commit/jenkins/3f01a774662d0e6e3d4f644e6a3197009f0c7b14 Log: JENKINS-49635 Defining new VirtualFile methods to better support external artifact storage. 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-50626) PCT "-mavenProperties" argument does nothing
Title: Message Title Oleg Nenashev updated JENKINS-50626 Jenkins / JENKINS-50626 PCT "-mavenProperties" argument does nothing Change By: Oleg Nenashev Status: In Review Resolved Assignee: Oleg Nenashev Resolution: Fixed 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-50454) PCT Docker Image improperly parses ultra-long versions
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-50454 PCT Docker Image improperly parses ultra-long versions Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed 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-50920) NPM registry credentials not correctly formatted
Title: Message Title
John Case updated an issue
Jenkins / JENKINS-50920
NPM registry credentials not correctly formatted
Change By:
John Case
I am trying to use Jenkins to publish npm packages to a private npm repository. I use the config-file-provider plugin to create a new npm config file.Creating the config looks like this:!npmConfig.PNG!The credentials used in that config is a "username with password" credentials configured with the correct username/password for publishing to my repository. The publish part of my Jenkinsfile looks like:{code:java}nodejs(nodeJSInstallationName: "6.12.0", configId: "npm-publish-config") {lerna publish --conventional-commits --yes}{code} When I run the build I get the following error when it tries to publish: {noformat}need auth You need to authorize this machine using `npm adduser`{noformat} I did a little debugging. I was able to fine find the file it claims to have used as it's npm config:{code:java}@myScope:registry = http://my.private.registry/ //my.private.registry/:always-auth = true //my.private.registry/:username = jenkins //my.private.registry/:_password = <>{code}I have found no information online about the :username and :_password properties being supported by NPM. Everything I have found has said that the .npmrc config file should have an _authToken property like this:{code:java}@myScope:registry = http://my.private.registry/ //my.private.registry/:always-auth = true //my.private.registry/:_authToken="SECRET"{code}What am I doing wrong?
Add Comment
This
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title
John Case created an issue
Jenkins / JENKINS-50920
NPM registry credentials not correctly formatted
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Attachments:
npmConfig.PNG
Components:
config-file-provider-plugin, nodejs-plugin
Created:
2018-04-20 21:53
Priority:
Major
Reporter:
John Case
I am trying to use Jenkins to publish npm packages to a private npm repository. I use the config-file-provider plugin to create a new npm config file. Creating the config looks like this: The credentials used in that config is a "username with password" credentials configured with the correct username/password for publishing to my repository. The publish part of my Jenkinsfile looks like:
nodejs(nodeJSInstallationName: "6.12.0", configId: "npm-publish-config") {
lerna publish --conventional-commits --yes
}
When I run the build I get the following error when it tries to publish:
need auth You need to authorize this machine using `npm adduser`
I did a little debugging. I was able to fine the file it claims to have used as it's npm config:
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Matt Gaspar commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume I'm seeing some similar behavior on a few masters running 2.89.3 workflow-cps: 2.48 workflow-job: 2.19 It appears to even try and resume on a build that completed successfully previously after any restart of jenkins: Job Console snippet GitHub has been notified of this commit’s build result Finished: SUCCESS Resuming build at Wed Apr 18 03:45:16 MST 2018 after Jenkins restart Resuming build at Fri Apr 20 01:21:23 MST 2018 after Jenkins restart Resuming build at Fri Apr 20 01:52:35 MST 2018 after Jenkins restart Resuming build at Fri Apr 20 11:53:07 MST 2018 after Jenkins restart Resuming build at Fri Apr 20 12:13:33 MST 2018 after Jenkins restart jenkins.log Apr 20, 2018 12:18:52 PM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6 onFailure WARNING: Failed to interrupt steps in Owner[JOB_NAME1:JOB_NAME #1] java.lang.IllegalStateException: completed or broken execution at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:741) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:821) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:694) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:500) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:482) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:380) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:345) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:275) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.(LazyLoadRunMapEntrySet.java:65) at jenkins.model.lazy.LazyLoadRunMapEntrySet.iterator(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.(AbstractMap.java:411) at java.util.AbstractMap$2.iterator(AbstractMap.java:410) at hudson.util.RunList.iterator(RunList.java:113) at com.google.common.collect.Iterables$15.apply(Iterables.java:1128) at com.google.common.collect.Iterables$15.apply(Iterables.java:1125) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$MergingIterator.(Iterators.java:1306) at com.google.common.collect.Iterators.mergeSorted(Iterators.java:1274) at com.google.common.collect.Iterables$14.iterator(Iterables.java:1113) at com.google.common.collect.Iterables$UnmodifiableIterable.iterator(Iterables.java:94) at hudson.util.RunList.iterator(RunList.java:113) at jenkins.widgets.RunListProgressiveRendering.compute(RunListProgressiveRendering.java:60) at jenkins.util.ProgressiveRendering$1.run(ProgressiveRendering.java:122) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
[JIRA] (JENKINS-50916) Add support for JUnit health factor configuration attribute
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50916 Re: Add support for JUnit health factor configuration attribute Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher/config.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher/help-healthScaleFactor.html jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher/help-keepLongStdio.html http://jenkins-ci.org/commit/pipeline-maven-plugin/3d45d3b2902f10a63a92943ee31fc672af28993a Log: Merge pull request #146 from jenkinsci/JENKINS-50916 JENKINS-50916 Add support for JUnit health factor attribute Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/679063311440...3d45d3b2902f 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-49619) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title eerik aljas commented on JENKINS-49619 Re: Team Foundation Sercer plugin error: workspace is already mapped I am using plugin version 5.133.0 and also experienced it on 5.126.0 // Mapping '$/QA/iTrak/iTrak12' to local folder 'C:\wrkspc\iTrak(multi-browser)' in workspace 'Hudson-iTrak(multi-browser)-MASTER'... FATAL: com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER. com.microsoft.tfs.core.clients.versioncontrol.exceptions.MappingConflictException: The path C:\wrkspc\iTrak(multi-browser)\SELENIUM_DRIVER\Windows_10chromelatest is already mapped in workspace Hudson-SELENIUM_DRIVER=Windows_10chromelatest-MASTER. at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:229) at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCache.checkForMappingConflicts(InternalCache.java:176) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1014) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:950) at hudson.plugins.tfs.model.MockableVersionControlClient.createWorkspace(MockableVersionControlClient.java:114) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:81) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:24) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233) Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Workspaces.newWorkspace(Workspaces.java:109) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:144) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:59) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:352) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
[JIRA] (JENKINS-50918) Bitbucket Source webhook endpoint fails: X-Event-Key HTTP header not found
Title: Message Title R T closed an issue as Won't Fix Line 94 of the code throws this when an eventKey is not passed as part of the request. Using a browser would do that. https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/fed749a4860d0171d89422fb0f5aa8dcfc48c6cd/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/hooks/BitbucketSCMSourcePushHookReceiver.java Jenkins / JENKINS-50918 Bitbucket Source webhook endpoint fails: X-Event-Key HTTP header not found Change By: R T Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50919) Ephemeral/Cloud Slaves History Present (in massive quantities)
Title: Message Title Steven Christenson updated an issue Jenkins / JENKINS-50919 Ephemeral/Cloud Slaves History Present (in massive quantities) Change By: Steven Christenson Environment: CloudBees Jenkins Enterprise 2.89.4.2-rolling;changelog-history-plugin 2.18 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-50919) Ephemeral/Cloud Slaves History Present (in massive quantities)
Title: Message Title Steven Christenson created an issue Jenkins / JENKINS-50919 Ephemeral/Cloud Slaves History Present (in massive quantities) Issue Type: Bug Assignee: Emilio Escobar Components: changelog-history-plugin Created: 2018-04-20 21:00 Environment: CloudBees Jenkins Enterprise 2.89.4.2-rolling; Labels: plugins Priority: Minor Reporter: Steven Christenson While we weren't paying close attention, the changelog-history-plugin created 1 million entries in the config-history/nodes folder. The reason is apparently that we have been allocating slaves from a cloud/swarm that live for a few minutes and then are reclaimed. For example here is a snippet of some of the directories created: ./docker-8cd90563e4bb5_deleted_20180420_201419_896 ./docker-8ccdf12fbb215_deleted_20180420_200757_598 ./docker-8c9b06442f1b3_deleted_20180420_190621_902 ./docker-8cdbb299a77ee ./docker-8cdd7cf907080 ./docker-8cb4634d8051c_deleted_20180420_193442_663 ./docker-8c97a7968_deleted_20180420_190313_641 ./docker-8cb8ebbab1aa8_deleted_20180420_193606_401 ./docker-8cbdc8cfa9186_deleted_20180420_195041_264 ./docker-8c8bfc4dfd5ba_deleted_20180420_184741_165 ./docker-8cd3b4d6da0ed_deleted_20180420_200527_843 ./docker-8c8dee6436c49_deleted_20180420_184730_195 ./docker-8cafb29f67d1c_deleted_20180420_192601_188 ./docker-8cd90560b2493_deleted_20180420_201451_943 ./docker-8cbddff5b52a6_deleted_20180420_194238_688 ./docker-8caca89cd5a6f_deleted_20180420_192758_912 ./docker-8cbaf4fff12fd_deleted_20180420_194208_624 ./docker-8c8ba6d61cff9_deleted_20180420_184756_715 The release notes for this
[JIRA] (JENKINS-50918) Bitbucket Source webhook endpoint fails: X-Event-Key HTTP header not found
Title: Message Title R T created an issue Jenkins / JENKINS-50918 Bitbucket Source webhook endpoint fails: X-Event-Key HTTP header not found Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-04-20 20:56 Environment: CentOS 7 centos-release-7-4.1708.el7.centos.x86_64 openjdk version "1.8.0_161" OpenJDK Runtime Environment (build 1.8.0_161-b14) OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode) Jenkins 2.100-1.1 installed via Yum Bitbucket Branch Source 2.2.10 Bitbucket Build Status Notifier 1.3.3 Bitbucket Plugin 1.1.8 Pipeline 2.5 Pipeline API 2.26 Apache HttpComponents Client 4.x API 4.5.3-2.1 Display URL API 2.2.0 Labels: webhook bitbucket Priority: Major Reporter: R T I've got one webhook working on Bitbucket Cloud for freestyle jobs. I have created a multibranch pipeline and added the Bitbucket Source plugin to facilitate a separate webhook for it. I created a second webhook for the bitbucket-scmsource-hook/notify endpoint endpoint. Jenkins is not recognizing payloads from Bitbucket for this new webhook. When I simply visit https://myjenkins/bitbucket-scmsource-hook/notify, the following is displayed: java.lang.Exception: X-Event-Key HTTP header not found at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:83) at
[JIRA] (JENKINS-43995) Individual Pipeline steps and stages/blocks should have Result statuses
Title: Message Title Surya Bharath Bommadevara edited a comment on JENKINS-43995 Re: Individual Pipeline steps and stages/blocks should have Result statuses y...@payrailz.com [~yinly] : The workaround you mentioned does it mark stages in parallel also as failed and not the entire pipeline. Can you also provide us your workaround if possible. Thanks in advance. 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-43995) Individual Pipeline steps and stages/blocks should have Result statuses
Title: Message Title Surya Bharath Bommadevara edited a comment on JENKINS-43995 Re: Individual Pipeline steps and stages/blocks should have Result statuses Yin Ly y...@payrailz.com : The workaround you mentioned does it mark stages in parallel also as failed and not the entire pipeline. Can you also provide us your workaround if possible. Thanks in advance. 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-43995) Individual Pipeline steps and stages/blocks should have Result statuses
Title: Message Title Surya Bharath Bommadevara commented on JENKINS-43995 Re: Individual Pipeline steps and stages/blocks should have Result statuses Yin Ly: The workaround you mentioned does it mark stages in parallel also as failed and not the entire pipeline. Can you also provide us your workaround if possible. Thanks in advance. 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-50736) Calling another vars step in inheritance context fails with MissingMethodException
Title: Message Title Jesse Glick commented on JENKINS-50736 Re: Calling another vars step in inheritance context fails with MissingMethodException acme is an attribute of WorkflowScript. SpecialBuild is a top-level class. Therefore unqualified acme is not resolvable. That is not a bug. If unqualified acme does work inside Build, that would be a bug. Unless it were a field. Which it does not look like, since you are using def, which is used for defining local variables. I was not aware that is even syntactically legal in Groovy. Declare a type, or use @Field, or do not declare it at all and just refer to it with @acme notation. I am pretty confident this is all just a user error. 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-32778) Jenkins plugin installation path traversal vulnerability
Title: Message Title Jesse Glick resolved as Not A Defect consider a new feature that allowed an administrator to upload an 'skin' package that changed colors, logos, style sheets, etc. Such a package wouldn't run any code after installation, but depending on the implementation it may reuse this code that unpackages 'jar'/'zip' files. I would not recommend that such a feature be created, but if it were (as a plugin on the update site), it would be the responsibility of the plugin author to ensure that all submitted ZIP files were treated as potentially malicious and the contents checked accordingly. If and when such a feature is created and the author is negligent about security and someone discovers this, file a SECURITY report and the plugin can be either fixed or blacklisted. Jenkins / JENKINS-32778 Jenkins plugin installation path traversal vulnerability Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-50722) origins field is never saved
Title: Message Title Baptiste Mathus updated JENKINS-50722 Jenkins / JENKINS-50722 origins field is never saved Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed 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-50736) Calling another vars step in inheritance context fails with MissingMethodException
Title: Message Title Andrew Bayer commented on JENKINS-50736 Re: Calling another vars step in inheritance context fails with MissingMethodException Throwing some notes here - first, this is impossible to recreate directly in a single source file, even with multiple classes in it. I believe this is because the CPS transformation here in the subclass happens before the autogenerated getter method is added to the superclass when they're all in the same source file. You can recreate it in a single file by either adding a getter method to the superclass directly. You can create by referencing the field in the subclasses with the this.@someField attribute syntax, but I believe that fails in vanilla Groovy too, so eh. What's actually happening is that we're actually calling (via some layers of abstraction) InvokerHelper.getAttribute(object, name), which ends up getting the MetaBeanProperty for that object/name combo. And the field field of that MetaBeanProperty is null. This is the same behavior you get in vanilla Groovy if you do this.@someField in the subclass. So the problem seems to be that you can't actually call InvokerHelper.getAttribute(object, name) for a field on a superclass, and our hacks to avoid recursion hell with getter methods (which I think was intended primarily to deal with explicit getters, not autogenerated getters, but don't quote me on that) will end up doing that. How to fix this? Well, I've got a couple hacks I've tried that seem to "fix" this for some value of "fixed" - most notably changing DefaultInvoker#getAttribute(lhs, name) to catch MissingFieldException when it shows up and try forcing a MetaClass#getAttribute call with InvokerHelper.getMetaClass(lhs.getClass().getSuperclass()), recursing on until we get to Object.class. But that feels really really dirty, so I'm trying to think of something better. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title Jesse Glick updated JENKINS-50777 Fixes released for scm-api, branch-api, and github-branch-source, ensuring adequate metadata at least for PR builds. Fix in git merged but as of this writing unreleased, meaning metadata will be missing for origin branch builds. Jenkins / JENKINS-50777 Exported API for SCMRevisionAction & SCMSource Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Matt Sicker updated JENKINS-13128 Jenkins / JENKINS-13128 Artifacts Permissions Stripped Change By: Matt Sicker Status: In Progress Review 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-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50777 Exported API for SCMRevisionAction & SCMSource Change By: Jesse Glick Component/s: branch-api-plugin 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-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50777 Re: Exported API for SCMRevisionAction & SCMSource Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/jenkins/branch/BranchSource.java src/main/java/jenkins/branch/MultiBranchProject.java http://jenkins-ci.org/commit/branch-api-plugin/7f6accc3a946f468da2919cfcf3435520c537ad1 Log: JENKINS-50777 Export the SCMSource(s) from a MultiBranchProject. 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-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50777 Re: Exported API for SCMRevisionAction & SCMSource Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/jenkins/branch/BranchSource.java src/main/java/jenkins/branch/MultiBranchProject.java http://jenkins-ci.org/commit/branch-api-plugin/bd62524703191938798a676ad70ea4b9e103a1f0 Log: Merge pull request #126 from jglick/export-JENKINS-50777 JENKINS-50777 Export the SCMSource(s) from a MultiBranchProject Compare: https://github.com/jenkinsci/branch-api-plugin/compare/e53a2a9d5f51...bd6252470319 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-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-50777
Re: Exported API for SCMRevisionAction & SCMSource
Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/d1c4689caf4895db7219788bc09b8058f5a5db84 Log: Merge pull request #181 from jglick/export-JENKINS-50777 JENKINS-50777 Export GitHubSCMSource. {repoOwner,repository} Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/2aaa13771c05...d1c4689caf48
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-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-50777
Re: Exported API for SCMRevisionAction & SCMSource
Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/eef6bd570fc96d4447d45bee543ea8ba07e4e976 Log: JENKINS-50777 Export GitHubSCMSource. {repoOwner,repository} .
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-50722) origins field is never saved
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50722 Re: origins field is never saved Code changed in jenkins User: Stephen Connolly Path: src/main/resources/jenkins/metrics/api/MetricsAccessKey/config.jelly http://jenkins-ci.org/commit/metrics-plugin/80038f7ba4d523be32815de3f969e20a0f73f869 Log: Merge pull request #33 from batmat/JENKINS-50722 JENKINS-50722 origins field is not saved Compare: https://github.com/jenkinsci/metrics-plugin/compare/39718de3379b...80038f7ba4d5 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-50722) origins field is never saved
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50722 Re: origins field is never saved Code changed in jenkins User: Baptiste Mathus Path: src/main/resources/jenkins/metrics/api/MetricsAccessKey/config.jelly http://jenkins-ci.org/commit/metrics-plugin/b56fd9904855fbb590767719f026c5be0bf51836 Log: JENKINS-50722 origins field is not saved 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-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title Sam Van Oort closed an issue as Done Solved as of workflow-cps 2.49, workflow-job 2.20 (plus some ancillary PRs) Jenkins / JENKINS-50784 "Replay" pipeline button/link is not (always?) available (anymore?) Change By: Sam Van Oort Status: In Progress Closed Resolution: Done 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
[JIRA] (JENKINS-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50777 Re: Exported API for SCMRevisionAction & SCMSource Code changed in jenkins User: Jesse Glick Path: src/main/java/jenkins/scm/api/SCMSource.java http://jenkins-ci.org/commit/scm-api-plugin/77799131b869c9e6b7e346e745378057fdf7d15c Log: JENKINS-50777 Also allow an SCMSource to define exported fields (but do not define any generic ones). 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-50777) Exported API for SCMRevisionAction & SCMSource
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50777 Re: Exported API for SCMRevisionAction & SCMSource Code changed in jenkins User: Jesse Glick Path: src/main/java/jenkins/scm/api/SCMSource.java http://jenkins-ci.org/commit/scm-api-plugin/ba21d6ea8d45852ed6a5fa9ccf2002b60d0abb42 Log: Merge pull request #53 from jglick/export-JENKINS-50777 JENKINS-50777 Also allow an SCMSource to define exported fields Compare: https://github.com/jenkinsci/scm-api-plugin/compare/bed5b69fe4d0...ba21d6ea8d45 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-50917) Safe navigation operator doesn't work for setting a property
Title: Message Title Roman Donchenko created an issue Jenkins / JENKINS-50917 Safe navigation operator doesn't work for setting a property Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-04-20 17:11 Environment: Jenkins 2.107.2 Pipeline: Groovy 2.48 Priority: Minor Reporter: Roman Donchenko Normally, this works in Groovy: groovy:000> null?.foo = 'bar' ===> bar But in a pipeline, it does not: java.lang.NullPointerException: Cannot set property 'foo' on null object at org.codehaus.groovy.runtime.NullObject.setProperty(NullObject.java:80) at org.codehaus.groovy.runtime.InvokerHelper.setProperty(InvokerHelper.java:197) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.setProperty(ScriptBytecodeAdapter.java:484) at org.kohsuke.groovy.sandbox.impl.Checker$7.call(Checker.java:347) at org.kohsuke.groovy.sandbox.impl.Checker.checkedSetProperty(Checker.java:351) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.setProperty(SandboxInvoker.java:33) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawSet(PropertyAccessBlock.java:24) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.set(PropertyishBlock.java:88) at
[JIRA] (JENKINS-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction.java src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction/index.jelly src/test/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayActionTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/b29500120684e54eb202f2dad46ad7269e631ab4 Log: Full test and fix for lazy-load issues with ReplayAction JENKINS-50784 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-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Code changed in jenkins User: Sam Van Oort Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction.java src/test/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayActionTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/64848b1f7f83d7846f607181b675e04aaf8caed0 Log: Fixes to JENKINS-50784 to ensure we hard-fetch FlowExecutions when we need to 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-50784) "Replay" pipeline button/link is not (always?) available (anymore?)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50784 Re: "Replay" pipeline button/link is not (always?) available (anymore?) Code changed in jenkins User: Sam Van Oort Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction.java src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayPipelineCommand.java src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction/index.jelly src/test/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayActionTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/9a54fd25886a301502121918f91bc0b5be29ca13 Log: Merge pull request #222 from svanoort/lazy-load-fixToGetOrNull-JENKINS-50784 Lazy load fix to get or null JENKINS-50784 Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/56f3fde1d5c6...9a54fd25886a 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-42836) Build parameter not expanded in script path
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42836 Re: Build parameter not expanded in script path Code changed in jenkins User: Andrew Bayer Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java src/test/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinitionTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/2dc4bf82a1e095b09dde4638a50c893320432f93 Log: [FIXED JENKINS-42836] env expand the script path from SCM. 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-50164) 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
Title: Message Title Jesse Glick commented on JENKINS-50164 Re: 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running W.r.t. JENKINS-21942, so long as you check what happens with your patch given an installation using config-as-code (e.g., in Docker) where root config.xml is not saved during initial startup yet there is a jobs directory—we expect to be using the preferred $JENKINS_HOME/workspace/ location when the system property is undefined. 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-50843) Cannot call closure element of map as method in sandbox
Title: Message Title Jesse Glick started work on JENKINS-50843 Change By: Jesse Glick Status: Open In Progress 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-50843) Cannot call closure element of map as method in sandbox
Title: Message Title Jesse Glick assigned an issue to Rudolf-Walter Kiss-Szakacs Jenkins / JENKINS-50843 Cannot call closure element of map as method in sandbox Change By: Jesse Glick Assignee: Andrew Bayer Rudolf-Walter Kiss-Szakacs 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-50843) Cannot call closure element of map as method in sandbox
Title: Message Title Jesse Glick updated JENKINS-50843 Jenkins / JENKINS-50843 Cannot call closure element of map as method in sandbox Change By: Jesse Glick Status: In Progress Review 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-50915) Update BouncyCastle API plugin to latest version (bcpkix-jdk15on:1.59)
Title: Message Title Devin Nusbaum started work on JENKINS-50915 Change By: Devin Nusbaum Status: Open In Progress 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-50915) Update BouncyCastle API plugin to latest version (bcpkix-jdk15on:1.59)
Title: Message Title Devin Nusbaum updated JENKINS-50915 Jenkins / JENKINS-50915 Update BouncyCastle API plugin to latest version (bcpkix-jdk15on:1.59) Change By: Devin Nusbaum Status: In Progress Review 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-50916) Add support for JUnit health factor configuration attribute
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50916 Re: Add support for JUnit health factor configuration attribute Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher/config.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher/help-healthScaleFactor.html jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher/help-keepLongStdio.html http://jenkins-ci.org/commit/pipeline-maven-plugin/06b663d1d0cd0a3e0517c9324a2eab1b2a98cdc7 Log: JENKINS-50916 Add support for JUnit health factor attribute 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-50916) Add support for JUnit health factor configuration attribute
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-50916 Add support for JUnit health factor configuration attribute Issue Type: New Feature Assignee: Cyrille Le Clerc Attachments: image-2018-04-20-18-01-20-169.png Components: pipeline-maven-plugin Created: 2018-04-20 16:01 Priority: Minor Reporter: Cyrille Le Clerc Add support for JUnit health factor configuration attribute. Add Comment
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Matt Sicker started work on JENKINS-13128 Change By: Matt Sicker Status: Open In Progress 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-13128) Artifacts Permissions Stripped
Title: Message Title Matt Sicker commented on JENKINS-13128 Re: Artifacts Permissions Stripped Added a PR. 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-47427) Poll per change with pipeline jobs
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-47427 Poll per change with pipeline jobs Change By: Paul Allen Assignee: Paul Allen 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-47427) Poll per change with pipeline jobs
Title: Message Title Paul Allen started work on JENKINS-47427 Change By: Paul Allen Status: Open In Progress 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-47427) Poll per change with pipeline jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-47427 Re: Poll per change with pipeline jobs Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/tasks/PollTask.java src/test/java/org/jenkinsci/plugins/p4/DefaultEnvironment.java src/test/java/org/jenkinsci/plugins/p4/client/GraphTest.java src/test/java/org/jenkinsci/plugins/p4/client/PollingTest.java http://jenkins-ci.org/commit/p4-plugin/931f05a111a66c2002deb8dc80f321bcb3abee72 Log: Poll per change for Pipeline. JENKINS-47427 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-50915) Update BouncyCastle API plugin to latest version (bcpkix-jdk15on:1.59)
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-50915 Update BouncyCastle API plugin to latest version (bcpkix-jdk15on:1.59) Issue Type: Improvement Assignee: Devin Nusbaum Components: bouncycastle-api-plugin Created: 2018-04-20 15:52 Priority: Minor Reporter: Devin Nusbaum We should update to the latest release of BouncyCastle. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-13128) Artifacts Permissions Stripped
Title: Message Title Matt Sicker commented on JENKINS-13128 Re: Artifacts Permissions Stripped Also important to note: this bug seems to only affect local->local file copying. Any local->remote or remote->local file copying happens via tar archives which preserve file permissions and are already handled as such. 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-50912) XUnit plugin seems not to be maintained any more
Title: Message Title Nikolas Falco resolved as Won't Do Yes, if you have a look on github there are new commits this week. Jenkins / JENKINS-50912 XUnit plugin seems not to be maintained any more Change By: Nikolas Falco Status: Open Resolved Resolution: Won't Do 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
[JIRA] (JENKINS-50912) XUnit plugin seems not to be maintained any more
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-50912 XUnit plugin seems not to be maintained any more Change By: Nikolas Falco Assignee: Andrew Bayer Nikolas Falco 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-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez commented on JENKINS-42851 Re: secretVolume not created read only https://github.com/jenkinsci/kubernetes-plugin/#using-yaml-to-define-pod-templates 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-50909) Using jenkins snapshots with the docker image makes some plugins to fail
Title: Message Title Oleg Nenashev started work on JENKINS-50909 Change By: Oleg Nenashev Status: Open In Progress 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-50909) Using jenkins snapshots with the docker image makes some plugins to fail
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50909 Using jenkins snapshots with the docker image makes some plugins to fail Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-13128) Artifacts Permissions Stripped
Title: Message Title Matt Sicker commented on JENKINS-13128 Re: Artifacts Permissions Stripped I should be more specific about the umask. The way file creation works by default generally means working with a directory umask of 022 and "file umask" (not really a thing) of 133. The difference, of course, is because an executable directory means that it can be listed, not executed. 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-42851) secretVolume not created read only
Title: Message Title Vladislav Trayanov commented on JENKINS-42851 Re: secretVolume not created read only Sorry, for the dumb question, but how to use the yaml syntax of the plugin? Not sure where I can find it in the docs 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-50558) Valgrind plugin results error
Title: Message Title Marshall Galbraith commented on JENKINS-50558 Re: Valgrind plugin results error It's good to know I'm not the only one with the problem. I would look into fixing it my self, but I don't have any skills with Java... 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-50914) Pipeline snippet generator doesn't work for the publishValgrind step
Title: Message Title Roman Donchenko created an issue Jenkins / JENKINS-50914 Pipeline snippet generator doesn't work for the publishValgrind step Issue Type: Bug Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 2018-04-20 14:30 Environment: Jenkins 2.107.2 Valgrind plugin 0.28 Priority: Major Reporter: Roman Donchenko If I select the publishValgrind step in the snippet generator, nothing appears underneath it, and this appears in the Jenkins log: Apr 20, 2018 2:26:50 PM hudson.widgets.RenderOnDemandClosure$1 generateResponse WARNING: Failed to evaluate the template closure org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/plugins/valgrind/WEB-INF/lib/valgrind.jar!/org/jenkinsci/plugins/valgrind/steps/ValgrindPublisherStep/config.jelly:3:85: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Eric St-Amand edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Using Jenkins 2.107.1I have this error this morning, not sure why exactly, but I checked for those JCE and they were already bundled with java 1.8u151 64 bits. Didn't help to use the one downloaded from Oracle. I found a temporary solution by reverting to JNLP protocol v3 (in Configure Global Security / Agents section / Advanced Agent protocols... button), which I do not like because it is a deprecated protocol. Using fixed port for JNLP connection. EDIT: Also tried to update to java 1.8u171 64 bits, no luck. 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-38181) withCredentials variables that are extracted are not masked outside of block
Title: Message Title Jesse Glick commented on JENKINS-38181 Re: withCredentials variables that are extracted are not masked outside of block Agreed, this is not a defect and can be closed. FWIW I recently cut a release of credentials-binding that attempted to explain the security model more clearly in the Pipeline Syntax help text. 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-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Eric St-Amand edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Using Jenkins 2.107.1I have this error this morning, not sure why exactly, but I checked for those JCE and they were already bundled with java 1.8u151 64 bits. Didn't help to use the one downloaded from Oracle. I found a temporary solution by reverting to JNLP protocol v3 (in Configure Global Security / Agents section / Advanced button), which I do not like because it is a deprecated protocol. EDIT: Also tried to update to java 1.8u171 64 bits, no luck. 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-50558) Valgrind plugin results error
Title: Message Title Knut Karlsen commented on JENKINS-50558 Re: Valgrind plugin results error Hm, I've got to retract my hypothesis: Some older builds broke again without any obvious event in the jenkins session. Still I can get back the trends if I delete broken builds. 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title
Régis Maura edited a comment on JENKINS-49744
Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
I have updated Jenkins to 2.117 but still have the issue.I found that it may be related to Folder plugin too.When I copy a job *from a folder to the same folder*, there is no error.In this case, I am the owner of both the folder and the original job. I'm also set as owner of the copy job.So this scenario is : from URL http://jenkins/job/ * FOLDER_NAME * / New Item --> job name = MY_JOB_IN_FOLDER_COPY / copy from = MY_JOB_IN_FOLDER {color:#14892c}=> Copy is OK{color}When I copy a job *from a folder to root*, I get the error.In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_ROOT_COPY / copy from = *FOLDER_NAME*/MY_JOB_IN_FOLDER {color:#d04437}=> Copy fails{color}When I copy a job *from a root to root*, I get the error.In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_IN_ROOT_COPY / copy from = MY_JOB_IN_ROOT {color:#d04437}=> Copy fails{color}When I copy a job *from root to a subfolder*, there is no error.In this case, the scenario is: from URL : http://jenkins/job/FOLDER_NAME/ New item --> job name = MY_JOB_IN_FOLDER2 / copy from = *..*/MY_JOB_IN_ROOT {color:#14892c}=> Copy is OK{color}I don't know if this is the use of both ownership and folder plugins, but it seems that only *copy* of job in *root* folder is causing issue.Note that users can still create new job in root folder without errors.Hope this help :)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title
Régis Maura edited a comment on JENKINS-49744
Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
I have updated Jenkins to 2.117 but still have the issue.I found that it may be related to Folder plugin too.When I copy a job *from a folder to the same folder*, there is no error.In this case, I am the owner of both the folder and the original job. I'm also set as owner of the copy job.So this scenario is : from URL http://jenkins/job/*FOLDER_NAME*/ New Item --> job name = MY_JOB_IN_FOLDER_COPY / copy from = MY_JOB_IN_FOLDER {color:#14892c}=> Copy is OK{color}When I copy a job *from a folder to root*, I get the error.In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_ROOT_COPY / copy from = *FOLDER_NAME*/MY_JOB_IN_FOLDER {color:#d04437}=> Copy fails{color}When I copy a job *from a root to root*, I get the error.In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_IN_ROOT_COPY / copy from = MY_JOB_IN_ROOT {color:#d04437}=> Copy fails{color}When I copy a job *from root to a subfolder*, there is no error.In this case, the scenario is: from URL : http://jenkins/job/*FOLDER_NAME*/ New item --> job name = MY_JOB_IN_FOLDER2 / copy from = *..*/MY_JOB_IN_ROOT {color:#14892c}=> Copy is OK{color}I don't know if this is the use of both ownership and folder plugins, but it seems that only *copy* of job in *root* folder is causing issue.Note that users can still create new job in root folder without errors.Hope this help :)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title
Régis Maura edited a comment on JENKINS-49744
Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
I have updated Jenkins to 2.117 but still have the issue.I found that it may be related to Folder plugin too.When I copy a job *from a folder to the same folder*, there is no error.In this case, I am the owner of both the folder and the original job. I'm also set as owner of the copy job.So this scenario is : from URL http://jenkins/job/*FOLDER_NAME*/ New Item --> job name = MY_JOB_IN_FOLDER_COPY / copy from = MY_JOB_IN_FOLDER {color:#14892c}=> Copy is OK{color}When I copy a job *from a folder to root*, I get the error.In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_ROOT_COPY / copy from = *FOLDER_NAME*/MY_JOB_IN_FOLDER {color:#d04437}=> Copy fails{color}When I copy a job *from a root to root*, I get the error.In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_IN_ROOT_COPY / copy from = MY_JOB_IN_ROOT {color:#d04437}=> Copy fails{color}When I copy a job *from root to a subfolder*, there is no error.In this case, the scenario is: from URL : http://jenkins/job/ * FOLDER_NAME * / New item --> job name = MY_JOB_IN_FOLDER2 / copy from = *..*/MY_JOB_IN_ROOT {color:#14892c}=> Copy is OK{color}I don't know if this is the use of both ownership and folder plugins, but it seems that only *copy* of job in *root* folder is causing issue.Note that users can still create new job in root folder without errors.Hope this help :)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-32998) add condition to the GIT clone/pull step
Title: Message Title Sebastien Bonami commented on JENKINS-32998 Re: add condition to the GIT clone/pull step Any news on this? I would also like this. 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title
Régis Maura edited a comment on JENKINS-49744
Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
I have updated Jenkins to 2.117 but still have the issue.I found that it may be related to Folder plugin too.When I copy a job* from a folder to the same folder*, there is * no error * .In this case, I am the owner of both the folder and the original job. I'm also set as owner of the copy job.So this scenario is : from URL http://jenkins/job/*FOLDER_NAME*/ New Item --> job name = MY_JOB_IN_FOLDER_COPY / copy from = MY_JOB_IN_FOLDER {color:#14892c}=> Copy is OK{color}When I copy a job *from a folder to root*, I get the error.In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_ROOT_COPY / copy from = *FOLDER_NAME*/MY_JOB_IN_FOLDER {color:#d04437}=> Copy fails{color}When I copy a job * from root to a folder subfolder* , there is no error.In this case, the scenario is: from URL : http://jenkins/job/*FOLDER_NAME*/ New item --> job name = MY_JOB_IN_FOLDER2 / copy from = *..*/MY_JOB_IN_ROOT {color:#14892c}=> Copy is OK{color}I don't know if this is the use of both ownership and folder plugins, but it seems that only *copy* of job in *root* folder is causing issue.Note that users can still create new job in root folder without errors.Hope this help :)
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
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Régis Maura commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API I have updated Jenkins to 2.117 but still have the issue. I found that it may be related to Folder plugin too. When I copy a job* from a folder to the same folder*, there is no error. In this case, I am the owner of both the folder and the original job. I'm also set as owner of the copy job. So this scenario is : from URL http://jenkins/job/*FOLDER_NAME*/ New Item --> job name = MY_JOB_IN_FOLDER_COPY / copy from = MY_JOB_IN_FOLDER => Copy is OK When I copy a job from a folder to root, I get the error. In this case, the scenario is: from URL : http://jenkins/job/ New item --> job name = MY_JOB_ROOT_COPY / copy from = FOLDER_NAME/MY_JOB_IN_FOLDER => Copy fails When I copy a job from root to a folder, there is no error. In this case, the scenario is: from URL : http://jenkins/job/*FOLDER_NAME*/ New item --> job name = MY_JOB_IN_FOLDER2 / copy from = ../MY_JOB_IN_ROOT => Copy is OK I don't know if this is the use of both ownership and folder plugins, but it seems that only copy of job in root folder is causing issue. Note that users can still create new job in root folder without errors. Hope this help 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-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Eric St-Amand commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Using Jenkins 2.107.1 I have this error this morning, not sure why exactly, but I checked for those JCE and they were already bundled with java 1.8u151 64 bits. Didn't help to use the one downloaded from Oracle. I found a temporary solution by reverting to JNLP protocol v3 (in Configure Global Security / Agents section / Advanced button), which I do not like because it is a deprecated protocol. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Mark Waite commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Michael Porter, if you're able to explore further in your failure case, could you download and install the git-client-plugin.hpi from the [pull request artifacts|https://ci.jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi?|https://ci.jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi]] That version of the git client plugin adds an additional logging statement which shows that command line git has completed. That will allow us to confirm that git rev-list is not hanging. It doesn't help us identify what is hanging, but it at least allows us to remove the git rev-list call from the list of suspects. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title
Mark Waite edited a comment on JENKINS-48357
Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
[~michaelpporter], if you're able to explore further in your failure case, could you download and install the [git-client-plugin.hpi|https://ci.jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi] from the [pull request artifacts| [ https://ci.jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi] ?|https://ci . jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi]] That version of the git client plugin adds an additional logging statement which shows that command line git has completed. That will allow us to confirm that {{git rev-list}} is not hanging. It doesn't help us identify what is hanging, but it at least allows us to remove the {{git rev-list}} call from the list of suspects.
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.
