[JIRA] (JENKINS-48945) wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files)
Title: Message Title Sascha Friederich commented on JENKINS-48945 Re: wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files) it took some amount of time, to track down the problem - could just anyone take a look at this issue? 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-49604) Wrong cleaning generated files in overlaying multiple depot directories
Title: Message Title
Alexey Larsky updated an issue
Jenkins / JENKINS-49604
Wrong cleaning generated files in overlaying multiple depot directories
Change By:
Alexey Larsky
I use overlay syntax for merge two depot's folders into one workspace folder.When I overlaying folder 'Project_*1*/folder/' by 'Project_*2*/folder/...' like below and enable 'DELETE generated files' option - all files from original 'Project_*1*/folder/...' are removing and stays only '//depot/Project_*2*/folder/' files. It works with native client and another Perforce plugin.{code:java} //depot/Project_1/...//workspace/...+//depot/Project_2/folder/... //workspace/folder/...{code} PS. The workaround is explicit mapping 'Project_*1*/folder'.{code:java} //depot/Project_1/...//workspace/... //depot/Project_1/folder/... //workspace/folder/...+//depot/Project_2/folder/... //workspace/folder/...{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subsc
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nicolas De Loof closed an issue as Fixed
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Nicolas De Loof
Status:
Resolved Closed
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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title Michael Neale commented on JENKINS-49610 Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned Right, this is tricky. Can I ask if this has been around, with jobDSL, and only recently being noted? A warning/error may be ok for jobDSL, but for blue ocean would want it to not suddenly blow up. If a work around for blue users is to open and save the config in classic - I think that is ok, if that is the main impact (assuming it is fixed so NEW jobs get a reasonable non null id). Assuming I understood 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-49225) Graph not generated on scheduled performance jobs
Title: Message Title Artem Fedorov updated an issue Jenkins / JENKINS-49225 Graph not generated on scheduled performance jobs Change By: Artem Fedorov Attachment: all_builds.png 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-49225) Graph not generated on scheduled performance jobs
Title: Message Title Artem Fedorov updated an issue Jenkins / JENKINS-49225 Graph not generated on scheduled performance jobs Change By: Artem Fedorov Attachment: builds_history.png 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-49604) Wrong cleaning generated files in overlaying multiple depot directories
Title: Message Title
Alexey Larsky updated an issue
Jenkins / JENKINS-49604
Wrong cleaning generated files in overlaying multiple depot directories
Change By:
Alexey Larsky
I use overlay syntax for merge two depot's folders into one workspace folder.When I overlaying folder 'Project_*1*/folder/' by 'Project_*2*/folder/...' like below and enable 'DELETE generated files' option - all files from original 'Project_*1*/folder/...' are removing and stays only '//depot/Project_*2*/folder/' files. It works with native client and another Perforce plugin.{code:java} //depot/Project_1/...//workspace/...+//depot/Project_2/folder/... //workspace/folder/...{code} PS. The workaround is explicit mapping 'Project_*1*/folder'.{code:java} //depot/Project_1/...//workspace/... //depot/Project_1/folder/... //workspace/folder/...+//depot/Project_2/folder/... //workspace/folder/...{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subs
[JIRA] (JENKINS-49225) Graph not generated on scheduled performance jobs
Title: Message Title Artem Fedorov commented on JENKINS-49225 Re: Graph not generated on scheduled performance jobs I tried with config Build periodically : "H 10 * * *" I got 3 build for weekend 19-21 And when I opened it i saw graphs So, I really don't understand how I can reproduce this bug.. Maybe answers for the following questions can help me: 1) Did You open Performance Report manually ? (Or use some automatization scripts) 2) How you generate your report before use this post build step? 3) Could you recheck whick plugins version you use 4) Can you share your config of this post build step? Thanks, Artem 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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Michael Neale commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs Stephen Connolly Vivek Pandey I think open/save from classic is a perfectly fine work around for blue users. If blueis patched so new created pipelines are saved correctly, I still think it is ok to apply that fix/work around of open and save for older pipelines. Whilst this issue was flagged originally by Tyler with codevalet and blue ocean creation, it seems most comments are from jobDSL users (who I think can fix it in the scripts?). So perhaps all that is needed is for blue ocean to do the right thing for new pipelines (older ones can be worked around), and perhaps some warning for jobDSL users that they need to set an id? Also - nice sleuthing! this is a tricky one. 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-49617) P4 task being blocked
Title: Message Title Robert Squire created an issue Jenkins / JENKINS-49617 P4 task being blocked Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-02-19 08:53 Environment: Jenkins 2.46.3 p4 plugin 1.8.4 Priority: Blocker Reporter: Robert Squire When we have jobs queued for a slave and the slave bcomes free we may hvae jobs 1-5 queued if jenkins starts to run job 2 whilst 1 is queued it will start but gets to the P4 task save changes then goes no further it does not timeout or stop but blocks the slave. To unblocj it we have to kill the quesued job 1 and then 2 will continue to run correctly. As we have a large number of tests to run this is causing us major problems and we are losing test data as w have to kill testsuite runs to get some results through. Example of the log below 08:13:14 P4 Task: syncing files at change: 373809 08:13:14 ... p4 sync -parallel=threads=4,min=1,minsize=1024 -q c:\jenkins2\workspace_atf_atf__ + 08:13:14 duration: (73ms) 08:13:14 08:13:14 P4 Task: saving built changes. 08:42:48 No previous build found... 08:42:48 ... p4 client o jenkins-TEST-gb-mlb-dt-011-SIT_atf_atf-int-mlb-MAT2-tester-L1PHY_LAR__ + 08:42:48 ... p4 info + 08:42:48 ... done At 08.42 I aborted the previous queued job
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Michael Neale edited a comment on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs [~stephenconnolly] [~vivek] I think open/save from classic is a perfectly fine work around for blue users. If blueis blue is patched so *new* created pipelines are saved correctly, I still think it is ok to apply that fix/work around of open and save for *older* pipelines. Whilst this issue was flagged originally by Tyler with codevalet and blue ocean creation, it seems most comments are from jobDSL users (who I think can fix it in the scripts?). So perhaps all that is needed is for blue ocean to do the right thing for new pipelines (older ones can be worked around), and perhaps some warning for jobDSL users that they need to set an id? Also - nice sleuthing! this is a tricky one. 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-49211) Build gets stuck on Publish Over CIFS
Title: Message Title Tobias Getrost commented on JENKINS-49211 Re: Build gets stuck on Publish Over CIFS Hi, the reason for #2 is that the constructor of CifsHostConfiguration has an additional argument bufferSize which is of primitive type int. 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-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-39664 Docker builds do not work with Kubernetes Pipeline plugin Change By: Carlos Sanchez Component/s: docker-workflow-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-49022) Performance plugin. Allow choosing percentiles to track
Title: Message Title Artem Fedorov commented on JENKINS-49022 Re: Performance plugin. Allow choosing percentiles to track I think we're fixed these errors in this release. Maybe you use snapshot that attached to this issue? Can you reinstall this plugins from jenkins marketplace? or download http://updates.jenkins-ci.org/download/plugins/performance/ http://jenkinsci.github.io/performance-plugin/Changelog.html Thanks, Artem 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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title Michael Neale commented on JENKINS-49610 Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned On talking with stephen - the short term more urgent thing is to fix up blue ocean https://issues.jenkins-ci.org/browse/JENKINS-48571 first - get that out. Then can look at this to warn/error out for jobdsl/future users. 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-49110) withSonarQubeEnv in Jenkins pipeline not setting SonarQube env whe using Kubernetes
Title: Message Title Carlos Sanchez commented on JENKINS-49110 Re: withSonarQubeEnv in Jenkins pipeline not setting SonarQube env whe using Kubernetes this is probably the same issue as JENKINS-49370, adding the steps inside container will not work, but adding them outside will 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-49370) Environment variables cannot be set within the container step
Title: Message Title Carlos Sanchez commented on JENKINS-49370 Re: Environment variables cannot be set within the container step looks like it affects any step that sets env vars, see JENKINS-49110 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-49460) Connection error via PTC integrity plugin
Title: Message Title Saad Azam resolved as Fixed Article - CS186156 did the trick. Jenkins / JENKINS-49460 Connection error via PTC integrity plugin Change By: Saad Azam Status: Open 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-49460) Connection error via PTC integrity plugin
Title: Message Title Saad Azam edited a comment on JENKINS-49460 Re: Connection error via PTC integrity plugin Article - CS186156 did the trick. # Install Jenkins as a service - Review [Jenkins|https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin] Installation Preparations section # Use SSL Connections (Jenkins) - During the install of Jenkins on the *Step: 2 Valudate Successful Plug-in Installation*, enter the appropriate information for: * Default Integration Point Server Hostname: * If using server integration, *use Integrity server hostname* * If using client side integration, *use client hostname* * Default Integration Point Server Port: * If using server integration, *use Integrity server port* * If using client side integration, *leave port at 0* * Use Secure Connections? *Check the box* # Enable API Connections on Integrity server - KB [119722|https://support.ptc.com/images/cs/articles/2014/10/09141517_ajr0.jar] # Replace Jenkins mksapi.jar file with an Integrity 10.5 jar file * Download and install *Integrity Client 10.5* * Once installed, navigate to the \lib directory and locate the *mksapi.jar* file * Replace *Jenkins mksapi.jar* file in the \plugins\integrity-plugin\WEB-INF\lib\ directory # Replace commons-httpclient 2.0.2 with the commons-httpclient 3.01: * Backup *commons-httpclient-2.0.2.jar* in *\war\WEB-INF\lib and remove from directory* * Replace the commons-httpclient-2.0.2.jar file with *commons-httpclient-3.0.1.jar* file (Download file [here|https://support.ptc.com/images/cs/articles/2014/10/09141517_ajr0.jar]) * Make the replaced file *read-only* * *Note*: This file must be replaced if Jenkins was upgraded and the integration no longer works # Jenkins *must* use the same JVM version as the Integrity server * Recommended workaround is to install the *same* *version* of the Integrity client * Once the Integrity client is installed, navigate to the Jenkins install directory and edit the Jenkins.xml file * Change the java line to point to the Integrity client Java file: * Eg: *Integrity_Client_Install_Directory\jre\bin\java.exe* # Restart Jenkins service and log in via Web UI - *[http://localhost:8080|http://localhost:8080/]* # Initiate your build Add Comment
[JIRA] (JENKINS-49460) Connection error via PTC integrity plugin
Title: Message Title Saad Azam edited a comment on JENKINS-49460 Re: Connection error via PTC integrity plugin Article - CS186156 did the trick . # Install Jenkins as a service - Review [Jenkins|https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin] Installation Preparations section # Use SSL Connections (Jenkins) - During the install of Jenkins on the *Step: 2 Valudate Successful Plug-in Installation*, enter the appropriate information for: * Default Integration Point Server Hostname: * If using server integration, *use Integrity server hostname* * If using client side integration, *use client hostname* * Default Integration Point Server Port: * If using server integration, *use Integrity server port* * If using client side integration, *leave port at 0* * Use Secure Connections? *Check the box* # Enable API Connections on Integrity server - KB [119722|https://support.ptc.com/images/cs/articles/2014/10/09141517_ajr0.jar] # Replace Jenkins mksapi.jar file with an Integrity 10.5 jar file * Download and install *Integrity Client 10.5* * Once installed, navigate to the \lib directory and locate the *mksapi.jar* file * Replace *Jenkins mksapi.jar* file in the \plugins\integrity-plugin\WEB-INF\lib\ directory # Replace commons-httpclient 2.0.2 with the commons-httpclient 3.01: * Backup *commons-httpclient-2.0.2.jar* in *\war\WEB-INF\lib and remove from directory* * Replace the commons-httpclient-2.0.2.jar file with *commons-httpclient-3.0.1.jar* file (Download file [here|https://support.ptc.com/images/cs/articles/2014/10/09141517_ajr0.jar]) * Make the replaced file *read-only* * *Note*: This file must be replaced if Jenkins was upgraded and the integration no longer works # Jenkins *must* use the same JVM version as the Integrity server * Recommended workaround is to install the *same* *version* of the Integrity client * Once the Integrity client is installed, navigate to the Jenkins install directory and edit the Jenkins.xml file * Change the java line to point to the Integrity client Java file: * Eg: *Integrity_Client_Install_Directory\jre\bin\java.exe* # Restart Jenkins service and log in via Web UI - *[http://localhost:8080|http://localhost:8080/]* # Initiate your build Add Comment
[JIRA] (JENKINS-49460) Connection error via PTC integrity plugin
Title: Message Title Saad Azam edited a comment on JENKINS-49460 Re: Connection error via PTC integrity plugin Article - CS186156 did the trick # Install Jenkins as a service - Review [Jenkins|https://wiki.jenkins-ci.org/display/JENKINS/PTC+Integrity+Plugin] Installation Preparations section # Use SSL Connections (Jenkins) - During the install of Jenkins on the *Step: 2 Valudate Successful Plug-in Installation*, enter the appropriate information for: * Default Integration Point Server Hostname: * If using server integration, *use Integrity server hostname* * If using client side integration, *use client hostname* * Default Integration Point Server Port: * If using server integration, *use Integrity server port* * If using client side integration, *leave port at 0* * Use Secure Connections? *Check the box* # Enable API Connections on Integrity server - KB [119722|https://support.ptc.com/images/cs/articles/2014/10/09141517_ajr0.jar] # Replace Jenkins mksapi.jar file with an Integrity 10.5 jar file * Download and install *Integrity Client 10.5* * Once installed, navigate to the \lib directory and locate the *mksapi.jar* file * Replace *Jenkins mksapi.jar* file in the \plugins\integrity-plugin\WEB-INF\lib\ directory # Replace commons-httpclient 2.0.2 with the commons-httpclient 3.01: * Backup *commons-httpclient-2.0.2.jar* in *\war\WEB-INF\lib and remove from directory* * Replace the commons-httpclient-2.0.2.jar file with *commons-httpclient-3.0.1.jar* file (Download file [here|https://support.ptc.com/images/cs/articles/2014/10/09141517_ajr0.jar]) * Make the replaced file *read-only* * *Note*: This file must be replaced if Jenkins was upgraded and the integration no longer works # Jenkins *must* use the same JVM version as the Integrity server * Recommended workaround is to install the *same* *version* of the Integrity client * Once the Integrity client is installed, navigate to the Jenkins install directory and edit the Jenkins.xml file * Change the java line to point to the Integrity client Java file: * Eg: *Integrity_Client_Install_Directory\jre\bin\java.exe* # Restart Jenkins service and log in via Web UI - *[http://localhost:8080|http://localhost:8080/]* # Initiate your build Add Comment
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title Oleg Nenashev commented on JENKINS-49596 Re: User session memory leak Ivan Fernandez Calvo olamy I would like to highlight that the integrated pull request is not backportable. So it won't get into 2.107.x unless we prepare a separate patch-release for that. My proposal would be to... 1) Create a separate branch and backport the issue fix to the Winstone baseline with old Jetty 2) Release that version and integrate it into the next weekly. Mark this issue for backporting 3) After that release the current master baseline and integrate it into a later weekly release. 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-49616) Estimated time remaining NA
Title: Message Title Oleg Nenashev commented on JENKINS-49616 Re: Estimated time remaining NA Please provide more info about the issue: Job types you use, UI screenshots, etc. 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-39880) Jenkins agents should offer better Diagnostics remote operation failures due to JDK-8017777
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-39880 Jenkins agents should offer better Diagnostics remote operation failures due to JDK-801 Change By: Oleg Nenashev Labels: newbie-friendly 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-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-39289 Better diagnostics on "Backing channel is disconnected" Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi 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-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" Jan Duris why have you reopened it? Could you please clarify the status? 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-49263) Determine minimal useful test case for running ATH for Jenkins Core
Title: Message Title Raul Arabaolaza updated JENKINS-49263 No comments against using the SmokeTest so closing this now Jenkins / JENKINS-49263 Determine minimal useful test case for running ATH for Jenkins Core Change By: Raul Arabaolaza Status: In Review Resolved 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 more options,
[JIRA] (JENKINS-34322) Graceful error reporting if build agent runs unsupported version of Java
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34322 Graceful error reporting if build agent runs unsupported version of Java Change By: Oleg Nenashev Labels: newbie-friendly 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-17115) In a master/slave environment, the "Workspace" display should make it clear which workspace is being displayed
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-17115 In a master/slave environment, the "Workspace" display should make it clear which workspace is being displayed Change By: Oleg Nenashev Assignee: OHTAKE Tomohiro 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-17115) In a master/slave environment, the "Workspace" display should make it clear which workspace is being displayed
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-17115 In a master/slave environment, the "Workspace" display should make it clear which workspace is being displayed Change By: Oleg Nenashev Component/s: core Component/s: remoting 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-7165) Execute a command on master to launch JNLP on slave
Title: Message Title Oleg Nenashev commented on JENKINS-7165 Re: Execute a command on master to launch JNLP on slave Nothing related to remoting. Command Launcher plugin is the place to fix that if there is anything left to be 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 more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7165) Execute a command on master to launch JNLP on slave
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-7165 Execute a command on master to launch JNLP on slave Change By: Oleg Nenashev Assignee: Jesse Glick 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-7165) Execute a command on master to launch JNLP on slave
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-7165 Execute a command on master to launch JNLP on slave Change By: Oleg Nenashev Component/s: command-launcher-plugin Component/s: remoting 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-6722) Show slave error status on Dashboard
Title: Message Title Oleg Nenashev commented on JENKINS-6722 Re: Show slave error status on Dashboard Still actual in 2018 AFAICT 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-6722) Show slave error status on Dashboard
Title: Message Title Oleg Nenashev commented on JENKINS-6722 Re: Show slave error status on Dashboard Somebody could take this patch and to try integrating a version of it into the modern Jenkins core 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-6722) Show slave error status on Dashboard
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-6722 Show slave error status on Dashboard Change By: Oleg Nenashev Component/s: core 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-49596) User session memory leak
Title: Message Title olamy commented on JENKINS-49596 Re: User session memory leak a bit conservative... but fair enough I can do that 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-5793) Would like the ability to exclude hosts from auto labelling
Title: Message Title Oleg Nenashev resolved as Incomplete Closing as incomplete. No response to the last comment in 2010, no need to keep it after 8 years. I also do not understand what was the request Jenkins / JENKINS-5793 Would like the ability to exclude hosts from auto labelling Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete 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 e
[JIRA] (JENKINS-43875) Cleanup following SECURITY-429
Title: Message Title Oleg Nenashev resolved as Fixed It has been fixed by JEP-200 (JENKINS-47736) in Jenkins 2.102 Jenkins / JENKINS-43875 Cleanup following SECURITY-429 Change By: Oleg Nenashev Status: Open 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-47134) Allow SSH connectivity check before marking agent online
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47134 Allow SSH connectivity check before marking agent online Change By: Oleg Nenashev Component/s: ssh-slaves-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-47132) Log strings not resolved
Title: Message Title Oleg Nenashev updated JENKINS-47132 Fixed in Remoting 3.13 Jenkins / JENKINS-47132 Log strings not resolved Change By: Oleg Nenashev 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-48810) How to disable hudson.remoting.RemoteInvocationHandler$Unexporter reportStats?
Title: Message Title Oleg Nenashev resolved as Done Jenkins / JENKINS-48810 How to disable hudson.remoting.RemoteInvocationHandler$Unexporter reportStats? Change By: Oleg Nenashev Status: Open Resolved 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 more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49618) Display Remoting version in the agent log when starting up the agent
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-49618 Display Remoting version in the agent log when starting up the agent Issue Type: Improvement Assignee: Unassigned Components: remoting Created: 2018-02-19 10:27 Labels: newbie-friendly Priority: Minor Reporter: Oleg Nenashev Currently Remoting agents do not print their versions to logs on the startup. Although there are plugins showing that on the Jenkins side (Version Column plugin, Support Core plugin), it would be still useful to print the version when the agent starts. Acceptance criteria: Agent version is printed when the agent is connected to the master from CLI Agent version is printed when the connection is established over SSH (e.g. by SSH Slaves plugin) Agent version is printed when the agent is launched over Java Web Start In order to address these requirement, it is generally required to add log messaging in a generic Remoting class like Engine.
[JIRA] (JENKINS-49619) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title Yannick Lehmann created an issue Jenkins / JENKINS-49619 Team Foundation Sercer plugin error: workspace is already mapped Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin, tfs-plugin Created: 2018-02-19 10:30 Environment: Jenkins 2.89.3 TFS-plugin 5.126.0 matrix-plugin 1.12 Priority: Major Reporter: Yannick Lehmann 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-49619) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49619 Team Foundation Sercer plugin error: workspace is already mapped Change By: Oleg Nenashev Component/s: matrix-project-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-49619) Team Foundation Sercer plugin error: workspace is already mapped
Title: Message Title Oleg Nenashev assigned an issue to redsolo Jenkins / JENKINS-49619 Team Foundation Sercer plugin error: workspace is already mapped Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi redsolo 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 Oleg Nenashev commented on JENKINS-49619 Re: Team Foundation Sercer plugin error: workspace is already mapped Nothing to do ion the Matrix Project side from what I see. I had issues with that in 2012 and worked around by using custom workspace names, but generally the plugin should have logic to prevent that 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-49596) User session memory leak
Title: Message Title Oleg Nenashev commented on JENKINS-49596 Re: User session memory leak Well, 2.107.1 is already on the crashlanding course due to JEP-200. I do not want to add more risks like fresh Jetty release there. Thanks for doing that! I am happy to share the release legwork if needed 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-49620) Anchore report exception
Title: Message Title
Zoltan Medovarszky created an issue
Jenkins / JENKINS-49620
Anchore report exception
Issue Type:
Bug
Assignee:
Daniel Nurmi
Components:
anchore-container-scanner-plugin
Created:
2018-02-19 10:41
Environment:
Jenkins LTS ver. 2.89.4, ubuntu:16.04 Anchore version 1.0.13
Priority:
Major
Reporter:
Zoltan Medovarszky
After upgrade of Jenkins LTS to 2.89.4 the existing Anchore reports cannot be opened with exception: org.apache.commons.jelly.JellyTagException: jar:file:/opt/data/jenkins/var/lib/jenkins/plugins/anchore-container-scanner/WEB-INF/lib/anchore-container-scanner.jar!/com/anchore/jenkins/plugins/anchore/AnchoreAction/index.jelly:43:64: 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.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.TagSupport.invokeBody(TagSupport.java:161)}} {{ at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)}} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)}} {{ at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)}} {{ at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)}} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)}}
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title olamy commented on JENKINS-49596 Re: User session memory leak well I'm doing more check before releasing anything. Do you have the issue without using javamelody? 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-47897) Blue Ocean pipeline view shows stages and steps from previous build, until given step starts
Title: Message Title John Hus commented on JENKINS-47897 Re: Blue Ocean pipeline view shows stages and steps from previous build, until given step starts Greg Dubicki Is there a way to clean the predefined steps? like a parameter / function in the script to clean the view of the previous run? 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-47897) Blue Ocean pipeline view shows stages and steps from previous build, until given step starts
Title: Message Title John Hus edited a comment on JENKINS-47897 Re: Blue Ocean pipeline view shows stages and steps from previous build, until given step starts [~ grzegorz_dubicki jamesdumay ] Is there a way to clean the predefined steps? like a parameter / function in the script to clean the view of the previous run? 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-49621) Script approvals require a reboot to take effect
Title: Message Title
pjdarton created an issue
Jenkins / JENKINS-49621
Script approvals require a reboot to take effect
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
script-security-plugin
Created:
2018-02-19 11:02
Environment:
Jenkins 2.89.2 Script Security Plugin 1.39 and 1.41 Pipeline build calling methods that are not whitelisted by default.
Priority:
Major
Reporter:
pjdarton
TL;DR: It appears that pressing the "Approve" button on the .../scriptApproval/ WebUI has no effect until after Jenkins has been restarted. Full story: I defined a pipeline build that contained the code: final snapshotPropertiesReader = new java.io.StringReader(snapshotPropertiesAsString) final snapshotProperties = new Properties() snapshotProperties.load(snapshotPropertiesReader) discoHostedSnapshotName = snapshotProperties.getProperty('productUnderTest.SNAPSHOT') First time I ran this pipeline code, I was using script security plugin version 1.39 and the pipeline code failed because "Scripts not permitted to use new java.util.Properties" (as one would expect). So I approved that method using the UI at http://myjenkinsserver/scriptApproval/. However, the second time I ran it, despite having "approved" the code, the pipeline code failed with exactly the same error at the same point. Taking a look at the UI at http://myjenkinsserver/scriptApproval/ , I saw that "new java.util.Properties" was in the "Signatures already approved" list, but was also listed as needing approval. That shouldn't happen - a method can't be both "already approved" and in need of approval... Pressing the "approve" button (again) made no difference to the list of "Signatures already approved" but did make the "pending approval" entry go away ... until I re-ran the build when it came back a
[JIRA] (JENKINS-49348) BlueOcean misses a button to re-run a build
Title: Message Title Jim Klimov updated an issue Jenkins / JENKINS-49348 BlueOcean misses a button to re-run a build Change By: Jim Klimov Attachment: nonpipeline-noreplay.png Attachment: nonpipeline-with-RunBtn.png Attachment: pipeline-native-replayed.png Attachment: pipeline-native-with-replayBtn.png 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
[JIRA] (JENKINS-49621) Script approvals require a reboot to take effect
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-49621 Script approvals require a reboot to take effect Change By: pjdarton Attachment: buildFailure.png Attachment: console_output.txt Attachment: pipeline.groovy Attachment: scriptApprovalUI.png 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-49622) Support Stride
Title: Message Title Vadim Kotov created an issue Jenkins / JENKINS-49622 Support Stride Issue Type: New Feature Assignee: Unassigned Components: hipchat-plugin Created: 2018-02-19 11:06 Priority: Major Reporter: Vadim Kotov I'm not sure if this is a right place for such kind of request. Since Atlassian encourages all teams to migrate to Stride (https://www.stride.com/help-center/upgrade-guide#faq-7c7613ab-1cde-44f0-81ca-2d1475c216e4), I think it's pretty important to support new API (https://developer.atlassian.com/cloud/stride/). Looks like HipChat is deprecated, after you migrate your Jenkins plugin integrations with HipChat will not work. Add Comment
[JIRA] (JENKINS-49623) Resource list stored in env variable empty when label is used in locking
Title: Message Title Janne Myllyla created an issue Jenkins / JENKINS-49623 Resource list stored in env variable empty when label is used in locking Issue Type: Bug Assignee: Unassigned Components: lockable-resources-plugin Created: 2018-02-19 11:08 Environment: Jenkins 2.89.4 Lockable resources 2.1 Priority: Minor Reporter: Janne Myllyla When using lock from jenkinsfile and using label, then the list stored to env variable is empty. Lock seemed to work, but in my use case I need to have access to the fields of locked resource. Unfortunately there does not seem to be any easy way to access locked resources name and details, except via the env variable. I tried locking with resources name and then list was populated properly, but this is not an option when the lock is used to monitor access to multiple resources of same type and there is a need to have the name and details field of the resource. Add Comment
[JIRA] (JENKINS-49348) BlueOcean misses a button to re-run a build
Title: Message Title Jim Klimov commented on JENKINS-49348 Re: BlueOcean misses a button to re-run a build I've attached a few screenshots nonpipeline-noreplay.png - a freestyle job sports no "replay/rerun" button in the build results at all nonpipeline-with-RunBtn.png - history of that freestyle job does have a big Run button, which yields a popup that this job has inputs not supported by BO but that I can continue into Classic Interface to fill out the Build arguments form - which I do happily pipeline-native-with-replayBtn.png - this one for a job made "natively" via Jenkinsfile pipeline scripts (Organization => MultiBranch Pipeline => PR and branch jobs) has the curly-arrow button hinted as "Rerun", but actually does a pipeline replay according to the message (in particular, it does not ask for Build arguments) pipeline-native-replayed.png - history of those native pipeline jobs, the completed ones also have a "Rerun" button with a no-questions-asked "Replay" action 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 opti
[JIRA] (JENKINS-49348) BlueOcean misses a button to re-run a build
Title: Message Title Jim Klimov edited a comment on JENKINS-49348 Re: BlueOcean misses a button to re-run a build I've now attached a few screenshots :)* nonpipeline-noreplay.png - a freestyle job sports no "replay/rerun" button in the build results at all* nonpipeline-with-RunBtn.png - history of that freestyle job does have a big Run button, which yields a popup that this job has inputs not supported by BO but that I can continue into Classic Interface to fill out the Build arguments form - which I do happily ;)* pipeline-native-with-replayBtn.png - this one for a job made "natively" via Jenkinsfile pipeline scripts (Organization => MultiBranch Pipeline => PR and branch jobs) has the curly-arrow button hinted as "Rerun", but actually does a pipeline replay according to the message (in particular, it does not ask for Build arguments)* pipeline-native-replayed.png - history of those native pipeline jobs, the completed ones also have a "Rerun" button with a no-questions-asked "Replay" action 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright assigned an issue to Chisel Wright Jenkins / JENKINS-49278 cat command in docker agents not detected correctly Change By: Chisel Wright Assignee: Nicolas De Loof Chisel Wright 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright assigned an issue to Unassigned Jenkins / JENKINS-49278 cat command in docker agents not detected correctly Change By: Chisel Wright Assignee: Chisel Wright 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright assigned an issue to Nicolas De Loof Jenkins / JENKINS-49278 cat command in docker agents not detected correctly Change By: Chisel Wright Assignee: Nicolas De Loof 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright commented on JENKINS-49278 Re: cat command in docker agents not detected correctly I was about to type a comment, and weird things happened with focus and Jenkins shortcuts; I ended up (accidentally) assigning this to myself - apologies for that. I've set to "Unassigned". 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright commented on JENKINS-49278 Re: cat command in docker agents not detected correctly We're (still) seeing failures after updating to 1.15.1: $ docker run -t -d -u 497:495 -w /tmp/jenkins-prime/agent/workspace/er-G2PEKDXUWD77U -v /tmp/jenkins-prime/agent/workspace/er-G2PEKDXUWD77U:/tmp/jenkins-prime/agent/workspace/er-G2PEKDXUWD77U:rw,z -v /tmp/jenkins-prime/agent/workspace/er-G2PEKDXUWD77U@tmp:/tmp/jenkins-prime/agent/workspace/er-G2PEKDXUWD77U@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e docker.endpoint/servicectl:9.6.0 cat $ docker top b6170c275fb28d292a179ecec4d40c2452091b44074360dec0280ba08f65c3dc -eo pid,comm ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Title: Message Title TraceTronic GmbH commented on JENKINS-26313 Re: Workflow script fails if CPS-transformed methods are called from constructors Is there any news on this problem? We are encountering the same CpsCallableInvocation message when calling a static method from inside a Groovy class constructor. 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-47641) FAILURE during Repository Connector build step
Title: Message Title sivakumari peddireddy commented on JENKINS-47641 Re: FAILURE during Repository Connector build step Hi Jae Gangemi, I am facing similar issue, can you please provide solution , what needs to be done to work 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-49348) BlueOcean misses a button to re-run a build
Title: Message Title Jim Klimov edited a comment on JENKINS-49348 Re: BlueOcean misses a button to re-run a build I've now attached a few screenshots :)* nonpipeline-noreplay.png - a freestyle job sports no "replay/rerun" button in the build results at all* nonpipeline-with-RunBtn.png - history of that freestyle job does have a big Run button, which yields a popup that this job has inputs not supported by BO but that I can continue into Classic Interface to fill out the Build arguments form - which I do happily ;)* pipeline-native-with-replayBtn.png - this one for a job made "natively" via Jenkinsfile pipeline scripts (Organization => MultiBranch Pipeline => PR and branch jobs) has the curly-arrow button hinted as "Rerun", but actually does a pipeline replay according to the message (in particular, it does not ask for Build arguments)* pipeline-native-replayed.png - history of those native pipeline jobs, the completed ones also have a "Rerun" button with a no-questions-asked "Replay" action The "native" Jenkinsfile pipeline script in examples above is https://github.com/42ity/tntnet/blob/558f33b48569998fc82f3c38065c6141254b66fd/Jenkinsfile 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-47641) FAILURE during Repository Connector build step
Title: Message Title sivakumari peddireddy assigned an issue to Jae Gangemi Jenkins / JENKINS-47641 FAILURE during Repository Connector build step Change By: sivakumari peddireddy Assignee: Jae Gangemi 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-49368) Last Changes causes the JENKINS-45892
Title: Message Title Emil Wypych commented on JENKINS-49368 Re: Last Changes causes the JENKINS-45892 Rafael Pestano , could you please update me on the status of this issue? 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-43556) Stage View shows incorrect build result
Title: Message Title Russell Gallop edited a comment on JENKINS-43556 Re: Stage View shows incorrect build result I also see this with jenkins 2.73.3, pipeline stage view 2.9 and pipeline rest api plugin 2.9.Build history view on the left shows success, stage view shows the whole row in red with no cell highlighted in stripey red.The normal api for the build: //api/python?pretty=true says "result": "SUCCESS"The wfapi: /wfapi/ run runs shows as having "status": "FAILED" . All stages within that report "SUCCESS".The pipeline steps view shows SUCCESS for every step so it seems like a problem with the overall status from the wfapi. 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-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title Jim Klimov updated an issue Jenkins / JENKINS-49347 BlueOcean unusably slow, maybe related to having a lot of builds stored in history Change By: Jim Klimov Attachment: pipeline-BO-loadtimes-console.png Attachment: pipeline-BO-loadtimes.7z Attachment: pipeline-BO-loadtimes.png 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-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title Jim Klimov commented on JENKINS-49347 Re: BlueOcean unusably slow, maybe related to having a lot of builds stored in history Added HAR and respective screenshots (console is rather empty and uninteresting, but load times are spectacular). 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-49368) Last Changes causes the JENKINS-45892
Title: Message Title Rafael Pestano commented on JENKINS-49368 Re: Last Changes causes the JENKINS-45892 Hi Emil, thank you for all the details. I'm working on another issue (SECURITY-308) and as soon I fix It In will look into this one. 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-49368) Last Changes causes the JENKINS-45892
Title: Message Title Rafael Pestano edited a comment on JENKINS-49368 Re: Last Changes causes the JENKINS-45892 Hi Emil, thank you for all the details.I'm working on another issue (SECURITY-308) and as soon I fix It In got it fixed I will look into this one. 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-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)
Title: Message Title mike cirioli commented on JENKINS-49588 Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035) I will test this out later today 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-40667) Support of Rundeck usage in Pipeline script
Title: Message Title Martin Ra commented on JENKINS-40667 Re: Support of Rundeck usage in Pipeline script Awesome, thanks! 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-49622) Support Stride
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49622 Support Stride Change By: Oleg Nenashev Component/s: plugin-proposals 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-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title Jim Klimov updated an issue Jenkins / JENKINS-49347 BlueOcean unusably slow, maybe related to having a lot of builds stored in history Change By: Jim Klimov Attachment: support_2018-02-19_12.57.04.zip 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-49622) Support Stride
Title: Message Title Oleg Nenashev commented on JENKINS-49622 Re: Support Stride Related thread: https://community.atlassian.com/t5/Stride-questions/Stride-integration-with-Nagios-and-Jenkins/qaq-p/686104 I doubt that Atlassian has plans to work on Stride plugin for Jenkins, but maybe I am wrong. 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-49624) Can’t select SVN credentials for shared library in folder using Modern SCM
Title: Message Title Andy Neebel created an issue Jenkins / JENKINS-49624 Can’t select SVN credentials for shared library in folder using Modern SCM Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 2018-02-19 13:21 Environment: Jenkins 2.73.3 Subversion plug-in 2.8+ Priority: Minor Reporter: Andy Neebel When setting up a shared library on a folder, can’t pick credentials if Modern SCM is used. All of our credentials are scoped to specific domains, the drop-down box never populates. Add Comment
[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis created an issue Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Issue Type: Bug Assignee: Unassigned Components: core, maven-plugin Created: 2018-02-19 13:29 Priority: Blocker Reporter: Christoph Dreis Hi, we did an upgrade from 2.103 to 2.108 today. After the update we noticed that some xUnit related jobs were failing. So we went ahead and tried to open the job configurations page and failed. We were and are unable to open job configuration pages. This seems to "only" affect Maven jobs for us, but we see no error logs or anything else that would give us a hint what the root cause of this error is. I already tried creating a fresh job, but this doesn't work as well. Any help is highly appreciated as this is basically blocking any work with Jenkins at the moment. Cheers, Christoph Add Comment
[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis updated an issue Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Change By: Christoph Dreis Environment: Jenkins 2.108 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis updated an issue Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Change By: Christoph Dreis Hi,we did an upgrade from 2.103 to 2.108 today. After the update we noticed that some xUnit related jobs were failing.So we went ahead and tried to open the job configurations page and failed. We were and are unable to open job configuration pages. This seems to "only" affect Maven jobs for us, but we see no error logs or anything else that would give us a hint what the root cause of this error is.I already tried creating a fresh job, but this doesn't work as well. Any help is highly appreciated as this is basically blocking any work with Jenkins at the moment. It would also help if you could clarify if the xUnit step problem might be related or not. Cheers,Christoph 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
[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title Jim Klimov edited a comment on JENKINS-49347 Re: BlueOcean unusably slow, maybe related to having a lot of builds stored in history Added HAR and respective screenshots (console is rather empty and uninteresting, but load times are spectacular). UPDATE: Added somewhat redacted support data.Statistics-wise, at the moment there are about 40k builds stored in history (and yes, much of the time spent in rendering BO can be Java walking the filesystem to find and parse all that build data):[root@jenkins2 jenkins/jobs]# sync; echo 3 > /proc/sys/vm/drop_caches[root@jenkins2 jenkins/jobs]# find . -name build.xml | wc -l39847real12m40.689suser0m12.259ssys 0m36.710sand 94 known "users" (many of which were auto-registered from upstream/3rd party projects' commits that were built here; about 20 actual internal users). Listing `$JENKINS_URL/view/Masters/asynchPeople/` or going into the active users and listing builds they are associated with at `$JENKINS_URL/user/myusername/builds` also takes several minutes, at least first time after a filesystem cache flush for cleaner results (and comparably long with a "dirty" cache too).The system is a KVM VM, has 4Gb RAM assigned and about 1.3Gb of that is free. I'll try bumping it to 8Gb so more FS (meta)data can be cached, at least... 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://gro
[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title
Jim Klimov edited a comment on JENKINS-49347
Re: BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Added HAR and respective screenshots (console is rather empty and uninteresting, but load times are spectacular).UPDATE: Added somewhat redacted support data.Statistics-wise, at the moment there are about 40k builds stored in history (and yes, much of the time spent in rendering BO can be Java walking the filesystem to find and parse all that build data): {noformat} [root@jenkins2 jenkins/jobs]# sync; echo 3 > /proc/sys/vm/drop_caches[root@jenkins2 jenkins/jobs]# find . -name build.xml | wc -l39847real12m40.689suser0m12.259ssys 0m36.710s {noformat} and 94 known "users" (many of which were auto-registered from upstream/3rd party projects' commits that were built here; about 20 actual internal users). Listing ` {{ $JENKINS_URL/view/Masters/asynchPeople/ ` }} or going into the active users and listing builds they are associated with at ` {{ $JENKINS_URL/user/myusername/builds ` }} also takes several minutes, at least first time after a filesystem cache flush for cleaner results (and comparably long with a "dirty" cache too).The system is a KVM VM, has 4Gb RAM assigned and about 1.3Gb of that is free. I'll try bumping it to 8Gb so more FS (meta)data can be cached, at least...
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...@google
[JIRA] (JENKINS-49626) Wrong timestamps in build timeline (twice GMT shift it seems)
Title: Message Title JF L created an issue Jenkins / JENKINS-49626 Wrong timestamps in build timeline (twice GMT shift it seems) Issue Type: Bug Assignee: Unassigned Attachments: DoubleShiftInTimeline.gif Components: other Created: 2018-02-19 14:02 Environment: Jenkins ver. 2.73.2 Priority: Minor Reporter: JF L At a GMT+1 location with time correctly shown in build history, timeline shows builds at GMT+2. Add Comment
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc stopped work on JENKINS-49592 Change By: Cyrille Le Clerc Status: In Progress Open 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-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc started work on JENKINS-49592 Change By: Cyrille Le Clerc 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-48588) Artifacts uploaded to S3 does not show up in Blue Ocean
Title: Message Title Ben Dean commented on JENKINS-48588 Re: Artifacts uploaded to S3 does not show up in Blue Ocean James Dumay, it displays them in the classic UI (although not in the same way as normal archived artifacts). The managedArtifacts option tells the step manage the artifacts in the same way normal artifacts would be managed on the Jenkins master. Here's what the documentation for that option says: When enabled, this lets Jenkins fully manage the artifacts, exactly like it does when the artifacts are published to the master. In this case, the artifacts are stored in the "jobs/[job]/[build-number]/" path in the selected bucket and prefix path. This means the following features are enabled: artifacts are finger printed and linked to the build artifacts can be downloaded directly from the build page in the S3 Artifact section artifacts are automatically deleted when the build is deleted the S3 Copy Artifact build step can be used to download artifacts from S3 automatically, helping build complex pipelines Because of that, I would expect the artifacts to show up in Blue Ocean too (either in the artifacts section or some new S3 Artifacts section like in the classic UI (although, personally I'd rather all the artifacts display in the same place, regardless of where they are archived)). This is not to dispute what you said about the extension points in Blue Ocean, but rather the idea that the S3 plugin doesn't display uploaded artifacts (because it definitely does, just not in Blue Ocean ). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title
Simon Watts created an issue
Jenkins / JENKINS-49628
Perforce "Workspace Name Format" reset to literal
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-02-19 14:46
Environment:
Jenkins 2.89.2 P4 Plugin 1.8.5 Java: 1.8.0_51-b31 (Oracle, 64-bit) Master on RedHat Enterprise Linux 6.6 x86_64. Perforce Server version: P4D/LINUX26X86_64/2017.1/1545029 (2017/08/16)
Priority:
Major
Reporter:
Simon Watts
When configuring a Pipeline project with source from Perforce, it is required to set a "Workspace Name Format" as a template which can be used to generate per-node, per-executor workspace names required by Perforce. The default value for this field is adequate and we have not felt the need to change it:
jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}
Furthermore the field requires that the value contains at least one substitution variable to be accepted. I recently noticed that our project's workspace name formats had changed to literal values such as:
jenkinsTemp-87602970-2871-43c1-9759-0b16964ffa42
Which does not match any expansion of the original name format. This change also corresponds to issues recently observed whereby de
[JIRA] (JENKINS-49627) Last Changes Plugin shows git changes only in the first directory of the multidirectory pipeline
Title: Message Title
Anastasiia Vlaskina created an issue
Jenkins / JENKINS-49627
Last Changes Plugin shows git changes only in the first directory of the multidirectory pipeline
Issue Type:
Bug
Assignee:
Rafael Pestano
Attachments:
Screenshot from 2018-02-19 15-44-34.png
Components:
last-changes-plugin
Created:
2018-02-19 14:46
Environment:
Jenkins 2.101 Last Changes Plugin 2.6
Priority:
Major
Reporter:
Anastasiia Vlaskina
I'd like to see git changes in all 3 projects PIPELINE_PROJECT, FOO_PROJECT and BAR_PROJECT under the link workspace//last-changes/. However, I see only the change in the first repo PIPELINE_PROJECT. Nevertheless, the links themselves contain right info about commits in all 3 repos. As you can see, all commit ids are different.
// Last changes from revision f566cf1 to d1e91ab published successfully!
Last changes from revision 5d837fd to 4ea9b64 published successfully!
Last changes from revision 1e840f9 to e53ecf8 published successfully!
This is my Jenkinsfile
//node(JENKINS_NODE) {
try {
stage('Checkout repos') {
echo '\n== Checking out
[JIRA] (JENKINS-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title Simon Watts updated an issue Jenkins / JENKINS-49628 Perforce "Workspace Name Format" reset to literal Change By: Simon Watts Attachment: JENKINS-49628-1.png 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-49628) Perforce "Workspace Name Format" reset to literal
Title: Message Title
Simon Watts updated an issue
Jenkins / JENKINS-49628
Perforce "Workspace Name Format" reset to literal
Change By:
Simon Watts
When configuring a Pipeline project with source from Perforce, it is required to set a _*"Workspace Name Format"*_ as a template which can be used to generate per-node, per-executor workspace names required by Perforce.The default value for this field is adequate and we have not felt the need to change it:{noformat}jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}{noformat}Furthermore the field requires that the value contains at least one substitution variable to be accepted.I recently noticed that our project's workspace name formats had changed to literal values such as:{noformat}jenkinsTemp-87602970-2871-43c1-9759-0b16964ffa42{noformat}Which does not match any expansion of the original name format.This change also corresponds to issues recently observed whereby developers have stopped getting emails on failed builds (which was previously working). In fact, even though builds are triggered by SCM changes, the associated change list is empty.We presume that this is a consequence of the Jenkins build now using the same workspace name for different build nodes and executors – I believe that Perforce frowns on such things.Having changed all projects back to the default template on Friday evening, looking again today and every project which has been rebuilt since then once again has a literal value in place of the template.*Light weight checkout?*_Since this wasn't happening before, we look for something that has changed..._The most likely candidate is that all projects were recently switched to using _"Lightweight Checkout"_ to obtain the Jenkinsfile – this capability became supported by P4 Plugin with release 1.8.4. This mechanism saves a lot (in our case) of disk space by avoiding the need for an additional workspace sync just to get the Jenkinsfile.This would also be in line with the literal workspace name appearing in project configurations not being related to the original template format.*Hypothesis*P4 Plugin light weight checkout of the Jenkins file is overwriting the workspace name template for projects with the literal workspace name used during the lightweight checkout, and rendering the project incompatible with Perforce.*Scenario*Our builds are principle C/C++ code built using a makefile, driven by a script which sets the variables as appropriate to the build host and target.Each project interacts with Perforce as follows: # A template workspace defined in Perforce. # A Jenkinsfile from Perforce in the project's home directory – using lightweight checkout. # A Jenkins extension library also held in Perforce is loaded by default. # The project sources from Perforce as defined by the template workspace.This has been the same for a while now, and the recent change of enabling lightweight checkout on the Jenkinsfile (2) seems the most likely candidate for triggering the bug. *Attached:* * Pipeline configuration with corrupted "Wo
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Christian Höltje commented on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) Under the covers, the Github Organization Folder should be tracking the repository ID (a number) instead of the name of the 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-49629) Provide Perforce environment for scripts
Title: Message Title
Simon Watts created an issue
Jenkins / JENKINS-49629
Provide Perforce environment for scripts
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-02-19 15:04
Environment:
Jenkins 2.89.2 P4 Plugin 1.8.5
Priority:
Minor
Reporter:
Simon Watts
Our Jenkins build wraps build scripts and makefiles which are also used by developers. Some scripts will use the Perforce p4 command during their invocation – for example, to determine the mapped path of a file or directory, or to extract the version number of a file for documentation purposes. Developers already have their environment set-up and will be using p4 both on the command line, from IDEs, and from within the build scripts. However the Jenkins build does not have a valid Perforce environment as required by p4, even though it the build is operating with a workspace. Please make the P4 environment that defines the workspace available to shell commands invoked from the Jenkinsfile. If necessary, via a "withEnv()" type context. Workaround I acknowledge that the P4 Plugin exports a set of variables to the environment; however these do not have the naming required by p4. Therefore I have a custom step which uses these to create P4 Config and P4 Tickets files in the root of the workspace, and exports a P4CONFIG variable. This needs to be called in each stage of the pipeline in which shell commands may invoke p4. Have I overlooked something? Is there a {{"withEnv ("p4") {...}"-}}like step already that I don't know about that will do this?
[JIRA] (JENKINS-49613) SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response
Title: Message Title Michael joye commented on JENKINS-49613 Re: SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response Ivan, Thank you very. I am still kinda new to this saml, and guild from cloudbee never said that to change that. Now that i have change that it now works 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-49613) SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response
Title: Message Title Michael joye closed an issue as Fixed Ivan, Thank you very. I am still kinda new to this saml, and guild from cloudbee never said that to change that. Now that i have change that it now works Jenkins / JENKINS-49613 SAML Plug org.pac4j.saml.exceptions.SAMLException: No valid subject assertion found in response Change By: Michael joye Status: Open Closed 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
[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Oleg Nenashev commented on JENKINS-49625 Re: Config pages of Maven jobs do no load It is not possible to say anything without startup logs 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-41051) withRegistry is not doing a "docker login"
Title: Message Title Michael Ermer commented on JENKINS-41051 Re: withRegistry is not doing a "docker login" Docker 1.17+ no longer supports ~/.dockercfg so jenkins needs to create ~/.docker/config.json from now on. https://github.com/moby/moby/commit/18c9b6c6455f116ae59cde8544413b3d7d294a5e 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers created an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-19 15:50 Environment: Centos 7 Java 8 Priority: Major Reporter: Ralph Goers I upgraded Jenkins to 2.107 yesterday and upgraded all the plugins to their latest version. After that some of our jobs can no longer be configured. The page just shows "Loading" with a blinking icon. In addition, the chrome developer tool shows hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach () at behavior.js:111 at Array.forEach () at behavior.js:107 at Array.forEach () at Object.applySubtree (behavior.js:93) at select.js:269 registerValidator @ hudson-behavior.js:424 (anonymous) @ behavior.js:111 (anonymous) @ behavior.js:107 applySubtree @ behavior.js:93 (anonymous) @ select.js:269 setTimeout (async) (anonymous) @ select.js:263 I am also seeing errors in the logs which may or may not be related. Caught exception evaluating: preloader.stateJson in /jenkins/blue/organizations/jenkins/js-modules/dashboard-ui/detail/PR-1/19/. Reason: java.lang.reflect.InvocationTargetException java.lang.NullPointerException at io.jenkins.blueocean.preload.PipelineActivityStatePreloader.getFetchData(PipelineActivityStatePreloader.java:67) at io.jenkins.blueocean.commons.RESTFetchPreloader.getStateJson(RESTFetchPreloader.java:64) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1738.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache
