[JIRA] (JENKINS-36519) Exception DNSStateTask "Could not recover we are Down"
Title: Message Title Sam Gleske created an issue Jenkins / JENKINS-36519 Exception DNSStateTask "Could not recover we are Down" Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/08 7:07 AM Environment: Ubuntu 16.04 LTS Jenkins ver. 2.7.1 java version "1.7.0_79" Java(TM) SE Runtime Environment (build 1.7.0_79-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode) Priority: Minor Reporter: Sam Gleske It seems Jenkins is behaving strangely. I get the following stack traces when I start the latest LTS version. INFO: Jenkins is fully up and running Jul 07, 2016 11:59:08 PM javax.jmdns.impl.tasks.state.DNSStateTask run WARNING: Prober(fe80:0:0:0:dc4e:d109:3bcd:3585%2.local.).run() exception java.io.IOException: Operation not permitted at java.net.PlainDatagramSocketImpl.send(Native Method) at java.net.DatagramSocket.send(DatagramSocket.java:697) at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537) at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Jul 07, 2016 11:59:08 PM javax.jmdns.impl.JmDNSImpl __recover WARNING: RECOVERING Jul 07, 2016 11:59:08 PM javax.jmdns.impl.tasks.state.DNSStateTask run WARNING: Canceler(fe80:0:0:0:dc4e:d109:3bcd:3585%2.local.).run() exception java.io.IOException: Operation not permitted at java.net.PlainDatagramSocketImpl.send(Native Method) at java.net.DatagramSocket.send(DatagramSocket.java:697) at javax.jmdns.impl.JmDNSImpl.send(J
[JIRA] (JENKINS-36519) Exception DNSStateTask "Could not recover we are Down"
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-36519
Exception DNSStateTask "Could not recover we are Down"
Change By:
Sam Gleske
It seems Jenkins is behaving strangely. I get the following stack traces when I start the latest LTS version.{code}INFO: Jenkins is fully up and runningJul 07, 2016 11:59:08 PM javax.jmdns.impl.tasks.state.DNSStateTask runWARNING: Prober(fe80:0:0:0:dc4e:d109:3bcd:3585%2.local.).run() exception java.io.IOException: Operation not permittedat java.net.PlainDatagramSocketImpl.send(Native Method)at java.net.DatagramSocket.send(DatagramSocket.java:697)at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)at java.util.TimerThread.mainLoop(Timer.java:555)at java.util.TimerThread.run(Timer.java:505)Jul 07, 2016 11:59:08 PM javax.jmdns.impl.JmDNSImpl __recoverWARNING: RECOVERINGJul 07, 2016 11:59:08 PM javax.jmdns.impl.tasks.state.DNSStateTask runWARNING: Canceler(fe80:0:0:0:dc4e:d109:3bcd:3585%2.local.).run() exception java.io.IOException: Operation not permittedat java.net.PlainDatagramSocketImpl.send(Native Method)at java.net.DatagramSocket.send(DatagramSocket.java:697)at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)at java.util.TimerThread.mainLoop(Timer.java:555)at java.util.TimerThread.run(Timer.java:505)Jul 07, 2016 11:59:13 PM javax.jmdns.impl.DNSStatefulObject$DefaultImplementation waitForCanceledWARNING: Wait for canceled timed out: DNS: fe80:0:0:0:dc4e:d109:3bcd:3585%2.local. state: canceling 1 task: nullJul 07, 2016 11:59:13 PM javax.jmdns.impl.JmDNSImpl __recoverWARNING: fe80:0:0:0:dc4e:d109:3bcd:3585%2.local.recover() Could not recover we are Down!{code} Also, please note I don't have IPv6 configured on my host. Only IPv4.
Add Comment
[JIRA] (JENKINS-36520) MultiModule Maven Projects break after copied
Title: Message Title Michael Moossen created an issue Jenkins / JENKINS-36520 MultiModule Maven Projects break after copied Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Jul/08 7:19 AM Environment: Maven Integration Plugin 2.12.1 Jenkins 1.651 Tomcat 8.0.15 Oracle Java 1.8.0_51 SLES 11 SP3 64bit Labels: plugin jenkins configuration Priority: Major Reporter: Michael Moossen I have an issue while copying a multimodule maven project. after changing the root pom path and saving, the hidden rootmodule node in the config.xml is not updated. the only way i found to fix it, is to edit the config.xml and reload it. not sure sure of the consecuences of the wrong rootmodule because i found the error before using the copied job. Add Comment
[JIRA] (JENKINS-36521) Newline characters in commit logs not parsed correctly
Title: Message Title chikigai created an issue Jenkins / JENKINS-36521 Newline characters in commit logs not parsed correctly Issue Type: Bug Assignee: Unassigned Components: core, subversion-plugin Created: 2016/Jul/08 7:32 AM Environment: Master (Windows 7), Slaves (Windows 7, Ubuntu 14.04 LTS) Jenkins: 2.7.1 LTS Subversion plugin 2.6 Priority: Minor Reporter: chikigai I have several jobs building via subversion commit triggers. The commit messages contain several lines with the majority in the following format: Commiter Name: Details of change1. Details of change2. Up to Jenkins version 1.651.1, the build page displayed the commit message with several lines correctly under "change history". After upgrading to 1.651.3 and now 2.7.1, the commit message is displayed as a single line. For example, the commit message above would be displayed as follows: Commiter Name:Details of change1.Details of change2. Checking the page source of the build page, it looks like the newline characters in the commit message are being generated as:
[JIRA] (JENKINS-36498) Copying item with new name same as invisible item hijacks the invisible item.
Title: Message Title Taneli Vallo updated an issue Jenkins / JENKINS-36498 Copying item with new name same as invisible item hijacks the invisible item. Change By: Taneli Vallo Attachment: plugins_1_651_3.json Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36498) Copying item with new name same as invisible item hijacks the invisible item.
Title: Message Title Taneli Vallo updated an issue Jenkins / JENKINS-36498 Copying item with new name same as invisible item hijacks the invisible item. Change By: Taneli Vallo Environment: Ubuntu 14.04 LTSjava version "1.7.0_101"Jenkins version 1.651.3 & 2.7.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36521) Newline characters in commit logs not parsed correctly
Title: Message Title
chikigai updated an issue
Jenkins / JENKINS-36521
Newline characters in commit logs not parsed correctly
Change By:
chikigai
I have several jobs building via subversion commit triggers.The commit messages contain several lines with the majority in the following format:{code}Commiter Name:Details of change1.Details of change2.{code} Up to Jenkins version 1.651.1, the build page displayed the commit message with several lines correctly under "change history".After upgrading to 1.651.3 and now 2.7.1, the commit message is displayed as a single line.For example, the commit message above would be displayed as follows:{code}Commiter Name:Details of change1.Details of change2.{code}Checking the html page source of the build page, it looks like the newline characters in the commit message are being generated as:{code:html}
{code}As a result, the commit message is being displayed as a single line.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received thi
[JIRA] (JENKINS-36498) Copying item with new name same as invisible item hijacks the invisible item.
Title: Message Title Taneli Vallo updated an issue Jenkins / JENKINS-36498 Copying item with new name same as invisible item hijacks the invisible item. Change By: Taneli Vallo This issue is based on JENKINS-23457Replicating this issue in minimal, fresh environment. Only plugin installed is Matrix Authorisation Strategy Plugin, (added Folders Plugin for testing folders hijacking). Admin has all privileges, user has overall/read job/create privileges. Admin creates a template job that the user can copy, and another job the user can't see. The template job/folder has elevated privileges so the users can modify it. If the user copies the template job with same name as the hidden job, he overrides the data on the job, gaining access to the parts that were not overridden. When this happens with folders, only the folder data is replaced. This effectively means the user hijacks the folder and all the jobs and folders inside that folder.Duplicated the error in both 1.651.3 and 2.7.1 LTS versions. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36215) Weblogic Deployer plugin 3.3 issue
Title: Message Title Bharath Natarajan commented on JENKINS-36215 Re: Weblogic Deployer plugin 3.3 issue "But we are able to run this deploy job from Jenkins node. Is there anyway we can do that" : So you can or cannot deploy from a node? --We are unable to deploy from Windows node, presently we are trying to deploy from a Linux node, we are getting below error when doing so. [WeblogicDeploymentPlugin] - UNDEPLOYING ARTIFACT... $ /usr/java/jdk1.8.0_25/jre/bin/java -Xms256M -Xmx256M -cp /apps/opt/jenkinsnfs/internal-vd/jnmisc/weblogic/wlfullclient.jar:/apps/opt/jenkinsnfs/internal-vd/jnmisc/weblogic/wlthint3client.jar weblogic.Deployer -debug -remote -verbose -noexit -name vzkauthoring -targets WLS_Cluster -adminurl t3://xyz.com:2001 -user xyz -password xyz -undeploy -library [WeblogicDeploymentPlugin] - ARTIFACT UNDEPLOYED SUCCESSFULLY. [WeblogicDeploymentPlugin] - TRANSFERING LIBRARY : (local=vzkauthoring.war) (remote=null/vzkauthoring.war) to (ftp=ewdsacovn54.ebiz.verizon.com@null) ... org.jenkinsci.plugins.deploy.weblogic.exception.TransfertFileException: Failed to download file completely at org.jenkinsci.plugins.deploy.weblogic.util.FTPUtils.transfertFile(FTPUtils.java:61) at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:222) at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:173) at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:239) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at org.apache.commons.net.SocketClient.connect(SocketClient.java:171) at org.apache.commons.net.SocketClient.connect(SocketClient.java:192) at org.apache.commons.net.SocketClient.connect(SocketClient.java:285) at org.jenkinsci.plugins.deploy.weblogic.util.FTPUtils.transfertFile(FTPUtils.java:33) ... 12 more ERROR: [WeblogicDeploymentPlugin] - Failed to deploy. [INFO] [INFO] DEPLOYMENT FAILURE [INFO] "We are getting "No JDK error" whenever trying to use JDK installed in Jenkins node". Do you mean : "if we set the JDK installed on the jenkins node in the jenkins global configuration there's no problem."? In the node configuration (you can see on your jenkins master instance (http://://computer//configure)) did you try to override JDK installation with the jdk installation node path ? --if we set the JDK installed on the jenkins node in the jenkins global configuration there's "No JDK error". – Yes we tried to override
[JIRA] (JENKINS-31256) hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection
Title: Message Title jbq commented on JENKINS-31256 Re: hudson.Remoting.Engine#waitForServerToBack does not use credentials for connection I can confirm the fix solves the problem. I think you can mark this issue as resolved, at least a fresh install from the git remoting repo works for me, the slave reconnects successfully after the connection has dropped. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36522) An additional final stage is required to make previous stage fail when it should
Title: Message Title
Will Berriss created an issue
Jenkins / JENKINS-36522
An additional final stage is required to make previous stage fail when it should
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin, pipeline-view-plugin
Created:
2016/Jul/08 7:59 AM
Environment:
Red Hat 7 Linux (RHEL 7)
Labels:
pipeline
Priority:
Minor
Reporter:
Will Berriss
If I have a single stage that calls an sh script, and that script fails, and I use try..catch, then this stage is marked as green success in the pipeline view, but it should be marked as a failure. I can "fix" this by adding an additional final stage at the end of the Jenkinsfile and then the first stage (previous stage) will correctly be marked as failed. Here is some simple Jenkinsfile test code that shows how to reproduce this bug: #!groovy def machine1 = 'mymachine' node (machine1) { currentBuild.result='SUCCESS' stage "Stage One" try { sh "banana" } catch (err) { echo "Stage One Failed: $ {err} " currentBuild.result='FAILURE' } // // We need this final stage to mark the end of the preceding stage, // so that the preceding stage's code will fail if its sh script fails // // stage "End" echo "We've reached the end of the '$ {env.JOB_NAME} ' pipeline. The build has finished." } Simply uncomment the penultimate line that says stage "End" and you'll see what I mean.
[JIRA] (JENKINS-36523) An additional final stage is required to make previous stage fail when it should
Title: Message Title
Will Berriss created an issue
Jenkins / JENKINS-36523
An additional final stage is required to make previous stage fail when it should
Issue Type:
Bug
Assignee:
Sergei Egorov
Components:
pipeline-view-plugin
Created:
2016/Jul/08 8:05 AM
Environment:
Red Linux 7 (RHEL 7)
Labels:
jenkins
Priority:
Minor
Reporter:
Will Berriss
If I have a single stage the calls a sh script that fails, and I use try..catch, then the stage is marked as green success in the pipeline, but it should be marked as pink failed. If I add a final additional stage, then the original first stage (previous stage) will correctly my marked as failed. Here is some simple Jenkinsfile code that demonstrates the problem. #!groovy def machine1 = 'mymachine' node (machine1) { currentBuild.result='SUCCESS' stage "Stage One" try { sh "banana" } catch (err) { echo "Stage One Failed: $ {err} " currentBuild.result='FAILURE' } // // We need this final stage to mark the end of the preceding stage, // so that the preceding stage's code will fail if its sh script fails // // stage "End" echo "We've reached the end of the '$ {env.JOB_NAME} ' pipeline. The build has finished." } You will see that the first (and only) stage is marked as green passed. If you uncomment the penultimate line stage "End" then you will find the first stage to be marked as pink failed, which is correct. Thanks
[JIRA] (JENKINS-36522) An additional final stage is required to make previous stage fail when it should
Title: Message Title Will Berriss closed an issue as Duplicate Sorry, I thought the create failed - so I reported the same bug twice. Jenkins / JENKINS-36522 An additional final stage is required to make previous stage fail when it should Change By: Will Berriss Status: Open Closed 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.
[JIRA] (JENKINS-36522) An additional final stage is required to make previous stage fail when it should
Title: Message Title Will Berriss commented on JENKINS-36522 Re: An additional final stage is required to make previous stage fail when it should Sorry, I accidentally created the bug report twice. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Giovanni Gargiulo updated an issue Jenkins / JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Giovanni Gargiulo Attachment: Screen Shot 2016-07-08 at 09.52.58.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Giovanni Gargiulo updated an issue Jenkins / JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Giovanni Gargiulo Attachment: Screen Shot 2016-07-08 at 10.09.17.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36523) An additional final stage is required to make previous stage fail when it should
Title: Message Title
Will Berriss updated an issue
Jenkins / JENKINS-36523
An additional final stage is required to make previous stage fail when it should
Change By:
Will Berriss
If I have a single stage the pipeline that calls a an sh script that deliberately fails, and I use try..catch around the script , then the stage is marked as " green / success " in the pipeline, but it should be marked as " pink / failed. " If However, if I then add a final additional stage, then the original first stage (previous stage) will then correctly my be marked as "pink/ failed. " Here is some simple Jenkinsfile code that demonstrates the problem.#!groovydef machine1 = 'mymachine'node (machine1) {currentBuild.result='SUCCESS'stage "Stage One"try {sh "banana"}catch (err) {echo "Stage One Failed: ${err}"currentBuild.result='FAILURE'}// // We need this final stage to mark the end of the preceding stage,// so that the preceding stage's code will fail if its sh script fails// // stage "End"echo "We've reached the end of the '${env.JOB_NAME}' pipeline. The build has finished."}You will see that the first (and only) stage is marked as green passed.If you uncomment the penultimate line stage "End" then you will find the first stage to be marked as pink failed, which is correct.Thanks
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Giovanni Gargiulo commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Hi all, As of today with official plugins the issue is still outstanding. So no way to work it around. You will have to recur to the beta plugins of both: Git plugin Gut client plugin Steps to achieve this are: enable experimental plugins, process https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/ go to "Manage Jenkins" >> "Plugin Manager" >> "Updates" and then press "Check Now" you should something like below: Download the new experimental plugins, and restart. In the git "Advanced Submodules Behaviour" block tick the options like below:Happy days Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36490) Add API for fetching the current users info
Title: Message Title James Dumay resolved as Fixed Jenkins / JENKINS-36490 Add API for fetching the current users info Change By: James Dumay 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-36215) Weblogic Deployer plugin 3.3 issue
Title: Message Title Raphael CHAUMIER commented on JENKINS-36215 Re: Weblogic Deployer plugin 3.3 issue About the issue on failed deploy from linux node. You deployed your artifact as a library. It seems the user used for ftp transfer is not set. Can you check your configuration.xml? [WeblogicDeploymentPlugin] - TRANSFERING LIBRARY : (local=vzkauthoring.war) (remote=null/vzkauthoring.war) to (ftp=ewdsacovn54.ebiz.verizon.com@null) ... The deployment from a windows slave node needs a fix or an improvement. So I renamed the ticket and plan a fix for the next release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36215) Unable to deploy from a windows slave node
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-36215 Unable to deploy from a windows slave node Change By: Raphael CHAUMIER Summary: Weblogic Deployer plugin 3.3 issue Unable to deploy from a windows slave node Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36215) Unable to deploy from a windows slave node
Title: Message Title Raphael CHAUMIER updated an issue Jenkins / JENKINS-36215 Unable to deploy from a windows slave node Change By: Raphael CHAUMIER Labels: plugin weblogic-deployer-plugin-3.3 weblogic-deployer-plugin-3.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36215) Unable to deploy from a windows slave node
Title: Message Title Raphael CHAUMIER edited a comment on JENKINS-36215 Re: Unable to deploy from a windows slave node About the issue on failed deploy from linux node. You deployed your artifact as a library. It seems the localPath used for ftp transfer is not set. Can you check your configuration.xml?[WeblogicDeploymentPlugin] - TRANSFERING LIBRARY : (local=vzkauthoring.war) (remote=null/vzkauthoring.war) to (ftp=ewdsacovn54.ebiz.verizon.com@null) ...I can improve this by set setting a default local path if it's not set.The deployment from a windows slave node needs a fix or an improvement. So I renamed the ticket and plan a fix for the next release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36215) Unable to deploy from a windows slave node
Title: Message Title Raphael CHAUMIER edited a comment on JENKINS-36215 Re: Unable to deploy from a windows slave node About the issue on failed deploy from linux node. You deployed your artifact as a library. It seems the user localPath used for ftp transfer is not set. Can you check your configuration.xml?[WeblogicDeploymentPlugin] - TRANSFERING LIBRARY : (local=vzkauthoring.war) (remote=null/vzkauthoring.war) to (ftp=ewdsacovn54.ebiz.verizon.com@null) ... I can improve by set a default local path if it's not set. The deployment from a windows slave node needs a fix or an improvement. So I renamed the ticket and plan a fix for the next release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36524) Set a default localPath when there's not value
Title: Message Title Raphael CHAUMIER created an issue Jenkins / JENKINS-36524 Set a default localPath when there's not value Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2016/Jul/08 8:40 AM Priority: Minor Reporter: Raphael CHAUMIER Actually, When the plugin transfers a library to the remote server, it uses the localPath defined in the configuration.xml. If no value is set, the plugins try to download to null/ The improvement is to use a default localPath when no value is set and add a warning in the log file Add Comment
[JIRA] (JENKINS-36422) Unable to remove workspace
Title: Message Title Paul Allen resolved as Fixed Fixed in 1.4.3 Jenkins / JENKINS-36422 Unable to remove workspace Change By: Paul Allen 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-27885) Publish reconcile options
Title: Message Title Paul Allen resolved as Fixed Fixed in 1.4.2 Jenkins / JENKINS-27885 Publish reconcile options Change By: Paul Allen 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-36525) HTTP403 loading script.js on login page when anonymous doesn't have Overall/Read
Title: Message Title Vincent Latombe started work on JENKINS-36525 Change By: Vincent Latombe 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-36525) HTTP403 loading script.js on login page when anonymous doesn't have Overall/Read
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-36525 HTTP403 loading script.js on login page when anonymous doesn't have Overall/Read Issue Type: Bug Assignee: Vincent Latombe Components: form-element-path-plugin Created: 2016/Jul/08 8:48 AM Priority: Major Reporter: Vincent Latombe When being anonymous on an instance that is secured, if Overall/Read hasn't been granted to Anonymous, then retrieving the script.js from the plugin will issue a 403. Request GET /static/331cd866/plugin/form-element-path/script.js Response Authentication required This prevents elements from the login page from being properly decorated.
[JIRA] (JENKINS-36112) Add to p4publish groovy option to control +S modifiers (only the head revision of the file is stored in the depot)
Title: Message Title Paul Allen started work on JENKINS-36112 Change By: Paul Allen 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-36112) Add to p4publish groovy option to control +S modifiers (only the head revision of the file is stored in the depot)
Title: Message Title
Paul Allen commented on JENKINS-36112
Re: Add to p4publish groovy option to control +S modifiers (only the head revision of the file is stored in the depot)
There have been a few Groovy requests lately, so I'm in the process of writing 'p4groovy'. Similar to the other derived APIs (p4perl, p4ruby, p4python, etc...) you get a p4 object and can run commands/update specs. Let me know if you would like to try it out...
node('linux’) {
stage 'Build’
env.PATH = "${tool 'Maven 3'}/bin:${env.PATH}”
format = 'jenkins-${NODE_NAME}-${JOB_NAME}’
stream = '//streams/st1-main'
ws = [$class: 'StreamWorkspaceImpl', charset:'none', format:format , pinHost:false, streamName:stream]
p4 = p4 (credential: 'phooey1666', workspace: ws)
p4.run('sync', '-q, //...')
sh 'mvn clean package'
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36525) HTTP403 loading script.js on login page when anonymous doesn't have Overall/Read
Title: Message Title Vincent Latombe commented on JENKINS-36525 Re: HTTP403 loading script.js on login page when anonymous doesn't have Overall/Read Converting the
[JIRA] (JENKINS-36112) Add to p4publish groovy option to control +S modifiers (only the head revision of the file is stored in the depot)
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-36112 Add to p4publish groovy option to control +S modifiers (only the head revision of the file is stored in the depot) Change By: Paul Allen Assignee: Paul Allen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24591) Unable to run perforce commands within build steps
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-24591 Unable to run perforce commands within build steps Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33417) P4 and Sonar plugins generates circular dependency warning
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-33417 P4 and Sonar plugins generates circular dependency warning Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35667) p4 plugin should give a mechanism to delete p4 clients after use
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-35667 p4 plugin should give a mechanism to delete p4 clients after use Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27885) Publish reconcile options
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-27885 Publish reconcile options Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33734) P4 Plugin does not reload UI configuration using the Pipeline Workflow
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-33734 P4 Plugin does not reload UI configuration using the Pipeline Workflow Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34770) Report failure to Jenkins when a p4 submit fails so that the build can be marked Failed
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-34770 Report failure to Jenkins when a p4 submit fails so that the build can be marked Failed Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36409) Support Email Extension Plugin
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-36409 Support Email Extension Plugin Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32814) Add "Only poll using master" option
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-32814 Add "Only poll using master" option Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36422) Unable to remove workspace
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-36422 Unable to remove workspace Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-24070 Error: Wipe Out Workspace blocked by SCM Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35210) P4 plugin does not pass build review parameters to job after SECURITY-170 fix
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-35210 P4 plugin does not pass build review parameters to job after SECURITY-170 fix Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29979) Workflow plugin unable to save perforce paramters
Title: Message Title Paul Allen closed an issue as Fixed Released. Jenkins / JENKINS-29979 Workflow plugin unable to save perforce paramters Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33114) Multibranch project should provide separate SCM source instead of using Branch source
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-33114 Multibranch project should provide separate SCM source instead of using Branch source Change By: Rick Liu Environment: Jenkins 1.642.1 Jenkins 2.12 Oracle JDK 1.7Multi-Branch Project Plugin (any version) 0.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36526) Cannot parse Where map on windows
Title: Message Title Ondrej Kunc created an issue Jenkins / JENKINS-36526 Cannot parse Where map on windows Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 2016/Jul/08 9:21 AM Priority: Major Reporter: Ondrej Kunc Jenkins Perforce plugin can not parse where map on windows slave. It is not problem to do it on any other slave (running customized ubuntu), so problem is likely not on server. Tried multiple versions of P4 client (currently 2016.1). $ p4 -G where //... Caught exception communicating with perforce. Could not parse Where map.com.tek42.perforce.PerforceException: Could not parse Where map. at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:174) at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:83) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:72) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:431) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:1073) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:301) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.io.IOException: Expected 's', but got '108'. at hudson.plugins.perforce.PerforceSCMHelper.readPythonDictionary(PerforceSCMHelper.java:113) at hudson.plugins.perforce.PerforceSCMHelper.parseWhereMapping(PerforceSCMHelper.java:149) ... 12 more ERROR: Unable to communicate with perforce. Could not parse Where map.
[JIRA] (JENKINS-34998) Make CMake plugin compatible with pipeline
Title: Message Title Wilfried Goesgens commented on JENKINS-34998 Re: Make CMake plugin compatible with pipeline +1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34738) Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Robert Paasche commented on JENKINS-34738 Re: Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM You simply need to add to your pipline somthing like: properties [[$class: 'BuildDiscarderProperty', strategy: [$class: 'LogRotator', artifactDaysToKeepStr: '20', artifactNumToKeepStr: '30', daysToKeepStr: '20', numToKeepStr: '30']]] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19916) Confusing failure mode when no classes found by classPattern
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-19916 Confusing failure mode when no classes found by classPattern Change By: Martin Heinzerling Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27766) Jacoco with Jenkins on Apache Tomcat: /jacoco/classes does not exist
Title: Message Title Martin Heinzerling closed an issue as Duplicate Closed as duplicate of JENKINS-19916. Jenkins / JENKINS-27766 Jacoco with Jenkins on Apache Tomcat: /jacoco/classes does not exist Change By: Martin Heinzerling Status: Open Closed 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 http
[JIRA] (JENKINS-23544) Jacoco-plugin fails to compile when depending on newer jenkins builds.
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-23544 Jacoco-plugin fails to compile when depending on newer jenkins builds. Change By: Martin Heinzerling Labels: ReadyForDevelopment Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23544) Jacoco-plugin fails to compile when depending on newer jenkins builds.
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-23544 Jacoco-plugin fails to compile when depending on newer jenkins builds. Change By: Martin Heinzerling Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23544) Jacoco-plugin fails to compile when depending on newer jenkins builds.
Title: Message Title Martin Heinzerling commented on JENKINS-23544 Re: Jacoco-plugin fails to compile when depending on newer jenkins builds. We are at 1.609.3 now. JaCoCoColumnTest seems to be fine in general. Nevertheless HudsonTestCase reverences still exists and there are many commented tests, that need to be deleted or 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-23544) Jacoco-plugin fails to compile when depending on newer jenkins builds.
Title: Message Title Martin Heinzerling assigned an issue to Unassigned Jenkins / JENKINS-23544 Jacoco-plugin fails to compile when depending on newer jenkins builds. Change By: Martin Heinzerling Assignee: Ognjen Bubalo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23544) Jacoco-plugin fails to compile when depending on newer jenkins builds.
Title: Message Title Martin Heinzerling edited a comment on JENKINS-23544 Re: Jacoco-plugin fails to compile when depending on newer jenkins builds. We are at 1.609.3 now. JaCoCoColumnTest seems to be fine in general.Nevertheless HudsonTestCase reverences still exists and there are many commented tests, that need to be deleted or fixed. TODO:- cleanup all test (fix or delete them) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28636) Jacoco.exec can not be deleted
Title: Message Title Martin Heinzerling assigned an issue to Mike Craig Jenkins / JENKINS-28636 Jacoco.exec can not be deleted Change By: Martin Heinzerling Assignee: Ognjen Bubalo Mike Craig Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28636) Jacoco.exec can not be deleted
Title: Message Title Martin Heinzerling commented on JENKINS-28636 Re: Jacoco.exec can not be deleted Mike Craig, is this still an issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28636) Jacoco.exec can not be deleted
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-28636 Jacoco.exec can not be deleted Change By: Martin Heinzerling Labels: WaitingForInput Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16785) Stacktrace after plugin installation
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-16785 Stacktrace after plugin installation Change By: Martin Heinzerling Labels: WaitingForInput Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16785) Stacktrace after plugin installation
Title: Message Title Martin Heinzerling assigned an issue to Markus KARG Jenkins / JENKINS-16785 Stacktrace after plugin installation Change By: Martin Heinzerling Assignee: Nicolas De Loof Markus KARG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16785) Stacktrace after plugin installation
Title: Message Title Martin Heinzerling commented on JENKINS-16785 Re: Stacktrace after plugin installation Markus KARG, is this still an issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19057) ProjectName with variables in CopyArtifact < 1.26 is improperly upgraded.
Title: Message Title ikedam resolved as Won't Fix 1.26 is so old version and it's not reasonable to support it. Jenkins / JENKINS-19057 ProjectName with variables in CopyArtifact < 1.26 is improperly upgraded. Change By: ikedam Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit http
[JIRA] (JENKINS-36527) Not able to launch jenkins suddenly
Title: Message Title Shanker Mothkuri created an issue Jenkins / JENKINS-36527 Not able to launch jenkins suddenly Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/08 10:26 AM Priority: Blocker Reporter: Shanker Mothkuri I am new to Jenkins and configured master on my machine. Executed few builds to understand how it works. Configured a slave tried to trigger a build on slave thru master by binding a project to the slave. I changed the root directory of the slave and tried to trigger build on slave. I got "Oops!". The error shows even after restarting Jenkins. Following is the Stack Trace: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission at hudson.security.ACL.checkPermission(ACL.java:63) at hudson.model.Node.checkPermission(Node.java:461) at jenkins.model.Jenkins.getTarget(Jenkins.java:3880) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:674) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) 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:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doF
[JIRA] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Title: Message Title ikedam updated an issue Jenkins / JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Looks an issue of `FilePath` in Jenkins core. Anyway, all reports are exceptions from artifactarchiver and doesn't look related to copyartifact. Removed copyartifact from component/s. Change By: ikedam Component/s: copyartifact-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19197) Plug-in does not support matrix builds
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-19197 Plug-in does not support matrix builds Change By: Martin Heinzerling 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-36528) Return list of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Title: Message Title
Cameron I created an issue
Jenkins / JENKINS-36528
Return list of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Issue Type:
New Feature
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Jul/08 10:46 AM
Labels:
pipeline-build-step-plugin
Priority:
Minor
Reporter:
Cameron I
With the Pipeline Plugin, I'd like a list of environment variables to be returned from the build result of a job (like you can already with `duration` and `description` [already do](https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job)) For example, ``` def e = build "test-env" echo "$ {e.environment.GIT_COMMIT} " echo "$ {e.environment.FOO} " ``` I believe the fix is to add a whitelisted getEnvironment() method to the RunWrapper, similar to the one done in this merged PR [here](https://github.com/jenkinsci/workflow-support-plugin/pull/6) for JENKINS-36306 The current fix is to access the environment variables is to access it via the rawBuild, however that needs to be explicitly whitelisted as RunWrapper.getRawBuild is [blacklisted](https://github.com/jenkinsci/script-security-plugin/pull/69) ``` def e = build "test-env" echo "$ {e.rawBuild.environment.GIT_COMMIT} " ``` Thanks
[JIRA] (JENKINS-36528) Return list of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Title: Message Title
Cameron I updated an issue
Jenkins / JENKINS-36528
Return list of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Change By:
Cameron I
With the Pipeline Plugin, I'd like a list of environment variables to be returned from the build result of a job (like you can already with `duration` and `description` [already do](https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job))For example, ``` {code} def e = build "test-env"echo "${e.environment.GIT_COMMIT}"echo "${e.environment.FOO}" ``` {code} I believe the fix is to add a whitelisted getEnvironment() method to the RunWrapper, similar to the one done in this merged PR [here](https://github.com/jenkinsci/workflow-support-plugin/pull/6) for JENKINS-36306The current fix is to access the environment variables is to access it via the rawBuild, however that needs to be explicitly whitelisted as RunWrapper.getRawBuild is [blacklisted](https://github.com/jenkinsci/script-security-plugin/pull/69) ``` {code} def e = build "test-env"echo "${e.rawBuild.environment.GIT_COMMIT}" ``` {code} Thanks :)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36528) Return list of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Title: Message Title
Cameron I updated an issue
Jenkins / JENKINS-36528
Return list of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Change By:
Cameron I
With the Pipeline Plugin, I'd like a list of environment variables to be returned from the build result of a job (like you can already with `duration` and `description` [already do ]( | https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job ] ) ) For example,{code}def e = build "test-env"echo "${e.environment.GIT_COMMIT}"echo "${e.environment.FOO}"{code}I believe the fix is to add a whitelisted getEnvironment() method to the RunWrapper, similar to the one done in this merged PR [here ]( | https://github.com/jenkinsci/workflow-support-plugin/pull/6 ) ] for [ JENKINS-36306 ] The current fix is to access the environment variables is to access it via the rawBuild, however that needs to be explicitly whitelisted as RunWrapper.getRawBuild is [blacklisted ]( | https://github.com/jenkinsci/script-security-plugin/pull/69 ) ] {code}def e = build "test-env"echo "${e.rawBuild.environment.GIT_COMMIT}"{code}Thanks :)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-16787) Code coverage trend is empty if only one build exists
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-16787 Code coverage trend is empty if only one build exists Change By: Martin Heinzerling Labels: ReadyForDevelopment Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16787) Code coverage trend is empty if only one build exists
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-16787 Code coverage trend is empty if only one build exists Change By: Martin Heinzerling 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-23822) Wiki page has images in German
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-23822 Wiki page has images in German Change By: Martin Heinzerling Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23822) Wiki page has images in German
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-23822 Wiki page has images in German Change By: Martin Heinzerling Labels: ReadyForDevelopment Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Niccolò Olivieri commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials I tryed not to use the aws configuration on the server, so: add the AWS Credential to Jenkins in the build: Build Environment -> Use secret text(s) or file(s) -> AWS Build -> Execute Shell export AWS_DEFAULT_REGION='eu-west-1' eval `aws ecr get-login` Build -> Docker Build & Publish -> do not put the registry credentials In this way my build is ok Hope it helped, I spent two days searching a solution!!! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Grou
[JIRA] (JENKINS-35436) Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports
Title: Message Title Martin Heinzerling commented on JENKINS-35436 Re: Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports TODO: add legend or 'title' tooltip Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35436) Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports
Title: Message Title Martin Heinzerling updated an issue Jenkins / JENKINS-35436 Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports Change By: Martin Heinzerling Labels: ReadyForDevelopment Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35436) Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports
Title: Message Title Martin Heinzerling assigned an issue to Unassigned Jenkins / JENKINS-35436 Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports Change By: Martin Heinzerling Assignee: Ognjen Bubalo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36528) Return map of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Title: Message Title Cameron I updated an issue Jenkins / JENKINS-36528 Return map of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper Change By: Cameron I Summary: Return list map of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33832) Slack Notifications not available directly in Job configuration
Title: Message Title James Perrin commented on JENKINS-33832 Re: Slack Notifications not available directly in Job configuration I've have the same issue too with 2.01 in jenkins 1.651.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-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title
Wilfried Goesgens created an issue
Jenkins / JENKINS-36529
jenkins blocks on pipeline, won't terminate until restart
Issue Type:
New Feature
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2016/Jul/08 11:22 AM
Priority:
Minor
Reporter:
Wilfried Goesgens
Tried to run this tiny script from an git scm pipeline: #!groovy node { git url: 'https://github.com/arangodb/arangodb.git' if (isUnix()) { echo 'Hello Unix' sh 'cmake . ' sh 'make' } else { echo 'hello else' } } It starts cloning into arangodb: [Pipeline] { [Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/arangodb/arangodb.git # timeout=10 Fetching upstream changes from https://github.com/arangodb/arangodb.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/arangodb/arangodb.git +refs/heads/:refs/remotes/origin/ > git rev-parse refs/remotes/origin/master^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision ed80c3d2e88953e5054c1ea43e35eda39052f043 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ed80c3d2e88953e5054c1ea43e35eda39052f043 # timeout=10 it then remains stuck. the git process vanishes from top/pstree. The complete pipeline will then remain in 'active' state, without a reaction to the X-button. Only restarting jenkins will get it out of this state.
[JIRA] (JENKINS-36440) Build Failure Analyzer: consoleFull/contextMenu is invalid
Title: Message Title Jinha Park updated an issue Jenkins / JENKINS-36440 Build Failure Analyzer: consoleFull/contextMenu is invalid Change By: Jinha Park As you hover over the right-side of "Indication_1", a down-arrow appears. If you click on the arrow, a contextMenu XHR request fires in the background. Unfortunately, they all seem to fail with a 404 "not found" response.Error message on Web debugger console: prototype.js:1585 POST http://jenkins/job/job_name/build_number/consoleFull/contextMenu 404 (Not Found)I believe it is because of invalid URL for contextMenu; consoleFull/contextMenu.Context menus for others work with JSON, however, consoleFull/contextMenu just redirects to the build page, also hard to expect any contextMenu from console output. Thus I would like to know Just in case it has been probably caused from old version of plug-in ? , please let me know. Otherwise, I strongly recommend that the URL for down-arrow menu can should be removed to avoid confusion modified for users proper purposes, for example a selection for highlighted (claimed) lines for the build log indication . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Martin Heinzerling commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Sorry my bad, just saw the blocker, but Jacoco is actually not using analysis-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-36530) Support for Jenkinsfile
Title: Message Title francisdb created an issue Jenkins / JENKINS-36530 Support for Jenkinsfile Issue Type: Bug Assignee: vjuranek Components: ws-cleanup-plugin Created: 2016/Jul/08 11:50 AM Priority: Minor Reporter: francisdb We would like to use the plugin in our pipelines Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Daniel Beck commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release Jesse Glick You mentioned yesterday that this cannot be implemented, period? Could you update this issue accordingly? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36525) HTTP403 loading script.js on login page when anonymous doesn't have Overall/Read
Title: Message Title Jesse Glick resolved as Fixed Merged. Jenkins / JENKINS-36525 HTTP403 loading script.js on login page when anonymous doesn't have Overall/Read Change By: Jesse Glick 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-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title
Wilfried Goesgens updated an issue
Jenkins / JENKINS-36529
jenkins blocks on pipeline, won't terminate until restart
Change By:
Wilfried Goesgens
Tried to run this tiny script from an git scm pipeline: #!groovynode { git url: 'https://github.com/arangodb/arangodb.git' if (isUnix()) {echo 'Hello Unix'sh 'cmake . 'sh 'make' } else {echo 'hello else' }} Pressed twice 'play' by accident. stopped the upper run. This seemed to have voided my workspace. The checkout command below would block in all subsequent attepmts: It starts cloning into arangodb:[Pipeline] {[Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/arangodb/arangodb.git # timeout=10Fetching upstream changes from https://github.com/arangodb/arangodb.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/arangodb/arangodb.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision ed80c3d2e88953e5054c1ea43e35eda39052f043 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ed80c3d2e88953e5054c1ea43e35eda39052f043 # timeout=10it then remains stuck. the git process vanishes from top/pstree. The complete pipeline will then remain in 'active' state, without a reaction to the X-button. Only restarting jenkins will get it out of this state. Flushing my workspace resolved this issue.
Add Comment
[JIRA] (JENKINS-25416) text parameter with newlines causing the default goal run
Title: Message Title Daniel Beck resolved as Fixed Fix released in 2.12 Jenkins / JENKINS-25416 text parameter with newlines causing the default goal run 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-36215) Unable to deploy from a windows slave node
Title: Message Title Bharath Natarajan commented on JENKINS-36215 Re: Unable to deploy from a windows slave node Hi Raphael CHAUMIER, Thanks for your input. Regarding Linux node deploy issue, I hope I had to use "Publish Over FTP Plugin" to set my local path for FTP transfers in Jenkins Configuration. I am doing that. Will keep you posted on this. And to answer your question "What was the problem with the key authentication ?" --We were getting "JSAFE Invalid Use case exception" when trying to use key authentication. Not sure about the root cause for this issue. We will be debugging this issue soon after fixing our problem with Linux node, will keep you posted. Thanks for your guidance. With Regards, Bharath N Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35906) Exception saving jobs using ClearCase after update to Jenkins Core 2.9 (Our case 14788)
Title: Message Title Daniel Beck resolved as Fixed Fix released in 2.12 Jenkins / JENKINS-35906 Exception saving jobs using ClearCase after update to Jenkins Core 2.9 (Our case 14788) Change By: Daniel Beck 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.
[JIRA] (JENKINS-32027) Jobs with very long configuration cause script errors in browser and extremely long loading times (10+ minutes)
Title: Message Title Daniel Beck resolved as Fixed Fix released in 2.12 Jenkins / JENKINS-32027 Jobs with very long configuration cause script errors in browser and extremely long loading times (10+ minutes) 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
[JIRA] (JENKINS-36280) DescriptorVisibilityFilters are not applied to DumbSlave's launchers or retention strategies
Title: Message Title Daniel Beck resolved as Fixed Fix released in 2.12 Jenkins / JENKINS-36280 DescriptorVisibilityFilters are not applied to DumbSlave's launchers or retention strategies Change By: Daniel Beck 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.go
[JIRA] (JENKINS-36277) Process lauchner should check if working directory exists
Title: Message Title Daniel Beck resolved as Fixed Fix released in 2.12 Jenkins / JENKINS-36277 Process lauchner should check if working directory exists 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-36528) Return map of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Title: Message Title
Cameron I updated an issue
Jenkins / JENKINS-36528
Return map of environment variables of job in org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper
Change By:
Cameron I
With the Pipeline Plugin, I'd like a list of environment variables to be returned from the build result of a job (like you can already with `duration` and `description` [already do|https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job] with `duration` and `description` )For example,{code}def e = build "test-env"echo "${e.environment.GIT_COMMIT}"echo "${e.environment.FOO}"{code}I believe the fix is to add a whitelisted getEnvironment() method to the RunWrapper, similar to the one done in this merged PR [here|https://github.com/jenkinsci/workflow-support-plugin/pull/6] for [JENKINS-36306]The current fix is to access the environment variables is to access it via the rawBuild, however that needs to be explicitly whitelisted as RunWrapper.getRawBuild is [blacklisted|https://github.com/jenkinsci/script-security-plugin/pull/69]{code}def e = build "test-env"echo "${e.rawBuild.environment.GIT_COMMIT}"{code}Thanks :)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36531) Pipeline sh generating rogue characters
Title: Message Title
Sion Williams created an issue
Jenkins / JENKINS-36531
Pipeline sh generating rogue characters
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Jul/08 12:20 PM
Labels:
shell pipeline
Priority:
Blocker
Reporter:
Sion Williams
I have a rather complex command that needs to be run in an "sh" step:
withCredentials([[$class: 'UsernamePasswordMultiBinding', credentialsId: '3548afa5-6360-428f-8ae2-xx', passwordVariable: 'dbPassword', usernameVariable: 'dbUser']]) {
def cmd = """kubectl run ${serviceName} --image=${dockerRegistry}/${serviceName}:${env.BUILD_NUMBER} --replicas=2 --port=${externalPort} --env=\'MONGODB_URL=mongodb://${env.dbUser}:${env.dbPassword}@${dbCluster}/${serviceName}-uat?${dbOptions}\' --expose --service-overrides='{ "spec": { "type": "LoadBalancer" }}' || true"""
// execute shell for the command above
sh cmd
}
Now, if I print this command, it renders as expected.
kubectl run my-service --image=.eu-west-1.amazonaws.com/my-service:124 --replicas=2 --port=8083 --env='MONGODB_URL=mongodb://:@-shard-00-00-.mongodb.net:27017,-shard-00-01-.mongodb.net:27017,-shard-00-02-.mongodb.net:27017/my-service-uat?ssl=true&replicaSet=-shard-0
[JIRA] (JENKINS-36532) Additional refactor on Run Selector plugin
Title: Message Title Alexandru Somai created an issue Jenkins / JENKINS-36532 Additional refactor on Run Selector plugin Issue Type: Task Assignee: Alexandru Somai Components: run-selector-plugin Created: 2016/Jul/08 12:31 PM Priority: Major Reporter: Alexandru Somai Additional refactoring needs to be done for the Run Selector plugin. Where possible, replace @DataBoundConstructor with @DataBoundSetter to minimize the Snippet Generator code output for Pipeline. Include the suggestions from the https://github.com/jenkinsci/run-selector-plugin/pull/1 Find an appropriate name for the exposed API method. Current is pickBuildToCopyFrom(). A possible candidate may be selectRun() Any other changes that may seem appropriate. Add Comment
[JIRA] (JENKINS-36507) git plugin 2.5.2 breaks some existing builds
Title: Message Title
Mark Waite edited a comment on JENKINS-36507
Re: git plugin 2.5.2 breaks some existing builds
It appears that your build is defined with a narrow refspec ("refs/heads/develop"), but your build then assumes that the entire repository was fetched, even though a narrow refspec was provided. I believe that means your build depends on bug JENKINS-31393 in the git plugin.JENKINS-31393 was fixed in git plugin 2.5.1. Prior to git plugin 2.5.1, the refspec provided by the user was ignored for the initial fetch. That meant that no matter what refspec was provided by the user, the entire repository was fetched. Users with large repositories didn't like that the refspec they constructed was ignored on initial fetch, since it increased the size of the cloned repository and took longer to clone that repository.With the fix of JENKINS-31393, the refspec is honored on the initial fetch. One alternative to handle that case is to add an additional refspec to your job definition which will include all the commits. For example, your current refspec seems to be "refs/heads/develop". The new refspec could be{noformat}refs/heads/develop +refs/heads/*:refs/remotes/origin/*{noformat}I'm not sure how your build could have been working for months with git plugin 2.5.0, since git plugin 2.5.0 released less than a month ago, 19 Jun 2016. Were you using one of the 2.5.0 beta versions prior to 19 Jun 2016, or was it that you were using git plugin 2.4.4 successfully for months?There is a note in the [changelog|https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Changelog] under 2.5.1 describing the risk of this happening. It says "some users may depend on the old, poor behavior that the plugin fetched all refspecs even though the user had specified a narrower refspec. Those users can delete their refspec or modify it to be as wide as they need". Unfortunately, I didn't see a way to preserve the old behavior (fetch everything) and fix JENKINS-31393. Another way to retain compatibility with the old "fetch everything initially" behavior would be to require that users who want the fix for JENKINS-31393 must add the "Additional Behaviour" for "Advanced clone behaviours". In that "advanced behaviors" there would be a check box added to "Honor refspec on initial clone". If a large number of users are affected by this same condition, that may be the preferred approach.
Add Comment
[JIRA] (JENKINS-36507) git plugin 2.5.2 breaks builds which use a narrow refspec but expect all refs were fetched
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-36507 git plugin 2.5.2 breaks builds which use a narrow refspec but expect all refs were fetched Change By: Mark Waite Summary: git plugin 2.5.2 breaks some existing builds which use a narrow refspec but expect all refs were fetched Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36533) I am running Jenkins on Websphere Application Server and trying to deploy my application on the same server using Websphere deployer plugin. While installing artifact, it is giv
Title: Message Title Shilpa N created an issue Jenkins / JENKINS-36533 I am running Jenkins on Websphere Application Server and trying to deploy my application on the same server using Websphere deployer plugin. While installing artifact, it is giving NotSerializableException for ConfigServiceServerProxy. Issue Type: Bug Assignee: Unassigned Components: websphere-deployer-plugin Created: 2016/Jul/08 12:47 PM Priority: Blocker Reporter: Shilpa N I am running Jenkins on Websphere Application Server 8.5.5 and trying to deploy my application on the same server. It is a local one. I have installed the websphere deployer plugin. But during deployment I am facing an issue. While installing artifact, it is giving NotSerializableException for ConfigServiceServerProxy class. I am not able to resolve this issue since this class is getting added in preferences which is later checked against Serializable or not. [7/8/16 17:54:43:975 IST] 0092 SystemErr R java.io.NotSerializableException: com.ibm.ws.management.configservice.ConfigServiceServerProxy [7/8/16 17:54:43:976 IST] 0092 SystemErr R at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1203) [7/8/16 17:54:43:976 IST] 0092 SystemErr R at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:364) [7/8/16 17:54:43:976 IST] 0092 SystemErr R at java.util.Hashtable.writeObject(Hashtable.java:971) [7/8/16 17:54:43:976 IST] 0092 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [7/8/16 17:54:43:976 IST] 0092 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) [7/8/16 17:54:43:976 IST] 0092 SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [7/8/16 17:54:43:976 IST] 0092 SystemErr R at java.lang.reflect.Method.invoke(Method.java:618) [7/8/16 17:54:43:976 IST] 0092 SystemErr R at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1060) [7/8/16 17:54:
[JIRA] (JENKINS-36215) Unable to deploy from a windows slave node
Title: Message Title Raphael CHAUMIER edited a comment on JENKINS-36215 Re: Unable to deploy from a windows slave node Concerning the localPath, the plugin uses remoteDir value to transfer the library ```xml _weblogic.remote.host_ _weblogic.remote.user_ _weblogic.remote.password_ /remote/file/to/path/used/to/deploy/libraries ``` Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36215) Unable to deploy from a windows slave node
Title: Message Title Raphael CHAUMIER commented on JENKINS-36215 Re: Unable to deploy from a windows slave node Concerning the localPath, the plugin uses remoteDir value to transfer the library ```xmlweblogic.remote.host weblogic.remote.user weblogic.remote.password /remote/file/to/path/used/to/deploy/libraries ``` Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
