[JIRA] (JENKINS-28222) Thread labels in console output don't persist after a node block
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28222 Re: Thread labels in console output don't persist after a node block Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/1b586ec4149faa0f68619d14e07cdf7647a2ca3f Log: JENKINS-28222 Moving getLogPrefix test to workflow-job, where this is implemented anyway. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28222) Thread labels in console output don't persist after a node block
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28222 Re: Thread labels in console output don't persist after a node block Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/b5b1ed0d06aa057666ec43d55e99e18de058740b Log: Merge pull request #54 from jglick/getLogPrefix-JENKINS-28222 JENKINS-28222 Moving getLogPrefix test to workflow-job, where this is implemented anyway Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/788eccc2cfd3...b5b1ed0d06aa 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-37877) Permission and role checks for run, re-run and stop buttons
Title: Message Title Cliff Meyers updated JENKINS-37877 Jenkins / JENKINS-37877 Permission and role checks for run, re-run and stop buttons Change By: Cliff Meyers 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-37877) Permission and role checks for run, re-run and stop buttons
Title: Message Title Cliff Meyers commented on JENKINS-37877 Re: Permission and role checks for run, re-run and stop buttons PR: https://github.com/jenkinsci/blueocean-plugin/pull/504 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-33379) Importing jobs doenst do anything since version 1.3
Title: Message Title David Gomes commented on JENKINS-33379 Re: Importing jobs doenst do anything since version 1.3 Even if Jenkins uses 8080 port i asked our Client to give access to the port 443. Is that right ? I made telnet test and port 443 is not working for communication. To work this plugin both ports 8080 and 443 should be open, right ? It is works would help me a lot, since i have to replicate about 100 jobs in my new Pipeline. Thank you in advance 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-33379) Importing jobs doenst do anything since version 1.3
Title: Message Title Werner Keil commented on JENKINS-33379 Re: Importing jobs doenst do anything since version 1.3 It also worked for me in my last project. 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-18464) Build Pipeline and Join plugin do not play nicely together
Title: Message Title John McGehee commented on JENKINS-18464 Re: Build Pipeline and Join plugin do not play nicely together After attending Jenkins World over the past two days, I think it might be better to use the new Pipeline functionality in place of the mashup of plugins that we have historically had to use. With Pipeline on the scene, I suspect that piecemeal solutions like the Build Pipeline and Join plugin will become obsolete. 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-35677) build-timeout-plugin cannot be used with pipelines (workflows)
Title: Message Title ikedam commented on JENKINS-35677 Re: build-timeout-plugin cannot be used with pipelines (workflows) Reference to switch to SimpleBuildWrapper: https://github.com/jenkinsci/xvnc-plugin/pull/5/files 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-33379) Importing jobs doenst do anything since version 1.3
Title: Message Title Emilio Escobar commented on JENKINS-33379 Re: Importing jobs doenst do anything since version 1.3 It's supposed to work. That connection refused could be related to connectivity problem between each server. Do you have a proxy configured? Could you try to execute a curl for testing it from the Jenkins server console to the other? 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-38256) Merged branches are still processed
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-38256 Merged branches are still processed Change By: Antonio Muñiz Summary: Merged branches are still procesed processed 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-33506) Allow users to include/exclude branches on Bitbucket Team/Project
Title: Message Title Michael Martz commented on JENKINS-33506 Re: Allow users to include/exclude branches on Bitbucket Team/Project It seems to me like there are actually two potential aspects to this request. Configure which branches will be used to detect repositories (ie, only add multibranch pipeline jobs if the master branch of the repository has a jenkins file) Configure which branches are eligible for building (ie, only build master and feature/* branches which also have a jenkinsfile) 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-37215) Update generated documentation for JENKINS-29922
Title: Message Title Jesse Glick commented on JENKINS-37215 Re: Update generated documentation for JENKINS-29922 R. Tyler Croy points us to https://github.com/jenkins-infra/pipeline-steps-doc-generator. 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-19756) Build Periodically Should Include Bi-Weekly as an Option
Title: Message Title Mark Sinclair commented on JENKINS-19756 Re: Build Periodically Should Include Bi-Weekly as an Option I just came looking for bi-weekly support as well. I tried setting the schedule like this: @monthly @monthly It's not a real replacement for bi-weekly, but it seems to get me 2 runs per month which is what I needed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38148) NullPointerException in AccuRev Launcher
Title: Message Title Mark Berchem commented on JENKINS-38148 Re: NullPointerException in AccuRev Launcher I saw that the AccuRev Plugin version 0.7.1 was available. I installed it and verified that it fixed the NullPointerException referenced above. I especially like the new checkbox for turning off the color change commands entirely (with off being the default). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34540) Can't use Pipeline Parameter in Branch Specifier on Jenkins 1.651.2/2.0-2.6
Title: Message Title Jesse Glick resolved as Duplicate Not sure why this was reopened; AFAICT it is a duplicate. Jenkins / JENKINS-34540 Can't use Pipeline Parameter in Branch Specifier on Jenkins 1.651.2/2.0-2.6 Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate 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
[JIRA] (JENKINS-38227) Allow letting CMake choose the generator
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38227 Re: Allow letting CMake choose the generator Code changed in jenkins User: 15knots Path: .project src/main/java/hudson/plugins/cmake/CmakeBuilder.java src/main/resources/hudson/plugins/cmake/CmakeBuilder/config.jelly src/main/resources/hudson/plugins/cmake/CmakeBuilder/help-generator.html src/test/java/hudson/plugins/cmake/CmakeBuilderTest.java http://jenkins-ci.org/commit/cmakebuilder-plugin/cfa73debff9f0706e9b20b40b906788795ff79ed Log: Progress on JENKINS-38227 Compare: https://github.com/jenkinsci/cmakebuilder-plugin/compare/c0d6b8243d7d...cfa73debff9f 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-33379) Importing jobs doenst do anything since version 1.3
Title: Message Title David Gomes commented on JENKINS-33379 Re: Importing jobs doenst do anything since version 1.3 Hey Guys, i installed Import Job 1.3.1 version as you recommended. However it shows the same message: "FAILED - Connection refused: connect" Jenkins version i am using is: 1.589 Does this plugin indeed work ? Thank you David 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-29977) Git Plugin truncates changelog
Title: Message Title Ryan Milligan commented on JENKINS-29977 Re: Git Plugin truncates changelog I agree with Patrick. If this could be made configurable, with the default behavior being the current behavior, those of us that would prefer the full commit message could then toggle to option on the git plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38284) Handle per-stage configuration in declarative
Title: Message Title Andrew Bayer commented on JENKINS-38284 Re: Handle per-stage configuration in declarative We most definitely will be. This is specifically for figuring out how to present the per-stage configuration in the syntax and model, not the actual configs themselves. 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-29977) Git Plugin truncates changelog
Title: Message Title Patrick Carson commented on JENKINS-29977 Re: Git Plugin truncates changelog Mark, Would this be a feature that would be difficult to make configurable? As you said its a recommendation, not a standard, and the recommendation is only a style preference. I'm sure there are many people out there who would like to be able to see the full change log at a glance even if it was a checkbox or update to a configuration. 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-37825) Pipeline Model: Add the ability to load shared libraries in the model
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-37825 Pipeline Model: Add the ability to load shared libraries in the model Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate 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-38284) Handle per-stage configuration in declarative
Title: Message Title Patrick Wolf commented on JENKINS-38284 Re: Handle per-stage configuration in declarative can we break this into smaller stories? 1. per stage agent 2. per stage notifications 3. stage DAG I'm a little concerned that matrix, parallel, and DAG are all going to get confused into a big mush of competing ways to do the same thing. 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-35677) build-timeout-plugin cannot be used with pipelines (workflows)
Title: Message Title ikedam commented on JENKINS-35677 Re: build-timeout-plugin cannot be used with pipelines (workflows) Just like this: https://github.com/jenkinsci/xvnc-plugin/pull/11 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-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title Kevin Smith closed an issue as Fixed The changes needed for this defect were fixed once I correctly implemented the Cloud API. Jenkins / JENKINS-30203 When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution Change By: Kevin Smith Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title Kevin Smith edited a comment on JENKINS-30203 Re: When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution @ [~ pjdarton , ] Thanks for the update. In fact those changes were done by me as there was no one else looking at them. I've been using them in-house for about 1 year now with excellent success.Regards,Kevin J. Smith 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-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title Kevin Smith commented on JENKINS-30203 Re: When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution @pjdarton, Thanks for the update. In fact those changes were done by me as there was no one else looking at them. I've been using them in-house for about 1 year now with excellent success. Regards, Kevin J. Smith 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-38285) Add extension point for declarative config sections
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-38285 Add extension point for declarative config sections Issue Type: Story Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/16 5:44 PM Priority: Minor Reporter: Andrew Bayer The top-level config sections in Declarative Pipelines are currently hardcoded in the plugin. We need to make them an ExtensionPoint instead. =) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:25
[JIRA] (JENKINS-35677) build-timeout-plugin cannot be used with pipelines (workflows)
Title: Message Title ikedam commented on JENKINS-35677 Re: build-timeout-plugin cannot be used with pipelines (workflows) Steps to make build-timeout-plugin compatibile with pipeline: Swtich BuildWrapper to SimpleBuildWrapper (https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#build-wrappers) The target Jenkins switches to 1.609. Use @Symbol (https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#defining-symbols) 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-38284) Handle per-stage configuration in declarative
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-38284 Handle per-stage configuration in declarative Issue Type: Story Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/16 5:39 PM Priority: Minor Reporter: Andrew Bayer A number of things are going to be extended to support per-stage configuration (for example, notifications and agent) and at least one new thing is coming that will be exclusively per-stage configuration (stage dependency graph). We need to figure out what that'll look like in general before we can implement it for the particular sections. Add Comment
[JIRA] (JENKINS-32659) Cannot start a job located in a Folder
Title: Message Title Emory Penney resolved as Fixed Fixed in 2.6.3 Jenkins / JENKINS-32659 Cannot start a job located in a Folder Change By: Emory Penney Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22422) Make the name of the node that trigger the startup job available
Title: Message Title Emory Penney resolved as Fixed Fixed in 2.6.3 Jenkins / JENKINS-22422 Make the name of the node that trigger the startup job available Change By: Emory Penney Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title Raphael CHAUMIER commented on JENKINS-38205 Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1) Good news Did you identify the problem about your current installation : the jenkins version? the java version? If you run outside docker with the same jenkins version and the same configuration is it correct ? You said you deploy jenkins.war on weblogic. If you just run jenkins as a java process. is it correct ? Regards 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-22422) Make the name of the node that trigger the startup job available
Title: Message Title Emory Penney assigned an issue to Emory Penney Jenkins / JENKINS-22422 Make the name of the node that trigger the startup job available Change By: Emory Penney Assignee: ashlux Emory Penney 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-18464) Build Pipeline and Join plugin do not play nicely together
Title: Message Title Eric Moreau commented on JENKINS-18464 Re: Build Pipeline and Join plugin do not play nicely together Is there an update on this issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38227) Allow letting CMake choose the generator
Title: Message Title Martin Weber started work on JENKINS-38227 Change By: Martin Weber 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-38227) Allow letting CMake choose the generator
Title: Message Title Martin Weber assigned an issue to Martin Weber Jenkins / JENKINS-38227 Allow letting CMake choose the generator Change By: Martin Weber Assignee: Martin Weber 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-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title pjdarton started work on JENKINS-30203 Change By: pjdarton 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-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title pjdarton assigned an issue to pjdarton Jenkins / JENKINS-30203 When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution Change By: pjdarton Assignee: pjdarton 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-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title pjdarton commented on JENKINS-30203 Re: When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution Kevin Smith I think that the plugin now meets this requirement. The 2.13 plugin had quite a bit of code that went some way towards doing this, and I've done some enhancements such that "it works for me" now. I'm reasonably pleased with how it's gone. I'd suggest that you grab a build of the bleeding-edge code, or wait for the 2.14 release, and try that - you might like what you see... ...and if it does everything this issue was asking for, I'd ask that you close 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-22437) Is it possible to pass a parameters when deploy vm from template?
Title: Message Title pjdarton updated JENKINS-22437 Code changes merged. Jenkins / JENKINS-22437 Is it possible to pass a parameters when deploy vm from template? Change By: pjdarton Status: In Review 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-38283) jabber-plugin does not list out pipeline jobs
Title: Message Title Derek Choi created an issue Jenkins / JENKINS-38283 jabber-plugin does not list out pipeline jobs Issue Type: Bug Assignee: kutzi Components: jabber-plugin Created: 2016/Sep/16 4:44 PM Priority: Minor Reporter: Derek Choi Unable to list or launch pipeline jobs from jabber plugin Running: jobs does not list out pipeline jobs Running: build does not allow me to launch the pipeline job Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Derek Choi commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications +1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton updated JENKINS-38269 Jenkins / JENKINS-38269 Make vSphere cloud slave template's launcher and retention fields configurable Change By: pjdarton 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-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton commented on JENKINS-38269 Re: Make vSphere cloud slave template's launcher and retention fields configurable Implemented in https://github.com/jenkinsci/vsphere-cloud-plugin/pull/54 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-37597) ECS nodes not removed from build executor list
Title: Message Title Eric Goedtel commented on JENKINS-37597 Re: ECS nodes not removed from build executor list Nope. I gave up didn't use ECS and just ran my own Docker host. Sorry . Would be great if this worked because I would love to defer this to ECS. 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-35277) ssh executable not found
Title: Message Title Gregg Stewart commented on JENKINS-35277 Re: ssh executable not found Mark Waite I'm really sorry you haven't heard back from me on this in so long. I wasn't ignoring this on purpose. I had moved on without the feature since it would have been a bonus feature but not a requirement. I've been struggling with finding time to get this tested especially since I had introduced changes to that environment that I think exposed either different problems or bugs. I will give it a try as soon as I am able. Just working through some more pressing issues at this time. Best regards, Gregg 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-38272) The credentials section of the SCM section does not get populated
Title: Message Title Marcus Philip commented on JENKINS-38272 Re: The credentials section of the SCM section does not get populated Just updated this plugin to get the new functionality but cannot because of this bug. I try to use the 'Legacy SCM' because with the 'Modern SCM' option I see nothing. What is it? Can I use it somehow? I have git-client (version:1.19.7) git-server (version:1.7) scm-api (version:1.3) 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-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Title: Message Title x86 nick commented on JENKINS-12096 Re: ThinBackup Worker Thread thread is still running. Execution aborted. Same issue with Jenkins ver. 2.7.2 ameter names, even though it represents a security breach Sep 16, 2016 9:10:15 AM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun WARNING: ThinBackup Worker Thread thread is still running. Execution aborted. Sep 16, 2016 9:11:15 AM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun WARNING: ThinBackup Worker Thread thread is still running. Execution aborted. 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-38272) The credentials section of the SCM section does not get populated
Title: Message Title Marcus Philip updated an issue Jenkins / JENKINS-38272 The credentials section of the SCM section does not get populated Change By: Marcus Philip 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-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Vivek Pandey commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Thorsten Scherler Just the response of /nodes API when graph is flat line. 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-38282) Actions contain duplicate "_class" property
Title: Message Title
Cliff Meyers created an issue
Jenkins / JENKINS-38282
Actions contain duplicate "_class" property
Issue Type:
Bug
Assignee:
Vivek Pandey
Components:
blueocean-plugin
Created:
2016/Sep/16 3:51 PM
Priority:
Minor
Reporter:
Cliff Meyers
The main /search API to fetch pipelines is returning duplicate _class properties in all actions. e.g. http://localhost:8080/jenkins/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26 returns a pipeline with this JSON:
{
"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineImpl",
"_links": {
"activities": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/simple-pipeline-jobs/pipelines/pipeline-success-1m/activities/"
},
"self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/simple-pipeline-jobs/pipelines/pipeline-success-1m/"
},
"actions": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/simple-pipeline-jobs/pipelines/pipeline-success-1m/actions/"
},
"runs": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/simple-pipeline-jobs/pipelines/pipeline-success-1m/runs/"
},
"queue": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/simple-pipeline-jobs/pipelines/pipeline-success-1m/queue/"
}
},
"actions": [
{
"_class": "io.jenkins.blueocean.service.e
[JIRA] (JENKINS-37877) Permission and role checks for run, re-run and stop buttons
Title: Message Title Cliff Meyers started work on JENKINS-37877 Change By: Cliff Meyers 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-37597) ECS nodes not removed from build executor list
Title: Message Title Ruslan Vlasyuk commented on JENKINS-37597 Re: ECS nodes not removed from build executor list Have the same issue. Eric Goedtel have you found any workaround? 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-38281) Global variables starting with capital letter regression
Title: Message Title
Phil Grayson updated an issue
Jenkins / JENKINS-38281
Global variables starting with capital letter regression
Change By:
Phil Grayson
h3. ProblemCalling a function like `Myvariable.myFunctionName()` from a global library returns the following error; {code:java}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Class myFunctionName{code}This only happens when calling global variables beginning with a capital letter. Downgrading the workflow-cps-global-lib plugin to v2.0 results in the error going away. Upgrading to v2.1 makes the error appear.From my point of view this is a regression between v2.0 and v2.1.Am I not supposed to create global variables starting with a capital letter? This represents a breaking changein some of my global library code. h3. Steps to reproduce1. Setup a global library like;{code:java}# directory structure+- vars | +- one.groovy | +- Two.groovy {code}{code:java}# in vars/one.groovydef call() { echo "in one()"}def fn() { echo "In one.fn()"}{code}{code:java}# in vars/Two.groovydef call() { echo "In Two()"}def fn() { echo "In Two.fn()"}{code}2. Load the global library into jenkins (git push)3. Create a pipeline job with the following pipeline script{code:java}one()one.fn()Two()Two.fn(){code}h5. Expected Output{code}[Pipeline] echoin one()[Pipeline] echoIn one.fn()[Pipeline] echoIn Two()[Pipeline] echoIn Two.fn(){code}h5. Actual Output{code}in one()[Pipeline] echoIn one.fn()[Pipeline] echoIn Two()[Pipeline] End of Pipelineorg.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Class fn at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)[... truncated - full stack trace attached to ticket ...]{code}
Add Comment
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Lorelei McCollum commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Yeah we really need this update too, do we know when this plugin will be available and released? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38281) Global variables starting with capital letter regression
Title: Message Title Phil Grayson created an issue Jenkins / JENKINS-38281 Global variables starting with capital letter regression Issue Type: Bug Assignee: Jesse Glick Attachments: full_stacktrace.txt, workflow-cps-global-lib-2.0.png, workflow-cps-global-lib-2.1.png Components: workflow-cps-global-lib-plugin Created: 2016/Sep/16 3:00 PM Environment: Jenkins: 2.7.4 workflow-cps-global-lib: 2.3 Priority: Major Reporter: Phil Grayson Problem Calling a function like `Myvariable.myFunctionName()` from a global library returns the following error; org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Class myFunctionName This only happens when calling global variables beginning with a capital letter. Downgrading the workflow-cps-global-lib plugin to v2.0 results in the error going away. Upgrading to v2.1 makes the error appear. From my point of view this is a regression between v2.0 and v2.1. Am I not supposed to create global variables starting with a capital letter? This represents a breaking change Steps to reproduce 1. Setup a global library like;
[JIRA] (JENKINS-38280) M2 release plugin now showing release option
Title: Message Title anurag dubey created an issue Jenkins / JENKINS-38280 M2 release plugin now showing release option Issue Type: Bug Assignee: James Nord Components: m2release-plugin Created: 2016/Sep/16 2:56 PM Priority: Blocker Reporter: anurag dubey Installed M2 Release plugin on CloudBeese JEnkins (Jenkins ver. 1.625.16.1 (CloudBees Jenkins Enterprise 15.11) ) We can see release config option in "Build Environment" section in job config, however after configuration on job page "perform maven release option" does not apper https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin Regards Anurag Add Comment
[JIRA] (JENKINS-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers commented on JENKINS-37715 Re: Make gulp builds consistent across main blueocean modules shrinkwrap hotfix: https://github.com/jenkinsci/blueocean-plugin/pull/500 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-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers commented on JENKINS-37715 Re: Make gulp builds consistent across main blueocean modules shrinkwrap: https://github.com/jenkinsci/blueocean-plugin/pull/493 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-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers commented on JENKINS-37715 Re: Make gulp builds consistent across main blueocean modules JDL versioning / release: https://github.com/jenkinsci/jenkins-design-language/pull/96 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-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37715 Make gulp builds consistent across main blueocean modules Change By: Cliff Meyers Sprint: 1.0-b05/b-06 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-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers started work on JENKINS-37715 Change By: Cliff Meyers 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-38279) Workflow support for build publisher plugin
Title: Message Title Ali Al-Shabibi created an issue Jenkins / JENKINS-38279 Workflow support for build publisher plugin Issue Type: Improvement Assignee: vjuranek Components: build-publisher-plugin Created: 2016/Sep/16 2:45 PM Labels: pipeline plugin Priority: Major Reporter: Ali Al-Shabibi Build publisher plugin should be made compatible with Workflow (implement SimpleBuildWrapper). Add Comment
[JIRA] (JENKINS-37884) p4-plugin repeatedly builds job when workspace deleted after build
Title: Message Title Staffan Forsell commented on JENKINS-37884 Re: p4-plugin repeatedly builds job when workspace deleted after build OK, so I found https://issues.jenkins-ci.org/browse/JENKINS-32814. I will try use the new poll on master filer and report back. 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-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Filip Pytloun edited a comment on JENKINS-27421 Re: Unserializable iterator & entry classes from Java Collections This seems to be totally broken in workflow-cps version 2.17 - when I updated, every map throw NotSerializableException. I had to update back to 2.13 to make this working work again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Filip Pytloun commented on JENKINS-27421 Re: Unserializable iterator & entry classes from Java Collections This seems to be totally broken in workflow-cps version 2.17 - when I updated, every map throw NotSerializableException. I had to update back to 2.13 to make this working again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38278) Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception
Title: Message Title Andrew Gunnerson created an issue Jenkins / JENKINS-38278 Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception Issue Type: Bug Assignee: Carlos Sanchez Components: core, kubernetes-plugin Created: 2016/Sep/16 2:33 PM Environment: Jenkins 2.7.3 (official docker image jenkins:2.7.3) - Docker host has 16GB of memory and runs nothing else Slave (official docker image jenkinsci/jnlp-slave:latest) - Kubernetes hosts all have 48GB of memory Kubernetes plugin 0.8 Priority: Minor Reporter: Andrew Gunnerson I'm running into an issue where the slaves dynamically spun up by the Kubernetes plugin randomly cause an "unable to create new native thread" exception during the slave.jar connection phase. As far as I can tell, the exception is throws on the Jenkins master, not the slave. Both the master and slave are running in the official docker containers (jenkins:2.7.3 and jenkinsci/jnlp-slave:latest, respectively). The first thing I did was check the process limits from the "jenkins" user inside the Jenkins master container. The limits seem to be much higher than what should be needed for a server that only has 7 jobs (where everything runs on slaves). It usually gets to the point where a build for a job is created, but doesn't actually do anything. The job hangs with either no output or the same OOM exception. I've included the process limits and relevant logs below. Is there anything else I can provide that would help solve the problem? — Jenkins master process limits from inside the container: https://gist.github.com/agunnerson-ibm/dccb6c8c2edc6a498f9c377d96f43481#file-process_limits_master-txt Slave connection log: https://gist.github.com/agunnerson-ibm/dccb6c8c2edc6a498f9c377d96f43481#file-slave-log slave.jar log: https
[JIRA] (JENKINS-38053) JellyTagException on Multijob project view with Jenkins 2.7.3 LTS
Title: Message Title Koen Franken commented on JENKINS-38053 Re: JellyTagException on Multijob project view with Jenkins 2.7.3 LTS Alternative to defining all parameters individually (which will be harder to find when also using custom predefined parameters on sub-jobs) is to re-enable the old "policy"... Add -Dhudson.model.ParametersAction.keepUndefinedParameters=true to the JAVA_ARGS in /etc/default/jenkins. Tested on Jenkins 2.22 with Multijob plugin 1.21. 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-36263) Kubernetes pod deleted before BuildWrapper cleanup
Title: Message Title Tomasz Wojtun commented on JENKINS-36263 Re: Kubernetes pod deleted before BuildWrapper cleanup Terminating a pod in a extension of hudson.model.listeners.RunListener on finalised event also can cause another RunListener to fail. Maybe keeping slave idle for customizable amount of time, before killing it is a good idea. 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-38275) Unable to pull extra repository on build step when running on a Jenkins slave
Title: Message Title Mark Waite resolved as Not A Defect You said: when running a build step (shell script) the slave is losing the GIT_SSH information or that information is not used by git anymore That is the expected behavior. A build step does not have access to the credentials used to clone the repository. Reliably providing credentials to command line git for all credential cases without invoking the command line git program is quite difficult (since there may be a passphrase protected public key, for example), so the plugin does not attempt to share credential information with build steps. If you're using a pipeline job, you can share credential information with pipeline stages using the credentials ID defined in Jenkins. You can refer to the JENKINS-34309 pipeline file in my jenkins-bugs repository for an example pipeline definition that uses a credentials ID. Jenkins / JENKINS-38275 Unable to pull extra repository on build step when running on a Jenkins slave Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-38135) docker plugin reads legacy network setting from docker
Title: Message Title
Andreas Merkel updated an issue
Jenkins / JENKINS-38135
docker plugin reads legacy network setting from docker
Change By:
Andreas Merkel
The In case the container exposes the SSH port on {{0.0.0.0}} and the docker daemon is running on a unix socket, the plugin reads the {{NetworkSettings.IPAddress}} field from the docker container to determine what host to connect to in order to talk to the container . However, the field is only filled when the container runs with the default "bridge" network. If another network is used (e.g., if a custom network is configured in the "Network" field of the docker template setting) this field is empty and the field {{NetworkSettings..IPAddress}} has to be used. (cf. https://github.com/docker/docker/issues/21658#issuecomment-203527083).
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 rece
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Mike Kobit commented on JENKINS-31155 Re: Workflow shared library improvements Is there a separate issue tracking the above behavior (I'm guessing there should be)? 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-38277) The webhook registration didn't register the push hook
Title: Message Title Marc Ende commented on JENKINS-38277 Re: The webhook registration didn't register the push hook The logs are showing that: GitHub webhooks activated for job / with [GitHubRepositoryName[host=github.com,username=,repository=]] (events: [PULL_REQUEST, REPOSITORY]) I think there is the PUSH missing. 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-38277) The webhook registration didn't register the push hook
Title: Message Title Marc Ende updated an issue Jenkins / JENKINS-38277 The webhook registration didn't register the push hook Change By: Marc Ende Summary: The Webhook webhook registration doesn didn 't work register the push hook 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-22437) Is it possible to pass a parameters when deploy vm from template?
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22437 Re: Is it possible to pass a parameters when deploy vm from template? Code changed in jenkins User: Jason Swager Path: src/main/java/org/jenkinsci/plugins/vsphere/VSphereGuestInfoProperty.java http://jenkins-ci.org/commit/vsphere-cloud-plugin/8971edf3a5ee5c7c3e92d31cbc342b4019ca4027 Log: Merge pull request #53 from pjdarton/enhance_jenkins_22437 Enhance JENKINS-22437 Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/ef95e6f6fcf9...8971edf3a5ee 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-38277) The Webhook registration doesn't work
Title: Message Title Marc Ende created an issue Jenkins / JENKINS-38277 The Webhook registration doesn't work Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Sep/16 1:34 PM Environment: Jenkins (2.7.3) github-plugin (latest) Priority: Major Reporter: Marc Ende When registering the webhooks at github. Regardless if using explicitly the "re-register"-button or indirectly while creating a multipipeline build the Webhooks for "Repository" and "Pull Requests" are set. Not set is the "Push" Webhook. This leads to the behaviour that pushes to github repositories aren't sent to jenkins. For that case I've got to use timebased polling which makes the whole webhook-thing useless. To get the pushes working I've got to activate the webhook manually. This works until I push the re-register button. Then they're gone. Add Comment
[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title Raffi B created an issue Jenkins / JENKINS-38276 Increase size of text area for pipeline script code Issue Type: Improvement Assignee: Jesse Glick Components: pipeline Created: 2016/Sep/16 1:30 PM Environment: Jenkins 2.7.2 Pipeline plugin 2.11 Window 7 x64 SP1 Labels: ui pipeline jenkins Priority: Minor Reporter: Raffi B The text area for pipeline script code is too small, and neither Chrome or Firefox allow for custom resizing; text area size is likely hard coded in Jenkins. Add Comment
[JIRA] (JENKINS-38275) Unable to pull extra repository on build step when running on a Jenkins slave
Title: Message Title Etienne Lachance created an issue Jenkins / JENKINS-38275 Unable to pull extra repository on build step when running on a Jenkins slave Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Sep/16 1:21 PM Environment: Ubuntu 14.04.5 Jenkins ver. 2.22 Priority: Major Reporter: Etienne Lachance I am using Jenkins with docker slaves (same issue with normal slaves) When the job start on the slave, the initial git repository is pull correctly but when running a build step (shell script) the slave is losing the GIT_SSH information or that information is not used by git anymore. When the script try to run git command (pull, commit, push), the git command don't have access to the remote repository. The only workaround for now is to copy the ssh key to the slave (don't want this for security reason) Log example Building remotely on docker-d2539c5d3982 (ubuntu1404-php55) in workspace /home/jenkins/workspace/projectName Cloning the remote Git repository Cloning repository g...@github.com:companyName/projectName.git > git init /home/jenkins/workspace/projectName # timeout=10 Fetching upstream changes from g...@github.com:companyName/projectName.git > git --version # timeout=10 using GIT_SSH to set credentials Jenkins Git key > git fetch --tags --progress g...@github.com:companyName/projectName.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url g...@github.com:companyName/projectName.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url g...@github.c
[JIRA] (JENKINS-38274) Archiving artifacts loses file permissions
Title: Message Title Lars W created an issue Jenkins / JENKINS-38274 Archiving artifacts loses file permissions Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Sep/16 1:16 PM Environment: Jenkins 2.22 Priority: Major Reporter: Lars W Make a file in a job's workspace executable. Let the job archive this file. The archived artifact is not executable any more. Add Comment
[JIRA] (JENKINS-38273) Condense the appearance of static analysis results on a delivery pipeline view
Title: Message Title Michael Baran commented on JENKINS-38273 Re: Condense the appearance of static analysis results on a delivery pipeline view PR 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-38273) Condense the appearance of static analysis results on a delivery pipeline view
Title: Message Title Michael Baran started work on JENKINS-38273 Change By: Michael Baran 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-38273) Condense the appearance of static analysis results on a delivery pipeline view
Title: Message Title Michael Baran assigned an issue to Unassigned Jenkins / JENKINS-38273 Condense the appearance of static analysis results on a delivery pipeline view Change By: Michael Baran Assignee: Michael Baran 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-38273) Condense the appearance of static analysis results on a delivery pipeline view
Title: Message Title Michael Baran created an issue Jenkins / JENKINS-38273 Condense the appearance of static analysis results on a delivery pipeline view Issue Type: Improvement Assignee: Michael Baran Attachments: Screen Shot 2016-09-12 at 9.32.45 PM.png, Screen Shot 2016-09-16 at 7.52.17 AM.png Components: delivery-pipeline-plugin Created: 2016/Sep/16 12:53 PM Environment: OSX 10.11.6 Java 1.8.0_66 Maven 3.3.9 Firefox 48.0.2 Safari 9.1.3 Priority: Minor Reporter: Michael Baran I was very happy and surprised when built-in support for displaying static analysis results was added to this plugin as it was something I wanted my pipelines to show. However when using several different static analysis plugins like my employer does results in a pipeline stage that is very tall, repeats itself (ex. separate 'High/Normal/Low' headers appear for every static analysis result), obfuscates the data that it is trying to bring attention to, and just outright isn't easy on the eyes. I feel it would be beneficial if all the static analysis results were condensed into just one table such as something like this.
[JIRA] (JENKINS-38272) The credentials section of the SCM section does not get populated
Title: Message Title emanuelez created an issue Jenkins / JENKINS-38272 The credentials section of the SCM section does not get populated Issue Type: Bug Assignee: Jesse Glick Components: workflow-cps-global-lib-plugin Created: 2016/Sep/16 12:30 PM Priority: Major Reporter: emanuelez In the Global preferences, the drop-down menu for the credentials does not get populated. Credentials are indeed configured and available and work fine while used to configure jobs. Add Comment This message was sen
[JIRA] (JENKINS-38271) When creating a new item from copy which has parameter, SVN does not record any revision
Title: Message Title Marcus Arganso updated an issue Jenkins / JENKINS-38271 When creating a new item from copy which has parameter, SVN does not record any revision Change By: Marcus Arganso Environment: Jenkins 2.22, Subversion Plug-in 2.6 , Random string parameter plugin 1.0 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-38271) When creating a new item from copy which has parameter, SVN does not record any revision
Title: Message Title Marcus Arganso created an issue Jenkins / JENKINS-38271 When creating a new item from copy which has parameter, SVN does not record any revision Issue Type: Bug Assignee: Unassigned Components: core, random-string-parameter-plugin, subversion-plugin Created: 2016/Sep/16 12:22 PM Environment: Jenkins 2.22, Subversion Plug-in 2.6 Priority: Major Reporter: Marcus Arganso I have a job with a random string parameter using svn. I copied that job. The new job kept queuing up new builds for every SCM poll. The output messages said: Job console output: No revision recorded for https://1af.se/svn/WIS2/tags/2.7.0.11 in the previous build SVN polling log: Workspace doesn't contain https://1af.se/svn/WIS2/tags/2.7.0.11. Need a new build. I removed the random string parameter from the new job and the problem disappeared. Add Comment
[JIRA] (JENKINS-38270) Conditional build step config discarded when upgrading to plugin 1.3.5
Title: Message Title Jukka Lehtniemi created an issue Jenkins / JENKINS-38270 Conditional build step config discarded when upgrading to plugin 1.3.5 Issue Type: Bug Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin Created: 2016/Sep/16 12:05 PM Environment: Jenkins 2.22 conditional-buildstep plugin 1.3.5 Priority: Critical Reporter: Jukka Lehtniemi We upgraded conditional-buildstep plugin from 1.3.3 to 1.3.5 and noticed that all the conditional build steps vanished from the job configuration. We restored the job configuration from backups but even when the 1.3.3 XML nodes are present in the config.xml the build steps are neither visible in the web-UI nor executed during the build. Add Comment
[JIRA] (JENKINS-38243) NPE when RESERVED attribute content is empty
Title: Message Title Pavel Janoušek edited a comment on JENKINS-38243 Re: NPE when RESERVED attribute content is empty Caught NPE is probably related to [JENKINS-38196?focusedCommentId=270181| https://issues.jenkins-ci.org/browse/JENKINS-38196?focusedCommentId=270181&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270181 ] , nevertheless we should above detected issues. 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-38243) NPE when RESERVED attribute content is empty
Title: Message Title Pavel Janoušek commented on JENKINS-38243 Re: NPE when RESERVED attribute content is empty Caught NPE is probably related to https://issues.jenkins-ci.org/browse/JENKINS-38196?focusedCommentId=270181&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270181, nevertheless we should above detected issues. 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-38253) Optimize static resource fetch
Title: Message Title Cliff Meyers commented on JENKINS-38253 Re: Optimize static resource fetch I know all assets are fetched via the Jenkins "adjuncts" which includes a hash in the URL. Just curious, what controls the generation of this hash? 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-36662) Downstream projects should not be triggered anymore after upstream project pom version is changed
Title: Message Title tsbx edited a comment on JENKINS-36662 Re: Downstream projects should not be triggered anymore after upstream project pom version is changed The issue is that *everytime* (not only the first time) jobA is rebuilt (for example, triggered by a commit), jobB is triggered ; even if projectA version has changed.If it was only the first build after the version change , it would be _not too bad_. 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-36662) Downstream projects should not be triggered anymore after upstream project pom version is changed
Title: Message Title tsbx commented on JENKINS-36662 Re: Downstream projects should not be triggered anymore after upstream project pom version is changed The issue is that everytime (not only the first time) jobA is rebuilt (for example, triggered by a commit), jobB is triggered ; even if projectA version has changed. If it was only the first build after the version, it would be not too bad. 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-38196) NPE during node provision
Title: Message Title Pavel Janoušek commented on JENKINS-38196 Re: NPE during node provision Uh, the fix isn't completed private String getHostToReserve(Label label) is affected as well. 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-38243) NPE when RESERVED attribute content is empty
Title: Message Title Pavel Janoušek commented on JENKINS-38243 Re: NPE when RESERVED attribute content is empty I've found several problematic pieces. Missing @CheckForNull annotation: here: public String getHostParameterValue(String hostname, String parameterName) here: public String getHostAttributeValue(String hostname, String attribute) here: public String getLabelsForHost(String hostName) and other methods defined in ForemanAPI which can return null. Possible unhandled NPE: in public boolean isHostFree(String host) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton started work on JENKINS-38269 Change By: pjdarton 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-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton created an issue Jenkins / JENKINS-38269 Make vSphere cloud slave template's launcher and retention fields configurable Issue Type: Improvement Assignee: pjdarton Components: vsphere-cloud-plugin Created: 2016/Sep/16 10:54 AM Priority: Minor Reporter: pjdarton The vSphere plugin 2.13 has a facility to define a slave "template", allowing Jenkins to ask for more slaves to satisfy build workload demands. However, the implementation is currently limited to only SSH-launcher slaves (with hard-coded settings too), and with a "retention strategy" limited to only "run one build then dispose of the slave" (with a hard-coded timeout). This has two negative implications: 1) a Windows slave connecting via the Java Web Start method (JNLP) will cause errors in the logs as the SSHLauncher fails to connect. 2) in situations where builds complete quickly, Jenkins can spend longer waiting for each slave to start up than the build takes itself, which isn't very efficient. The docker cloud implementation allows for different launcher methods and different retention strategies - the vSphere plugin should be similarly enhanced to: 1) Allow the slave connection method to be configured, exposing all configuration options for each of the connection methods. 2) Allow the slave "retention strategy" to be configured, exposing all configuration options for each of the connection methods. 3) Add a new strategy (e.g. based on the Jenkins CloudRetentionStrategy) to allow a cloud slave to be reused for multiple builds.
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Phil Grayson created an issue
Jenkins / JENKINS-38268
Parallel step and closure scope
Issue Type:
Bug
Assignee:
Jesse Glick
Attachments:
console_output.png, console_output_no_node_step.png, pipeline_step.png
Components:
pipeline, workflow-cps-plugin
Created:
2016/Sep/16 10:42 AM
Environment:
Jenkins: 2.7.4 (affecting 1.6 too) Pipeline: 2.3 (tested on fresh install with latest dependencies) Environment setup; 1. Run "docker run -p 8080:8080 -p 5:5 jenkins" 2. Browse to http://localhost:8080 3. Perform initial jenkins setup - install 'pipeline' plugin
Labels:
pipeline parallel
Priority:
Major
Reporter:
Phil Grayson
I'm experiencing some odd behaviour with the parallel step related to variable scoping. The following minimal pipeline script demonstrates my problem.
def closure = { val ->
node { }
println val
}
parallel([
a: { closure.call('a') },
b: { closure.call('b') }
])
Expected output
[JIRA] (JENKINS-38265) incorrect PATH set on build environment
Title: Message Title Nicolas De Loof commented on JENKINS-38265 Re: incorrect PATH set on build environment https://github.com/Dockins/docker-slaves-plugin/pull/14 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-36878) vSphere plugin not respecting or saving per slave instance Cap
Title: Message Title pjdarton updated JENKINS-36878 Jenkins / JENKINS-36878 vSphere plugin not respecting or saving per slave instance Cap Change By: pjdarton Status: In Review 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-36878) vSphere plugin not respecting or saving per slave instance Cap
Title: Message Title pjdarton commented on JENKINS-36878 Re: vSphere plugin not respecting or saving per slave instance Cap Pull request merged. 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.
