[JIRA] (JENKINS-38186) java.io.NotSerializableException: groovy.lang.MapWithDefault
Title: Message Title
Bahram Parsapour created an issue
Jenkins / JENKINS-38186
java.io.NotSerializableException: groovy.lang.MapWithDefault
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
core, pipeline
Created:
2016/Sep/14 6:59 AM
Labels:
pipeline
Priority:
Major
Reporter:
Bahram Parsapour
Take the code snippet below to reproduce the failing build.
@NonCPS
static def createMapWithDefault() {
return [:].withDefault { [] }
}
def defaultMap= createMapWithDefault()
echo "defaultMap: ${defaultMap}"
node('default') {
stage('checkout') {
checkout scm
}
}
Console Output shows:
[Pipeline] echo
defaultMap: [:]
[Pipeline] node
[Pipeline] End of Pipeline
java.io.NotSerializableException: groovy.lang.MapWithDefault
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65)
at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56)
at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50)
at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
at java.util.HashMap.internalW
jenkinsci-issues@googlegroups.com
Title: Message Title simon chen updated an issue Jenkins / JENKINS-38185 Could not find JSON in http://updates.jenkins-ci.org/update-center.json?id=default&version=2.22 Change By: simon chen Environment: centos7 ping updates.jenkins-ci.org, return 52.202.51.185 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
jenkinsci-issues@googlegroups.com
Title: Message Title simon chen updated an issue Jenkins / JENKINS-38185 Could not find JSON in http://updates.jenkins-ci.org/update-center.json?id=default&version=2.22 Change By: simon chen Environment: centos7 openjdk-1.8.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-32462) Checking Status of remote job fail
Title: Message Title Rishabh Sharma commented on JENKINS-32462 Re: Checking Status of remote job fail I am also facing same issue with Jenkins while triggering remote jenkins job: Remote Jenkins server returned empty response or invalid JSON - but we can still proceed with the remote build. ERROR: Build step failed with exception java.lang.NullPointerException at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.isRemoteJobParameterized(RemoteBuildConfiguration.java:1167) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:488) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:136) at hudson.model.Run.execute(Run.java:1738) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Build step 'Trigger a remote parameterized job' marked build as failure Notifying upstream projects of job completion Finished: FAILURE Is it just the same we are discussing here? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37288) option to continue processing dsl if an error occurs
Title: Message Title Daniel Spilker commented on JENKINS-37288 Re: option to continue processing dsl if an error occurs This conceptually difficult. Depending on the setting for "Action for removed jobs", Job DSL will disable or remove any job that has not been generated. So if a script should generate job A and B, but fails to generate B, Job DSL can't decide if job B has not been generated on purpose (and should be disabled or deleted) or if it has not been generated due to an error (and should not be disabled or deleted). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
squalou jenkins commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
on the prod environments : jenkins lts 2.7.2 (sidenote : even the 'lts' cycle has accelerated these times, just can't catch up the pace! 2.7.4 just released, we were about to update to .3) pipeline 2.2
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35315) Timestamper panel is not displayed because of mixed content block
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35315 Re: Timestamper panel is not displayed because of mixed content block Code changed in jenkins User: Steven Brown Path: src/main/java/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2.java src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2/script.js src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2/style.css src/main/webapp/annotator.js src/main/webapp/style.css http://jenkins-ci.org/commit/timestamper-plugin/bb7e2ce76a86127ffa3de95a4aec9d6419a38412 Log: JENKINS-38085 Revert to default way of loading the script and CSS A custom approach was previously used to load the script and CSS for displaying the timestamps. It caused the script and CSS to be reloaded when the Timestamper plugin is upgraded or downgraded, rather than being cached for the next day. It seems this doesn't work for everyone (JENKINS-38085), so I'm reverting back to the default behaviour. Note that it is known to work with HTTPS and through a HTTPS proxy (JENKINS-35315) at least for some users. As a result, the TimestampAnnotatorFactory class will have to be manually renamed each time the script or CSS is changed in a new 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-38085) Settings not appearing in the sidebar
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38085 Re: Settings not appearing in the sidebar Code changed in jenkins User: Steven Brown Path: src/main/java/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2.java src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2/script.js src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2/style.css src/main/webapp/annotator.js src/main/webapp/style.css http://jenkins-ci.org/commit/timestamper-plugin/bb7e2ce76a86127ffa3de95a4aec9d6419a38412 Log: JENKINS-38085 Revert to default way of loading the script and CSS A custom approach was previously used to load the script and CSS for displaying the timestamps. It caused the script and CSS to be reloaded when the Timestamper plugin is upgraded or downgraded, rather than being cached for the next day. It seems this doesn't work for everyone (JENKINS-38085), so I'm reverting back to the default behaviour. Note that it is known to work with HTTPS and through a HTTPS proxy (JENKINS-35315) at least for some users. As a result, the TimestampAnnotatorFactory class will have to be manually renamed each time the script or CSS is changed in a new 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Christoph Obexer commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Matrix projects have such an option called "Use custom child workspace". If multibranch projects had such an option it could be used to solve this issue and the feature branch disk space problem at the same time. I hope "My current proposal is to fix this in the core code for default workspace selection, since I have heard no reports of the project name per se being a problem" means that this will then simply be the default? aka all branches building in the same folder called after the project? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19142) Don't add jobs to a view
Title: Message Title Vincent Latombe resolved as Fixed Fixed in 2.22 Jenkins / JENKINS-19142 Don't add jobs to a view Change By: Vincent Latombe Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38187) jenkins.model.Jenkins.slaveAgentPort is not honored since Jenkins 2.0
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-38187 jenkins.model.Jenkins.slaveAgentPort is not honored since Jenkins 2.0 Change By: Vincent Latombe SetupWizard forcibly disables jnlp even if it is explicitely explicitly set through this system property documented on https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38187) jenkins.model.Jenkins.slaveAgentPort is not honored since Jenkins 2.0
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-38187 jenkins.model.Jenkins.slaveAgentPort is not honored since Jenkins 2.0 Issue Type: Bug Assignee: Vincent Latombe Components: core Created: 2016/Sep/14 8:25 AM Priority: Major Reporter: Vincent Latombe SetupWizard forcibly disables jnlp even if it is explicitely set through this system property documented on https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties Add Comment This message was
[JIRA] (JENKINS-38168) job-params being overwritten by template
Title: Message Title Matthew Storey commented on JENKINS-38168 Re: job-params being overwritten by template for assistance on people rolling back: in order to fix after rolling back, we found that you have to fully restart jenkins, edit the original template file and save it, then go into the templated job and re-enter the job-specific parameters. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37088) Run docker build inside the ephemeral slave
Title: Message Title Nicolas De Loof commented on JENKINS-37088 Re: Run docker build inside the ephemeral slave This is definitively something we want to support. bind mount for docker.sock is the easy part, the more complex one is for the remoting container user (which own the workspace volume) to have access to it, i.e belong to 'docker' group. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26107) Allow stage to operate as a labelled block
Title: Message Title mohamed badran commented on JENKINS-26107 Re: Allow stage to operate as a labelled block I haven't installed the latest released version but any idea what the code will look like for it? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37339) Global security throws NullPointerException after installing Slack Plugin
Title: Message Title Martin Klinke commented on JENKINS-37339 Re: Global security throws NullPointerException after installing Slack Plugin I have also installed the Slack Plugin and now not even the login page of Jenkins works. The stack trace is similar to the one mentioned in the "Caused by" section, at least it's also the call to WebhookEndpoint.getUrlName where the NPE occurs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37339) Global security throws NullPointerException after installing Slack Plugin
Title: Message Title Martin Klinke commented on JENKINS-37339 Re: Global security throws NullPointerException after installing Slack Plugin However, I have deactivated the plugin and reactivated it upon restart (which caused another restart). Now it seems to be working. I can also open the Global Security page without problems. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38187) jenkins.model.Jenkins.slaveAgentPort is not honored since Jenkins 2.0
Title: Message Title Vincent Latombe started work on JENKINS-38187 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-38187) jenkins.model.Jenkins.slaveAgentPort is not honored since Jenkins 2.0
Title: Message Title Vincent Latombe updated JENKINS-38187 Jenkins / JENKINS-38187 jenkins.model.Jenkins.slaveAgentPort is not honored since Jenkins 2.0 Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38188) The filename, directory name, or volume label syntax is incorrect when running the apigeetool command on build step
Title: Message Title Junnes Pineda created an issue Jenkins / JENKINS-38188 The filename, directory name, or volume label syntax is incorrect when running the apigeetool command on build step Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jenkins.PNG Components: batch-task-plugin, nodejs-plugin Created: 2016/Sep/14 9:08 AM Environment: I am running on a WIndows 7 64bit Jenkins ver. 2.7.1 Nodejs with apigeetool installed Priority: Blocker Reporter: Junnes Pineda I am getting this error whenever I build my jenkins job: Building in workspace C:\Program Files (x86)\Jenkins\workspace\ApigeeBuildAndDeploy [ApigeeBuildAndDeploy] $ cmd /c call C:\windows\TEMP\hudson1850497119464236620.bat C:\Program Files (x86)\Jenkins\workspace\ApigeeBuildAndDeploy>cd C:\Program Files\nodejs C:\Program Files\nodejs>nodevars.bat Your environment has been set up for using Node.js 6.5.0 (x64) and npm. The filename, directory name, or volume label syntax is incorrect. Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE
[JIRA] (JENKINS-38148) NullPointerException in AccuRev Launcher
Title: Message Title Joseph Petersen commented on JENKINS-38148 Re: NullPointerException in AccuRev Launcher Have you considered giving your jenkins accurev login admin privileges? Trying to capture these null pointers that can occur with runCommand Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36683) Exclusion Plugin Resources set in jobs generated from DSL do not show up on the list of declared resources inside Exclusion control panel.
Title: Message Title
Daniel Spilker commented on JENKINS-36683
Re: Exclusion Plugin Resources set in jobs generated from DSL do not show up on the list of declared resources inside Exclusion control panel.
The problems seems to be upper vs lower case for the resource names. The Exclusions plugin seems to use upper case only and converts lower case to upper case when saving the config page. This should do:
job('example') {
wrappers {
exclusionResources('FIRST', 'SECOND')
}
steps {
criticalBlock {
shell('echo Hello World!')
}
}
}
I will fix Job DSL so that it generates upper case names.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38189) Build remoting image on jenkins startup
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-38189 Build remoting image on jenkins startup Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-slaves-plugin Created: 2016/Sep/14 9:18 AM Priority: Minor Reporter: Nicolas De Loof Remoting do copy classes to the slave into jarcache. On startup, we could build a pre-populated docker image from jenkins master, so that slave launch would be faster as cache would be fully populated with all jenkins installation classes. Add Comment
[JIRA] (JENKINS-32580) Plugin enable/disable information and dependencies are broken
Title: Message Title Arend v. Reinersdorff updated an issue Jenkins / JENKINS-32580 Plugin enable/disable information and dependencies are broken Change By: Arend v. Reinersdorff Attachment: Jenkins Update Center - Windows Slaves Plugin.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-32580) Plugin enable/disable information and dependencies are broken
Title: Message Title Arend v. Reinersdorff commented on JENKINS-32580 Re: Plugin enable/disable information and dependencies are broken I still have this problem with Jenkins 2.7.4 LTS. For example the Windows Slaves Plugin cannot be disabled, it claims that the jQuery plugin and other plugins depend on it. See attached screenshot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Craig Carnell commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Can confirm I have this issue also. With yum update I can see: root 8466 1.4 0.0 110128 992 pts/0 R+ 09:32 0:42 chown -R jenkins /var/lib/jenkins It takes a very long time to run CentOS Linux release 7.2.1511
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the same logs indefinitely
Title: Message Title Lutz Neugebauer commented on JENKINS-37575 Re: Jenkins node keeps sending the same logs indefinitely Hello, I’m experiencing this issue, too. My suspicion is that this is caused by the way org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep currently works. In its check() method the call to controller.writeLog(…) is effected by the Timer defined in that method. As far as I understand the Timer interrupts the execution after 10 seconds. If writeLog() has not completed within those 10 seconds it is interrupted. Within those 10 seconds it has already written a certain amount of the log, but at the next attempt it will restart again. If the log on the node has meanwhile grown and machine load or network load conditions don’t allow to complete the writeLog() within 10 seconds this will loop indefinitely until disk space is filled up. The dependency on those conditions makes it that hard to reproduce. I observed the following exception in log approximately every 10 seconds when the problem occurred: Sep 14, 2016 10:26:49 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution check could not check [workspace path here] java.lang.InterruptedException at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:400) at java.util.concurrent.FutureTask.get(FutureTask.java:187) at hudson.remoting.Request.call(Request.java:158) at hudson.remoting.Channel.call(Channel.java:780) at hudson.FilePath.act(FilePath.java:1007) at hudson.FilePath.act(FilePath.java:996) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.writeLog(FileMonitoringTask.java:132) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:264) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:233) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Note: The line numbers from classes of the durable-task plugin may vary compared to official versions since I have changes in there relating to https://github.com/jenkinsci/durable-task-plugin/pull/28. Regards, Lutz Add Comment
[JIRA] (JENKINS-33103) AccuRev Stream color is reset without a clear purpose
Title: Message Title Joseph Petersen assigned an issue to Joseph Petersen Jenkins / JENKINS-33103 AccuRev Stream color is reset without a clear purpose Change By: Joseph Petersen Assignee: Scott Tatum Joseph Petersen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the same logs indefinitely
Title: Message Title Lutz Neugebauer updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the same logs indefinitely Change By: Lutz Neugebauer Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33103) AccuRev Stream color is reset without a clear purpose
Title: Message Title Joseph Petersen commented on JENKINS-33103 Re: AccuRev Stream color is reset without a clear purpose This option, should it be global for the accurev server or for each job? I do believe the option should start out as false, that way users would have to enable it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
mariem baccar created an issue
Jenkins / JENKINS-38190
Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Artifact Resolver.png, Build.png, Error-Build.PNG, maven-repository-artifact.PNG, POM.xml
Components:
repository-connector-plugin
Created:
2016/Sep/14 9:46 AM
Environment:
Jenkins 2.11, Nexus 2.12.0.01, Maven 3.3.9
Priority:
Critical
Reporter:
mariem baccar
Hello, We are using repository-connector plugin (version 1.1.3) for resolving maven repository artifact in jenkins 2.11. When I launch the "build with parameters", it succed to give me the release versions stored in Nexus 2.12.0.01. But after choosing a version and building the job, it fails with the following error (org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'version' in '$ {version} '). For more details please check the attached files. I am looking for your help. Best regards
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
mariem baccar updated an issue
Jenkins / JENKINS-38190
Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Change By:
mariem baccar
Hello,We are using repository-connector plugin (version 1.1.3) for resolving maven repository artifact in jenkins 2.11. When I launch the "build with parameters", it succed to give me the release versions stored in Nexus 2.12.0.01. But after choosing a version and building the job, it fails with the following error ( : org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'version' in '${version}' ). For more details please check the attached files.I am looking for your help.Best regards
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
mariem baccar updated an issue
Jenkins / JENKINS-38190
Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Change By:
mariem baccar
Hello,We are using repository-connector plugin (version 1.1.3) for resolving maven repository artifact in jenkins 2.11. When I launch the "build with parameters", it succed to give me the release versions stored in Nexus 2.12.0.01. But after choosing a version and building the job, it fails with the following error: ( org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'version' in '${version}' ) For more details please check the attached files.I am looking for your help.Best regards
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
Fo
[JIRA] (JENKINS-38191) Files uploaded using File Parameter are not copied in matrix job
Title: Message Title Jaroslaw Niec created an issue Jenkins / JENKINS-38191 Files uploaded using File Parameter are not copied in matrix job Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 2016/Sep/14 10:00 AM Environment: Jenkins 1.651 Matrix Project Plugin 1.7.1 Priority: Major Reporter: Jaroslaw Niec Files are not copied to child jobs workspace if it was uploaded by File Parameter. This functionality was working few months ago. It is probably connected with security-170 How to reproduce: 1) Create matrix job with few axis 2) Make job parametrized with at least one File Parameter 3) As a build step print content of WORKSPACE (dir or ls) 4) Run job and upload some file. 5) WORKSPACE of child jobs is still empty. Add Comment
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
Bilel Krichen commented on JENKINS-38190
Re: Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Hi, I have the same problem,anyone can need Help us
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38192) workspace isn't reused between builds
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-38192 workspace isn't reused between builds Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-slaves-plugin Created: 2016/Sep/14 10:13 AM Priority: Minor Reporter: Nicolas De Loof jenkinsci/slave docker image has change so /home/jenkins isn't a volume (see https://github.com/jenkinsci/docker-jnlp-slave/issues/14) as job workspace is created under /home/jenkins/workspace, files here aren't stored in volume and can't be retrieved on next build. Add Comment
[JIRA] (JENKINS-38192) workspace isn't reused between builds
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-38192 workspace isn't reused between builds Change By: Nicolas De Loof Issue Type: Improvement Bug Priority: Minor 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-38193) Incorrect state shown for non completed stages after a failure
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-38193
Incorrect state shown for non completed stages after a failure
Issue Type:
Bug
Assignee:
Cliff Meyers
Attachments:
Screen Shot 2016-09-14 at 8.18.40 PM.png
Components:
blueocean-plugin
Created:
2016/Sep/14 10:22 AM
Priority:
Minor
Reporter:
Michael Neale
If you create a 3 stage pipeline, run it a few times (successfully) and then change it so it breaks in an early stage, the stage graph will show the incorrect "waiting" state.
node {
stage('first') {
//after a few runs break this script
sh 'echo 42'
}
stage('second') {
sh 'echo 42'
}
stage('third') {
sh 'echo 42'
}
}
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Reeves created an issue Jenkins / JENKINS-38194 Ampersand in Git password causes authentication failure Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2016/Sep/14 10:23 AM Environment: Windows server 2012 R2 git-client-plugin 2.0.0 Priority: Critical Reporter: Mark Reeves Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials) Escaping the & in the password stored in the credentials by using ^& work round the issue (but if the same credentials are used elsewhere they will break) Add Comment
[JIRA] (JENKINS-38193) Incorrect state shown for non completed stages after a failure
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38193 Incorrect state shown for non completed stages after a failure Change By: Michael Neale Sprint: 1.0-b07/b08 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title Oliver Gondža commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging DJ Lee, because the fix was naturally absorbed by the next LTS line based on 2.17. RC to be pushed today. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Reeves updated an issue Jenkins / JENKINS-38194 Ampersand in Git password causes authentication failure Change By: Mark Reeves Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials)Escaping the & in the password stored in the credentials by using ^& work works round the issue (but if the same credentials are used elsewhere they will break) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Reeves updated an issue Jenkins / JENKINS-38194 Ampersand in Git password causes authentication failure Change By: Mark Reeves Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials)Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere they then will break) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Reeves updated an issue Jenkins / JENKINS-38194 Ampersand in Git password causes authentication failure Change By: Mark Reeves Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials)Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere then they will break) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38179) Authentication Error with GIT Client version 2.0.0
Title: Message Title Mark Reeves commented on JENKINS-38179 Re: Authentication Error with GIT Client version 2.0.0 I've just opened JENKINS-38194 which seems similar (& in password) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38192) workspace isn't reused between builds
Title: Message Title Nicolas De Loof commented on JENKINS-38192 Re: workspace isn't reused between builds fixed by https://github.com/Dockins/docker-slaves-plugin/commit/b8906d7d638d1a7f253900a2a9285d0d44d1abcf Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
mariem baccar updated an issue
Jenkins / JENKINS-38190
Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Change By:
mariem baccar
Hello,We are using repository-connector plugin (version 1.1.3) for resolving maven repository artifact in jenkins 2.11. When I launch the "build with parameters", it succed succeed to give me the release versions stored in Nexus 2.12.0.01. But after choosing a version and building the job, it fails with the following error: (org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'version' in '${version}')For more details please check the attached files.I am looking for your help.Best regards
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.c
[JIRA] (JENKINS-37625) exception in logs when hitting /monitoring?action=gc
Title: Message Title evernat commented on JENKINS-37625 Re: exception in logs when hitting /monitoring?action=""> I have not reproduced the issue using Jenkins 2.21 and monitoring plugin 1.61.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-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
yosra AKROUT commented on JENKINS-38190
Re: Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
hello, I have the same problem too, can you help us please. Thank you.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38195) Jenkins available plugin list is emtpy
Title: Message Title Hariharan Kuppusamy created an issue Jenkins / JENKINS-38195 Jenkins available plugin list is emtpy Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Sep/14 10:41 AM Environment: Jenkins ver. 2.7.4 Priority: Minor Reporter: Hariharan Kuppusamy Fresh installed Jenkins ver. 2.7.4 and tried to access/install some plugins but it is empty with the message saying "No updates". If I try to update the update site url and "check now", it thorws below exception, java.io.IOException: Could not find JSON in http://updates.jenkins-ci.org/update-center.json?id=default&version=2.7.4 at hudson.model.DownloadService.loadJSON(DownloadService.java:174) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:176) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1615) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) 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.MetaCla
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-38196 NPE during node provision Issue Type: Bug Assignee: Scott Hebert Components: foreman-node-sharing-plugin Created: 2016/Sep/14 10:46 AM Priority: Major Reporter: Pavel Janoušek My testing environment went to the state when it is unable to provision any Foreman node. In the server.log, I've found this exception: 2016-09-14 04:59:50,035 SEVERE [hudson.triggers.SafeTimerTask] (jenkins.util.Timer [#8]) Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@77be2155 failed java.lang.NullPointerException at com.redhat.foreman.ForemanSharedNodeCloud.canProvision(ForemanSharedNodeCloud.java:155) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:661) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:286) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:57) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:775) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title Pavel Janoušek commented on JENKINS-38196 Re: NPE during node provision I'll digger deeper what goes wrong... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-38196
NPE during node provision
Change By:
Pavel Janoušek
My testing environment went to the state when it is unable to provision any Foreman node. In the server.log, I've found this exception:{code}2016-09-14 04:59:50,035 SEVERE [hudson.triggers.SafeTimerTask] (jenkins.util.Timer [#8]) Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@77be2155 failedjava.lang.NullPointerExceptionat com.redhat.foreman.ForemanSharedNodeCloud.canProvision(ForemanSharedNodeCloud.java:155)at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:661)at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:286)at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:57)at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:775)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)at java.lang.Thread.run(Thread.java:682){code}. In * in the Foreman there are defined three compatible nodes currently, each with some label assigned. * click on Test connection works
Add Comment
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title Pavel Janoušek edited a comment on JENKINS-38196 Re: NPE during node provision * just Just realized, I've defined a job which isn't restricted to *any* label... so the Label is probably *null*, what'd be the cause of this issue. Working on verification of my idea... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-38196
NPE during node provision
Change By:
Pavel Janoušek
My testing environment went to the state when it is unable to provision any Foreman node. In the server.log, I've found this exception:{code}2016-09-14 04:59:50,035 SEVERE [hudson.triggers.SafeTimerTask] (jenkins.util.Timer [#8]) Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@77be2155 failedjava.lang.NullPointerExceptionat com.redhat.foreman.ForemanSharedNodeCloud.canProvision(ForemanSharedNodeCloud.java:155)at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:661)at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:286)at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:57)at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:775)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)at java.lang.Thread.run(Thread.java:682){code}. The sourcecode of canProvision:{code}@Override public boolean canProvision(Label label) {Map hostsMap = getForemanAPI().getCompatibleHosts();Set hosts = hostsMap.keySet();for (String host: hosts) {boolean match = label.matches(Label.parse(hostsMap.get(host)));if (match) {return true;}}return false;}{code}line 155:{code}boolean match = label.matches(Label.parse(hostsMap.get(host)));{code} * in the Foreman there are defined three compatible nodes currently, each with some label assigned.* click on Test connection works
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title Pavel Janoušek commented on JENKINS-38196 Re: NPE during node provision just realized, I've defined a job which isn't restricted to any label... so the Label is probably null, what'd be the cause of this issue. Working on verification of my idea... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title
Pavel Janoušek edited a comment on JENKINS-38196
Re: NPE during node provision
Just realized, I've defined a job which isn't restricted to *any* label... so the {{ Label }} is probably *null*, what'd be the cause of this issue. Working on verification of my idea...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35269) Job configuration UI Layout is broken
Title: Message Title Roee Rakovsky commented on JENKINS-35269 Re: Job configuration UI Layout is broken Daniel Beckgus reiber Hi Friends, Is there any idea when this bug is going to be 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-37753) REGRESSION: Steps showing up as incomplete when they are in fact complete
Title: Message Title Michael Neale commented on JENKINS-37753 Re: REGRESSION: Steps showing up as incomplete when they are in fact complete As discussed with Thorsten Scherler we think the problem is that when the job completes it does not reload the stage graph... (it was designed to) with a fetch? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title
Michael Neale commented on JENKINS-37962
Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly
OK after some digging and a hangout with Thorsten Scherler I think we are closer now. Using Viveks PR, the followin are the remaining bugs: 1) You are not able to select any parallel branch other than the default one 2) when a branch finishes early, it doesn't show its state as completed in the stage graph. The pipeline to reproduce this:
node {
stage("hey") {
sh 'ping -c 5 www.apple.com'
}
stage("par") {
parallel (
"b1" : {
sh 'ping -c 2 www.apple.com'
},
"b2" : {
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
}
)
}
stage("ho") {
sh 'ping -c 10 www.apple.com'
}
}
Add this to a non multibranch pipeline, and follow along. Try to click on "b2" - you will note it never selects it. "b1" will finish early, but never shows up in the stage graph as finished early.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38197) -DskipTests doesn't work on this project
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-38197 -DskipTests doesn't work on this project Issue Type: Bug Assignee: Scott Hebert Components: foreman-node-sharing-plugin Created: 2016/Sep/14 11:15 AM Priority: Minor Reporter: Pavel Janoušek The standard ways how to skip test execution as mvn package -DskipTests or mvn install -DskipTests doesn't work, I've found as working usage of -Dmaven.test.skip=true or -Dskip.unit.tests=true only. This should be fixed. Add Comment
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title
Michael Neale edited a comment on JENKINS-37962
Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly
OK after some digging and a hangout with [~tscherler] I think we are closer now. Using Viveks PR, the followin are the remaining bugs: 1) You are not able to select any parallel branch other than the default one2) when a branch finishes early, it doesn't show its state as completed in the stage graph. The pipeline to reproduce this: {noformat}node {stage("hey") {sh 'ping -c 5 www.apple.com'}stage("par") {parallel ("b1" : {sh 'ping -c 2 www.apple.com'},"b2" : {sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'} )}stage("ho") {sh 'ping -c 10 www.apple.com'}}{noformat}Add this to a non multibranch pipeline, and follow along. Try to click on "b2" - you will note it never selects it. "b1" will finish early, but never shows up in the stage graph as finished early.It seems to "steal focus" back to b1 (which has finished early) in this case. If you replace all the step with "ping -c 10 www.apple.com" you see slightly differnet behavior (but still not correct)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
Ghassen Khalil ATI commented on JENKINS-38190
Re: Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Same criticial problem here !
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37753) REGRESSION: Steps showing up as incomplete when they are in fact complete
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37753 REGRESSION: Steps showing up as incomplete when they are in fact complete Change By: Michael Neale Attachment: Screen Shot 2016-09-14 at 8.41.38 PM.png Attachment: Screen Shot 2016-09-14 at 8.45.02 PM.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-37753) REGRESSION: Steps showing up as incomplete when they are in fact complete
Title: Message Title Michael Neale commented on JENKINS-37753 Re: REGRESSION: Steps showing up as incomplete when they are in fact complete Related, the logs are truncated when you click back to a previously executed stage after you have followed along the pipeline: Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37753) REGRESSION: Steps showing up as incomplete when they are in fact complete
Title: Message Title
Michael Neale edited a comment on JENKINS-37753
Re: REGRESSION: Steps showing up as incomplete when they are in fact complete
Related, the logs are truncated when you click back to a previously executed stage *after* you have followed along the pipeline: !Screen Shot 2016-09-14 at 8.41.38 PM.png|thumbnail! !Screen Shot 2016-09-14 at 8.45.02 PM.png|thumbnail!(these logs should have more lines in them, it is only showing the last bit). The pipeline to see this: {noformat}node {stage("hey") {sh 'ping -c 5 www.apple.com'}stage("par") {parallel ("b1" : {sh 'ping -c 2 www.apple.com'},"b2" : {sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'sh 'sleep 1 && ping -c 1 www.apple.com'} )}stage("ho") {sh 'ping -c 10 www.apple.com'}}{noformat}create that as a basic pipeline and follow it along to see it.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from thi
[JIRA] (JENKINS-24955) Quiet period doesn't work
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-24955 Quiet period doesn't work Change By: pooja shah Attachment: Screen Shot 2016-09-14 at 5.17.36 pm.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-24955) Quiet period doesn't work
Title: Message Title pooja shah commented on JENKINS-24955 Re: Quiet period doesn't work Hi Daniel, yes root cause is: default param "build?delay=0sec" in job's build with parameters option, it overrides the 'quiet period' setting any idea how can I make it work when I'm calling this job in my build step? refer screenshot, test_test is the job which has quiet period set but it doesn't work because of the obvious reason Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24955) Quiet period doesn't work
Title: Message Title pooja shah edited a comment on JENKINS-24955 Re: Quiet period doesn't work Hi Daniel, Jenkins version: 1.629 yes root cause is: default param "build?delay=0sec" in job's build with parameters option, it overrides the 'quiet period' settingany idea how can I make it work when I'm calling this job in my build step? refer screenshot, test_test is the job which has quiet period set but it doesn't work because of the obvious reason!Screen Shot 2016-09-14 at 5.17.36 pm.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24955) Quiet period doesn't work
Title: Message Title pooja shah commented on JENKINS-24955 Re: Quiet period doesn't work seeing similar issue : https://issues.jenkins-ci.org/browse/JENKINS-6660 any work around? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6660) quiet period ignored for parameterized builds
Title: Message Title pooja shah edited a comment on JENKINS-6660 Re: quiet period ignored for parameterized builds does it still exist broken on Jenkins version: 1.629 ?Getting same issue: https://issues.jenkins-ci.org/browse/JENKINS-24955any work around would be helpful Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6660) quiet period ignored for parameterized builds
Title: Message Title pooja shah commented on JENKINS-6660 Re: quiet period ignored for parameterized builds does it still exist on Jenkins version: 1.629 ? Getting same issue: https://issues.jenkins-ci.org/browse/JENKINS-24955 any work around would be helpful Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title Pavel Janoušek commented on JENKINS-38196 Re: NPE during node provision Confirmed, the cause of the issue is an empty Label. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30058) Support Maven Core Extensions
Title: Message Title Marco Descher updated an issue Jenkins / JENKINS-30058 Support Maven Core Extensions Change By: Marco Descher Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30058) Support Maven Core Extensions
Title: Message Title Marco Descher commented on JENKINS-30058 Re: Support Maven Core Extensions From my point of view this feature is getting more and more important with every day that passes. New developers are likely to prefer the pomless style against the manual management of poms ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title Pavel Janoušek started work on JENKINS-38196 Change By: Pavel Janoušek 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-38196) NPE during node provision
Title: Message Title Pavel Janoušek commented on JENKINS-38196 Re: NPE during node provision PR with the fix sent. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38196) NPE during node provision
Title: Message Title Pavel Janoušek assigned an issue to Pavel Janoušek Jenkins / JENKINS-38196 NPE during node provision Change By: Pavel Janoušek Assignee: Scott Hebert Pavel Janoušek Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34979) Port allocation duplicate on "Concurrent builds"
Title: Message Title Ryan Cocks commented on JENKINS-34979 Re: Port allocation duplicate on "Concurrent builds" Rick Oosterholt - do you know what version Jenkins you were on before you updated? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38198) Jenkins and Maven SOA BPEL project deployment issue
Title: Message Title Atul Gupta created an issue Jenkins / JENKINS-38198 Jenkins and Maven SOA BPEL project deployment issue Issue Type: Bug Assignee: Oliver Gondža Attachments: pom.xml, pom.xml Components: jenkins-test-harness Created: 2016/Sep/14 12:42 PM Environment: development Labels: jenkins plugin api configuration Priority: Major Reporter: Atul Gupta Hi Team, I am trying to deploy SOA BPEL project using Jenkins and Maven, but I am facing one issue here. I am not able to deploy the code using Jenkins while I am able to deploy my code using Maven. I am getting below error message. Please find an attachment of my POM file. this file is present in my user/.m2/ folder. com.oracle.soa:sar-common:pom:12.2.1-0-0 Building in workspace C:\Users\.jenkins\workspace\sca-test Updating https:///svn/repos/oracleidp/BPEL/Trunk/test-soa-application at revision '2016-09-14T17:55:37.554 +0530' At revision 232 No changes for https://-/svn/repos/oracleidp/BPEL/Trunk/test-soa-application since the previous build Parsing POMs ERROR: Failed to parse POMs org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Failure to find com.oracle.soa:sar-common:pom:12.2.1-0-0 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be
[JIRA] (JENKINS-37985) please allow build job:name to have console output in blueocean pipeline view
Title: Message Title Jesse Glick resolved as Duplicate Should be done by the build step, not B.O. Jenkins / JENKINS-37985 please allow build job:name to have console output in blueocean pipeline view Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://g
[JIRA] (JENKINS-38156) Need branch name and other details from parallel branches
Title: Message Title Jesse Glick resolved as Duplicate JENKINS-28119 would give you the log message. If you just want the branch name, you can do this already with catch blocks. Jenkins / JENKINS-38156 Need branch name and other details from parallel branches Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+uns
[JIRA] (JENKINS-38156) Need branch name and other details from parallel branches
Title: Message Title Jesse Glick commented on JENKINS-38156 Re: Need branch name and other details from parallel branches As to the originally proposed syntax, no, this was deleted for good reason in JENKINS-25894. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38019) Pipeline Job:Integration with MongoDB required
Title: Message Title Jesse Glick assigned an issue to Unassigned Not exactly sure what is being requested. Probably you just want a sh step that runs some MongoDB CLI client. Jenkins / JENKINS-38019 Pipeline Job:Integration with MongoDB required Change By: Jesse Glick Component/s: mongodb-plugin Component/s: pipeline-build-step-plugin Labels: pipeline pipeline-build-step-plugin Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37867) Adding “Perform Maven Release” option from Jenkinsfile
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37867 Adding “Perform Maven Release” option from Jenkinsfile Change By: Jesse Glick 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-37867) Adding “Perform Maven Release” option from Jenkinsfile
Title: Message Title Jesse Glick assigned an issue to James Nord The M2 Release plugin only works with Maven projects, not freestyle or Pipeline. I doubt something like this would be implemented per se. Better to create a separate job dedicated to running releases, which would have different triggering—for example, no polling or SCM trigger, but a string parameter asking to select the branch to release—and different build steps (mvn -B release:prepare release:perform, probably just pass/fail, no detailed reporting needed). Jenkins / JENKINS-37867 Adding “Perform Maven Release” option from Jenkinsfile Change By: Jesse Glick Component/s: m2release-plugin Component/s: pipeline-build-step-plugin Labels: pipeline Assignee: Jesse Glick James Nord Add Comment
[JIRA] (JENKINS-38199) Allow native as an alias for @NonCPS
Title: Message Title
Jesse Glick created an issue
Jenkins / JENKINS-38199
Allow native as an alias for @NonCPS
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-cps-plugin
Created:
2016/Sep/14 1:19 PM
Labels:
groovy
Priority:
Minor
Reporter:
Jesse Glick
The @NonCPS annotation is hard to remember, and the meaning of the acronym is cryptic. The rule we want users to remember is something like: "there is Pipeline script code, which is limited in functionality, for example using non-Serializable local variables, but can run steps; and there is native code, which can do anything (subject to script security where applicable) but cannot run steps or other Pipeline script code". So perhaps it would be more intuitive to use the existing native method modifier:
native String findSomeMetadata() {
currentBuild.rawBuild.getAction(SomeJenkinsAPI).someGetter
}
sh "this is Pipeline script but it can call ${findSomeMetadata()}"
Would need compiler patches, since by default the method attribute is left in and at runtime you get
java.lang.ClassFormatError: Code attribute in native or abstract methods in class file WorkflowScript
[JIRA] (JENKINS-36541) Integrate UI with Capabilities API on backend and update Folder filtering logic
Title: Message Title Cliff Meyers resolved as Won't Do Jenkins / JENKINS-36541 Integrate UI with Capabilities API on backend and update Folder filtering logic Change By: Cliff Meyers Status: In Progress Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36541) Integrate UI with Capabilities API on backend and update Folder filtering logic
Title: Message Title Cliff Meyers commented on JENKINS-36541 Re: Integrate UI with Capabilities API on backend and update Folder filtering logic Folders are being filtered out via the ?filter=no-folders query param, so there is no UI work to do here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title
Christian Höltje commented on JENKINS-38111
Re: github organization should allow 'clean before checkout' behavior
The way GitHub Org Folder works is the first git checkout you see is the Jenkins Server (in a "sub job" or "mini job" or whatever it is called) checking out the source on the Jenkins Server (In a directory like JENKINS_HOME/workspace///@script}}) to get the Jenkinsfile. It then uses that Jenkinsfile to actually do the build. The Jenkinsfile then allocates Workspaces via node() {} commands which may-or-may-not be empty.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34979) Port allocation duplicate on "Concurrent builds"
Title: Message Title Ryan Cocks commented on JENKINS-34979 Re: Port allocation duplicate on "Concurrent builds" I just did some more investigation. I noticed the plugin hasn't been updated in a while and our version of Jenkins is a year old anyway so it's unlikely we have upgraded anything recently. However, we did add a second pool around the time we started seeing this issue. If I remove that second pool then the bug disappears and we see jobs getting allocated different ports again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Waite commented on JENKINS-38194 Re: Ampersand in Git password causes authentication failure Mark Reeves are you using a username / password (as used with https based git repository access) where the the password contains the "&" character, or are you using a private key protected by a passphrase where the passphrase contains the "&" character (as used for ssh and scp based git repository access)? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37867) Adding “Perform Maven Release” option from Jenkinsfile
Title: Message Title Harsha B commented on JENKINS-37867 Re: Adding “Perform Maven Release” option from Jenkinsfile Hi Jesse, Thanks for the response. Ok. That was my plan B. I would like to provide an option to the user in the pipeline job to trigger this maven release job. I am thinking of using jobDSL command to create a Maven release job from Jenkinsfile for every pipeline job that gets created. Is there a way to ensure that this step in Jenkinsfile is run only once (.i.e. the very first time a new pipeline job is created) ? I was thinking may I will set some env variable and run this step based on whether it is set or not. Is there a any other way of doing that? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Reeves commented on JENKINS-38194 Re: Ampersand in Git password causes authentication failure username/password yes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Reeves edited a comment on JENKINS-38194 Re: Ampersand in Git password causes authentication failure username/password yes . , using http not https (internal stash server) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38179) Authentication Error with GIT Client version 2.0.0
Title: Message Title Cole Mietzner commented on JENKINS-38179 Re: Authentication Error with GIT Client version 2.0.0 Mark Waite: The credentials are Username / Password using the credentials manager. I have not tried any other locations. I dont think there is anything unique about our environment. I was able to clone a repo on the node using the username and password without using Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Cole Mietzner commented on JENKINS-38194 Re: Ampersand in Git password causes authentication failure Mark Reeves, you might be right with this being a similar issue that I was having in JENKINS-38179, I dont have a "&" character in my password but I do have a ")" and a "^". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Mark Waite commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior As far as I know, those behaviors are available from jobs generated by the GitHub Organizations Folder plugin, so long as the behavior is added in the Jenkinsfile. Refer to [the JENKINS-22547 branch}https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-22547/Jenkinsfile] of my jenkins-bugs repository for an example of a Jenkinsfile which includes several additional behaviors added to the checkout() step, including CleanBeforeCheckout. Could you try that technique and see if it works as expected in your GitHub Organization Folders? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38194) Ampersand in Git password causes authentication failure
Title: Message Title Mark Reeves commented on JENKINS-38194 Re: Ampersand in Git password causes authentication failure Pretty certain the "^" would have broken it, which means this is effectively a duplicate of yours. Under certain circumstances (Delayed Expansion has been enabled in the command session) '!' will also have the same 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-37831) Favoriting on Matrix style project broken
Title: Message Title Cliff Meyers updated JENKINS-37831 Jenkins / JENKINS-37831 Favoriting on Matrix style project broken Change By: Cliff Meyers Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
