[JIRA] (JENKINS-49666) Error while building project
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49666 Error while building project Change By: Oleg Nenashev Component/s: maven-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49665) Failed intial boot attempt.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49665 Failed intial boot attempt. Change By: Oleg Nenashev Component/s: _unsorted Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49665) Failed intial boot attempt.
Title: Message Title Oleg Nenashev commented on JENKINS-49665 Re: Failed intial boot attempt. Please provide system logs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49667) Swarm plugin should print to log if job fails because of full disk
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49667 Swarm plugin should print to log if job fails because of full disk Change By: Oleg Nenashev Component/s: _unsorted Component/s: swarm-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49667) Swarm plugin should print to log if job fails because of full disk
Title: Message Title Oleg Nenashev commented on JENKINS-49667 Re: Swarm plugin should print to log if job fails because of full disk Sounds like a valid feature request, but generally it requires some changes on the Jenkins/Remoting side. Build events are generally not redirected to agent logs though it could be relatively easy to do that. The problem is to define a criteria for "when should it be done?" Please provide a full stacktrace so that I can identify from where this particular message comes in your case Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49667) Swarm plugin should print to log if job fails because of full disk
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49667 Swarm plugin should print to log if job fails because of full disk Change By: Oleg Nenashev Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49667) Swarm plugin should print to log if job fails because of full disk
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-49667 Swarm plugin should print to log if job fails because of full disk Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49667) Swarm plugin should print to log if job fails because of full disk
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49667 Swarm plugin should print to log if job fails because of full disk Change By: Oleg Nenashev Component/s: remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title Carlos Sanchez commented on JENKINS-49660 Re: Unable to configure plugin using ibm k8s typically you would create a ServiceAccount in k8s and use its token for authentication. oidc could work if you use refresh-token as token but it has an expiration time Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49224) Rebuild plugin (v1.25) does not remember merge request params
Title: Message Title alex d updated an issue Jenkins / JENKINS-49224 Rebuild plugin (v1.25) does not remember merge request params Change By: alex d Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49527) Use Global rule Parsing is not working
Title: Message Title pramendra kumar commented on JENKINS-49527 Re: Use Global rule Parsing is not working Can anyone please look into this issue. It's really required feature which is not working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Andreas Tscharner commented on JENKINS-46067 Re: Pipeline task scheduled on uninitialized node We have the same problem on Jenkins 2.60.3, host system is Debian 9, with KVM/QEMU and the libvirt plugin. OS on the VMs is Windows 7 with the Jenkins service installed. We have configured the VMs to shutdown after each job and to revert to a certain snapshot when shutting down. We have noticed that the machines do not shut down every time, especially if there is heavy load (lots of jobs in the queue) or if the job failed during compilation. And if they do not shut down, this error appears Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar assigned an issue to Denys Digtiar Jenkins / JENKINS-49668 Root CAs component appears broken Change By: Denys Digtiar Assignee: Denys Digtiar Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-49668 Root CAs component appears broken Issue Type: Bug Assignee: Unassigned Components: support-core-plugin Created: 2018-02-21 07:35 Environment: core 2.89.4 support-core 2.44 Java 1.8.0_121 Priority: Minor Reporter: Denys Digtiar It looks the component just tries to list an uninitialized KeyStore which results in: java.security.KeyStoreException: Uninitialized keystore at java.security.KeyStore.aliases(KeyStore.java:1233) at com.cloudbees.jenkins.support.impl.RootCAs.getRootCAList(RootCAs.java:149) at com.cloudbees.jenkins.support.impl.RootCAs$GetRootCA.call(RootCAs.java:132) at com.cloudbees.jenkins.support.impl.RootCAs$GetRootCA.call(RootCAs.java:125) at hudson.remoting.LocalChannel$1.call(LocalChannel.java:52) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) For reference on how to do it: https://stackoverflow.com/questions/8884831/listing-certificates-in-jvm-trust-store https://github.com/jenkinsci/jenkins-scripts/pull/82/files
[JIRA] (JENKINS-49667) Swarm plugin should print to log if job fails because of full disk
Title: Message Title Juho Saarinen created an issue Jenkins / JENKINS-49667 Swarm plugin should print to log if job fails because of full disk Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 2018-02-21 07:10 Priority: Minor Reporter: Juho Saarinen When running swarm slaves as Openshift containers, we have seen multiple times job failing with error: [INFO] IOError: No space left on device Problem is, that this is not printed to slave's own log, so there's no easy way to handle that situation automatically. Would it be possible to get that also printed to slave's stdout/stderr? Add Comment
[JIRA] (JENKINS-49666) Error while building project
Title: Message Title Jino philp updated an issue Jenkins / JENKINS-49666 Error while building project Change By: Jino philp *Error Message* *Running jenkins using war* * Selenium 3.8.1 maven-compiler-plugin 2.4 * maven-surefire-plugin 2.7.1 * testng6.8 Started by user [anonymous|http://localhost:8080/user/unknown] Building in workspace C:\Users\Jino\.jenkins\jobs\Zmarta _Sweden\workspace No emails were triggered. Parsing POMs Modules changed, recalculating dependency graph Established TCP socket on 60517 [Zmarta_se] $ "C:\Program Files\Java\jdk1.8.0_151/bin/java" -cp "C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven33-agent-1.8.1.jar;E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2\boot\plexus-classworlds-2.5.2.jar;E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2/conf/logging" jenkins.maven3.agent.Maven33Main "E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2" C:\Users\Jino\.jenkins\war\WEB-INF\lib\remoting-3.15.jar C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven33-interceptor-1.8.1.jar C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.8.1.jar 60517 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f E:\Jino_testing\Git_Hub\Zmarta_se\pom.xml clean install java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven33Main.launch(Maven33Main.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.maven.Maven3Builder.call(Maven3Builder.java:133) at hudson.maven.Maven3Builder.call(Maven3Builder.java:68) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.settings(DefaultMavenExecutionRequestBuilder.java:658) at
[JIRA] (JENKINS-49666) Error while building project
Title: Message Title Jino philp updated an issue Jenkins / JENKINS-49666 Error while building project Change By: Jino philp *Error Message* Started by user [anonymous|http://localhost:8080/user/unknown]Building in workspace C:\Users\Jino\.jenkins\jobs\Zmarta _Sweden\workspaceNo emails were triggered.Parsing POMsModules changed, recalculating dependency graphEstablished TCP socket on 60517[Zmarta_se] $ "C:\Program Files\Java\jdk1.8.0_151/bin/java" -cp "C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven33-agent-1.8.1.jar;E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2\boot\plexus-classworlds-2.5.2.jar;E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2/conf/logging" jenkins.maven3.agent.Maven33Main "E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2" C:\Users\Jino\.jenkins\war\WEB-INF\lib\remoting-3.15.jar C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven33-interceptor-1.8.1.jar C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.8.1.jar 60517<===[JENKINS REMOTING CAPACITY]===>channel startedExecuting Maven: -B -f E:\Jino_testing\Git_Hub\Zmarta_se\pom.xml clean installjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven33Main.launch(Maven33Main.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.maven.Maven3Builder.call(Maven3Builder.java:133) at hudson.maven.Maven3Builder.call(Maven3Builder.java:68) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.settings(DefaultMavenExecutionRequestBuilder.java:658) at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.getMavenExecutionRequest(DefaultMavenExecutionRequestBuilder.java:149) at
[JIRA] (JENKINS-49666) Error while building project
Title: Message Title Jino philp created an issue Jenkins / JENKINS-49666 Error while building project Issue Type: Bug Assignee: Unassigned Components: pom2config-plugin Created: 2018-02-21 07:02 Priority: Blocker Reporter: Jino philp Started by user anonymous Building in workspace C:\Users\Jino\.jenkins\jobs\Zmarta _Sweden\workspace No emails were triggered. Parsing POMs Modules changed, recalculating dependency graph Established TCP socket on 60517 [Zmarta_se] $ "C:\Program Files\Java\jdk1.8.0_151/bin/java" -cp "C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven33-agent-1.8.1.jar;E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2\boot\plexus-classworlds-2.5.2.jar;E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2/conf/logging" jenkins.maven3.agent.Maven33Main "E:\Jino_testing\Test Automation\Maven\apache-maven-3.5.2" C:\Users\Jino\.jenkins\war\WEB-INF\lib\remoting-3.15.jar C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven33-interceptor-1.8.1.jar C:\Users\Jino\.jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.8.1.jar 60517 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f E:\Jino_testing\Git_Hub\Zmarta_se\pom.xml clean install java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven33Main.launch(Maven33Main.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at
[JIRA] (JENKINS-49643) java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79
Title: Message Title santhosh s commented on JENKINS-49643 Re: java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79 Thanks Andrew for the update.. Is there any resolution without updating the plugins? Regards, Santhosh Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49665) Failed intial boot attempt.
Title: Message Title John Daniel Babu created an issue Jenkins / JENKINS-49665 Failed intial boot attempt. Issue Type: Bug Assignee: Unassigned Attachments: Localhost.png Components: core Created: 2018-02-21 05:55 Environment: Windows 8.1, Java version 8, jenkins 2.89.4 Priority: Blocker Reporter: John Daniel Babu Hi Team, I installed Jenkins 2.89.4 locally on OS windows 8 and done all the setup of java as well. however installer is opening a blank white screen in my browser. Please find the attachment. i have checked all over, didn't got a solution.Please help with the same. Add Comment
[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Ralph Goers commented on JENKINS-49625 Re: Config pages of Maven jobs do no load Please take a look at the workaround we found for JENKINS-49630. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49618) Display Remoting version in the agent log when starting up the agent
Title: Message Title Willy Aguirre commented on JENKINS-49618 Re: Display Remoting version in the agent log when starting up the agent Hi Oleg Nenashev, Could you tell me more how to I can fix this? please Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44143) ECR plugin: no basic auth credentials
Title: Message Title Peter Brunner commented on JENKINS-44143 Re: ECR plugin: no basic auth credentials Tom Manterfield a question for you, if you will. I too ran into this problem and noticed that the $JENKINS_HOME that this ECR plugin runs with differed from the $JENKINS_HOME that the docker plugin used. This essentially caused the config.json to be written to one place while docker looked in another. Was this the case for you too? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49664) ThinBackup Multi-Branch Branches Directory and SSH Key
Title: Message Title Mitchell Maler created an issue Jenkins / JENKINS-49664 ThinBackup Multi-Branch Branches Directory and SSH Key Issue Type: Bug Assignee: Thomas Fürer Components: thinbackup-plugin Created: 2018-02-21 02:47 Priority: Minor Reporter: Mitchell Maler Hello, I tried testing a restore of a Jenkins Master using a ThinBackup Full Backup but once I did the multi-branch jobs did not have their branches or indexes folder. This causes a loss of build history especially the develop and master branches. I also noticed the ssh key that jenkins generates is not backed up which causes issues when trying to run/scan a multi-branch job after a restore. Either make sure the multi-branch jobs are backed up correctly or please allow for an option to just back up everything in the jeknins_home directory with exclusions. Add Comment
[JIRA] (JENKINS-47858) ERROR: RocketChat notification failed in login sequence
Title: Message Title Martin Reinhardt commented on JENKINS-47858 Re: ERROR: RocketChat notification failed in login sequence you can try if this one solves it: https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/rocketchatnotifier-alpha/1.2.1-SNAPSHOT/rocketchatnotifier-alpha-1.2.1-20180221.021551-2.jar Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49467) Jenkins credential issue
Title: Message Title rang cui updated an issue Jenkins / JENKINS-49467 Jenkins credential issue Change By: rang cui Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error
Title: Message Title Denys Digtiar commented on JENKINS-45575 Re: Multiple assignment in pipeline fails with LHS Error Andrew Bayer It sound's like I don't need to raise a separate script-security ticket after all. Correct? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34403) docker build fails if Dockerfile pip-installs simplejson
Title: Message Title Jon Hermansen closed an issue as Fixed The fix is released in 1.7.3, closing. Jenkins / JENKINS-34403 docker build fails if Dockerfile pip-installs simplejson Change By: Jon Hermansen Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-31137) Dependency to Maven 2.12 is not optional
Title: Message Title Jon Hermansen commented on JENKINS-31137 Re: Dependency to Maven 2.12 is not optional This is fixed in 1.7.3, which was released last night. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31137) Dependency to Maven 2.12 is not optional
Title: Message Title Jon Hermansen resolved as Fixed Jenkins / JENKINS-31137 Dependency to Maven 2.12 is not optional Change By: Jon Hermansen Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46706) "default to blue ocean" setting
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-46706 "default to blue ocean" setting Change By: Michael Neale Code for this available on: https://github.com/jenkinsci/blueocean-plugin/pull/1658 As suggested by Daniel Beck, it would be a good idea if blue ocean had a jenkins config setting that made the home page default to /blue (Tyler has done this with nginx rules before). This is a necessary precursor to making blue the default out of box experience/entry point, allowing people to opt in. In scope: * When set, accessing the root will redirect to /blue * Existing links back to classic will keep working * Configured in settings, but also via system property/env variable (off by default initially)Testing: * Should be tested via ATH in blue ocean * Need to ensure that links back to classic are not broken and "cool urls don't change" * Ensure only links to root redirect to /blue * Ensure that there are not any side effects (people using queries against root, for example) - investigation needed here. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-46706) "default to blue ocean" setting
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-46706 "default to blue ocean" setting Change By: Michael Neale Sprint: Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2, Blue Ocean 1.5 - beta 1 Candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46706) "default to blue ocean" setting
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-46706 "default to blue ocean" setting Change By: Michael Neale Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46706) "default to blue ocean" setting
Title: Message Title Michael Neale stopped work on JENKINS-46706 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46706) "default to blue ocean" setting
Title: Message Title Michael Neale updated JENKINS-46706 Jenkins / JENKINS-46706 "default to blue ocean" setting Change By: Michael Neale Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49647) Build Trigger Gitlab Merge Requests Builder java.io.FileNotFoundException ... api/v3/project
Title: Message Title Owen Mehegan commented on JENKINS-49647 Re: Build Trigger Gitlab Merge Requests Builder java.io.FileNotFoundException ... api/v3/project GitLab Plugin and GitLab Merge Request Builder are two different plugins that accomplish similar things. No need to reference GitLab Plugin if your bug/issue was in the other one. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49647) Build Trigger Gitlab Merge Requests Builder java.io.FileNotFoundException ... api/v3/project
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-49647 Build Trigger Gitlab Merge Requests Builder java.io.FileNotFoundException ... api/v3/project Change By: Owen Mehegan Component/s: gitlab-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42599) Newly added module locations' / additional credentials' "Add" credential button seems out of work
Title: Message Title Raphael Pionke updated an issue Jenkins / JENKINS-42599 Newly added module locations' / additional credentials' "Add" credential button seems out of work Change By: Raphael Pionke Component/s: credentials-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48588) Artifacts uploaded to S3 does not show up in Blue Ocean
Title: Message Title James Dumay commented on JENKINS-48588 Re: Artifacts uploaded to S3 does not show up in Blue Ocean Ilya Kulakov we query the run for its artifacts, transform them to a BlueArtifact model and display them. In order to get S3 plugin to display, you would need something like what I wrote in PR-113. I won't be implementing this but it should be a start for someone here who wants to. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title Steve Szabo commented on JENKINS-49660 Re: Unable to configure plugin using ibm k8s Using the basic token format works: users: - name: usern...@company.com user: token: AAA This version does not work: users: - name: usern...@company.com user: auth-provider: name: oidc config: client-id: bx client-secret: bx id-token: AAA idp-issuer-url: https://iam.ng.bluemix.net/kubernetes refresh-token: BBB Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title Steve Szabo updated an issue Jenkins / JENKINS-49660 Unable to configure plugin using ibm k8s Change By: Steve Szabo Attachment: config.token.fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Michael Neale updated JENKINS-48571 Jenkins / JENKINS-48571 checkout scm fails silently after "Could not determine exact tip revision of " in logs Change By: Michael Neale Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Michael Neale commented on JENKINS-39628 Re: Handle skipped stages and parallels in the Pipeline Graph Nat Sr not explicitly no - but like Josh says, could have an input step in an earlier stage that captures some environment variable that is then referred to in 'when'. A parametrised job could also provide the same variable I think. Can't put an input inside a 'when' (I think). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Michael Neale commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs ok good to know - I might close this now given the 'id' solution and the blue ocean fix. there is a linked follow on ticket to make the api (specifically for jobDSL) clearer here. Feel free to reopen if new information. R. Tyler Croy ok - well that fits with the theory, so that is good. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Josh McDonald commented on JENKINS-39628 Re: Handle skipped stages and parallels in the Pipeline Graph I imagine you'd achieve that easily enough with an input step to set a variable? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title
Nat Sr commented on JENKINS-39628
Re: Handle skipped stages and parallels in the Pipeline Graph
James Dumay Josh McDonald Hi guys, I wonder instead of adding "when{}" to determine whether the stage will be skipped or not, can we have user input feature to ask if they want to skip the stage or not. Do we have this feature too?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error
Title: Message Title Andrew Bayer commented on JENKINS-45575 Re: Multiple assignment in pipeline fails with LHS Error So this was my dumb mistake - I added support for multiple assignments...but only in non-sandboxed mode. Oops. Anyway, https://github.com/cloudbees/groovy-cps/pull/81 adds multiple assignment support in sandbox as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error
Title: Message Title Andrew Bayer started work on JENKINS-45575 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error
Title: Message Title Andrew Bayer updated JENKINS-45575 Jenkins / JENKINS-45575 Multiple assignment in pipeline fails with LHS Error Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48198) "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title
Title: Message Title Josh McDonald commented on JENKINS-48198 Re: "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title Not really. Once we have per-property skipability, it will get better in that we won't have partially-formed runs bringing the UI down, but instead we would just get a 500 (or some runs would be missing from the response completely, if it's a list). But I don't really know enough to diagnose why those runs' executions can't be iterated properly when attempting to create the nodes - the root exception is coming from non-BlueOcean code, so I'm not particularly familiar with it. Somebody on the pipeline team might have something more useful to add, though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45774) Cannot find files from reports generated in parallel
Title: Message Title Karol Woźniak commented on JENKINS-45774 Re: Cannot find files from reports generated in parallel Thank you for the response. Yes, this would probably be the simplest road, but it does not sound like a correct solution. As I've mentioned earlier, this is not a tool specific issue, so we'd have to workaround it like this in every parser [that we use]. I'd hope that it can be tracked down (or up?) to why this actually happens. For now, we're just not using parallel there, so it's not a deal breaker, but it is annoying . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48198) "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title
Title: Message Title Vivek Pandey commented on JENKINS-48198 Re: "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title Øyvind Rørtveit Not necessarily fixed. Josh has added some more server side logging to help see whats blowing up in server side resulting in to UI showing this error. Josh McDonald do you have more ideas on what else can be done on it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title Steve Szabo commented on JENKINS-49660 Re: Unable to configure plugin using ibm k8s Have you tested the plugin using a token? token Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49663) pre-authentication information leak from cli's add-job-to-view
Title: Message Title Assaf Berg updated an issue Jenkins / JENKINS-49663 pre-authentication information leak from cli's add-job-to-view Change By: Assaf Berg When accessing the CLI over HTTP without authentication getting different error messages which allows an attacker to deduce existence of views: When the view exists getting the correct message:$ java -jar jenkins-cli.jar -s [ https://my-jenkins |https://my-jenkins/] add-job-to-view ExistingView SomeJobERROR: anonymous is missing the View/Read permission When the view doesn't exist getting a different message:$ java -jar jenkins-cli.jar -s [ https://my-jenkins |https://my-jenkins/] add-job-to-view NonExistingView SomeJobERROR: No view named NonExistingView inside view Jenkins I think the permission check should be done first to avoid leaking information. Although this information doesn't seem critical this behavior is worrying and there might be other (or future) cases where critical information will be revealed to unauthenticated users. May be related to JENKINS-43963 although that issue is not concerned with security but rather usability. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49663) pre-authentication information leak from cli's add-job-to-view
Title: Message Title Assaf Berg created an issue Jenkins / JENKINS-49663 pre-authentication information leak from cli's add-job-to-view Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-20 23:12 Environment: Jenkins 2.89.4 (using the official docker image) Security enabled (authenticated users can do anything) Remoting disabled Labels: security Priority: Minor Reporter: Assaf Berg When accessing the CLI over HTTP without authentication getting different error messages which allows an attacker to deduce existence of views: When the view exists getting the correct message: $ java -jar jenkins-cli.jar -s https://my-jenkins add-job-to-view ExistingView SomeJob ERROR: anonymous is missing the View/Read permission When the view doesn't exist getting a different message: $ java -jar jenkins-cli.jar -s https://my-jenkins add-job-to-view NonExistingView SomeJob ERROR: No view named NonExistingView inside view Jenkins I think the permission check should be done first to avoid leaking information. Although this information doesn't seem critical this behavior is worrying and there might be other (or future) cases where critical information will be revealed to unauthenticated users.
[JIRA] (JENKINS-46532) Got "Error rendering PipelineRunGraph: TypeError: nodeStage is undefined" when removed steps from previous run
Title: Message Title Nat Sr commented on JENKINS-46532 Re: Got "Error rendering PipelineRunGraph: TypeError: nodeStage is undefined" when removed steps from previous run Thanks, yes I updated it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title
Kevin Lannen created an issue
Jenkins / JENKINS-49662
Ability to create custom stages in parallel blocks in pipeline shared library
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2018-02-20 22:46
Priority:
Minor
Reporter:
Kevin Lannen
I would like to be able to easily run the same steps across multiple nodes using the declarative pipeline and a shared library. This does not currently seem to be possible since only custom steps can be created in shared libraries. Example jenkinsfile:
pipeline {
agent any
stages {
stage('Build everywhere') {
runOnAllPlatforms {
sh 'doing build things'
}
}
}
}
Example shared library vars/runOnAllPlatforms.groovy:
def call(Closure body) {
parallel {
stage('RHEL') {
agent {
node { label 'rhel7' }
}
steps {
body()
}
stage('Apple') {
agent {
node { label 'apple' }
}
steps {
body()
}
steps {
body()
}
}
}
[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error
Title: Message Title Andrew Bayer commented on JENKINS-45575 Re: Multiple assignment in pipeline fails with LHS Error Denys Digtiar - Sorry for the late response. Yes, that'd be a separate issue specific to script-security. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22637) "Copy Artifacts Plugin" should support ArtifactManager
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-22637 "Copy Artifacts Plugin" should support ArtifactManager Change By: Jesse Glick Labels: plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Bayer commented on JENKINS-49558 Re: Run stages in separate Docker containers when top level agent declared Oh, and I went with an option instead of a flag on docker and dockerfile - the option is containerPerStage(). I feel like this may be relevant in other agent types down the road, so wanted to decouple the syntax from the Docker/Dockerfile implementations. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Bayer started work on JENKINS-49558 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Bayer commented on JENKINS-49558 Re: Run stages in separate Docker containers when top level agent declared PR up adding this at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/246 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Bayer updated JENKINS-49558 Jenkins / JENKINS-49558 Run stages in separate Docker containers when top level agent declared Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49649) JEP-200: Filesystem list parameter plugin: java.util.Formatter
Title: Message Title Oleg Nenashev started work on JENKINS-49649 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49649) JEP-200: Filesystem list parameter plugin: java.util.Formatter
Title: Message Title Oleg Nenashev updated JENKINS-49649 Jenkins / JENKINS-49649 JEP-200: Filesystem list parameter plugin: java.util.Formatter Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49649) JEP-200: Filesystem list parameter plugin: java.util.Formatter
Title: Message Title Oleg Nenashev commented on JENKINS-49649 Re: JEP-200: Filesystem list parameter plugin: java.util.Formatter Apparently there is a proposed fix for that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title Andrew Bayer updated JENKINS-49542 Merged, will be included in the next script-security release (which should be 1.42). Jenkins / JENKINS-49542 Scripts not permitted to use method java.util.Map isEmpty Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-49650) JEP-200: Unreliable Slave plugin: javax.mail.internet.InternetAddress
Title: Message Title Oleg Nenashev commented on JENKINS-49650 Re: JEP-200: Unreliable Slave plugin: javax.mail.internet.InternetAddress Lucie Votypkova could you please take a look? https://plugins.jenkins.io/unreliable-slave-plugin has only 78 installations, so I doubt we will prioritize it high as JEP-200 maintainers. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44786) HTML Publisher does not allow environment variables in fields
Title: Message Title Matthew Pistella edited a comment on JENKINS-44786 Re: HTML Publisher does not allow environment variables in fields Thanks for working on this! Do you have a timeline for when this might be available? Would this also fix the issue in a pipeline file as well? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44786) HTML Publisher does not allow environment variables in fields
Title: Message Title Matthew Pistella commented on JENKINS-44786 Re: HTML Publisher does not allow environment variables in fields Thanks for working on this! Do you have a timeline for when this might be available? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49661) DumbSlave class offers only "slave" and "dumb" in @Symbol
Title: Message Title Oleg Nenashev commented on JENKINS-49661 Re: DumbSlave class offers only "slave" and "dumb" in @Symbol https://github.com/jenkinsci/jenkins/pull/3304 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49661) DumbSlave class offers only "slave" and "dumb" in @Symbol
Title: Message Title Oleg Nenashev started work on JENKINS-49661 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title
Steve Szabo commented on JENKINS-49660
Re: Unable to configure plugin using ibm k8s
Using the token from config.token I'm able to list pods using kubectl and curl:
sszabo@xxx [/home/sszabo/tmp] $ curl -s --cacert $KUBE_CERT -X GET -H "$KUBE_HEADER" $KUBE_MASTER/api/v1/namespaces/$KUBE_NAMESPACE/pods
{
"kind": "PodList",
"apiVersion": "v1",
"metadata": {
"selfLink": "/api/v1/namespaces/jenkins/pods",
"resourceVersion": "882144"
},
"items": []
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49661) DumbSlave class offers only "slave" and "dumb" in @Symbol
Title: Message Title Oleg Nenashev updated JENKINS-49661 Jenkins / JENKINS-49661 DumbSlave class offers only "slave" and "dumb" in @Symbol Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22637) "Copy Artifacts Plugin" should support ArtifactManager
Title: Message Title Jesse Glick started work on JENKINS-22637 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22637) "Copy Artifacts Plugin" should support ArtifactManager
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-22637 "Copy Artifacts Plugin" should support ArtifactManager Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49542 Re: Scripts not permitted to use method java.util.Map isEmpty Code changed in jenkins User: Andrew Bayer Path: src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/generic-whitelist http://jenkins-ci.org/commit/script-security-plugin/7a76cd1753c4f02850194ab06824a5d4e8a4b9f5 Log: [FIXED JENKINS-49542] Whitelist Map#isEmpty() Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title Steve Szabo commented on JENKINS-49660 Re: Unable to configure plugin using ibm k8s I'm not running the master in k8s however I was able to get it working with my local cluster by pointing the service endpoints to the master. I don't think this is the issue under ibm as it gives a permission error when I test the connection from jenkins config page. How are you authenticating from the master to k8s - you seem to be using the kubectl config. --- kind: Endpoints apiVersion: v1 metadata: name: jenkins-master namespace: jenkins labels: oiqclient: jenkins subsets: - addresses: - ip: 192.168.0.100 ports: - port: 8080 name: jenkins-master - addresses: - ip: 192.168.0.100 ports: - port: 5 name: jenkins-jnlp --- kind: Service apiVersion: v1 metadata: name: jenkins-master namespace: jenkins labels: oiqclient: jenkins spec: ports: - name: jenkins-master protocol: TCP port: 8080 targetPort: 8080 nodePort: 0 - name: jenkins-jnlp protocol: TCP port: 5 targetPort: 5 nodePort: 0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title Vivek Pandey updated JENKINS-48820 Jenkins / JENKINS-48820 Blue Ocean plug-in causes stack overflow for big pipeline jobs Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-48820 Blue Ocean plug-in causes stack overflow for big pipeline jobs Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 2 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title Vivek Pandey commented on JENKINS-48820 Re: Blue Ocean plug-in causes stack overflow for big pipeline jobs Thomas Johansen I have PR opened, https://github.com/jenkinsci/blueocean-plugin/pull/1667/:) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title Vivek Pandey started work on JENKINS-48820 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49661) DumbSlave class offers only "slave" and "dumb" in @Symbol
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-49661 DumbSlave class offers only "slave" and "dumb" in @Symbol Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-20 21:19 Priority: Minor Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-49466) job directory empty when using declarative pipeline
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-49466 job directory empty when using declarative pipeline Change By: Andrew Bayer Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42816) Slave to Agent renaming leftovers
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42816 Re: Slave to Agent renaming leftovers Code changed in jenkins User: Nicolas De loof Path: core/src/main/java/hudson/slaves/DumbSlave.java http://jenkins-ci.org/commit/jenkins/bc10eca4ff16054321f514fe396e8a0160adb5b1 Log: JENKINS-42816 use "agent" for Symbol Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49501) Facing NoClasssFoundError on running jobs in Jenkins 2.7.2
Title: Message Title Andrew Bayer commented on JENKINS-49501 Re: Facing NoClasssFoundError on running jobs in Jenkins 2.7.2 ping - have you tried restarting? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49501) Facing NoClasssFoundError on running jobs in Jenkins 2.7.2
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49501 Facing NoClasssFoundError on running jobs in Jenkins 2.7.2 Change By: Andrew Bayer Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title Andrew Bayer updated JENKINS-49542 Jenkins / JENKINS-49542 Scripts not permitted to use method java.util.Map isEmpty Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title Andrew Bayer commented on JENKINS-49542 Re: Scripts not permitted to use method java.util.Map isEmpty PR up at https://github.com/jenkinsci/script-security-plugin/pull/183 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title Andrew Bayer started work on JENKINS-49542 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49542 Scripts not permitted to use method java.util.Map isEmpty Change By: Andrew Bayer Component/s: script-security-plugin Component/s: pipeline Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49542) Scripts not permitted to use method java.util.Map isEmpty
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-49542 Scripts not permitted to use method java.util.Map isEmpty Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49505) workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago
Title: Message Title
Andrew Bayer resolved as Not A Defect
Jenkins / JENKINS-49505
workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago
Change By:
Andrew Bayer
Status:
Open Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49526) SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49526 SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded Change By: Andrew Bayer Component/s: github-branch-source-plugin Component/s: pipeline Component/s: pipeline-github-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49526) SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded
Title: Message Title Andrew Bayer assigned an issue to Unassigned Jenkins / JENKINS-49526 SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded Change By: Andrew Bayer Assignee: Aaron Whiteside Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49522) [withCredentials] MissingPropertyException from shared library class
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49522 [withCredentials] MissingPropertyException from shared library class Change By: Andrew Bayer Component/s: workflow-cps-global-lib-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49513) pipeline finally not reporting errors
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49513 pipeline finally not reporting errors Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49530) Declarative pipeline: 'agent any' doesn't honour node restriction
Title: Message Title Andrew Bayer commented on JENKINS-49530 Re: Declarative pipeline: 'agent any' doesn't honour node restriction So whatever's happening here would actually be an issue under the hood with the node step. agent any leads to calling the node step with no parameter - which should work the way you're expecting. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49530) Declarative pipeline: 'agent any' doesn't honour node restriction
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49530 Declarative pipeline: 'agent any' doesn't honour node restriction Change By: Andrew Bayer Component/s: workflow-durable-task-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49552) How to set component while creating new issue
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49552 How to set component while creating new issue Change By: Andrew Bayer Component/s: pipeline-build-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
