[JIRA] (JENKINS-41776) Extra Column Plugin Not Pulling In Test Results for Cucumber Tests Run With Maven
Title: Message Title Wesley Chinnapper commented on JENKINS-41776 Re: Extra Column Plugin Not Pulling In Test Results for Cucumber Tests Run With Maven Hi, I noticed that only JUnit Results are displayed. Would be great to add a column for Cucumber Reports. I have the Cucumber Reports Plugin installed. Latest version of Jenkins. Not its not public. 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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Karl Shultz commented on JENKINS-41945 Re: Eventual NPE while running many concurrent declarative pipelines I'll let the standard ones run overnight, and see how things look tomorrow. 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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Karl Shultz commented on JENKINS-41945 Re: Eventual NPE while running many concurrent declarative pipelines jenkins--failure.log I let the standard pipelines run 20 minutes or so. There wasn't any sign of degraded performance to speak of. Here's the beginning and end of the vmstat output: procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 02/11/2017 01:47:41c 2 0 0 12885760 189508 8319160015 268 273 144 75 0 24 1 0 (snip) 02/11/2017 02:06:41c 0 0 0 12805028 191464 83247200 0 432 175 204 0 0 99 1 0 That amount of decrease in free memory is pretty small. The UI remains responsive throughout. To contrast, here's a similar timespan, with the declarative jobs running. Bu the time I stopped vmstat recording, the UI had stopped responding. procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 02/11/2017 02:25:33c 1 0 0 13255960 195416 9155000013 251 251 144 65 0 33 1 0 (snip) 02/11/2017 02:45:33c 4 0 0 11748496 199188 98192800 0 1471 1290 735 93 0 7 0 0 The declarative jobs are consuming more resource, but I think that's expected. The log, which I'll attach as jenkins--failure.log, is interesting. The jobs run for a while. Then I start to see these: Feb 11, 2017 2:27:34 AM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: DeclarativePipelines/inlineThing72 #80 completed: SUCCESS Feb 11, 2017 2:27:35 AM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: DeclarativePipelines/inlineThing70 #80 completed: SUCCESS Feb 11, 2017 2:27:39 AM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution cleanUpHeap WARNING: failed to clean up memory from Owner[DeclarativePipelines/inlineThing63/81:DeclarativePipelines/inlineThing63 #81] java.lang.NullPointerException at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:57) at sun.reflect.UnsafeQualifiedObjectFieldAccessorImpl.get(UnsafeQualifiedObjectFieldAccessorImpl.java:38) at java.lang.reflect.Field.get(Field.java:393) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpGlobalClassSet(CpsFlowExecution.java:1034) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpLoader(CpsFlowExecution.java:966) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpLoader(CpsFlowExecution.java:968) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpLoader(CpsFlowExecution.java:968) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpLoader(CpsFlowExecution.java:957) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpLoader(CpsFlowExecution.java:957) at
[JIRA] (JENKINS-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-41945 Eventual NPE while running many concurrent declarative pipelines Change By: Karl Shultz Attachment: jenkins--failure.log 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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title
Karl Shultz commented on JENKINS-41945
Re: Eventual NPE while running many concurrent declarative pipelines
I ran the following standard pipeline script in the same way (100 concurrently, every minute):
node {
stage("TestingTesting") {
sh 'echo Hello world'
}
}
These standard pipelines feel like they run considerably faster than the declarative ones from before. So it could be that I'll need to run way more than 100 of them to reproduce the issue with standard pipeline. This time, I've got something running to tell me about system utilization:
vmstat 15 | awk '{system("X=$(date +\"%x %T\"); echo $X\\\c");print $0}' > vmstat.15.standard &
(Thanks Google!) I'll do likewise the next time I go to recreate this with declarative pipelines.
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-41876) Not respecting configuration in regards of global modules
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-41876 Not respecting configuration in regards of global modules Change By: Nikolas Falco Assignee: Nikolas Falco 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-41876) Not respecting configuration in regards of global modules
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41876 Re: Not respecting configuration in regards of global modules Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java http://jenkins-ci.org/commit/nodejs-plugin/e092acdca13d41e5065743289d0b986e652e6fe8 Log: JENKINS-41876 Check if global package value is blank instead null why after persistence migration value could not be null if in previous 0.2.x version value was spaces. XStream during de-serialisation does not instantiate object by its constructor, this means npmPackages value will empty (instead null) till a save is performed in configuration page. 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-41876) Not respecting configuration in regards of global modules
Title: Message Title Nikolas Falco started work on JENKINS-41876 Change By: Nikolas Falco 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-41186) java.security.spec.InvalidKeySpecException: key spec not recognised
Title: Message Title Fritz Elfert commented on JENKINS-41186 Re: java.security.spec.InvalidKeySpecException: key spec not recognised Ashley Taylor Thanks a lot for your analysis! I just wonder why I am unable to reproduce this error on my local jenkins. At least, I can prepare a fix now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24381) NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds
Title: Message Title Nikolas Falco stopped work on JENKINS-24381 Change By: Nikolas Falco Status: In Progress Open 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-24381) NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds
Title: Message Title Nikolas Falco commented on JENKINS-24381 Re: NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds I've try to reproduce your use case with defining a NodeJS installer and two jobs A and B (clone of A) with a nodejs build step. In debug mode I add a break point where the installer checks if has to skip npm package installation. Only one job can access to the installation tools because there is a global InstallerTranslator that run installations and use a semaphore per node per installation. So only one job at time can execute a specific installation on the same Jenkins node, all other will wait untill the first one has performed the installation. The only scenario where this issue could occurs is if you perform an npm install -g command in your build step. In this case is not possible syncronize installation because it's the npm command, this is the reason why you have to move global package to installation definition. 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-40964) update to latest config-file-provider
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40964 Re: update to latest config-file-provider Code changed in jenkins User: David van Laatum Path: src/main/java/hudson/plugins/emailext/GroovyTemplateConfig.java src/main/java/hudson/plugins/emailext/JellyTemplateConfig.java http://jenkins-ci.org/commit/email-ext-plugin/3fc19600e39dbac9cdb2f4e9fdf19a92e8174d32 Log: Bring back functions removed in JENKINS-40964 that are required for upgrade of existing config 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-41917) Fix wrong java.level
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41917 Re: Fix wrong java.level Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/display-url-api-plugin/b768bd85286f75f2c957cd155bb30a939eccfb89 Log: JENKINS-41917 Set java.level=6 as the one in baseline version. (#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-24381) NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds
Title: Message Title Nikolas Falco started work on JENKINS-24381 Change By: Nikolas Falco 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-41876) Not respecting configuration in regards of global modules
Title: Message Title Nikolas Falco commented on JENKINS-41876 Re: Not respecting configuration in regards of global modules I can not reproduce this issue. I have try with a clean Jenkins 1.625.3 / 2.32.2 / 2.44 installation (MacOS) for Jenkins 2.x installation I had select only the NodeJS 1.0.1 plugin to install after it completes setup I configure a new NodeJS installation in "Global Tool Configuration" page like in screenshot. Then save, the file jenkins.plugins.nodejs.tools.NodeJSInstallation.xml have to appear under jenkins home folder (master node, not slave). If the file does not exist means no installation have been saved. Maybe you could have nodejs.xml file, this because you have 0.2.x version installed not 1.0.x. I create a new Freestyle job named test1 I add a build step "Execute NodeJS script"; selecting nodejs-4-latest as installation this as script content console.log(2+2) leave npmrc default This is the job configuration file config.xml Follow the console ouput (the same for all Jenkins version): Started by user anonymous Building in workspace /Users/nikolasfalco/git/nodejs-plugin/work/workspace/test1 Unpacking https://nodejs.org/dist/v4.7.3/node-v4.7.3-darwin-x64.tar.gz to /Users/nikolasfalco/git/nodejs-plugin/work/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest on Jenkins [test1] $ /Users/nikolasfalco/git/nodejs-plugin/work/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin/node /var/folders/jq/2l9t7bw1103_jjyv9rzk7kcrgn/T/hudson7746704401481264781.js 4 Finished: SUCCESS Please to understand the issue provide me: the job config.xml file tools installation jenkins.plugins.nodejs.tools.NodeJSInstallation.xml file Alexander Komarov provide your operative system if job runs on a slave node or master
[JIRA] (JENKINS-35558) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Christian McHugh closed an issue as Fixed Fixed in 2.0 release Jenkins / JENKINS-35558 Upgrade to Credentials 2.1.0+ API for populating credentials drop-down Change By: Christian McHugh Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-41876 Not respecting configuration in regards of global modules Change By: Nikolas Falco Attachment: config.xml 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-41876) Not respecting configuration in regards of global modules
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-41876 Not respecting configuration in regards of global modules Change By: Nikolas Falco Attachment: jenkins.plugins.nodejs.tools.NodeJSInstallation.xml 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-41944) Unable to understand when AbortError is created by user`s action like pressing button Stop
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41944 Unable to understand when AbortError is created by user`s action like pressing button Stop Change By: Andrew Bayer Component/s: workflow-job-plugin Component/s: 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-41948) Scanning MultiBranchProject fails and logs NoSuchMethodError
Title: Message Title Mark Waite assigned an issue to Stephen Connolly Jenkins / JENKINS-41948 Scanning MultiBranchProject fails and logs NoSuchMethodError Change By: Mark Waite Assignee: Matthew DeTullio Stephen Connolly 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-41948) Scanning MultiBranchProject fails and logs NoSuchMethodError
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41948 Scanning MultiBranchProject fails and logs NoSuchMethodError Change By: Mark Waite Component/s: branch-api-plugin Component/s: scm-api-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-41948) Scanning MultiBranchProject fails and logs NoSuchMethodError
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41948 Scanning MultiBranchProject fails and logs NoSuchMethodError Change By: Mark Waite Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41948) Scanning MultiBranchProject fails and logs NoSuchMethodError
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41948
Scanning MultiBranchProject fails and logs NoSuchMethodError
Change By:
Mark Waite
Initial scan of branches in a multi-branch-project fails with an NoSuchMethodError in the log file.Steps to duplicate the problem:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS- xxx 41948 $ cd JENKINS- xxx 41948 $ git checkout -b lts-with-plugins 4dc4b070e072c452fbb6b42b28dae3445a9e20da # -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS- xxx 41948 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS- xxx 41948 {code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Git Client Plugin Folder"# Open the "Git Client Branches - Maven" multi-branch job# Click the "Scan Project" link and then the "Run Now" link to start branch indexing# Scan will complete, but no projects will be created. Console log will report an errorLog information is:{noformat}Feb 10, 2017 5:48:26 PM hudson.model.Executor finish1SEVERE: Executor threw an exceptionjava.lang.NoSuchMethodError: jenkins.branch.MultiBranchProject.getRootDirFor(Lhudson/model/Job;)Ljava/io/File;at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.getRootDirFor(TemplateDrivenMultiBranchProject.java:306)at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenMultiBranchProject.getRootDirFor(TemplateDrivenMultiBranchProject.java:89)at hudson.model.AbstractItem.getRootDir(AbstractItem.java:177)at hudson.model.Items.getConfigFile(Items.java:350)at hudson.model.AbstractItem.getConfigFile(AbstractItem.java:506)at hudson.model.AbstractItem.save(AbstractItem.java:501)at hudson.model.Job.save(Job.java:186)at hudson.model.AbstractProject.save(AbstractProject.java:306)at hudson.BulkChange.commit(BulkChange.java:98)at com.github.mjdetullio.jenkins.plugins.multibranch.TemplateDrivenBranchProjectFactory.setBranch(TemplateDrivenBranchProjectFactory.java:104)at com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleBranchProjectFactory.newInstance(FreeStyleBranchProjectFactory.java:55)at com.github.mjdetullio.jenkins.plugins.multibranch.FreeStyleBranchProjectFactory.newInstance(FreeStyleBranchProjectFactory.java:38)at jenkins.branch.MultiBranchProject$SCMHeadObserverImpl.observe(MultiBranchProject.java:1972)at jenkins.plugins.git.AbstractGitSCMSource$2.run(AbstractGitSCMSource.java:315)at jenkins.plugins.git.AbstractGitSCMSource$2.run(AbstractGitSCMSource.java:239)at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:209)at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:239)at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:300)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:210)at
[JIRA] (JENKINS-41948) Scanning MultiBranchProject fails and logs NoSuchMethodError
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-41948 Scanning MultiBranchProject fails and logs NoSuchMethodError Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2017/Feb/11 1:05 AM Environment: Docker instance Priority: Minor Reporter: Mark Waite Initial scan of branches in a multi-branch-project fails with an NoSuchMethodError in the log file. Steps to duplicate the problem: Clone, build, and run the docker instance $ git clone https://github.com/MarkEWaite/docker JENKINS-xxx $ cd JENKINS-xxx $ git checkout -b lts-with-plugins 4dc4b070e072c452fbb6b42b28dae3445a9e20da # -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS-xxx . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-xxx Connect a web browser to that docker instance (http://localhost:8080) Open the "Git Client Plugin Folder" Open the "Git Client Branches - Maven" multi-branch job Click the "Scan Project" link and then the "Run Now" link to start branch indexing
[JIRA] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-35230 The environment variables of git plugin not working in pipeline script. Change By: Patrick Wolf Labels: 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-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-35230 The environment variables of git plugin not working in pipeline script. Change By: Patrick Wolf Component/s: workflow-scm-step-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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) Strangely, the custom plugin from d6c6db7 seems to be working on our builds that run on Windows slaves, but the OSX slave, which worked fine on 0.2.2 is the one with the issue in the attached files above. 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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) Nikolas Falco, I've attached them all below. My setup really didn't change from the builds that were functioning previously on 0.2.2. Thanks for taking a look. config.xml build_output.txt 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-41919) System env/property for default implementation not usefull
Title: Message Title James Dumay commented on JENKINS-41919 Re: System env/property for default implementation not usefull Oops - I'll get to this shortly 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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille updated an issue Jenkins / JENKINS-41857 Correct path for installation is not provided to system/shells (build.steps) Change By: Adam Dille Attachment: config.xml 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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille updated an issue Jenkins / JENKINS-41857 Correct path for installation is not provided to system/shells (build.steps) Change By: Adam Dille Attachment: nodejs_setup.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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille updated an issue Jenkins / JENKINS-41857 Correct path for installation is not provided to system/shells (build.steps) Change By: Adam Dille Attachment: build_output.txt 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-41806) Error 500 rest call for Item
Title: Message Title James Dumay commented on JENKINS-41806 Re: Error 500 rest call for Item Vivek Pandey can you also submit a small patch upstream to Git plugin to avoid this problem? I think the annotation needs to be dropped 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-41433) Add new API for "permissions"
Title: Message Title James Dumay commented on JENKINS-41433 Re: Add new API for "permissions" Perfect! 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-37211) Support for Docker 1.13 Services (Swarm)
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-37211 Support for Docker 1.13 Services (Swarm) Change By: Patrick Wolf Summary: Support for Docker 1. 12 13 Services (Swarm) 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-41080) java.lang.IllegalStateException: The template variable has no value - since 1.37
Title: Message Title Grégoire Bellon-Gervais resolved as Fixed Version 1.39 fixes this issue. Well done !! Jenkins / JENKINS-41080 java.lang.IllegalStateException: The template variable has no value - since 1.37 Change By: Grégoire Bellon-Gervais 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
[JIRA] (JENKINS-41947) PATH value is being overwritten in declarative pipeline syntax
Title: Message Title
Chima Atufunwa created an issue
Jenkins / JENKINS-41947
PATH value is being overwritten in declarative pipeline syntax
Issue Type:
Bug
Assignee:
Unassigned
Components:
nodejs-plugin
Created:
2017/Feb/11 12:25 AM
Priority:
Major
Reporter:
Chima Atufunwa
Declarative pipeline example:
pipeline {
agent any
stages {
stage('Without NPM'){
steps {
echo PATH
}
}
stage('With NPM'){
tools {
nodejs 'Node v6'
}
steps {
echo PATH
}
}
}
}
Output
[Pipeline] node
Running on master in /data/jenkins/workspace/_playground
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Without NPM)
[Pipeline] echo
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (With NPM)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] echo
/data/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_v6/bin
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
[JIRA] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Brian Herrera edited a comment on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) _ "The correct way to handle this is to extend your triggered/downstream jobs (every "Job B") to accept additional parameters." By enabling in project B the option "This project is parameterized" and adding parameters with the same name as the one passed by the project A. _ Confirming this 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-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Brian Herrera commented on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) _"The correct way to handle this is to extend your triggered/downstream jobs (every "Job B") to accept additional parameters." By enabling in project B the option "This project is parameterized" and adding parameters with the same name as the one passed by the project A. _ Confirming this 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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Nikolas Falco commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) Both commit are valid, I suggest to use latest on that branch. Could you post me the configuration of NodeJS tool, the job config.xml and the output of echo $PATH from a shell script build step please? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) Nikolas Falco, I built plugins from both the custom branch at commit d6c6db7 as well as 2b6255c (just in case some of the post-1.0.1 stuff introduced an issue). After installing them and re-running builds, both of them gave me the same npm: command not found error as the public plugin v1.0.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-41806) Error 500 rest call for Item
Title: Message Title Vivek Pandey commented on JENKINS-41806 Re: Error 500 rest call for Item Manuel Santisteban Need help reproducing it, I installed bitbucket pull request builder plugin and have PR on my bitbucket private repo. Can you provide more details about your job config? This is going to be addressed by JENKINS-40088 where BO won't report this 500 error, but I wanted to keep it as way to verify my fix. The real fix needs to go in to git plugin where https://github.com/jenkinsci/git-plugin/blob/f6ace83fe36740a1ab35612d3b4c5b400647f6ea/src/main/java/hudson/plugins/git/util/Build.java#L87 is incorrectly marked hudson.model.Result as @Exported but Result is not exported bean. 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-41198) Per parallel branch agent configuration
Title: Message Title Andrew Bayer resolved as Duplicate This is covered implicitly by JENKINS-41334 Jenkins / JENKINS-41198 Per parallel branch agent configuration 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-41386) need to support or reject non string based environment variables.
Title: Message Title Andrew Bayer resolved as Duplicate So the implementation in the works for JENKINS-41748 deals with this properly, I believe. Jenkins / JENKINS-41386 need to support or reject non string based environment variables. 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
[JIRA] (JENKINS-41390) Argument not always in location of error
Title: Message Title Andrew Bayer commented on JENKINS-41390 Re: Argument not always in location of error Keith Zantow - is this still an issue with 1.0 or 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-41853) "when" is not recognized as part of the pipeline DSL
Title: Message Title Andrew Bayer commented on JENKINS-41853 Re: "when" is not recognized as part of the pipeline DSL Looks like you're not actually using a Declarative Pipeline? Is this all within a pipeline block? Can you attach your 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-41923) Different pipeline steps are executed in different directories
Title: Message Title Andrew Bayer commented on JENKINS-41923 Re: Different pipeline steps are executed in different directories Can you attach your 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-41876) Not respecting configuration in regards of global modules
Title: Message Title David Weber commented on JENKINS-41876 Re: Not respecting configuration in regards of global modules I can confirm that my configuration is clean. So the xml node for the global modules is not existing in my plugin xml config. 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-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Sean Mitchell commented on JENKINS-40695 Re: Allow running Pipeline shared library functions on executor Running pipeline code generates load on the server, currently our instance is quite small but my fear is that it will be added factor that will force us to go down the road of multiple Jenkins instances and deal with the complexity - much earlier than teams might expect. Or are we meant to take the statement "If you think you need this, you are not using Pipeline correctly" to mean we should not use pipeline for any real logic or flow control? 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-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Sean Mitchell edited a comment on JENKINS-40695 Re: Allow running Pipeline shared library functions on executor Running pipeline code generates load on the server, currently our instance is quite small but my fear is that it will be an added factor that will force us to go down the road of multiple Jenkins instances and deal with the complexity - much earlier than teams might expect. Or are we meant to take the statement "If you think you need this, you are not using Pipeline correctly" to mean we should not use pipeline for any real logic or flow control? 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-41876) Not respecting configuration in regards of global modules
Title: Message Title
Alexander Komarov edited a comment on JENKINS-41876
Re: Not respecting configuration in regards of global modules
I'm seeing the same thing, confirmed no spaces in global npm packages field, saved again.{noformat}00:00:08.923 $ /data/jenkins-slave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin/npm install -g 00:00:09.597 npm ERR! Usage:00:00:09.598 npm ERR! npm cache add 00:00:09.598 npm ERR! npm cache add @00:00:09.598 npm ERR! npm cache add 00:00:09.599 npm ERR! npm cache add 00:00:09.599 npm ERR! 00:00:09.611 ERROR: Build step failed with exception00:00:09.611 java.lang.NullPointerException00:00:09.612 at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:92)00:00:09.612 at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:87)00:00:09.612 at hudson.remoting.UserRequest.perform(UserRequest.java:121)00:00:09.612 at hudson.remoting.UserRequest.perform(UserRequest.java:49)00:00:09.612 at hudson.remoting.Request$2.run(Request.java:324)00:00:09.613 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)00:00:09.613 at java.util.concurrent.FutureTask.run(FutureTask.java:266)00:00:09.613 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)00:00:09.613 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)00:00:09.613 at hudson.remoting.Engine$1$1.run(Engine.java:63)00:00:09.614 at java.lang.Thread.run(Thread.java:745)00:00:09.614 at ..remote call to Channel to /10.130.221.14(Native Method)00:00:09.614 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1435)00:00:09.614 at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)00:00:09.614 at hudson.remoting.Channel.call(Channel.java:795)00:00:09.614 at jenkins.plugins.nodejs.tools.NodeJSInstallation.getExecutable(NodeJSInstallation.java:87)00:00:09.615 at jenkins.plugins.nodejs.NodeJSCommandInterpreter.perform(NodeJSCommandInterpreter.java:96)00:00:09.615 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)00:00:09.615 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)00:00:09.615 at hudson.model.Build$BuildExecution.build(Build.java:205)00:00:09.616 at hudson.model.Build$BuildExecution.doRun(Build.java:162)00:00:09.616 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)00:00:09.616 at hudson.model.Run.execute(Run.java:1728)00:00:09.616 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)00:00:09.616 at hudson.model.ResourceController.execute(ResourceController.java:98)00:00:09.616 at hudson.model.Executor.run(Executor.java:404)00:00:09.617 Build step 'Execute NodeJS script' marked build as failure{noformat}Made a separate job that just has the one npm step with nothing in it (or something simple like 2+2), in this job I only get the above Stacktrace and not the *npm install -g* error.My jenkins home folder (on the node) does not have anything resembling the xml file you requested. Tool config screenshot is attached.!Screenshot_2017-02-10_16-21-49.png|thumbnail!BTW: this worked with 0.2.1, I haven't changed the job or tool config after upgrading just this plugin.
[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-41876 Not respecting configuration in regards of global modules Change By: Alexander Komarov Attachment: Screenshot_2017-02-10_16-21-49.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-41876) Not respecting configuration in regards of global modules
Title: Message Title Alexander Komarov commented on JENKINS-41876 Re: Not respecting configuration in regards of global modules I'm seeing the same thing, confirmed no spaces in global npm packages field, saved again. 00:00:08.923 $ /data/jenkins-slave/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin/npm install -g 00:00:09.597 npm ERR! Usage: 00:00:09.598 npm ERR! npm cache add 00:00:09.598 npm ERR! npm cache add @ 00:00:09.598 npm ERR! npm cache add 00:00:09.599 npm ERR! npm cache add 00:00:09.599 npm ERR! 00:00:09.611 ERROR: Build step failed with exception 00:00:09.611 java.lang.NullPointerException 00:00:09.612 at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:92) 00:00:09.612 at jenkins.plugins.nodejs.tools.NodeJSInstallation$1.call(NodeJSInstallation.java:87) 00:00:09.612 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 00:00:09.612 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 00:00:09.612 at hudson.remoting.Request$2.run(Request.java:324) 00:00:09.613 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 00:00:09.613 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 00:00:09.613 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 00:00:09.613 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 00:00:09.613 at hudson.remoting.Engine$1$1.run(Engine.java:63) 00:00:09.614 at java.lang.Thread.run(Thread.java:745) 00:00:09.614 at ..remote call to Channel to /10.130.221.14(Native Method) 00:00:09.614 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1435) 00:00:09.614 at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) 00:00:09.614 at hudson.remoting.Channel.call(Channel.java:795) 00:00:09.614 at jenkins.plugins.nodejs.tools.NodeJSInstallation.getExecutable(NodeJSInstallation.java:87) 00:00:09.615 at jenkins.plugins.nodejs.NodeJSCommandInterpreter.perform(NodeJSCommandInterpreter.java:96) 00:00:09.615 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 00:00:09.615 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 00:00:09.615 at hudson.model.Build$BuildExecution.build(Build.java:205) 00:00:09.616 at hudson.model.Build$BuildExecution.doRun(Build.java:162) 00:00:09.616 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 00:00:09.616 at hudson.model.Run.execute(Run.java:1728) 00:00:09.616 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 00:00:09.616 at hudson.model.ResourceController.execute(ResourceController.java:98) 00:00:09.616 at hudson.model.Executor.run(Executor.java:404) 00:00:09.617 Build step 'Execute NodeJS script' marked build as failure Made a separate job that just has the one npm step with nothing in it (or something simple like 2+2), in this job I only get the above Stacktrace and not the npm install -g error. My jenkins home folder (on the node) does not have anything resembling the xml file you requested. Tool config screenshot is attached.
[JIRA] (JENKINS-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Nikolas Falco commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) Adam Dille I'm sorry BUT I become the maintainer of this plugin only on late november and the refactoring of this plugin was done by ndeloof (that I know, one of major bee developer). The refactor consist in a major update of Jenkins API for BuildWrapper (steps that contribute the Enviroment) that corrects the wrong way of NodeJS to set the PATH variable similar to Envinject that cause the same issue to other BuildWrapper plugins (see JENKINS-24425 for example). I strongly agree with the work of Nicolas De Loof. I aware of EnvInject issue but a release of NodeJS was expected since a lot of time (14th febrary 2014) to be compatible with Jenkins 2.x. NodeJS and EnvInject plugin are not related (nodejs has not dependences to EnvInject), so I could not stop the develop of this plugin due unresolved issue of other unrelated plugin (like no other plugins does). I could ship NodeJS with the workaround for JENKINS-26583, BUT it's not a best practice that I have to release workaround for issues in other plugin, consider that people could also not have EnvInject installed, and proposed workaround in the branch it's little bit dirty so I do not really want handle its side effect. I had propose to you some valid options: remove EnvInject (you can also push for resolution of JENKINS-26583 or propose a PR) remain to NodeJS 0.2.1 build and install a custom branch in our repository (the same that I have to use in my company) Consider that all this stuff of issue management (and develop of plugin) are done in my free time at the week end or after work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41946) Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
Title: Message Title Cyrille Le Clerc commented on JENKINS-41946 Re: Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes" I am almost sure that there is a different exception bumping jenkins-core to 2.x. I have to prove it. Reference CJP-6364 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-41946) Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-41946 Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes" Issue Type: Bug Assignee: Stephen Connolly Attachments: test.pfx Components: credentials-plugin Created: 2017/Feb/10 10:45 PM Environment: "mvn hpi:run" on the credentials plugin (Jenkins ver. 1.609) Priority: Major Reporter: Cyrille Le Clerc Navigate the "credentials" Create new credentials Type: certificate Scope Global Certificate: Upload PKCS#12 certificate Upload the pkcs#12 file Enter the password Define the ID Click on save You can test with the attached test.pfx , the password is "changeit"
[JIRA] (JENKINS-41926) 100% CPU after update
Title: Message Title Raphael Couto commented on JENKINS-41926 Re: 100% CPU after update And I've tried to disable builtin AV too. 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-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris resolved as Fixed Should work properly in the upcoming 2.1.1 version. Jenkins / JENKINS-41861 New message templates show "is not supported in this context" in Pipeline builds Change By: aldaris 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
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41861 Re: New message templates show "is not supported in this context" in Pipeline builds Code changed in jenkins User: Peter Major Path: src/main/java/jenkins/plugins/hipchat/ext/tokens/CommitMessageMacro.java src/main/java/jenkins/plugins/hipchat/ext/tokens/HipchatChangesMacro.java src/main/java/jenkins/plugins/hipchat/utils/TokenMacroUtils.java http://jenkins-ci.org/commit/hipchat-plugin/8d9167cf7db2791c9278b5da762d0154b810f5f9 Log: JENKINS-41861 Add full support for HIPCHAT_CHANGES* and COMMIT_MESSAGE tokens in pipeline builds 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-41759) Add posibilities to read environment from trusted properties file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41759 Re: Add posibilities to read environment from trusted properties file Code changed in jenkins User: rsandell Path: pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/PropertiesToMapTranslator.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/73ecf2531ce7af560933803b7c41cf351d1476b6 Log: JENKINS-41759 Fixed another regression caused by refactoring 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-41759) Add posibilities to read environment from trusted properties file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41759 Re: Add posibilities to read environment from trusted properties file Code changed in jenkins User: rsandell Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Root.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/998bad3a048f07750a05ef3ead986e3e24c5 Log: JENKINS-41759 Moved getEnvVars into CPS context So we can call steps without barfing Compare: https://github.com/jenkinsci/pipeline-model-definition-plugin/compare/5ad414e35a11...998bad3a048f 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-41759) Add posibilities to read environment from trusted properties file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41759 Re: Add posibilities to read environment from trusted properties file Code changed in jenkins User: rsandell Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Root.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/DeclarativeEnvironmentContributor.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/DeclarativeEnvironmentContributorDescriptor.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/DeclarativeEnvironmentContributorScript.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/Credentials.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/steps/CredentialWrapper.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/PropertiesToMapTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/CredentialsScript.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/331e432fab37266592e39247d3f0befe0bb5af9f Log: JENKINS-41759 First make the function calls in environment extensible Work in Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41759) Add posibilities to read environment from trusted properties file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41759 Re: Add posibilities to read environment from trusted properties file Code changed in jenkins User: rsandell Path: pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/Credentials.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/CredentialsScript.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/d460eaf6442075e0a3189c348e1c2d177116eec8 Log: JENKINS-41759 Fixing failing credentials tests after refactor Some other tests are still failing... 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-41759) Add posibilities to read environment from trusted properties file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41759 Re: Add posibilities to read environment from trusted properties file Code changed in jenkins User: rsandell Path: pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/TrustedProperties.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/TrustedPropertiesScript.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/TrustedPropertiesTest.java pipeline-model-definition/src/test/resources/environmentFromProperties.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/dab2511da72839711128709cba20234d09b272de Log: JENKINS-41759 Read properties file into environment 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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41945 Eventual NPE while running many concurrent declarative pipelines Change By: Andrew Bayer Environment: openjdk version "1.8.0_45-internal"Ubuntu 15.04 workflow-cps 2.26pipeline-model-definition 1.0.1core 2.32.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Andrew Bayer commented on JENKINS-41945 Re: Eventual NPE while running many concurrent declarative pipelines FYI - this line is the problem line in workflow-cps 2.26, which is what's installed. The NPE seems to be that classInfo is null. 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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Andrew Bayer assigned an issue to Jesse Glick Jenkins / JENKINS-41945 Eventual NPE while running many concurrent declarative pipelines Change By: Andrew Bayer Assignee: Andrew Bayer Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41945 Eventual NPE while running many concurrent declarative pipelines Change By: Andrew Bayer Component/s: workflow-cps-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-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title
Karl Shultz created an issue
Jenkins / JENKINS-41945
Eventual NPE while running many concurrent declarative pipelines
Issue Type:
Bug
Assignee:
Andrew Bayer
Attachments:
jenkins.log
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/10 10:11 PM
Environment:
openjdk version "1.8.0_45-internal" Ubuntu 15.04
Priority:
Major
Reporter:
Karl Shultz
After an hour or so of running 101 concurrent "hello world" pipeline scripts, the Jenkins server becomes unresponsive. The first signs of trouble in the log around here - I'll attach the entire log as well. The attached one probably has a bunch of noise in it from some earlier work. The pipeline script itself looks exactly like this:
pipeline {
agent any
stages {
stage("TestingTesting") {
steps {
sh 'echo Hello world'
}
}
}
}
INFO: DeclarativePipelines/inlineThing34 #32 completed: SUCCESS
Feb 10, 2017 8:27:44 PM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution cleanUpHeap
WARNING: failed to clean up memory from
[JIRA] (JENKINS-41602) Global Shared Library git ref overrides the project repo git info
Title: Message Title Scott Russell commented on JENKINS-41602 Re: Global Shared Library git ref overrides the project repo git info Jesse Glick - Okay, great, thank you. The goal anyway of the global-library for my team was to enable multibranch projects, where we could conditionally execute pipelines based upon branch awareness (e.g., deployment stages only on integration branches), so we will use bitbucket-branch-source instead of bitbucket-build-status. We are still blocked by JENKINS-41497 generally from adopting global-library, however. 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-32807) Jenkins openshift plugin not working
Title: Message Title
Adil Chahid commented on JENKINS-32807
Re: Jenkins openshift plugin not working
Same here Caused by: com.openshift.internal.client.httpclient.HttpClientException: { "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "User \"system:anonymous\" cannot \"get\" on \"/broker/rest/api\"", "reason": "Forbidden", "details": {}, "code": 403 }
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-39190) Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure
Title: Message Title Alexander Leibzon resolved as Fixed fixed in v0.2.5 Jenkins / JENKINS-39190 Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure Change By: Alexander Leibzon 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
[JIRA] (JENKINS-34922) NullPointerException Creating and Resolving Issues
Title: Message Title Alexander Leibzon updated JENKINS-34922 Jenkins / JENKINS-34922 NullPointerException Creating and Resolving Issues Change By: Alexander Leibzon 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-34922) NullPointerException Creating and Resolving Issues
Title: Message Title Alexander Leibzon started work on JENKINS-34922 Change By: Alexander Leibzon 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-34922) NullPointerException Creating and Resolving Issues
Title: Message Title Alexander Leibzon updated JENKINS-34922 Fixed in v0.2.5 Jenkins / JENKINS-34922 NullPointerException Creating and Resolving Issues Change By: Alexander Leibzon 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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title
Adam Dille edited a comment on JENKINS-41857
Re: Correct path for installation is not provided to system/shells (build.steps)
Those are some _horrible_ workarounds [~nfalco] . Since the EnvInject issue has existed since at least January 2015, something was obviously removed from the NodeJS plugin that was allowing {{npm}} commands to function prior to v1.0. I understand that the root problem is an EnvInject plugin issue, but you've just broken a bunch of users (including my company and all of our Node-dependent builds), in place, by removing the workaround. This is bad form. You don't force another project to fix their issues by breaking your product for a bunch of your own users. And my options are to uninstall another plugin and break 75% of our builds, or start rolling custom plugin builds? Really?
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-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) Those are some horrible workarounds. Since the EnvInject issue has existed since at least January 2015, something was obviously removed from the NodeJS plugin that was allowing npm commands to function prior to v1.0. I understand that the root problem is an EnvInject plugin issue, but you've just broken a bunch of users (including my company and all of our Node-dependent builds), in place, by removing the workaround. This is bad form. You don't force another project to fix their issues by breaking your product for a bunch of your own users. And my options are to uninstall another plugin and break 75% of our builds, or start rolling custom plugin builds? Really? 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-41944) Unable to understand when AbortError is created by user`s action like pressing button Stop
Title: Message Title Oleg Korsak commented on JENKINS-41944 Re: Unable to understand when AbortError is created by user`s action like pressing button Stop How about UserAbortException ? 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-41944) Unable to understand when AbortError is created by user`s action like pressing button Stop
Title: Message Title
Oleg Korsak created an issue
Jenkins / JENKINS-41944
Unable to understand when AbortError is created by user`s action like pressing button Stop
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Feb/10 9:38 PM
Priority:
Major
Reporter:
Oleg Korsak
This doesn't help and actually looks like a veeery huge hack:
try {
sh "bash do_magic.sh"
do_another_magic()
} catch (hudson.AbortException e) {
if (e.getMessage().contains('script returned exit code 143')) {
echo "aborted by user"
throw e
} else {
echo "aborted by error, continuing next stage"
}
}
Add Comment
[JIRA] (JENKINS-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Kenneth Brooks edited a comment on JENKINS-40695 Re: Allow running Pipeline shared library functions on executor Help me understand how this scenario should work if I'm "using pipelines correctly"Background: All of this should be happening on a slave node (that isn't on the same filesystem as the master).* Run a command to checkout files (could be "checkout scm" step)* Get a handle to one of the files that was checked out and do something with the contents via a shared library in the vars/ directory.This doesn't work today as the shared library will run on the master, yet the files were checked out on the node.How else would we accomplish this functionality? This severely limits the usefulness of any java code inside the global libraries if they can't interact with anything on the nodes, does it not? We aren't asking for the whole pipeline script itself to run on a node. We are asking how to get a cps global lib to run on the node. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Kenneth Brooks reopened an issue Help me understand how this scenario should work if I'm "using pipelines correctly" Background: All of this should be happening on a slave node (that isn't on the same filesystem as the master). Run a command to checkout files (could be "checkout scm" step) Get a handle to one of the files that was checked out and do something with the contents via a shared library in the vars/ directory. This doesn't work today as the shared library will run on the master, yet the files were checked out on the node. How else would we accomplish this functionality? This severely limits the usefulness of any java code inside the global libraries if they can't interact with anything on the nodes, does it not? Jenkins / JENKINS-40695 Allow running Pipeline shared library functions on executor Change By: Kenneth Brooks Resolution: Won't Do Status: Resolved Reopened Assignee: Jesse Glick Add Comment
[JIRA] (JENKINS-41943) DP should have an easy way to say don't run subsequent steps if result is set.
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-41943
DP should have an easy way to say don't run subsequent steps if result is set.
Change By:
James Nord
If I have a pipeline with a lot of stages* run unit tests* run smoke tests* run quick ATH* run slow ATH* deploy to staging* run UAT* run even more testsIf anything sets the build result to anything other than SUCCESS in one of the stages (e.g. unit test failures and junit plugin -> UNSTABLE) then I do not want to run the subsequent tests.Currently I have to remebmer remember to put the following on every stage - which is cumbersome and error prone.{noformat}when { _expression_ { currentBuild.result == null } }{noformat}It would be useful if there was a config option like {{skipSubsequentStagesWhenNotSucessfull : true}} at the top level which could be overridden by a stage if needed (e.g. a final reporter stage...)Obviously the configuration name above is bad - but just for example...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41943) DP should have an easy way to say don't run subsequent steps if result is set.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-41943 DP should have an easy way to say don't run subsequent steps if result is set. Change By: James Nord Summary: DP should have an easy way to say don ; ' t run subsequent steps if result is set. 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-41943) DP should have an easy way to say don;t run subsequent steps if result is set.
Title: Message Title
Jesse Glick commented on JENKINS-41943
Re: DP should have an easy way to say don;t run subsequent steps if result is set.
Actually I guess you could have
post {unstable {error message: 'Not continuing', result: 'UNSTABLE'}}
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-41943) DP should have an easy way to say don;t run subsequent steps if result is set.
Title: Message Title Jesse Glick commented on JENKINS-41943 Re: DP should have an easy way to say don;t run subsequent steps if result is set. JENKINS-27092 would provide a more straightforward approach for scripted Pipelines. Probably it could not be used from Declarative (without a script step). 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-36027) Build is failing
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-36027 Build is failing Change By: Victor Martinez Component/s: other Component/s: jenkinslint-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-41615) Problem while checking for updates in Jenkins
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-41615 Problem while checking for updates in Jenkins Change By: Victor Martinez Component/s: workflow-aggregator-plugin Component/s: jenkinslint-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-39499) There is no way to set changeSet property of shared library checkout to false
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39499 There is no way to set changeSet property of shared library checkout to false Change By: Jesse Glick 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-38281) Global variables starting with capital letter regression
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38281 Global variables starting with capital letter regression Change By: Jesse Glick Labels: robustness 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-39565) Global function with no parameters silently ignored when called without parenthesis
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-39565 Global function with no parameters silently ignored when called without parenthesis Change By: Jesse Glick 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39615 Global Pipeline Libraries triggers the 'poll SCM' of jobs Change By: Jesse Glick 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-41943) DP should have an easy way to say don;t run subsequent steps if result is set.
Title: Message Title
James Nord created an issue
Jenkins / JENKINS-41943
DP should have an easy way to say don;t run subsequent steps if result is set.
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/10 9:00 PM
Priority:
Minor
Reporter:
James Nord
If I have a pipeline with a lot of stages
run unit tests
run smoke tests
run quick ATH
run slow ATH
deploy to staging
run UAT
run even more tests
If anything sets the build result to anything other than SUCCESS in one of the stages (e.g. unit test failures and junit plugin -> UNSTABLE) then I do not want to run the subsequent tests. Currently I have to remebmer to put the following on every stage - which is cumbersome and error prone.
when { _expression_ { currentBuild.result == null } }
It would be useful if there was a config option like skipSubsequentStagesWhenNotSucessfull : true at the top level which could be overridden by a stage if needed (e.g. a final reporter stage...) Obviously the configuration name above is bad - but just for example...
[JIRA] (JENKINS-41339) Environment variables referencing other variables broken
Title: Message Title Daniel Beck commented on JENKINS-41339 Re: Environment variables referencing other variables broken How do I get back to working pipelines? Try actually restarting. Downgrading needs a restart. 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-40046) Add option to disable internal shared library
Title: Message Title Jesse Glick resolved as Won't Do The internal library system is deprecated. Just push a tombstone commit to it deleting all files. If someone tries to push something new, they will get a merge conflict and figure it out. Jenkins / JENKINS-40046 Add option to disable internal shared library Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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
[JIRA] (JENKINS-40129) Extend GitChangeSet to get the repository name
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40129 Extend GitChangeSet to get the repository name currentBuild.rawBuild.changeSets is deprecated; use currentBuild.changeSets. Probably there should be something in the form of a map, keyed by SCM.getKey(). Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: workflow-cps-global-lib-plugin Labels: changelog pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40055) p4-plugin exception when used with the shared pipeline libraries plugin. p4.tasks.AbstractTask.setEnvironment
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40055 p4-plugin exception when used with the shared pipeline libraries plugin. p4.tasks.AbstractTask.setEnvironment Change By: Jesse Glick Component/s: workflow-cps-global-lib-plugin Labels: 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-41339) Environment variables referencing other variables broken
Title: Message Title John Mellor commented on JENKINS-41339 Re: Environment variables referencing other variables broken I do not see a 1.14 plugin available, so I assume that this fix is in fact not released yet. As per the conversation in https://groups.google.com/forum/#!msg/jenkinsci-users/LN057YL_Xis/wyIBfAbfCwAJ, I downgraded the durable tasks plugin from 1.13 to 1.12 and the pipeline plugins to try to work around this killer bug. Interestingly, this apparently does not require a reboot (not sure if that is another bug or not). However, after reverting the plugin, I still cannot run simple shell commands as part of the pipeline. How do I get back to working pipelines? 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-40150) Git operations fail after global lib is loaded
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40150 Git operations fail after global lib is loaded Use status notifications from github-branch-source, which will track SCMRevisionAction, or make GitHubCommitStatusSetter do the same. Change By: Jesse Glick Component/s: github-plugin Component/s: workflow-cps-global-lib-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
[JIRA] (JENKINS-40285) global libraries test harness
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-40285 global libraries test harness Change By: Jesse Glick 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-40323) No SCM selected when adding a shared library
Title: Message Title
Jesse Glick commented on JENKINS-40323
Re: No SCM selected when adding a shared library
James Dumay yes, legacy means
you must use the ${library.NAME.version} hack
there is unlikely to be support for @abc1234 and generally selecting anything other than a branch head
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.
