[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Sebastian Götz edited a comment on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Same problem for me here using LTS 2.19.1 with MultiJob plugin 1.22.Me too asking for a release plan for 1.23Update: Downgrade to 1.21 worked for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Christoph Obexer commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I feel like the default workspace for node() should be special and should be removed as soon as the build is finished (or shortly after). NO! I don't want to git clone 700MB repositories for twice for every build! I also need to compile code on multiple slaves, then copy stuff around to other slaves and then package stuff up in installers. Local workspaces must not be modified in between. I'm pretty sure most git users would be upset about having to clone the repository for every build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38810) Deleting of builds not handled correctly in real-time
Title: Message Title John Way created an issue Jenkins / JENKINS-38810 Deleting of builds not handled correctly in real-time Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Oct/07 4:44 AM Priority: Major Reporter: John Way We have the stage view for one of our pipelines splashed up on a radiator - left unattended. The stage view automatically handles new builds gracefully by adding new lanes in real-time. However the stage view falters and gets out of sync when it comes to builds being deleted in the background. Specifically in our case, we delete/void the current/latest build under certain circumstances. That is when we notice the stage view either keeps showing the deleted build, rearrange some of the build lanes in the wrong order, or not display the correct stage names tied to the build in the first lane. Refreshing the page always corrects the stage view. Note: Our pipeline's stage names may vary from build to build - however we still experience problems when we use a static set of stage names. Add Comment
[JIRA] (JENKINS-38326) Redesign the headers hierarchy
Title: Message Title Brody Maclean updated JENKINS-38326 Jenkins / JENKINS-38326 Redesign the headers hierarchy Change By: Brody Maclean Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title
Connor Pozdolski edited a comment on JENKINS-36375
Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Had the same issue on plugin version 1.5.1, Windows Server 2012 R2 build slave.Here's a variant workaround with no external dependencies (e.g. sed). Worked on Windows Server 2012 R2.*Windows Powershell* {noformat} gci -recurse -filter "AssemblyInfo.cs" | %{ (gc $_.fullname) -replace '\?' | Set-content $_.fullname } {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title
Connor Pozdolski edited a comment on JENKINS-36375
Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Had the same issue on plugin version 1.5.1, Windows Server 2012 R2 build slave.Here's a variant workaround with no external dependencies (e.g. sed). Worked on Windows Server 2012 R2.*Windows Powershell* {{ gci -recurse -filter "AssemblyInfo.cs" | %{ (gc $_.fullname) -replace '\?' | Set-content $_.fullname } }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title
Connor Pozdolski commented on JENKINS-36375
Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Had the same issue on plugin version 1.5.1, Windows Server 2012 R2 build slave. Here's a variant workaround with no external dependencies (e.g. sed). Worked on Windows Server 2012 R2. Windows Powershell gci -recurse -filter "AssemblyInfo.cs" | % { (gc $_.fullname) -replace '\?' | Set-content $_.fullname }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title
Connor Pozdolski edited a comment on JENKINS-36375
Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Had the same issue on plugin version 1.5.1, Windows Server 2012 R2 build slave.Here's a variant workaround with no external dependencies (e.g. sed). Worked on Windows Server 2012 R2.*Windows Powershell* {{ gci -recurse -filter "AssemblyInfo.cs" | %{ (gc $_.fullname) -replace '\?' | Set-content $_.fullname } }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37667) Use ForkScanner to build DAG (ie adapt to bismuth api)
Title: Message Title Vivek Pandey updated JENKINS-37667 Jenkins / JENKINS-37667 Use ForkScanner to build DAG (ie adapt to bismuth api) Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38808) Jenkins fails to parse Maven poms with version ranges in parent elements
Title: Message Title Mark Lehky created an issue Jenkins / JENKINS-38808 Jenkins fails to parse Maven poms with version ranges in parent elements Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Oct/07 2:19 AM Priority: Minor Reporter: Mark Lehky I am running Jenkins 1.651.3, Linux, OracleJava8. From within Jenkins I installed Maven 3.3.9 "from Apache". In our poms, we are using version ranges in parent elements, as described here . In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine. If in the main build phase I specify target "clean install", the build fails with: Parsing POMs Failed to transfer Could not find artifact ::pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) ERROR: Failed to parse POMs org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact ::pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10
[JIRA] (JENKINS-38809) "rbenv build wrapper" disabled after Jenkins restart
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-38809 "rbenv build wrapper" disabled after Jenkins restart Issue Type: Bug Assignee: R. Tyler Croy Attachments: about.md Components: rbenv-plugin Created: 2016/Oct/07 2:22 AM Priority: Major Reporter: Owen Wood Issue: "rbenv build wrapper" is disabled in job after restarting Jenkins. Steps to reproduce: 1. Create a job 2. Enable "rbenv build wrapper" 3. Make changes (if you like) 4. Save job 5. Confirm changes (Check configure after saving). Config still intact 6. Restart Jenkins `JENKINS_URL/restart` 7. Check config. "rbenv build wrapper" is now disabled Jenkins === Version details --- * Version: `1.651` * Mode:WAR * Url: null * Servlet container - Specification: 3.0 - Name: `jetty/winstone-2.9` * Java - Home: `/Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home/jre` Active Plugins -- * ant:1.2 *(update available)* 'Ant Plugin' * antisamy-markup-formatter:1.1 *(update available)* 'OWASP Markup Formatter Plugin' * credentials:1.18 *(update available)* 'Credentials Plugin' * cvs:2.11 *(update available)* 'Jenkins CVS Plug-in' * external-monitor-job:1.4 *(update available)* 'External Monitor Job Type Plugin' *
[JIRA] (JENKINS-38807) Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection
Title: Message Title Greg Fraley created an issue Jenkins / JENKINS-38807 Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/07 1:56 AM Environment: Jenkins 2.7.4, Windows 7-10, Java 8 Labels: regression Priority: Critical Reporter: Greg Fraley We have a build step that runs a TestNG suite, with the command looking something like this: java -jar -Done-jar.main.class=org.testng.TestNG the-jar.jar TheTest.xml If the process is aborted in any way (manual intervention, Jenkins build timeout, etc.) OR if the slave loses connection from the master long enough to fail the build, then there is a Java process left behind. This is particularly damaging to us, as we load a DLL in the Java process, locking the file handle. If we attempt the job again, we cannot load the DLL again, meaning that all future builds will fail without manual intervention (killing the leftover process manually). It is possible to reproduce with ANY java process executed on the Windows slave. This bug seems similar to JENKINS-26048, but I did not understand from the title/description if it was the same problem or similar symptoms. Feel free to close as duplicate
[JIRA] (JENKINS-38806) Unloading of styles makes favourites look really bad
Title: Message Title Michael Neale commented on JENKINS-38806 Re: Unloading of styles makes favourites look really bad Not sure where personalization epic went to James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38806) Unloading of styles makes favourites look really bad
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38806 Unloading of styles makes favourites look really bad Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/07 1:24 AM Priority: Major Reporter: Michael Neale This has been mentioned before, but there are times when the dashboard looks quite bad briefly if/when the styles for personalisation have been unloaded and have to be reapplied. You can almost see this here: https://media.giphy.com/media/3o7TKHCeSLQY6WLp96/giphy.gif Ideally styles wouldn't be unloaded like this (but there may be other solutions). Add Comment
[JIRA] (JENKINS-38326) Redesign the headers hierarchy
Title: Message Title Brody Maclean updated JENKINS-38326 Jenkins / JENKINS-38326 Redesign the headers hierarchy Change By: Brody Maclean Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Brody Maclean updated JENKINS-37295 Jenkins / JENKINS-37295 Redesign the empty states Change By: Brody Maclean Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Alan Ranciato commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Anton Lundin - THANK YOU! I didn't catch the answer b/c I didn't think there was any way that was the actual fix... I feel dirty after doing it, but your fix works and gave me what I needed to move forward. Someday, maybe, the PRs will get accepted and we won't have to do this... Until then, THANK YOU for your assistance! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) DESIGN: Capturing of build parameters for parametrised builds
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38393 DESIGN: Capturing of build parameters for parametrised builds Change By: Michael Neale Summary: DESIGN: Capturing of build parameters for parametrised builds (Design) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds (Design)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds (Design) Change By: Michael Neale Summary: Capturing of build parameters for parametrised builds (Design) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38805) User can run parametrised pipeline
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38805 User can run parametrised pipeline Change By: Michael Neale Sprint: indian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38805) User can run parametrised pipeline
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38805 User can run parametrised pipeline Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/07 12:16 AM Priority: Major Reporter: Michael Neale Parametrised pipelines are to be supported in blue ocean. This means when a user presses run (either on a branch, dashboard favourite, or non multibranch button) it will need to immediately pop up asking for input. The run will not commence until input is captured. If user cancels it, no run starts. There is a linked design ticket for how this looks (and api) In scope: Form to dynamically render required parameters (based on api) Popup dialog Providing feedback on input (validation) and when accepted, redirect to running page for the run that has commenced Add Comment
[JIRA] (JENKINS-38677) Failure to create label in TFS
Title: Message Title Andrew Gray commented on JENKINS-38677 Re: Failure to create label in TFS I will add that this error seems to occur in this corporate environment where it will intermittently effect builds for a couple of days at a time and then I'll get a sequence of days where the problem goes away completely only to return later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38804) API(s) for capturing parameters for parametrised pipeline jobs
Title: Message Title Michael Neale commented on JENKINS-38804 Re: API(s) for capturing parameters for parametrised pipeline jobs This may be related to input capture api - or may be able to reuse some of the code Vivek Pandey to investigate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38804) API(s) for capturing parameters for parametrised pipeline jobs
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38804 API(s) for capturing parameters for parametrised pipeline jobs Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/07 12:05 AM Priority: Major Reporter: Michael Neale Parametrised jobs require input before they can start. An api needs to exist that exposes what parameters are required, and the "run pipeline" api needs to be enhanced to take these parameters. In scope: Show if a pipeline takes parameters before it can launch (this may ideally be returned in a pipeline listing/pipeline object, so that when the user presses a run button it can pop up immediately asing for input) API to show what parameters are required (and their types) Enhance run api to take parameters. Out of scope: GUI stuff
[JIRA] (JENKINS-38804) API(s) for capturing parameters for parametrised pipeline jobs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38804 API(s) for capturing parameters for parametrised pipeline jobs Change By: Michael Neale Sprint: atlantic Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35795) API(s) for acknowledging request for user input in a pipeline
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35795 API(s) for acknowledging request for user input in a pipeline Change By: Michael Neale Summary: API (s) for acknowledging request for user input in a pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38494) User can see the input form on an input step (UI)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38494 User can see the input form on an input step (UI) Change By: Michael Neale Summary: User can see the input form on an input step (UI) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38494) User can see the input form on an input step
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38494 User can see the input form on an input step Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38325) We need a logo mark for Blue Ocean
Title: Message Title Brody Maclean assigned an issue to Michael Neale Jenkins / JENKINS-38325 We need a logo mark for Blue Ocean Change By: Brody Maclean Assignee: Brody Maclean Michael Neale Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Michael Neale commented on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input (also can we keep comments on topic, I can't delete the comments/screen shot that isn't relevant) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38325) We need a logo mark for Blue Ocean
Title: Message Title Brody Maclean commented on JENKINS-38325 Re: We need a logo mark for Blue Ocean Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22539) Getting Bad AJP13 rcv packet Warnings
Title: Message Title Daniel Beck resolved as Won't Fix Jenkins / JENKINS-22539 Getting Bad AJP13 rcv packet Warnings Change By: Daniel Beck Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Brody Maclean edited a comment on JENKINS-38393 Re: Capturing of build parameters for parametrised builds Mock up of parametrised builds modal !Input Needed Modal.png|thumbnail! Zeplin Link https://zpl.io/ 2bLMX6 Z1o4pBU Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Change By: Brody Maclean Attachment: Activity Input Needed Modal.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Change By: Brody Maclean Attachment: Input Needed Modal.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Brody Maclean edited a comment on JENKINS-38393 Re: Capturing of build parameters for parametrised builds Mock up of parametrised builds modal ! Activity Input Needed Modal.png|thumbnail! Zeplin Link https://zpl.io/Z1o4pBU Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Brody Maclean assigned an issue to Michael Neale Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Change By: Brody Maclean Assignee: Brody Maclean Michael Neale Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Brody Maclean commented on JENKINS-38393 Re: Capturing of build parameters for parametrised builds Mock up of parametrised builds modal Zeplin Link https://zpl.io/2bLMX6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Change By: Brody Maclean Attachment: Input Needed Modal.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Brody Maclean commented on JENKINS-35899 Re: Form to capture user input when pipeline is waiting for user input Mockup of input needed Zeplin link https://zpl.io/20DP3w Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Brody Maclean assigned an issue to Michael Neale Jenkins / JENKINS-35899 Form to capture user input when pipeline is waiting for user input Change By: Brody Maclean Assignee: Brody Maclean Michael Neale Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35899) Form to capture user input when pipeline is waiting for user input
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-35899 Form to capture user input when pipeline is waiting for user input Change By: Brody Maclean Attachment: Input Form.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27303) integrate credentials plugin
Title: Message Title aldaris started work on JENKINS-27303 Change By: aldaris Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33214) Hipchat plugin not working with authenticating proxy
Title: Message Title aldaris resolved as Fixed This should be fixed now. Can you test the changes in your environment? I don't really have a forward proxy available to test this myself.. Jenkins / JENKINS-33214 Hipchat plugin not working with authenticating proxy Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33214) Hipchat plugin not working with authenticating proxy
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33214 Re: Hipchat plugin not working with authenticating proxy Code changed in jenkins User: Peter Major Path: src/main/java/jenkins/plugins/hipchat/HipChatService.java http://jenkins-ci.org/commit/hipchat-plugin/fb5c46ea6ae521615810ef44e99006b574297b66 Log: JENKINS-33214 Support authenticating proxies Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34918) Jenkins avatar not showing in Hipchat on web
Title: Message Title aldaris resolved as Not A Defect Not sure how could this be a fault of the plugin. Frankly I never seen an avatar for Jenkins notifications... Jenkins / JENKINS-34918 Jenkins avatar not showing in Hipchat on web Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) --
[JIRA] (JENKINS-36823) Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles
Title: Message Title Brian Holt commented on JENKINS-36823 Re: Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles It looks like someone already added the Task Role ARN functionality, but there is an upstream issue in the master POM that needs to be resolved? I'm not sure, but see https://github.com/jenkinsci/amazon-ecs-plugin/pull/32 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34934) Integrate token macro plugin
Title: Message Title aldaris commented on JENKINS-34934 Re: Integrate token macro plugin Excellent idea, thanks for letting me know that there is a plugin already for this. The supported template variables are slowly getting out of hand. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36031) hipchat-plugin ignores "No Proxy Host"
Title: Message Title aldaris resolved as Cannot Reproduce Works fine for me by carrying out the following test: Configure proxy: localhost:1234 Test that HipChat notifications fail Configure No Proxy Host setting to include: api.hipchat.com Test that HipChat notifications now work just fine I suppose this could happen if you have the proxy settings configured additionally on the JVM level or maybe at the OS level, which could override the No Proxy Host setting at Jenkins/HipChat plugin level. Jenkins / JENKINS-36031 hipchat-plugin ignores "No Proxy Host" Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Cannot Reproduce Add Comment
[JIRA] (JENKINS-38390) Timestamp background color white
Title: Message Title Daniel Kirkdorffer commented on JENKINS-38390 Re: Timestamp background color white Fixed verified. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37357) Allow messaging users
Title: Message Title aldaris commented on JENKINS-37357 Re: Allow messaging users Looks to be the same RFE as https://github.com/jenkinsci/hipchat-plugin/issues/74 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38074) No notification if build is open in browser
Title: Message Title aldaris resolved as Cannot Reproduce Works fine for me. I think it is more likely that you are not getting notifications of successful builds if they occur straight after a failed or an unstable build. For such scenarios you would need to configure the Back To Normal notification instead. Jenkins / JENKINS-38074 No notification if build is open in browser Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38803) Show an indicator if a filter is active in the API Viewer
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-38803 Show an indicator if a filter is active in the API Viewer Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Oct/06 10:13 PM Environment: Jenkins: 2.23 job-dsl: 1.51 Labels: usability Priority: Minor Reporter: Christopher Orr The API Viewer is really amazing, but someone on IRC just stumbled across a minor usability issue... They were trying to find a particular feature, and I shared a screenshot of where to find it in the API Viewer, but they could only see a few top-level items in the left-hand list: 23:53 orrc: my API Viewer is only showing a few items in its list (freeStyleJob, job, listView) 23:54 orrc Do I need to update something? (Jenkins 2.24 with up-to-date plugins) ... 00:02 orrc *facepalm* 00:03 orrc I had a filter on They must have unchecked "Filter by plugin" at some point. Since this filter is stored in a cookie, somebody could easily hide all the available methods, and later visit the API Viewer again and wonder why so many top-level items are missing. So it would be nice if there was maybe some sort of visual indicator, shown if something other than all plugins are selected.
[JIRA] (JENKINS-38758) Export and use badges/shields
Title: Message Title Michael Neale commented on JENKINS-38758 Re: Export and use badges/shields Thorsten Scherler I wonder if there is a list we could come up with of what makes sense here. Build badges is one, but I wonder if there are other uses where we actually components people can embed in HTML pages that let them build up read only dashboards (not sure how practical that embedding of things that aren't images is though) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31507) docker.build throw IOExceptions with some sources
Title: Message Title Bryan Hunt commented on JENKINS-31507 Re: docker.build throw IOExceptions with some sources I have just run into this problem. I have several projects that all use the same function to build a docker image. The one I set up a few minutes ago is throwing this same exception. The other projects seem to build fine. java.io.IOException: Cannot retrieve .Id from 'docker inspect gpuwa-docker.nvidia.com/java:8u102-1.1.0' at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:190) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:119) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38802) Use a more sensible default GC algorithm for jenkins
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-38802 Use a more sensible default GC algorithm for jenkins Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: packaging Created: 2016/Oct/06 9:34 PM Priority: Minor Reporter: Sam Van Oort Currently we run with the default Java GC algorithm (ParallelGC) - it is known that this can produce very long GC pauses when full GC cycles are run. ConcurrentMarkSweep or G1 would greatly reduce the maximum pause time and improve user experience and stability. Similar rationale to why Oracle is making G1 the default in Java 9. This is especially important for (for example) large heaps, because multi-second full GC pauses start to become frequent and painful. Add Comment
[JIRA] (JENKINS-38754) Failing test view omits important stdout/stderr information
Title: Message Title Michael Neale assigned an issue to Keith Zantow Jenkins / JENKINS-38754 Failing test view omits important stdout/stderr information Change By: Michael Neale Assignee: Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38754) Failing test view omits important stdout/stderr information
Title: Message Title Michael Neale commented on JENKINS-38754 Re: Failing test view omits important stdout/stderr information yes, this is fair enough, that stderr/out stuff should be made available, agree. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title
Pratith Kanagaraj updated an issue
Jenkins / JENKINS-38800
remoteUrls are unordered in build data JSON when multiple git repositories are configured
Change By:
Pratith Kanagaraj
When multiple Git repositories are added to the git plugin (not Multiple SCM plugin), the remoteUrls in the build data JSON are unordered (different from the order in which they were configured in the Jenkins job). This is because the remoteUrls are stored in a HashSet in BuildData.java. We can instead store them in a LinkedHashSet and preserve the order.This is needed so that we can associate the branch built, origin[x] (where x is the repository index) in lastBuiltRevision with the appropriate repository URL for which there is no provision right now when there are multiple repositories.{ quote}{ "buildsByBranchName" : {"origin/master" : {"buildNumber" : 1813,"buildResult" : null,"revision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin/master" }]}},"origin/mri" : {"buildNumber" : 50,"buildResult" : null,"revision" : {"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513","branch" : [{ "SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513", "name" : "origin/mri" }]}}},"lastBuiltRevision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin1/master" }],"remoteUrls" : ["https://github.com/repo1.git","https://github.com/repo2.git",]} ,{quote}
Add Comment
[JIRA] (JENKINS-38801) configure block can't be used in a static function from inside a publishers block.
Title: Message Title
Mike Nicholson created an issue
Jenkins / JENKINS-38801
configure block can't be used in a static function from inside a publishers block.
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2016/Oct/06 9:18 PM
Priority:
Minor
Reporter:
Mike Nicholson
When attempting to move some common code form a publishers {} block into helper methods I ran into a this error:
No signature of method: javaposse.jobdsl.dsl.helpers.publisher.PublisherContext.configure() is applicable for argument types: (StepsUtil$_valgrindPublisher_closure2$_closure4) values: [StepsUtil$_valgrindPublisher_closure2$_closure4@31f6a558]
Finished: FAILURE
It only seems to occur when I try to move the configure block to a static method that is called in the context of a publishers block. I was able to reproduce it in a simpler job using this Gist: https://gist.github.com/themikenicholson/421c83c345c6a343bbee56e7ea6c0372 Jenkins Version: 2.7.4 Job DSL version 1.51
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title Pratith Kanagaraj commented on JENKINS-38800 Re: remoteUrls are unordered in build data JSON when multiple git repositories are configured Created pull request Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title
Pratith Kanagaraj updated an issue
Jenkins / JENKINS-38800
remoteUrls are unordered in build data JSON when multiple git repositories are configured
Change By:
Pratith Kanagaraj
When multiple Git repositories are added to the git plugin (not Multiple SCM plugin), the remoteUrls in the build data JSON are unordered (different from the order in which they were configured in the Jenkins job). This is because the remoteUrls are stored in a HashSet in BuildData.java. We can instead store them in a LinkedHashSet and preserve the order.This is needed so that we can associate the branch built, origin[x] (where x is the repository index) in lastBuiltRevision with the appropriate repository URL for which there is no provision right now when there are multiple repositories.{ quote}{ "buildsByBranchName" : {"origin/master" : {"buildNumber" : 1813,"buildResult" : null,"revision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin/master" }]}},"origin/mri" : {"buildNumber" : 50,"buildResult" : null,"revision" : {"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513","branch" : [{ "SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513", "name" : "origin/mri" }]}}},"lastBuiltRevision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin1/master" }],"remoteUrls" : ["https://github.com/repo1.git","https://github.com/repo2.git",]}, {quote}
Add Comment
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title
Pratith Kanagaraj created an issue
Jenkins / JENKINS-38800
remoteUrls are unordered in build data JSON when multiple git repositories are configured
Issue Type:
Improvement
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Oct/06 8:37 PM
Environment:
Operating System: Jenkins server running on Windows 7 Enterprise SP1 (64-bit), slave node running on Ubuntu 3.13.0-85-generic (64-bit) VM launched via SSH. Java 1.8 Jenkins ver. 2.7.1, Git plugin ver. 3.0.0 Browser: Google Chrome Version 53.0.2785.116 m (64-bit)
Labels:
git-plugin remoteUrls
Priority:
Major
Reporter:
Pratith Kanagaraj
When multiple Git repositories are added to the git plugin (not Multiple SCM plugin), the remoteUrls in the build data JSON are unordered (different from the order in which they were configured in the Jenkins job). This is because the remoteUrls are stored in a HashSet in BuildData.java. We can instead store them in a LinkedHashSet and preserve the order. This is needed so that we can associate the branch built, origin[x] (where x is the repository index) in lastBuiltRevision with the appropriate repository URL for which there is no provision right now when there are multiple repositories. { "buildsByBranchName" : { "origin/master" : { "buildNumber" : 1813, "buildResult" : null, "revision" : { "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "branch" : [ { "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin/master" } ] } }, "origin/mri" : { "buildNumber" : 50, "buildResult" : null, "revision" : { "SHA1" :
[JIRA] (JENKINS-22539) Getting Bad AJP13 rcv packet Warnings
Title: Message Title Arnaud Héritier commented on JENKINS-22539 Re: Getting Bad AJP13 rcv packet Warnings As Jetty removed the AJP connector and thus we removed it in Jenkins 2.X, I think that we can close it as won't fix ? cc Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Zachary LaCelle edited a comment on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. EDIT: I misspelled the argument (disable vs disabled). Seems to work.PREVIOUS:I attempted the fix mentioned by [~ngrigoriev] (-Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1), but it doesn't seem to fix the problem.Here's the arguments given to Jenkins:/usr/bin/java -Dmail.smtp.starttls.enable=true -Dhudson.DNSMultiCast.disable=true -Dhudson.udp=-1 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --httpsPort=-1 --ajp13Port=-1Here's what my jenkins.log looks like:question: [DNSQuestion@2137451499 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@816664983 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1397021935 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@365274778 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1597387715 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2142995283 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@94356232 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@118673637 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1585153435 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@943519598 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1812730091 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1440318277 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1220146348 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@134233287 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1038834151 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@802211412 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@904112 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1234766810 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@170379198 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2106342031 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@998228220 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@163782323 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1134412540 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1672826511 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@339263853 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1631728593 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1129001243 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@575558159 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1850896725 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ]
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Zachary LaCelle commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. I attempted the fix mentioned by Nikolai Grigoriev (-Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1), but it doesn't seem to fix the problem. Here's the arguments given to Jenkins: /usr/bin/java -Dmail.smtp.starttls.enable=true -Dhudson.DNSMultiCast.disable=true -Dhudson.udp=-1 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --httpsPort=-1 --ajp13Port=-1 Here's what my jenkins.log looks like: question: [DNSQuestion@2137451499 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@816664983 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1397021935 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@365274778 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1597387715 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2142995283 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@94356232 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@118673637 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1585153435 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@943519598 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1812730091 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1440318277 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1220146348 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@134233287 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1038834151 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@802211412 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@904112 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1234766810 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@170379198 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@2106342031 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@998228220 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@163782323 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1134412540 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1672826511 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@339263853 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1631728593 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1129001243 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@575558159 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1850896725 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@618325458 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question: [DNSQuestion@1896930720 type: TYPE_IGNORE index 0, class: CLASS_UNKNOWN index 0, name: ] question:
[JIRA] (JENKINS-23784) Allow parallel class loading
Title: Message Title Jesse Glick commented on JENKINS-23784 Re: Allow parallel class loading Unfortunately it seems that Jetty’s WebAppClassLoader does not call ClassLoader.registerAsParallelCapable Fixed in bug 464442 and available as of 9.3.0. Currently we bundle 9.2.x. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title
mcrooney edited a comment on JENKINS-28386
Re: Workflow support for Copy to Slave plugin
Thanks [~jglick], that is a great work-around! It almost seems like Pipeline has this feature natively and perhaps this plugin support isn't needed? I couldn't seem to get it to stash something outside of the workspace (either by putting absolute paths or relative ../../ paths), and copy-to-slave prefers to copy things from userContent, so the work-around for me was to do something like this: {code :groovy }node('master') { sh "ln -sf $\{env.JENKINS_HOME\}/userContent ." stash includes: "userContent/foo/*", name: "master-stuff"}node('slave') { unstash 'master-stuff" sh "ls userContent/foo"}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title
mcrooney edited a comment on JENKINS-28386
Re: Workflow support for Copy to Slave plugin
Thanks [~jglick], that is a great work-around! It almost seems like Pipeline has this feature natively and perhaps this plugin support isn't needed? I couldn't seem to get it to stash something outside of the workspace (either by putting absolute paths or relative ../../ paths), and copy-to-slave prefers to copy things from userContent, so the work-around for me was to run an do something like this: { code:groovy}node('master') { sh "ln -sf $\{env.JENKINS_HOME\}/userContent ." }} first, and then you can{{ stash includes: "userContent/foo /* ", name: " master-stuff"}node('slave') { unstash 'master-stuff" sh "ls userContent/ foo" } {code }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title
mcrooney edited a comment on JENKINS-28386
Re: Workflow support for Copy to Slave plugin
Thanks [~jglick], that is a great work-around! It almost seems like Pipeline has this feature natively and perhaps this plugin support isn't needed? I couldn't seem to get it to stash something outside of the workspace (either by putting absolute paths or relative ../../ paths), and copy-to-slave prefers to copy things from userContent, so the work-around for me was to do something like this:{code}node('master') { sh "ln -sf $ \ {env.JENKINS_HOME \ }/userContent ." stash includes: "userContent/foo/*", name: "master-stuff"}node('slave') { unstash 'master-stuff" sh "ls userContent/foo"}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title
mcrooney edited a comment on JENKINS-28386
Re: Workflow support for Copy to Slave plugin
Thanks [~jglick], that is a great work-around! It almost seems like Pipeline has this feature natively and perhaps this plugin support isn't needed? I couldn't seem to get it to stash something outside of the workspace (either by putting absolute paths or relative ../../ paths), and copy-to-slave prefers to copy things from userContent, so the work-around for me was to run an{{sh "ln -sf $\{env.JENKINS_HOME\}/userContent . " }}first, and then you can{{stash includes: "userContent/foo", name: "foo"}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title
mcrooney edited a comment on JENKINS-28386
Re: Workflow support for Copy to Slave plugin
Thanks [~jglick], that is a great work-around! It almost seems like Pipeline has this feature natively and perhaps this plugin support isn't needed? I couldn't seem to get it to stash something outside of the workspace (either by putting absolute paths or relative ../../ paths), and copy-to-slave prefers to copy things from userContent, so the work-around for me was to run an {{sh "ln -sf ${env.JENKINS_HOME}/userContent .}} first , and then you can {{stash includes: "userContent/foo", name: "foo"}} :)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title
mcrooney edited a comment on JENKINS-28386
Re: Workflow support for Copy to Slave plugin
Thanks [~jglick], that is a great work-around! It almost seems like Pipeline has this feature natively and perhaps this plugin support isn't needed? I couldn't seem to get it to stash something outside of the workspace (either by putting absolute paths or relative ../../ paths), and copy-to-slave prefers to copy things from userContent, so the work-around for me was to run an{{sh "ln -sf $ \ {env.JENKINS_HOME \ }/userContent .}}first, and then you can{{stash includes: "userContent/foo", name: "foo"}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title
mcrooney commented on JENKINS-28386
Re: Workflow support for Copy to Slave plugin
Thanks Jesse Glick, that is a great work-around! It almost seems like Pipeline has this feature natively and perhaps this plugin support isn't needed? I couldn't seem to get it to stash something outside of the workspace (either by putting absolute paths or relative ../../ paths), and copy-to-slave prefers to copy things from userContent, so the work-around for me was to run an {{sh "ln -sf $ {env.JENKINS_HOME} /userContent .}} first and then you can stash includes: "userContent/foo", name: "foo"
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38799) Xcode 8 ${Version} Missing
Title: Message Title
doug lance created an issue
Jenkins / JENKINS-38799
Xcode 8 ${Version} Missing
Issue Type:
Bug
Assignee:
Unassigned
Components:
xcode-plugin
Created:
2016/Oct/06 7:55 PM
Environment:
Latest Jenkins & Xcode Plugin version as of October 6th 2016. Xcode 8.
Priority:
Major
Reporter:
doug lance
The plugin does not input the version number into archives using $ {VERSION} variable text any more. Previous versions worked as intended. Not sure if it is new plugin version issue or Xcode 8 issue. Thank you!
Add Comment
[JIRA] (JENKINS-19561) Unsafe & inefficient concurrency in XStream
Title: Message Title Jesse Glick commented on JENKINS-19561 Re: Unsafe & inefficient concurrency in XStream XStream2 could be a façade which keeps a per-thread pool of actual implementations Though this could introduce its own performance problems, if you have a lot of threads coming online and newly needing instances: initialization is not so cheap. The alternative is to not call AnnotationMapper.autodetectAnnotations, but this implies either not honoring XStream annotations (incompatible for some plugins—example), or processing them when the plugin is loaded (not practical without some way of quickly finding annotated classes without scanning every class file). Rather than a ThreadLocal it might be better to have an unbounded pool of instances. When a method is called and the pool is empty, a new instance would be created; otherwise an instance would be withdrawn from the pool. When the method completes the instance would be returned to the pool. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27284) Option to not make a build unstable under problem with the S3 pugin
Title: Message Title John Lamb commented on JENKINS-27284 Re: Option to not make a build unstable under problem with the S3 pugin This issue still exists, and is responsible for a number of false build failures that my teammates have spotted. The author of this ticket submitted a PR to address this over a year ago: https://github.com/jenkinsci/s3-plugin/pull/53 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38609) Shared libraries root to be specified in the PATH field
Title: Message Title Martin Fousek commented on JENKINS-38609 Re: Shared libraries root to be specified in the PATH field Sorry, my initial explanation wasn't likely good enough. I'm not looking for placement more Global Libraries into one repository/branch. I would like to place my Global Library files next to the common Sources of the project and in this case you don't want to mix the structure. Let's imagine following example of project repo structure: /src/org/sample/project/globals/BuildingUtils.groovy /src/org/sample/project/services/NewsService.java /src/org/sample/project/controllers/NewsController.java /src/org/sample/project/pom.xml I wanted to outline that mixing of Global Library source with the Project source is not desirable but moving the Globaly Library outside of the project's repository means that you need to handle all branches twice and do changes into two various repositories instead of straightforward change within single one (in that case you can just update pom.xml and BuildingUtils.groovy at one place, everytime together). Of couse there could be subfolder for the project MVN project but still the top-level 'src' folder will be always confusing to everybody who takes a look on the project repository. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-11046) Project deletion does not wipe out project workspaces
Title: Message Title R. Tyler Croy commented on JENKINS-11046 Re: Project deletion does not wipe out project workspaces In my opinion this is a pretty big issue for anybody with long-lived agents floating around Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38797) Resolve Jira customfields from within the parameter mapping
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-38797 Resolve Jira customfields from within the parameter mapping Change By: Wisen Tanasa Summary: Resolve Jira customefields customfields from within the parameter mapping Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19561) Unsafe & inefficient concurrency in XStream
Title: Message Title Jesse Glick commented on JENKINS-19561 Re: Unsafe & inefficient concurrency in XStream Codehaus is dead, and I cannot find a new location for XSTR-744, but mail archives can be found here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23784) Allow parallel class loading
Title: Message Title Jesse Glick commented on JENKINS-23784 Re: Allow parallel class loading A related issue I just found while looking at a thread dump from an unresponsive instance: some threads such as at hudson.util.MaskingClassLoader.getResource(MaskingClassLoader.java:80) - waiting to lock <…> (a hudson.util.MaskingClassLoader) at java.lang.ClassLoader.getResource(ClassLoader.java:1091) at jenkins.util.AntClassLoader.getResource(AntClassLoader.java:888) at org.kohsuke.stapler.ClassDescriptor$ASM.loadParametersFromAsm(ClassDescriptor.java:258) at org.kohsuke.stapler.ClassDescriptor$ASM.access$100(ClassDescriptor.java:212) at org.kohsuke.stapler.ClassDescriptor.loadParameterNames(ClassDescriptor.java:145) at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:179) at org.jenkinsci.plugins.workflow.cps.DSL.loadSoleArgumentKey(DSL.java:220) at org.jenkinsci.plugins.workflow.cps.DSL.parseArgs(DSL.java:356) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:152) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:124) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:117) at … or at hudson.util.MaskingClassLoader.loadClass(MaskingClassLoader.java:70) - waiting to lock <…> (a hudson.util.MaskingClassLoader) at java.lang.ClassLoader.loadClass(ClassLoader.java:411) - locked <…> (a hudson.ClassicPluginStrategy$DependencyClassLoader) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at jenkins.util.AntClassLoader.findBaseClass(AntClassLoader.java:1398) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1075) - locked <…> (a hudson.ClassicPluginStrategy$AntClassLoader2) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at hudson.util.XStream2$AssociatedConverterImpl.findConverter(XStream2.java:318) at hudson.util.XStream2$AssociatedConverterImpl.canConvert(XStream2.java:357) at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:59) - locked <…> (a com.thoughtworks.xstream.core.DefaultConverterLookup) at com.thoughtworks.xstream.XStream$1.lookupConverterForType(XStream.java:498) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:56) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:114) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1044) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1035) at … were blocked on one thread waiting for a lower-level lock:
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Tristan Lewis assigned an issue to bap Jenkins / JENKINS-27963 Please add support for jenkins pipeline plugin to publish-over-ssh Change By: Tristan Lewis Assignee: bap Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Tristan Lewis assigned an issue to Unassigned Jenkins / JENKINS-27963 Please add support for jenkins pipeline plugin to publish-over-ssh Change By: Tristan Lewis Assignee: Tristan Lewis Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Tristan Lewis assigned an issue to Tristan Lewis Jenkins / JENKINS-27963 Please add support for jenkins pipeline plugin to publish-over-ssh Change By: Tristan Lewis Assignee: bap Tristan Lewis Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38798) Dynamic node names for parallel branches in Jenkins pipeline
Title: Message Title
Danil Zvyagintsev updated an issue
Jenkins / JENKINS-38798
Dynamic node names for parallel branches in Jenkins pipeline
Change By:
Danil Zvyagintsev
I wonder how to accomplish dynamic node names or passing any variables to branches in general?How to pass variable nodeName into closure ? Please consider following code:{code: groovy java }def getBranches(def config){def branches = [:]for (node in config){def nodeName = node.get('node')def udid = node.get('udid')echo "node: ${nodeName}"echo "udid: ${udid}"branches[nodeName] = { node(nodeName){echo "1"echo "${udid}"}}}return branches}stage('My awesome parallel jobs stage'){node {def config = getConfig()def branches = getBranches(config)parallel branches}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-38798) Dynamic node names for parallel branches in Jenkins pipeline
Title: Message Title
Danil Zvyagintsev created an issue
Jenkins / JENKINS-38798
Dynamic node names for parallel branches in Jenkins pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline-build-step-plugin
Created:
2016/Oct/06 7:02 PM
Priority:
Minor
Reporter:
Danil Zvyagintsev
I wonder how to accomplish dynamic node names or passing any variables to branches in general? How to pass variable nodeName into closure ? Please consider following code:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
def getBranches(def config){
def branches = [:]
for (node in config){
def nodeName = node.get('node')
def udid = node.get('udid')
echo "node: ${nodeName}"
echo "udid: ${udid}"
branches[nodeName] = {
node(nodeName){
echo "1"
echo "${udid}"
}
}
}
return branches
}
stage('My awesome parallel jobs stage'){
node {
def config = getConfig()
def branches = getBranches(config)
parallel branches
}
}
[JIRA] (JENKINS-38797) Resolve Jira customefields from within the parameter mapping
Title: Message Title Chris Lambrecht created an issue Jenkins / JENKINS-38797 Resolve Jira customefields from within the parameter mapping Issue Type: New Feature Assignee: Wisen Tanasa Components: jira-trigger-plugin Created: 2016/Oct/06 6:49 PM Priority: Critical Reporter: Chris Lambrecht Presently unable to use the parameter mapping functionality of the jira-trigger-plugin to map fields on the issue attribute path to Jenkins parameters. When it is attempted, the following error message appears in the Jenkins log. org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrap.invoke Can't resolve attribute customfield_12345 from JIRA issue. Example: description, key, status.name. Read help for more information. Add Comment
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Tyrel Haveman updated an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline After seeing the effects this can cause I'm changing it to Critical. It's almost a blocker... Change By: Tyrel Haveman Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Alexander Raine commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Any further progress on this issue? I'm encountering it on some of my builds when I attempt to switch to the official Perforce plugin, as opposed to the third-party perforce plugin. I've upgraded to the latest plugin (1.4.7), and I'm on latest Jenkins (2.7.4); the target box in the failure cases is a Windows box hosted on AWS. I'm happy to share any other relevant details that could help diagnose it. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Ruud van Asseldonk commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I upgraded Jenkins from 2.22 to 2.24 today, and I simultaneously updated all plugins. After that we started seeing this issue, and it is causing all of our Python builds to fail. The issue is that Pip inside a virtualenv cannot handle long path names, because it is based on a script that uses a shebang. The length of a shebang is hard-coded in the kernel to 128 characters, which was not long enough for the workspaces that Jenkins now generates. See also https://github.com/pypa/pip/issues/1773. To try and mitigate the problem I downgraded Jenkins to 2.22 and the multibranch plugin to 2.8. This did not resolve the issue. (After downgrading more plugins, I ended up in a state of incompatible plugins, which caused the organization (of the GitHub plugin) with all repositories and branches to become corrupt in Jenkins. I had to add a new organisation which caused a rebuild of all branches of all repositories, and which reset all branch numbers. Fortunately we were using Jenkinsfiles so at least the build configuration was preserved.) At this point I still haven’t been able to revert back to our old configuration, but at least there exists a workaround for the Python/Pip issue: instead of invoking virtualenv/bin/pip, invoke virtualenv/bin/python -m pip. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38796) Classpath hashes are fragile at best
Title: Message Title Kevin Phillips created an issue Jenkins / JENKINS-38796 Classpath hashes are fragile at best Issue Type: Bug Assignee: Unassigned Components: script-security-plugin Created: 2016/Oct/06 5:07 PM Priority: Minor Reporter: Kevin Phillips Based on my brief review of the script-security-plugin source code, when a new classpath exception is added to the Jenkins master a hash is generated for the path, presumably to be able to track when changes are made to the path. Further, it appears as though the current implementation bases it's hash on the contents of the classpath folder itself (ie: file and subfolder names) rather than it's contents. For example, if a file within the classpath is modified the hash doesn't change but if a new file gets added to the classpath the hash does change. This is particularly fragile since any number of processes or operations may create files within the classpath folder, none of which have any functional impact on the jars and scripts contained therein. Here is a trivial example of a problem we just recently ran into. We have some system groovy scripts stored in Scriptler on our Jenkins master. In order for jobs to make use of those scripts we need to add the classpath to the build steps that make use of them. Further, when adding this classpath the job will only build if the path is in the approved classpath list. In one of our example cases we had logged into the Jenkins server and opened one of the groovy files therein using the 'vim' text editor. Further, when vim edits a file it creates a temporary file for storing changes within the current working folder. In so doing the temporary file causes the hash for the classpath to change (ie: new file detected in the classpath) causing all production builds that make use of those scripts to fail. To make matters worse the cause of these failures is difficult at best to diagnose. My first thought is - why do you need to store a hash of the classpath at all. Assuming only
[JIRA] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Title: Message Title Bart Bialek edited a comment on JENKINS-17386 Re: Gradle.properties ignored after 1.22 upgrade bq. Richard, I have version 1.24 installed... where is this option exposed? I can't find it. I see it now under each Job's Gradle options: "Force GRADLE_USER_HOME to use workspace". Is there a way to make this global for all Jobs? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Title: Message Title Bart Bialek commented on JENKINS-17386 Re: Gradle.properties ignored after 1.22 upgrade Richard, I have version 1.24 installed... where is this option exposed? I can't find it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather resolved as Fixed Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Coltrey Mather Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Coltrey Mather commented on JENKINS-37289 Re: authentication issue instant is too old or in the future Adjusting the max lifetime to 864000 seems to be working for now. Thank you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-4816) Allow for grepping console output
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-4816 Allow for grepping console output Change By: Daniel Beck Component/s: plugin-proposals Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Anton Lundin commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level I used devtoos in chrome to change the page. If you don't know how to do that this ain't the support forum for that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38795) global variables are not global singletons
Title: Message Title Javier Delgado created an issue Jenkins / JENKINS-38795 global variables are not global singletons Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Oct/06 3:14 PM Environment: Jenkins 2.24 cps-global-lib 2.3 Priority: Minor Reporter: Javier Delgado Similar to JENKINS-34416 (and might be another bad examples interpretation), having several global classes, an invocation from the Jenkinsfile makes a different object than a invocation from another class. Running a job with https://github.com/witokondoria/jenkins-multibranch-test as implicitly loaded global library and running the same repo Jenkinsfile, the job console output shows two different objects for invocations from Jenkinsfile:7 and closure vars.flow:24 Might be related to this, action.otherAction() cant be invoked from within the Jenkinsfile (replacing Jenkinsfile:7) Add Comment
[JIRA] (JENKINS-38794) Fix @WithPlugins annotation when uploadPlugins property is false
Title: Message Title Manuel Franco created an issue Jenkins / JENKINS-38794 Fix @WithPlugins annotation when uploadPlugins property is false Issue Type: Bug Assignee: Manuel Franco Components: acceptance-test-harness Created: 2016/Oct/06 3:07 PM Priority: Minor Reporter: Manuel Franco The @WithPlugins annotation is behaving inconsistently depending on the property uploadPlugins being set or not. When a test requires a plugin version, if uploadPlugins=false, the test will install whatever version is available, even if it's older than the required one, and then the test will most probably fail because some functionality is missing. We need to make it work the same way it does when uploadPlugins=true : it checks the available version is >= the required one, or skip the test if it is not. Add Comment
