[JIRA] (JENKINS-40303) Jenkinsfile node() command ignores maxConcurrentPerNode
Title: Message Title
Eduard Wirch updated an issue
Jenkins / JENKINS-40303
Jenkinsfile node() command ignores maxConcurrentPerNode
Change By:
Eduard Wirch
This is roughly the {{Jenkinsfile}} of our pipeline build:{code}properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '', numToKeepStr: '10')),[$class: 'ThrottleJobProperty', categories: [], limitOneJobWithMatchingParams: false, maxConcurrentPerNode: 1, maxConcurrentTotal: 4, paramsToUseForLimit: '', throttleEnabled: true, throttleOption: 'project'],pipelineTriggers([])])node('ff') {}{code}Note, that {{maxConcurrentPerNode}} is 1. "ff" is a node group, not the name of a single node. This morning I found two builds for the same job started at the same time on the same node:{code}#34: 08:21:35 Running on jenkins04 in /var/lib/jenkins/workspace/r-Framework-Pipeline_master-ANZFTZAHSF7Z3GZCE4P4EWA2KLDAN62QSMCCUDZ4BRCFVS5MIHAA#35: 08:21:35 Running on jenkins04 in /var/lib/jenkins/workspace/r-Framework-Pipeline_master-ANZFTZAHSF7Z3GZCE4P4EWA2KLDAN62QSMCCUDZ4BRCFVS5MIHAA@2{code}You see nicely by the {{@}} sign in the workspace path that both builds indeed started on the same node.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40303) Jenkinsfile node() command ignores maxConcurrentPerNode
Title: Message Title
Eduard Wirch created an issue
Jenkins / JENKINS-40303
Jenkinsfile node() command ignores maxConcurrentPerNode
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Dec/08 7:50 AM
Environment:
Jenkins ver. 2.8
Labels:
pipeline regression
Priority:
Major
Reporter:
Eduard Wirch
This is roughly the Jenkinsfile of our pipeline build:
properties([
buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '', numToKeepStr: '10')),
[$class: 'ThrottleJobProperty', categories: [], limitOneJobWithMatchingParams: false, maxConcurrentPerNode: 1, maxConcurrentTotal: 4, paramsToUseForLimit: '', throttleEnabled: true, throttleOption: 'project'],
pipelineTriggers([])
])
node('ff') {
}
Note, that maxConcurrentPerNode is 1. This morning I found two builds for the same job started at the same time on the same node:
#34: 08:21:35 Running on jenkins04 in /var/lib/jenkins/workspace/r-Framework-Pipeline_master-ANZFTZAHSF7Z3GZCE4P4EWA2KLDAN62QSMCCUDZ4BRCFVS5MIHAA
#35: 08:21:35 Running on jenkins04 in
[JIRA] (JENKINS-16024) SCM Sync fails to check in any files
Title: Message Title Doron Shai reopened an issue Jenkins / JENKINS-16024 SCM Sync fails to check in any files Change By: Doron Shai Resolution: Not A Defect Status: Resolved Reopened 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-16024) SCM Sync fails to check in any files
Title: Message Title
Doron Shai edited a comment on JENKINS-16024
Re: SCM Sync fails to check in any files
I have similar issues even that the ticket is closed. When I just started using the plugin it worked for an hour and then, when i deleted a job it stopped working and even worse, When looking at {color:#654982}*_ /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/ _*{color} I can see that all the jobs were disappeared and also from the git repo while they were still avail on the jenkins.I am using SCM-Sync 0.0.10 and Jenkins 2.19.4
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-16024) SCM Sync fails to check in any files
Title: Message Title Doron Shai commented on JENKINS-16024 Re: SCM Sync fails to check in any files I have similar issues even that the ticket is closed. When I just started using the plugin it worked for an hour and then, when i deleted a job it stopped working and even worse, When looking at /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/ I can see that all the jobs were disappeared and also from the git repo while they were still avail on the jenkins. I am using SCM-Sync 0.0.10 and Jenkins 2.19.4 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-40279) Disabling of Jenkins setup wizard not working as expected
Title: Message Title
Thomas Wikström updated an issue
Jenkins / JENKINS-40279
Disabling of Jenkins setup wizard not working as expected
Change By:
Thomas Wikström
We are deploying and installing Jenkins for customers using a framework of ours, where we are packaging Tomcat, Jenkins, plugins and other maintenance tools to have a full server up and running. To be able to do this in a controlled manner for the customer, in for example an upgrade situation, we want to disable the setup wizard. https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+propertiesjenkins.install.runSetupWizard: "_Set to false to skip install and upgrade wizards._"We are setting the system property *jenkins.install.runSetupWizard* to false to skip both install and upgrade wizards.{panel}JAVA_OPTS:-Xms500m -Xmx500m -XX:MetaspaceSize=128M -XX:MaxMetaspaceSize=1024M -XX:+HeapDumpOnOutOfMemoryError -XX:+UseCompressedOops -XX:+UseG1GC -XX:MaxGCPauseMillis=400 -XX:GCPauseIntervalMillis=8000 -Djava.awt.headless=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -Djenkins.install.runSetupWizard=false -javaagent:./dist/ssl/sys-props-agent.jar=props:./dist/ssl/private/syspropsagent.properties -XX:HeapDumpPath=//logs/{panel}But still the setup wizard is appearing when upgrading like below. Going from:Tomcat 7.0.50, Jenkins 1.651.3Going to:Tomcat 8.5.5, Jenkins 2.19.1, -Djenkins. install. runSetupWizard=falseUpgrading in our terms means: /usr//usr//usr/in_production//proj/jenkins_home/ [ JENKINS_HOME is kept separated from installation; plugins, jobs, customer data etc ]Stop old Tomcat/Jenkins, install new Tomcat/Jenkins in parallel, *change symlinks (old->new installation)*, start new Tomcat/Jenkins. And yes, we understand we might be doing a (parallel) install in your terms, when we perform the above "upgrade". 1) We simply can't understand under which situations this system property is supposed to DISABLE the setup wizard? Is it not supposed to be working when running Jenkins in Tomcat? It IS described to "skip install *and* upgrade wizards". As we somehow needed to get this to work we have done extensive googling and trying out several approaches where users seem to have struggling with this as well. One workaround tested was this: https://github.com/geerlingguy/ansible-role-jenkins/issues/50Where we ONLY are adding the mentioned file with the value of "2.0" (no newline) [ TEST THIS - ONLY the file, NOT the runSetupWizard=false option ] Create the file JENKINS_HOME/jenkins.install.UpgradeWizard.state with one line, 2.0( echo -n 2.0 > $JENKINS_HOME/jenkins.install.UpgradeWizard.state )VOILA, no setup wizard appearing after login to upgraded Jenkins! 2) Is this a supported, recommended way of disabling the wizard? Are there any pitfalls going this way? Or are we simply working around a bug here?
[JIRA] (JENKINS-40279) Disabling of Jenkins setup wizard not working as expected
Title: Message Title Thomas Wikström updated an issue Jenkins / JENKINS-40279 Disabling of Jenkins setup wizard not working as expected Change By: Thomas Wikström Environment: - Docker version 1.10.3, build 20f81dd- CentOS Linux release 7.2.1511 (Core)- Java(TM) SE Runtime Environment, 1.8.0_45-b14- Tomcat 8.5.5- Jenkins 2.19.1, -Djenkins. install. runSetupWizard=false 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-40278) Emails are not sent from pipeline
Title: Message Title
Pavel Polivka updated an issue
Jenkins / JENKINS-40278
Emails are not sent from pipeline
Change By:
Pavel Polivka
We started migrating our Jenkins jobs to pipeline jobs and our build status emails stopped working.SMTP configuration is working OK I received test email and non pipeline jobs are still sending emails.If I do something like this{code}node {mail body: 'test', subject: 'test', to: 'ppoli...@xxx.com'}{code}Email not sent.I start digging into mailer plugin and figured out how emails work.I did some basic debugging out in pipeline code{code}node {def transportClass = javax.mail.Session.getDefaultInstance(java.lang.System.getProperties(), (javax.mail.Authenticator)null).getTransport(new javax.mail.internet.InternetAddress("ppoli...@xxx.com")).getClass();echo transportClass.toString();mail body: 'test', subject: 'test', to: 'ppoli...@xxx.com'}{code}and figured out that email transported transporter used in this instance is org.jvnet.mock_javamail.MockTransport{code}[Pipeline] {[Pipeline] echoclass org.jvnet.mock_javamail.MockTransport[Pipeline] mail[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}Again emails are working fine in non pipeline jobs. Configuration to use MockTransport is going from mock-javamail.jar based on classpath scanning. Is is possible that pipeline exposes this test jar to the classpath somehow?Is there any easy workaround this configuration?
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-39907) Github pull requests gets unproper statuses url link
Title: Message Title Javier Delgado commented on JENKINS-39907 Re: Github pull requests gets unproper statuses url link Michael Neale the pr status has https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgit-plugin/detail/PR-212/22/ as target_url (as github api states: https://api.github.com/repos/jenkinsci/git-plugin/commits/4c6a0284bd46b7d5a4b4fc4f1c27e95fe651d03b/status) For my browser (rendering https://ci.jenkins.io/ in spanish), that url throws a 404. The blueocean url that server the proper content contains such space (%20) in the url 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-38587) User can add and edit a block scoped step
Title: Message Title Keith Zantow resolved as Fixed Jenkins / JENKINS-38587 User can add and edit a block scoped step Change By: Keith Zantow Status: In Progress 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-40290) unit tests failures in core on windows
Title: Message Title Alex Earl commented on JENKINS-40290 Re: unit tests failures in core on windows If I switch to a 64-bit JDK, the build completes successfully 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-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Hermes Cheng commented on JENKINS-22494 Re: Multiconfiguration project does not respect label restrictions Hi Mark Waite, Yes, elastic axis plugin works well. I just thought as a default feature, it should support the original 'label _expression_' restricting functionality instead depending on another plugin. Lower the priority since it has a workaround. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40302) Handle Pipelines that have many stages
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40302 Handle Pipelines that have many stages Issue Type: Task Assignee: Brody Maclean Components: blueocean-plugin Created: 2016/Dec/08 4:00 AM Priority: Minor Reporter: James Dumay At the moment constraining the width of the result dialog will hide parts of the graph. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37771) "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.
Title: Message Title Matthew Hessing commented on JENKINS-37771 Re: "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server. Our team is encountering the same issue. Our build machine is a mac mini running Jenkins 2.35. On each machine restart or jenkins restart, all Build Environment options are cleared. This includes Delete workspace, setting the Ruby environment using RVM or rbenv, and all Android emulator options. We have over a dozen jobs and are creating more daily; it is painful to go back and update these on each restart. Note: I rolled back to ruby-runtime 0.12 and did not see any improvements. 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-40290) unit tests failures in core on windows
Title: Message Title Alex Earl commented on JENKINS-40290 Re: unit tests failures in core on windows My bad, the JDK is 32-bit. 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-38381) Optimize log handling in Pipeline and Durable Task
Title: Message Title Jesse Glick commented on JENKINS-38381 Re: Optimize log handling in Pipeline and Durable Task Integrated demo is in the logstash PR. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40301) Create ATH test for pull requests using mocks
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-40301 Create ATH test for pull requests using mocks Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/08 3:14 AM Priority: Minor Reporter: Michael Neale Thanks to info unearthed in this pull request, it should be possible to create a mock pull request for testing the PR tab in blue ocean: https://github.com/jenkinsci/blueocean-plugin/pull/650 @michaelneale https://github.com/jenkinsci/branch-api-plugin/blob/12b8364d0fb1aa057b5a4ca81317b150a16121e1/src/test/java/integration/CategorizationTest.java#L147-L178 shows creating change requests @michaelneale if you use "execute groovy script" you can create a controller and set up the controller's repo as you want. then use that from the ath Add Comment
[JIRA] (JENKINS-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Hermes Cheng updated an issue Jenkins / JENKINS-22494 Multiconfiguration project does not respect label restrictions Change By: Hermes Cheng Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40290) unit tests failures in core on windows
Title: Message Title Alex Earl commented on JENKINS-40290 Re: unit tests failures in core on windows Mine is 64bit for both 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-40286) EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40286 EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it Change By: Daniel Beck Issue Type: Bug Improvement 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-40290) unit tests failures in core on windows
Title: Message Title Daniel Beck commented on JENKINS-40290 Re: unit tests failures in core on windows Is this 32 bit Windows or JDK? 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-40085) Builds kept forever no longer have an icon
Title: Message Title Daniel Beck commented on JENKINS-40085 Re: Builds kept forever no longer have an icon Linked issue (possible duplicate) contains a possible explanation. 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-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40281 No Badge shown, Exception build.badgeActions depending on KeepBuildForever Change By: Daniel Beck Labels: exception regression 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-40085) Builds kept forever no longer have an icon
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40085 Builds kept forever no longer have an icon Change By: Daniel Beck Labels: regression 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-40279) Disabling of Jenkins setup wizard not working as expected
Title: Message Title Daniel Beck commented on JENKINS-40279 Re: Disabling of Jenkins setup wizard not working as expected Huh. Seems I got this one wrong when documenting it. Try adding -Djenkins.install.UpgradeWizard.show=false to disable the upgrade wizard. IIUC this is the one you're concerned about. 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-40245) Couldn't build any Jenkins's job
Title: Message Title Daniel Beck resolved as Incomplete https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-40245 Couldn't build any Jenkins's job Change By: Daniel Beck Status: In Progress Resolved Resolution: Incomplete 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-40228) Security config hides certain parts with 2.32
Title: Message Title Daniel Beck commented on JENKINS-40228 Re: Security config hides certain parts with 2.32 Security cannot be enabled without selecting a security realm and authorization strategy. Check 'Jenkins user database' and 'anyone can do anything' and it should just work. Also, I recommend you actually set up security properly. 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-40133) Referencing non-existant variable in Pipeline causes CPU to spike and job to hang
Title: Message Title Daniel Beck commented on JENKINS-40133 Re: Referencing non-existant variable in Pipeline causes CPU to spike and job to hang The problem is the var is the same name as the getter and you're entering an infinite loop. I've seen this once or twice before and think this is a Groovy CPS specific issue. Jesse Glick Do we have an issue for this? 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-40171) The "Apply" button's "Saved" message obstructs the top menu
Title: Message Title Daniel Beck commented on JENKINS-40171 Re: The "Apply" button's "Saved" message obstructs the top menu FWIW one can click the green bar to make it disappear faster. 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-40133) Referencing non-existant variable in Pipeline causes CPU to spike and job to hang
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40133 Referencing non-existant variable in Pipeline causes CPU to spike and job to hang Change By: Daniel Beck Component/s: pipeline Component/s: core 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-39712) Error while save systme config
Title: Message Title Daniel Beck resolved as Incomplete No response to request for more information in several weeks, therefore incomplete. Jenkins / JENKINS-39712 Error while save systme config Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete 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-40128) Plugin Manager API inconsistencies, produces empty XML/JSON/Python
Title: Message Title Daniel Beck resolved as Not A Defect tree and depth parameters will resolve this. Jenkins / JENKINS-40128 Plugin Manager API inconsistencies, produces empty XML/JSON/Python Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect 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-40097) Build Executor Status is not aligned with long names
Title: Message Title Daniel Beck resolved as Incomplete Version 1.651.2 Please show that this happens on current Jenkins releases. Jenkins / JENKINS-40097 Build Executor Status is not aligned with long names Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete 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
[JIRA] (JENKINS-40085) Builds kept forever no longer have an icon
Title: Message Title Daniel Beck commented on JENKINS-40085 Re: Builds kept forever no longer have an icon Jesse Glick Did you break this? 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-40082) Changing hostname results in stack overflow
Title: Message Title Daniel Beck resolved as Incomplete https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-40082 Changing hostname results in stack overflow Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete 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-40029) Sometime build triggered does not gets killed and it went into a hang state
Title: Message Title Daniel Beck resolved as Incomplete Incomplete report and outdated Jenkins. This cannot reasonably be acted on. Jenkins / JENKINS-40029 Sometime build triggered does not gets killed and it went into a hang state Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete 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.
[JIRA] (JENKINS-39972) Export fullName from AbstractItem to the REST API
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-39972 Export fullName from AbstractItem to the REST API Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39971) Manual update button hidden if no plugins to update availabe.
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-39971 Manual update button hidden if no plugins to update availabe. Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39971) Manual update button hidden if no plugins to update availabe.
Title: Message Title Daniel Beck commented on JENKINS-39971 Re: Manual update button hidden if no plugins to update availabe. Core is correct. 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-39909) Incomplete downloads of artifacts
Title: Message Title Daniel Beck commented on JENKINS-39909 Re: Incomplete downloads of artifacts Not a bug then, but an aggressive timeout config paired with a terrible connection? 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-40291) Reconnect the session after the init.sh script runs
Title: Message Title Claudiu Guiman resolved as Fixed Jenkins / JENKINS-40291 Reconnect the session after the init.sh script runs Change By: Claudiu Guiman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39700) Saving external job throws "null object"
Title: Message Title Daniel Beck started work on JENKINS-39700 Change By: Daniel Beck 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-39539) Unable to create an external job (JSONException: null object)
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-39539 Unable to create an external job (JSONException: null object) Change By: Daniel Beck 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-39531) Warning the use of a custom workspace
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-39531 Warning the use of a custom workspace Change By: Daniel Beck Component/s: plugin-proposals Component/s: core 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-39434) failed to instanciate Key (callstack inside)
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-39434 failed to instanciate Key (callstack inside) https://github.com/jenkinsci/nuget-plugin/blob/master/src/main/java/org/jenkinsci/plugins/nuget/NugetGlobalConfiguration.java#L31...L32 This looks wrong to me. Change By: Daniel Beck Component/s: nuget-plugin Component/s: core 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-33708) Invocation of 'sh' on Windows should provide a more helpful error
Title: Message Title
Frederick Staats commented on JENKINS-33708
Re: Invocation of 'sh' on Windows should provide a more helpful error
I second the request to add WindowsCheck() on the line "if (!ws.act(new DarwinCheck())) { // JENKINS-25848" in src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java If you add Git Bash to a Windows master or slave node in the default "System Path", but the Path that is used to run the Windows Service that runs Jenkins does not include "nohup.exe" you run into an error as Jenkins is hardwired to run "nohup" using the Windows Service path running Jenkins and not the path configured for of the Pipeline executor. My work around to run Git Bash in Jenkins on Windows in a Pipeline step is to add a "C:\Nohup" directory with just "nohup.exe" and supporting DLLs into the global Path that is used by the Windows service, as it is not an option to add all of Git executables to the system level Path. Here is an example of the error when sh.exe (Bash) is on the path but nohup.exe is not on the path on Windows: [C:\Jenkins\workspace\Multibranch_Pipeline_master-HJ66KBORTDATZ4DJ3RHNWWLARKMDIQIPNIY5RCIPMIMMK37I2FUQ] Running shell script [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline GitHub has been notified of this commit’s build result java.io.IOException: Cannot run program "nohup" (in directory "C:\Jenkins\workspace\Multibranch_Pipeline_master-HJ66KBORTDATZ4DJ3RHNWWLARKMDIQIPNIY5RCIPMIMMK37I2FUQ"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:243) at hudson.Proc$LocalProc.(Proc.java:212) at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) at hudson.Launcher$ProcStarter.start(Launcher.java:381) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:147) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:61) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:158) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:184) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at BREDev.call(C:\Jenkins\jobs\ITSD BREDev Multibranch
[JIRA] (JENKINS-39907) Github pull requests gets unproper statuses url link
Title: Message Title Michael Neale commented on JENKINS-39907 Re: Github pull requests gets unproper statuses url link Possibly related to this fix: https://github.com/jenkinsci/blueocean-plugin/pull/634 (which is not yet released). Also - I don't follow. When I click on the link in the PR it takes to the right place - not sure what the https://ci.jenkins.io/blue/organizations/jenkins%20/Plugins%2Fgit-plugin/detail/PR-212/21/pipeline/ is from 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-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem DescriptionWithout _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins clones in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace.That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation.h2. SymptomWhen at first you do not use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory.h2. WorkaroundFirst, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration. Then, in In {{Jenkinsfile}}, {{stash}} the repo in the workspace directory, and {{unstash}} it into a subdirectory:{code:java}stage("setup") {node("sw") {deleteDir()checkout scmstash name: "repo"}}stage("test") {node("sw") {deleteDir()dir("subdir") {unstash "repo" }// Test stuff}}{code}
Add Comment
[JIRA] (JENKINS-39542) Tests tab "Cannot read property 'trim' of null"
Title: Message Title Ivan Meredith stopped work on JENKINS-39542 Change By: Ivan Meredith 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-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title Ivan Meredith started work on JENKINS-40296 Change By: Ivan Meredith 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-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40296 REGRESSION: Commit messages are not showing up in activities, branches and PR tables Change By: James Dumay Sprint: Bundles management UI Sprint frank 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-40299) Adapt to the new SCM API for detecting change requests
Title: Message Title James Dumay started work on JENKINS-40299 Change By: James Dumay 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-39761) Improve BlueRun loading performance with many artifacts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39761 Re: Improve BlueRun loading performance with many artifacts Code changed in jenkins User: Ivan Meredith Path: src/test/js/artifacts/artifacts.js src/test/resources/test_scripts/lots-of-artifacts.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/4dc0c1030e98d19cead6c1063e95d978629a601d Log: [JENKINS-39761 Adds tests to cover the artifacts tab on run details. (#82) JENKINS-39761 Check that only 100 artifacts are shown Commit groovy file Use bash to create files Fix tests Fix comments 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
[JIRA] (JENKINS-40291) Reconnect the session after the init.sh script runs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40291 Re: Reconnect the session after the init.sh script runs Code changed in jenkins User: R. Tyler Croy Path: src/main/java/com/microsoft/azure/remote/AzureVMAgentSSHLauncher.java http://jenkins-ci.org/commit/azure-vm-agents-plugin/e0c852a4fd5b2108cf8bfec3fb6b8b289eaa5ffe Log: Force a new session to be created after running the init script to pick up new settings In scenarios where new shells, groups, user settings or other environmental changes which are made by the 'Init Script', this patch will ensure that the launching of the `slave.jar` will pick those changes as part of the launched Jenkins agent Fixes JENKINS-40291 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-40299) Adapt to the new SCM API for detecting change requests
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40299 Adapt to the new SCM API for detecting change requests Change By: James Dumay Sprint: frank 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-40299) Adapt to the new SCM API for detecting change requests
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40299 Adapt to the new SCM API for detecting change requests Issue Type: Task Assignee: Stephen Connolly Components: blueocean-plugin Created: 2016/Dec/08 12:46 AM Priority: Minor Reporter: James Dumay Adapt to the correct API for detecting change requests see JENKINS-40138. This requires a upgrade to scm-api 2.0. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40287) Log information on template verification is incorrect
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40287 Re: Log information on template verification is incorrect Code changed in jenkins User: Arjun Roy Chaudhuri Path: src/main/java/com/microsoft/azure/AzureVMAgentTemplate.java http://jenkins-ci.org/commit/azure-vm-agents-plugin/4e766772393a820f688b3309bfe202d068948e79 Log: Merge pull request #6 from clguimanMSFT/log-output-fix Fixed logging [FIXED JENKINS-40287] Compare: https://github.com/jenkinsci/azure-vm-agents-plugin/compare/a5b8c76abe83...4e766772393a 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-40287) Log information on template verification is incorrect
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-40287 Log information on template verification is incorrect Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40287) Log information on template verification is incorrect
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40287 Re: Log information on template verification is incorrect Code changed in jenkins User: Claudiu Guiman Path: src/main/java/com/microsoft/azure/AzureVMAgentTemplate.java http://jenkins-ci.org/commit/azure-vm-agents-plugin/404bf78925277202cd5af02c7375fed52bc4f261 Log: Fixed logging [FIXED JENKINS-40287] 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-29726) InstallPluginCommand: Cannot upgrade bundled plugins
Title: Message Title Daniel Beck resolved as Won't Fix No response in several months, so assuming this actually is obsolete has most of the bundled plugin functionality including 'Pinned Plugins' has been removed in 2.0 Jenkins / JENKINS-29726 InstallPluginCommand: Cannot upgrade bundled plugins Change By: Daniel Beck Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Liam Newman edited a comment on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master This is where the default gets provided : https://github . com/jenkinsci/jenkins/blob/720b75f096e573b102323b529ec952e2106d4a57/core/src/main/java/hudson/tasks/Shell.java#L155 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-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Ahmed Musallam commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds Andor Dávid Mark Cariddi We have seen this issue on my project. It turned out to be a missing config for the clover publisher. Specifically the config. This config's absence is not handled properly in the plugin, I opened an issue here: https://issues.jenkins-ci.org/browse/JENKINS-40297 target/site/clover clover.xml 70 80 80 40 40 40 0 0 0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40298) Include automatically extracted licenses in plugin(s)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40298 Include automatically extracted licenses in plugin(s) Change By: Michael Neale Sprint: kraken 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-40298) Include automatically extracted licenses in plugin(s)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-40298 Include automatically extracted licenses in plugin(s) Issue Type: Bug Assignee: Keith Zantow Components: blueocean-plugin Created: 2016/Dec/08 12:07 AM Priority: Critical Reporter: Michael Neale Keith - to comply with various licences, we need to include licences for all js libraries used to be included with the blue ocean hpi. The data produced by: https://www.npmjs.com/package/npm-license-crawler automatically is just fine (it can output to a file, perhaps as part of build process? or even manually checked in somewhere is also fine). Some options on how to provide it to users: on /about somehow on /blue/licences or similar (or /blue/about) - even as plain text Just included in the bundle may be fine I will leave it up to you as to which was is easiest. Add Comment
[JIRA] (JENKINS-40297) Clover-Plugin NullPointer exception on build when config is missing
Title: Message Title Ahmed Musallam created an issue Jenkins / JENKINS-40297 Clover-Plugin NullPointer exception on build when config is missing Issue Type: Bug Assignee: Stephen Connolly Components: clover-plugin Created: 2016/Dec/08 12:04 AM Priority: Major Reporter: Ahmed Musallam Clover Plugin throws an NPE on build.. find exception below. Our team was able to debug the issue and it was due to missing config for clover publisher because the failing target fields were not populated. As you can see, this error is not helpful and it would be nice if the log can be more helpful in case of a missing config. The NPE happens exactly at this line in CloverPublisher.java Set failingMetrics = failingTarget.getFailingMetrics(result); where failingTarget is null.. well because it was not provided in the xml config. Disclaimer: I have not developed jenkins plugins before so I appologize if I'm not using correct terms. ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.clover.CloverPublisher.processCloverXml(CloverPublisher.java:250) at hudson.plugins.clover.CloverPublisher.performImpl(CloverPublisher.java:202) at hudson.plugins.clover.CloverPublisher.perform(CloverPublisher.java:160) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:764) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:724) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1769) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)
[JIRA] (JENKINS-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Liam Newman commented on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master This is where the default gets provided. 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-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40296 REGRESSION: Commit messages are not showing up in activities, branches and PR tables Change By: Michael Neale Sprint: Bundles management UI Sprint 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-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40296 REGRESSION: Commit messages are not showing up in activities, branches and PR tables Change By: Michael Neale This has been a regression since B12In scope: * ATH test to check this shows up on the branches and activity listing (show that it picks up failure first) * Fix for this in all 3 listings 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-40296) REGRESSION: Commit messages are not showing up in activities, branches and PR tables
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-40296 REGRESSION: Commit messages are not showing up in activities, branches and PR tables Issue Type: Bug Assignee: Ivan Meredith Components: blueocean-plugin Created: 2016/Dec/07 11:48 PM Priority: Blocker Reporter: Michael Neale This has been a regression since B12 In scope: ATH test to check this shows up on the branches and activity listing Fix for this in all 3 listings Add Comment
[JIRA] (JENKINS-38115) spot instance slaves are not removed, blocks instance termination
Title: Message Title Dimitri Gilbert commented on JENKINS-38115 Re: spot instance slaves are not removed, blocks instance termination Same here, everything works fine but that, it is extremelly frustrating. Here is the output of the crash : javax.servlet.ServletException: java.lang.IllegalStateException: Unknown instance terminated: i-4c8a415b at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at
[JIRA] (JENKINS-39761) Improve BlueRun loading performance with many artifacts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39761 Re: Improve BlueRun loading performance with many artifacts Code changed in jenkins User: Ivan Meredith Path: src/test/js/failingStages.js src/test/resources/test_scripts/stagesFailing.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/e8551919acb1016a029b0cc9147c32cc6df7b352 Log: Merge remote-tracking branch 'origin/master' into JENKINS-39761-performance-bluerun Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/a7c98cfe984b...e8551919acb1 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-39533) no graph displayed from warnings plugin in multi-branch-pipeline project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39533 Re: no graph displayed from warnings plugin in multi-branch-pipeline project Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubRepositoryEventSubscriber.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java src/main/java/org/jenkinsci/plugins/github_branch_source/PullRequestGHEventSubscriber.java src/main/java/org/jenkinsci/plugins/github_branch_source/PushGHEventSubscriber.java http://jenkins-ci.org/commit/github-branch-source-plugin/ef13b2f678b2da8f4901ed757d2dceaa4aacdcdd Log: Make releasable before JENKINS-39533 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-40208) Grammar error on BlueOcean page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40208 Re: Grammar error on BlueOcean page Code changed in jenkins User: Christopher Simons Path: content/projects/blueocean.adoc http://jenkins-ci.org/commit/jenkins.io/ea1d89c42006bf9efbe9b9ec98d4b9100c657fcd Log: [FIX JENKINS-40208] fix typographical error Fixes a typographical error discovered by Igor Ganapolsky. 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-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem DescriptionWithout _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins does clone clones in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace. Originally I was thinking that the {{Jenkinsfile}} reader should track _Additional Behaviors > Check out to a sub - directory_, but after gaining some experience with --- - That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation.h2. Symptom If you When at first you do * not * use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory. Pretty darn hard to diagnose... h2. WorkaroundFirst, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration.Then, in {{Jenkinsfile}}, {{stash}} the repo in the workspace directory, and {{unstash}} it into a subdirectory:{code:java}stage("setup") {node("sw") {deleteDir()checkout scmstash name: "repo"}}stage("test") {node("sw") {deleteDir()dir("subdir") {unstash "repo" }// Test stuff}}{code}
Add Comment
[JIRA] (JENKINS-40208) Grammar error on BlueOcean page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40208 Re: Grammar error on BlueOcean page Code changed in jenkins User: R. Tyler Croy Path: content/projects/blueocean.adoc http://jenkins-ci.org/commit/jenkins.io/4c6fcca60a4dc29f2d85b1eb5f76f194300b798b Log: Merge pull request #493 from csimons/JENKINS-40208 [FIX JENKINS-40208] fix typographical error Compare: https://github.com/jenkins-infra/jenkins.io/compare/565da54bbd9a...4c6fcca60a4d 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-40208) Grammar error on BlueOcean page
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-40208 Grammar error on BlueOcean page Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38211) JenkinsFiles cannot run on Linux agent of Windows master
Title: Message Title Liam Newman commented on JENKINS-38211 Re: JenkinsFiles cannot run on Linux agent of Windows master I discussed this with Justen Britain at CD Summit yesterday. This is at least partly being caused by a strange configuration on that specific Windows-based Jenkins Master. The "Shell Executable" has been manually set to "C:\Program Files (x86)\Git\git-bash.exe". This means that the sh step on all nodes (master and agents) will add #! C:\Program Files (x86)\Git\git-bash.exe -xe to the front of their shell scripts. On windows, I believe this gets ignored, but on linux it blows up. If we treat this as a feature request it would be that there should be a "Shell Executable" configuration available on each node agent that inherits from global configuration by default. Or treating "shell" as a tool that one can configure (like ant, maven, JDK, etc). But I'd like let's talk about work-arounds that Justen Britain can use (aside from switching to a linux master): 1. Set the "Shell executable" configuration value to empty. That is what is by default, and generally is correct. Then make sure you have Windows Git installed, and add C:\Program Files\Git\bin to the path on all windows machines that run Jenkins agents (including master). (based on http://stackoverflow.com/a/35045651/1637252) 2. If you cannot change the shell executable setting, you can get around this by manually adding #! to the start of all your sh steps, but this really is a distant second. The third point is that this and other difficulties and edge cases around running jenkins (either master or agents) need to be documented. I'll get a page started on jenkins.io and discuss this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem Description Without _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins does clone in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace. Originally I was thinking that the {{Jenkinsfile}} reader should track _Additional Behaviors > Check out to a sub - directory_, but after gaining some experience with --- - That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation. h2. Symptom If you first do *not* use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory. Pretty darn hard to diagnose... h2. WorkaroundFirst, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration.Then, in {{Jenkinsfile}}, {{stash}} the repo in the workspace directory, and {{unstash}} it into a subdirectory:{code:java}stage("setup") {node("sw") {deleteDir()checkout scmstash name: "repo"}}stage("test") {node("sw") {deleteDir()dir("subdir") {unstash "repo" }// Test stuff}}{code}
Add Comment
[JIRA] (JENKINS-40290) unit tests failures in core on windows
Title: Message Title Alex Earl commented on JENKINS-40290 Re: unit tests failures in core on windows I do get the following error though for the war [INFO] --- frontend-maven-plugin:1.0:install-node-and-npm (install node and npm) @ jenkins-war --- [INFO] Installing node version v4.0.0 [INFO] Downloading file:/C:/code/_external/jenkins/war/target/frontend/v4.0.0/win-x86/node.exe to C:\Users\USER\.m2\repository\com\github\eirslett\node\4.0.0\node-4.0.0-windows-x86.exe [INFO] [INFO] Reactor Summary: [INFO] [INFO] Jenkins main module SUCCESS [ 5.636 s] [INFO] Jenkins cli SUCCESS [ 19.834 s] [INFO] Jenkins core ... SUCCESS [10:58 min] [INFO] Jenkins war FAILURE [ 27.832 s] [INFO] Tests for Jenkins core . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 11:53 min [INFO] Finished at: 2016-12-07T15:37:17-07:00 [INFO] Final Memory: 55M/194M [INFO] [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.0:install-node-and-npm (install node and npm) on project jenkins-war: Could not download Node.js from: ile:/C:/code/_external/jenkins/war/target/frontend/v4.0.0/win-x86/node.exe: Could not download file:/C:/code/_external/jenkins/war/target/frontend/v4.0.0/win-x86/node.exe: Source 'C:\code\_external\jenkins\war\target\frontend\v4.0.0\win-x86\node.exe' does not exist -> [Help 1] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40290) unit tests failures in core on windows
Title: Message Title
Alex Earl commented on JENKINS-40290
Re: unit tests failures in core on windows
Part of the failures are because of symlinks. I get this warning:
Symbolic links enabled on this platform but disabled for this user; run as administrator or use Local Security Policy > Security Settings > Local Policies > User Rights Assignment > Create symbolic links
I ran powershell as an admin (didn't try the part about Local Security Policy yet) and the errors are down to 1
Failed tests:
RunTest.getLogReturnsAnRightOrder:192 expected:<[...truncated [6]8 B...]> but was:<[...truncated [7]8 B...]>
The issue with this one is that the person who wrote the test didn't take into account Windows line endings which add an additional 10 bytes to the trucated count. A small patch like follows allows that test to pass:
int byteCount = 68;
if(Utils.isWindows()) {
byteCount += 10;
}
assertEquals("[...truncated "+byteCount+" B...]", logLines.get(0));
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40295) Configure EC2-Plugin with Groovy
Title: Message Title John Mickey created an issue Jenkins / JENKINS-40295 Configure EC2-Plugin with Groovy Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Dec/07 9:48 PM Priority: Minor Reporter: John Mickey I am working on configuring the ec2-plugin with Groovy I have a bit of code, but need some help How do I setup the EC2Cloud and then configure it for my AMI import jenkins.model.* import hudson.plugins.ec2.* def cloud = new EC2Cloud( cloudName="foo", useInstanceProfileForCredentials=true, credentialsID="foo", region="us-west-2", privateKey="foo", instanceCapStr="foo", templates="" ) def cloudList = Jenkins.instance.clouds cloudList.add(EC2Cloud) Add Comment
[JIRA] (JENKINS-40208) Grammar error on BlueOcean page
Title: Message Title Christopher Simons commented on JENKINS-40208 Re: Grammar error on BlueOcean page Fixed in PR #493. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40208) Grammar error on BlueOcean page
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-40208 Grammar error on BlueOcean page Change By: Christopher Simons Assignee: Christopher Simons 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-40292) More Control of p4 task logging
Title: Message Title Bruce Evans commented on JENKINS-40292 Re: More Control of p4 task logging +vote also, this adds volume to the console log even though "quiet" is true in p4sync. Request is to reduce/eliminate but allow setting to re-engage if diagnostics required. 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-40263) Could not find credentials matching during docker build
Title: Message Title Nikolaus Demmel commented on JENKINS-40263 Re: Could not find credentials matching during docker build Maybe this has nothing to do the DTR update and was never actually working in the first place, we just never noticed because of the shared docker daemon and the machine being rebooted seldomly. Maybe an update in the plugin caused the error to surface where before it was ignored more or less silentlty: https://github.com/jenkinsci/docker-commons-plugin/commit/702579ffe9001f4394e696dcc1d7990012ce97df 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-40294) Exec Failure: HTTP:404. Message:Not Found
Title: Message Title
Daniel Serodio created an issue
Jenkins / JENKINS-40294
Exec Failure: HTTP:404. Message:Not Found
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
jenkins-kubernetes.log
Components:
kubernetes-plugin
Created:
2016/Dec/07 8:51 PM
Environment:
Jenkins 2.35, Kubernetes Plugin 0.9, Minikube 0.13.1
Labels:
kubernetes
Priority:
Minor
Reporter:
Daniel Serodio
I'm trying to run a simple pipeline based on the example on the README:
podTemplate(label: 'mypod', containers: [
containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', ttyEnabled: true, command: 'cat'),
containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave', args: '${computer.jnlpmac} ${computer.name}'),
]) {
node ('mypod') {
stage 'Get a Maven project'
git 'https://github.com/jenkinsci/kubernetes-plugin.git'
container('maven') {
stage 'Build a Maven project'
sh 'mvn clean install'
}
}
}
The pod is created and started, but when Jenkins tries to run the shell script for the build, I get:
[JIRA] (JENKINS-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
Title: Message Title
Prabhu Inbarajan commented on JENKINS-39695
Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
the fix works as advertised. i dont see the original issue anymore. however, a couple of observations - please validate: 1. now each container step is required to declare which cloud it needs to be launched in. would be great to have this inherit this info from the pod template, but seems like the design challenge is each pod templates can be inherited and each pod template can bind to a cloud, we cant derive the intent clean. 2. if the containerstep fails to declare the cloud, that results in a null pointer exception, we may need to handle it in a clean way. test snippet below for reference (modified slightly from the original for build time): Note: 1. that my jenkins instance runs from docker swarm , where as the slave workloads are scheduled on minikube 2. built with latest from master (0.10-SNAPSHOT)
podTemplate(
cloud: 'minikube',
label: 'docker',
containers: [
//containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave:2.62-alpine', args: '${computer.jnlpmac} ${computer.name}'),
containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', ttyEnabled: true, command: 'cat'),
containerTemplate(name: 'golang', image: 'golang:1.6.3-alpine', ttyEnabled: true, command: 'cat')
],
volumes: [secretVolume(secretName: 'shared-secret', mountPath: '/etc/shared-secrets')],
) {
node ('docker') {
stage 'Get a Maven project'
git 'https://github.com/pgrimard/spring-boot-hello-world.git'
container(name:'maven', cloud:'minikube') {
stage 'Build a Maven project'
try {
sh 'mvn clean install'
}catch (Exception ex) {
ex.printStackTrace()
}
}
stage 'Get a Golang project'
git url: 'https://github.com/golang/example.git'
container(name:'golang', cloud:'minikube') {
stage 'Build a Go project'
sh """
mkdir -p /go/src/github.com/golang/
ln -s `pwd` /go/src/github.com/golang/example
export GOPATH=/go
cd /go/src/github.com/golang/example/hello && go build
"""
}
}
}
Add Comment
[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Mike Stolls commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Same issue with Jenkins v2.35 and Subversion v2.7.1. Building a multibranch job, the branch indexing fails on an external before i even get into my Jenkins file pipeline. Any update on this issue? hudson.util.IOException2: revision check failed on https:// at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:85) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:215) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:66) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:798) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:391) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:862) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:698) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:195) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:194) ... 9 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:728) ... 27 more Finished: FAILURE
[JIRA] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Enrique Ramirez commented on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Is somebody looking at this issue? I am also experiencing the same problem on Windows 10 and Windows 7 whenever i run a program with Batch. 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-38105) Fail to set reference parameters with different type of drop down list
Title: Message Title Bruno P. Kinoshita commented on JENKINS-38105 Re: Fail to set reference parameters with different type of drop down list Hmmm, weird. Went to update center JSON to take a look, and nodelabel parameter 1.7.3 is not out, though I can see the tag has been created in GitHub. I think we will have to wait a bit more. 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-40288) Generated storage account name is only using "resource group" for generation of GUID
Title: Message Title Claudiu Guiman commented on JENKINS-40288 Re: Generated storage account name is only using "resource group" for generation of GUID The fix is waiting for code review and testing: https://github.com/jenkinsci/azure-vm-agents-plugin/pull/3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26828) Add support for installing the NodeJS windows msi
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26828 Re: Add support for installing the NodeJS windows msi Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/CPU.java src/main/java/jenkins/plugins/nodejs/tools/DetectionFailedException.java src/main/java/jenkins/plugins/nodejs/tools/InstallerPathResolver.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersion.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersionRange.java src/main/java/jenkins/plugins/nodejs/tools/Platform.java src/main/java/jenkins/plugins/nodejs/tools/pathresolvers/LatestInstallerPathResolver.java src/test/java/jenkins/plugins/nodejs/tools/InstallerPathResolversTest.java src/test/resources/updates/jenkins.plugins.nodejs.tools.NodeJSInstaller.json http://jenkins-ci.org/commit/nodejs-plugin/6d0487c12e51701da6ffc71a4f4295fd8f5cb846 Log: JENKINS-26828 Add support for installing the NodeJS windows msi Remove unused old method. Update some old duplicate code from jenkins core code. Extend version with range capabilities to check which version has only an msi installer. 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26828 Re: Add support for installing the NodeJS windows msi Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/CPU.java src/main/java/jenkins/plugins/nodejs/tools/DetectionFailedException.java src/main/java/jenkins/plugins/nodejs/tools/InstallerPathResolver.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersion.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersionRange.java src/main/java/jenkins/plugins/nodejs/tools/Platform.java src/main/java/jenkins/plugins/nodejs/tools/pathresolvers/LatestInstallerPathResolver.java src/test/java/jenkins/plugins/nodejs/tools/InstallerPathResolversTest.java src/test/resources/updates/jenkins.plugins.nodejs.tools.NodeJSInstaller.json http://jenkins-ci.org/commit/nodejs-plugin/0f8bbb7f58de3eedd3c7783e3a2c243f331ddd1c Log: FIXED JENKINS-26828 Add support for installing the NodeJS windows msi Remove unused old method. Update some old duplicate code from jenkins core code. Extend version with range capabilities to check which version has only an msi installer. 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-40292) More Control of p4 task logging
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-40292 More Control of p4 task logging Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Dec/07 8:04 PM Priority: Minor Reporter: Joel Brown Desire a way to control (limit) the logging in the Console Output. For example, when things go wrong in the actual build step, I always have to scroll done through all the P4 Tasks. There's part of the P4 Task output, like p4 info, p4 counter change, p4 client -i, p4 client -o, etc. that I only care about if it fails. Add Comment
[JIRA] (JENKINS-40293) "Add" button should allow opening the dialogue with a specific "Kind" of credential pre-selected
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-40293 "Add" button should allow opening the dialogue with a specific "Kind" of credential pre-selected Issue Type: New Feature Assignee: Stephen Connolly Attachments: Selection_017.png Components: credentials-plugin Created: 2016/Dec/07 8:04 PM Priority: Minor Reporter: R. Tyler Croy When a plugin introduces a new credential type (e.g. "Azure Credentials") it would be helpful if the views for those plugins to "Add" a credential could pre-select the "Kind" of credential. Instead of "Kind" defaulting to "Username with Password" in the "Add Credentials" dialogue, it would be much easier for the "Kind" to open to whatever Kind of credential the plugin is asking the user to enter. // cc Claudiu Guiman Arjun Roy Chaudhuri Add Comment
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-40292 More Control of p4 task logging Change By: Joel Brown Issue Type: Bug Improvement 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-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title
Ed Kaplonski commented on JENKINS-40281
Re: No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Experiencing the same problem in 2.35 on Ubuntu 14.04 delivered via Ubuntu package. I think the problem originated in commit 6360b96464f6c2498fe91a089a21992411b2ec34 (https://github.com/jenkinsci/jenkins/commit/6360b96464f6c2498fe91a089a21992411b2ec34) for issue JENKINS-38867. In `Actionable.java:138`, the change introduced return of the badge actions with `Collections.unmodifiableList()`. The list returned to caller `Run.getBadgeActions()` is then immediately added to, causing the exception. From Run.java:480:
public @Nonnull List getBadgeActions() {
List r = getActions(BuildBadgeAction.class); // This is now an unmodifiableList.
if(isKeepLog()) {
r.add(new KeepLogBuildBadge()); // Can't add to an unmodifiable List, so an exception is thrown.
}
return r;
}
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-40291) Reconnect the session after the init.sh script runs
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-40291 Reconnect the session after the init.sh script runs Issue Type: New Feature Assignee: Claudiu Guiman Components: azure-vm-agents-plugin Created: 2016/Dec/07 7:48 PM Priority: Minor Reporter: R. Tyler Croy This is a request that this pull request is ported to allow init scripts to modify user and group attributes for a VM Agent. This would allow my init script to set up Docker access for the jenkins user, for example Add Comment
[JIRA] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline
Title: Message Title Gavin Mogan resolved as Not A Defect Jenkins / JENKINS-40261 Sauce connect process not stopping as part of Jenkins pipeline Change By: Gavin Mogan Status: Open Resolved Resolution: Not A Defect 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-40290) unit tests failures in core on windows
Title: Message Title James Nord created an issue Jenkins / JENKINS-40290 unit tests failures in core on windows Issue Type: Bug Assignee: Unassigned Attachments: output.log, surefire-reports.zip Components: core Created: 2016/Dec/07 7:32 PM Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) Maven home: c:\Java\maven-3.3.9\bin\.. Java version: 1.8.0_91, vendor: Oracle Corporation Java home: c:\Java\jdk1.8.0_91\jre Default locale: en_GB, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos" Priority: Minor Reporter: James Nord See attached log and surefire reports directory. Failed tests: RunTest.getLogReturnsAnRightOrder:192 expected:<[...truncated [6]8 B...]> but was:<[...truncated [7]8 B...]> SecretRewriterTest.recursionDetection:100 assert 6==sw.rewriteRecursive(t, st) | | || | | | 5| hudson.util.StreamTaskListener@19855799 | | C:\workarea\source\github\jenkinsci\temp\jenkins\core\target\junit5825166057877884911\t | hudson.util.SecretRewriter@bd09a26 false RunIdMigratorTest.legacy:86 expected:<...otherstuff> '}[, 99=?2014-01-02_03-04-05, lastFailedBuild=?-1, lastSuccessfulBuild=?99]}> but was:<...otherstuff> '}[]}> RunIdMigratorTest.reRunMigration:105 expected:<.../number> '},
