[JIRA] [core] (JENKINS-29909) New method to force setResult
Title: Message Title
James Nord commented on JENKINS-29909
Re: New method to force setResult
Have you looked at any alternative job type.? Eg with workflow
node ('linux') {
sh 'mvn install'
archive '**/target/*.war's
sh 'scp project/target/*.war remote.server/path
sh 'ssh remote.server Runtestsinbackground.sh'
}
// Wait forcompletion - no executor used here
Input 'waitfor job complete' // trigger this with a curl call
node ('blah') {
// get the results from remote server
// parse them
// set result
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Title: Message Title James Nord commented on JENKINS-19139 Re: Xvnc plugin fails if the job has a space in the name which breaks other tools - could we not use a temporary file (appropriately secured) in /tmp as a workaround if the user wants to make progress? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Title: Message Title
James Nord edited a comment on JENKINS-19139
Re: Xvnc plugin fails if the job has a space in the name
Should be worked around in the plugin as you can start vncserver fine if you quote the string and escape the slashes spaces on Linux.It will require a long long time for any fix to make it into all distributions.{noformat}root@linux-slave:~# export XAUTHORITY="/home/jenkins/with\ space/.xauth"root@linux-slave:~# vncserverNew 'linux-slave:2 (root)' desktop is linux-slave:2Starting applications specified in /home/jenkins/.vnc/xstartupLog file is /home/jenkins/.vnc/linux-slave:2.log{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-19139) Xvnc plugin fails if the job has a space in the name
Title: Message Title James Nord reopened an issue Should be worked around in the plugin as you can start vncserver fine if you quote the string and escape the slashes on Linux. It will require a long long time for any fix to make it into all distributions. root@linux-slave:~# export XAUTHORITY="/home/jenkins/with\ space/.xauth" root@linux-slave:~# vncserver New 'linux-slave:2 (root)' desktop is linux-slave:2 Starting applications specified in /home/jenkins/.vnc/xstartup Log file is /home/jenkins/.vnc/linux-slave:2.log Jenkins / JENKINS-19139 Xvnc plugin fails if the job has a space in the name Change By: James Nord Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-29909) New method to force setResult
Title: Message Title James Nord commented on JENKINS-29909 Re: New method to force setResult This sounds like an abuse of a job. When it is finished it should be finished - and changing the Result after that fact can cause confusion. It sounds like you should be using a job type that does not consume an executor whilst it is waiting for the external job - but that can still accurately show the job as running. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-30081) Failing the build if all tests failed should be optional.
Title: Message Title James Nord closed an issue as Cannot Reproduce Jenkins / JENKINS-30081 Failing the build if all tests failed should be optional. Change By: James Nord Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-30081) Failing the build if all tests failed should be optional.
Title: Message Title James Nord commented on JENKINS-30081 Re: Failing the build if all tests failed should be optional. This is not the behaviour. Failed tests do not fall the build. If you are seeing this phase reopen with json, job configuration and log from a failed build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30084) FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.
Title: Message Title James Nord commented on JENKINS-30084 Re: FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L1439-L1446 https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L1539-L1549 The queue appears to just shunt flywieght tasks to blocked which then the NodeProvisioner will not care about creating new nodes for unless a slave with the right label is online. Aug 20, 2015 6:08:00 AM hudson.model.Queue scheduleInternal FINE: hudson.matrix.MatrixProject@a3c7785[myMatrixProject] added to queue Aug 20, 2015 6:08:00 AM hudson.model.Queue maintain FINE: Queue maintenance started hudson.model.Queue@111ab215 Aug 20, 2015 6:08:00 AM hudson.model.Queue$BlockedItem enter FINE: hudson.model.Queue$BlockedItem:hudson.matrix.MatrixProject@a3c7785[myMatrixProject]:71 is blocked Aug 20, 2015 6:08:00 AM hudson.model.Queue maintain FINE: Queue maintenance started hudson.model.Queue@111ab215 Aug 20, 2015 6:08:00 AM com.cloudbees.jenkins.QuickProvision$1 run FINE: standard.nodeProvisioner.suggestReviewNow() -> queue.length()=0 Aug 20, 2015 6:08:03 AM hudson.model.Queue maintain FINE: Queue maintenance started hudson.model.Queue@111ab215 Aug 20, 2015 6:08:04 AM jenkins.metrics.api.Metrics$HealthChecker$3 run FINE: Started jenkins.metrics.api.Metrics$HealthChecker Aug 20, 2015 6:08:04 AM jenkins.metrics.api.Metrics$HealthChecker$3 run FINE: Finished jenkins.metrics.api.Metrics$HealthChecker. 2 ms Aug 20, 2015 6:08:08 AM hudson.model.Queue maintain FINE: Queue maintenance started hudson.model.Queue@111ab215 Aug 20, 2015 6:08:10 AM hudson.slaves.NodeProvisioner$2 run FINE: Queue length 0 is less than the available capacity 0. No provisioning strategy required Aug 20, 2015 6:08:10 AM hudson.slaves.NodeProvisioner$2 run FINE: Queue length 0 is less than the available capacity 0. No provisioning strategy required Aug 20, 2015 6:08:10 AM hudson.slaves.NodeProvisioner$2 run FINE: Queue length 0 is less than the available capacity 0. No provisioning strategy required ... a node is provisioned sometime later for a different project... ... Aug 20, 2015 8:50:54 AM hudson.model.Queue$BlockedItem leaveFINE: hudson.model.Queue$BlockedItem:hudson.matrix.MatrixProject@a3c7785[myMatrixProject]:71 no longer blocked Add Comment
[JIRA] [core] (JENKINS-30084) FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.
Title: Message Title James Nord created an issue Jenkins / JENKINS-30084 FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever. Issue Type: Bug Assignee: Unassigned Components: core Created: 21/Aug/15 1:11 PM Environment: Jenkins 1.609.2 matrix project 1.6 (and others?) Labels: regression flyweight queue Priority: Major Reporter: James Nord When a flyweighttask is limited to run on a specific label (e.g. matrix project set restrict where this project can run) if there are no nodes with that label available when it enters the queue then it will immediatly move to blocked. As it is blocked the Node provisioner will not attempt to create any slaves, so the project will sit in the queue forever (or until some other project allocates a slave with the correct label). Seems to be a regression introduced by
[JIRA] [core] (JENKINS-30084) FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.
Title: Message Title James Nord commented on JENKINS-30084 Re: FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever. looks like it was caused by JENKINS-24519 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30025) expose ability to create/unpack tar.gz / zip as a workflow step
Title: Message Title James Nord commented on JENKINS-30025 Re: expose ability to create/unpack tar.gz / zip as a workflow step Although this is related to copying between workspaces - I feel this has functionality outside that area. If you could copy directories with JENKINS-26942 this would most likely make the main use case of this redundant - but I'm convinced there are some alternative use cases out there somewhere - so feel free to lower the priority. Running AntTasks may give lots more power - but I could see the syntax being not so nice. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30025) expose ability to create/unpack tar.gz / zip as a workflow step
Title: Message Title James Nord updated an issue Jenkins / JENKINS-30025 expose ability to create/unpack tar.gz / zip as a workflow step Change By: James Nord Summary: expose ability to create /unpack tar.gz / zip as a workflow step Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30060) Listeners are called back whilst holding locks which is prone to deadlocks
Title: Message Title James Nord created an issue Jenkins / JENKINS-30060 Listeners are called back whilst holding locks which is prone to deadlocks Issue Type: Bug Assignee: Unassigned Components: core Created: 20/Aug/15 2:44 PM Labels: deadlock Priority: Minor Reporter: James Nord many listeners are called whilst locks are held which leads to deadlocks (see JENKINS-30057 for one example). A listener may reasonably want to perform some action based on this which inevitably requires some call back to Jenkins which will require a different lock. However the listener is not at this point in control of what locks are held when it is called so it needs to jump through hoops in order to do things correctly. Whilst looking at listeners I have found zero instances of Listeners that do jump through the hoops - and it would seem like Jenkins should actually be handling this on behalf of the listener. For example Nodes may be provisioned with the Queue lock held - and if some jenkins configuration needs to be modified will call locking order of Queue -> Jenkins. Whilst someone saving Jenkins Clouds could lock Jenkins -> Queue. Whilst we can chase our tails unpicking these deadlocks individually I have seen 3 of these
[JIRA] [core] (JENKINS-30057) Slaves NodeProperties are owned by Jenkins not Nodes.
Title: Message Title James Nord started work on JENKINS-30057 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30057) Slaves NodeProperties are owned by Jenkins not Nodes.
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-30057 Slaves NodeProperties are owned by Jenkins not Nodes. Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30057) Slaves NodeProperties are owned by Jenkins not Nodes.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-30057 Slaves NodeProperties are owned by Jenkins not Nodes. Change By: James Nord Summary: Slaves NodeProperties are owneb owned by Jenkins not Nodes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30057) Slaves NodeProperties are owneb by Jenkins not Nodes.
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-30057
Slaves NodeProperties are owneb by Jenkins not Nodes.
Change By:
James Nord
A [Slaves nodeProperties ] | (https://github.com/jenkinsci/jenkins/blob/9c443c8d5bafd63fce574f6d0cf400cd8fe1f124/core/src/main/java/hudson/model/Slave.java#L130 ) ] are owned by Jenkins.So whenever a NodeProperty is changed this causes persistance of the entire jenkins configuration rather than just Nodes which is what actually persists the NodeProperties.Whilst this is just inefficient - if anyone wants to add a node property to new nodes created (e.g. by implementing a cloud listener) then is it possible to get a deadlock if someone also saves the Jenkins configuration at the same time. (as Jenkins.save() will lock Jenkins and then the queue, but callback for Nodes can happen with the queue locked).{noformat}"jenkins.util.Timer [#3]" id=34 (0x22) state=BLOCKED cpu=91%- waiting to lock <0x107c53da> (a hudson.model.Hudson) owned by Handling POST /configSubmit : http-8080-5 id=42at jenkins.model.Jenkins.save(Jenkins.java:2734)at hudson.util.PersistedList.onModified(PersistedList.java:173)at hudson.util.PersistedList._onModified(PersistedList.java:181)at hudson.util.PersistedList.add(PersistedList.java:72)at com.cloudbees.librato.CloudListener.onComplete(CloudListener.java:83)at hudson.slaves.NodeProvisioner$2.run(NodeProvisioner.java:223)at hudson.model.Queue._withLock(Queue.java:1235)at hudson.model.Queue.withLock(Queue.java:1171)at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:208)at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:57)at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:777)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)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)Locked synchronizers: count = 3 - java.util.concurrent.locks.ReentrantLock$NonfairSync@2e7d6057 - java.util.concurrent.ThreadPoolExecutor$Worker@6d40c3f9 - java.util.concurrent.locks.ReentrantLock$NonfairSync@640c882b"Handling POST /configSubmit : http-8080-5" id=42 (0x2a) state=WAITING cpu=96%- waiting on <0x2e7d6057> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)- locked <0x2e7d6057> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by jenkins.util.Timer [#3] id=34at sun.misc.Unsafe.park(Native Method)at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:
[JIRA] [core] (JENKINS-30057) Slaves NodeProperties are owneb by Jenkins not Nodes.
Title: Message Title James Nord created an issue Jenkins / JENKINS-30057 Slaves NodeProperties are owneb by Jenkins not Nodes. Issue Type: Bug Assignee: Unassigned Components: core Created: 20/Aug/15 1:52 PM Labels: deadlock Priority: Minor Reporter: James Nord A [Slaves nodeProperties](https://github.com/jenkinsci/jenkins/blob/9c443c8d5bafd63fce574f6d0cf400cd8fe1f124/core/src/main/java/hudson/model/Slave.java#L130) are owned by Jenkins. So whenever a NodeProperty is changed this causes persistance of the entire jenkins configuration rather than just Nodes which is what actually persists the NodeProperties. Whilst this is just inefficient - if anyone wants to add a node property to new nodes created (e.g. by implementing a cloud listener) then is it possible to get a deadlock if someone also saves the Jenkins configuration at the same time. (as Jenkins.save() will lock Jenkins and then the queue, but callback for Nodes can happen with the queue locked). "jenkins.util.Timer [#3]" id=34 (0x22) state=BLOCKED cpu=91% - waiting to lock <0x107c53da> (a hudson.model.Hudson) owned by Handling POST /config
[JIRA] [workflow-plugin] (JENKINS-30025) expose ability to create tar.gz / zip as a workflow step
Title: Message Title James Nord created an issue Jenkins / JENKINS-30025 expose ability to create tar.gz / zip as a workflow step Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 19/Aug/15 9:47 AM Priority: Minor Reporter: James Nord it is sometimes usefull to create a zip (or tar.gz) of some files ina workspace to archive as a single unit. However to do this you need to rely n platform tools to create the file. Whilst on Unix/Linux this is not too hard on windows it is a PITA requiring either extra tools or powershell scripting - neither of which is portable. It would be nice if Jenkins/javas ability to create tar.gz/zip was exposed as a native step. Add Comment
[JIRA] [workflow-plugin] (JENKINS-30025) expose ability to create tar.gz / zip as a workflow step
Title: Message Title James Nord commented on JENKINS-30025 Re: expose ability to create tar.gz / zip as a workflow step relates in part to JENKINS-30024 and ability to migrate from dist-fork to workflow. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30024) ability to copy artifacts from workspace without having to archive them.
Title: Message Title James Nord moved an issue Jenkins / JENKINS-30024 ability to copy artifacts from workspace without having to archive them. Change By: James Nord Project: Security Issues Jenkins Key: SECURITY JENKINS - 196 30024 Issue Type: Bug New Feature Workflow: Security v1.2 JNJira Status: Untriaged Open Component/s: workflow-plugin Component/s: workflow Add Comment
[JIRA] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title James Nord resolved as Fixed Fixed with PR 1796 Jenkins / JENKINS-29936 deadlock between OldDataMonitor and AuthorizationStrategy. Change By: James Nord Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title James Nord commented on JENKINS-29936 Re: deadlock between OldDataMonitor and AuthorizationStrategy. Jesse Glick unfortunately I only have a trimmed stack trace that doesn't fully show this. The rest has been identified with knowing what's been occuring at this time and inspecting the code. "Handling GET /job/myJob/groups/ from 192.168.13.182 : http-bio-8080-exec-81 GroupContainerMixIn/index.jelly" Id=149 BLOCKED on hudson.diagnosis.OldDataMonitor@145b2dc1 owned by "Computer.threadPoolForRemoting [#1622] for Channel to Maven [/usr/java/jdk1.7.0_05/bin/java, -Xmx1024m, -XX:MaxPermSize=256m, -cp, /data/jenkins_slave/epjenkins81/maven3-agent.jar:/opt/apache-maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /opt/apache-maven/apache-maven-3.0.4, /data/jenkins_slave/epjenkins81/slave.jar, /data/jenkins_slave/epjenkins81/maven3-interceptor.jar, /data/jenkins_slave/epjenkins81/maven3-interceptor-commons.jar, 37246]" Id=279517 at hudson.diagnosis.OldDataMonitor.remove(OldDataMonitor.java:106) - blocked on hudson.diagnosis.OldDataMonitor@145b2dc1 at hudson.diagnosis.OldDataMonitor.access$000(OldDataMonitor.java:67) at hudson.diagnosis.OldDataMonitor$1.onChange(OldDataMonitor.java:120) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:80) at hudson.model.User.save(User.java:708) at hudson.model.User.addProperty(User.java:273) at hudson.plugins.active_directory.ActiveDirectoryUserDetail.updateUserInfo(ActiveDirectoryUserDetail.java:163) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:321) ... "Computer.threadPoolForRemoting [#1622] for Channel to Maven [/usr/java/jdk1.7.0_05/bin/java, -Xmx1024m, -XX:MaxPermSize=256m, -cp, /data/jenkins_slave/epjenkins81/maven3-agent.jar:/opt/apache-maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /opt/apache-maven/apache-maven-3.0.4, /data/jenkins_slave/epjenkins81/slave.jar, /data/jenkins_slave/epjenkins81/maven3-interceptor.jar, /data/jenkins_slave/epjenkins81/maven3-interceptor-commons.jar, 37246]" Id=279517 BLOCKED on nectar.plugins.rbac.groups.Group@2f247cf9 owned by "Handling GET /job/myJob/groups/ from 192.168.13.182 : http-bio-8080-exec-81 GroupContainerMixIn/index.jelly" Id=149 at nectar.plugins.rbac.groups.Group.isMatch(Group.java:376) - blocked on nectar.plugins.rbac.groups.Group@2f247cf9 at nectar.plugins.rbac.groups.Group.isMatch(Group.java:349) at nectar.plugins.rbac.groups.Group.isMatch(Group.java:309) at nectar.plugins.rbac.groups.GroupContainerACL.hasPermission(GroupContainerACL.java:127) at nectar.plugins.rbac.groups.GroupContainerACL._hasPermission(GroupContainerACL.java:94) at nectar.plugins.rbac.groups.GroupContainerACL.hasPermission(GroupContainerACL.java:65) at hudson.security.ACL.hasPermission(ACL.java:73) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:505) ...
[JIRA] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-29936 deadlock between OldDataMonitor and AuthorizationStrategy. Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title James Nord created an issue Jenkins / JENKINS-29936 deadlock between OldDataMonitor and AuthorizationStrategy. Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Aug/15 3:24 PM Environment: 1.609.1 Labels: deadlock authorization Priority: -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord edited a comment on JENKINS-29548 Re: don't group both advanced and deprecated together - its not possible to know which is which. if there is no distinction then this section title is completely wrong.Deprecated means shouldn't use an and may be removed in a future version. Advanced means - normal users may not need this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord reopened an issue if there is no distinction then this section title is completely wrong. Deprecated means shouldn't use an may be removed in a future version. Advanced means - normal users may not need this. Jenkins / JENKINS-29548 don't group both advanced and deprecated together - its not possible to know which is which. Change By: James Nord Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-29891) ClassCastException in Workflow and Copy Artifact plugin
Title: Message Title James Nord closed an issue as Cannot Reproduce reporter needs more coffee... (workflow needs better exception reporting - was unrelated to the copyArtifact step) Jenkins / JENKINS-29891 ClassCastException in Workflow and Copy Artifact plugin Change By: James Nord Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-29891) ClassCastException in Workflow and Copy Artifact plugin
Title: Message Title James Nord created an issue Jenkins / JENKINS-29891 ClassCastException in Workflow and Copy Artifact plugin Issue Type: Bug Assignee: Jesse Glick Components: copyartifact-plugin, workflow-plugin Created: 11/Aug/15 12:53 PM Environment: Jenkins 1.609.1 Java8 workflow 1.9 copy artifact 1.35.2 Labels: workflow Priority: Major Reporter: James Nord use the snippet generator to create a copy artifact step using the General Build Step. step([$class: 'CopyArtifact', filter: '*.war', fingerprintArtifacts: true, projectName: 'war', selector: [$class: 'StatusBuildSelector', stable: false]]) add this to a simple workflow and run it. result -> workflow fails with exception
[JIRA] [durable-task-plugin] (JENKINS-29877) failure when incorrect shell is configured is not clear enough to diagnose root cause.
Title: Message Title
James Nord created an issue
Jenkins / JENKINS-29877
failure when incorrect shell is configured is not clear enough to diagnose root cause.
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
durable-task-plugin, workflow-plugin
Created:
10/Aug/15 2:03 PM
Environment:
jenkis 1.609.1 workflow 1.9-beta-1
Priority:
Minor
Reporter:
James Nord
If you have a shell configured in "manage jenkins" and that shell is not available on the slave used by a workflow sh step, then the error does not help you diagnose the issue.
e.g.
node ('different_slave') {
sh 'echo hello'
}
produces the following error
[workflow_test] Running shell script
sh: 1: /home/jenkins/slave/workspace/workflow_test/.e59a0d2c/script.sh: not found
this implies an error with Jenkins code and no
[JIRA] [git-plugin] (JENKINS-29840) when workflow uses multiple git repos the "git build data" and "tags" become next to useless.
Title: Message Title James Nord created an issue Jenkins / JENKINS-29840 when workflow uses multiple git repos the "git build data" and "tags" become next to useless. Issue Type: Bug Assignee: Nicolas De Loof Attachments: 2015-08-06_17h15_16.png Components: git-plugin, workflow-plugin Created: 06/Aug/15 4:25 PM Environment: Jenkins 1.609.1 Workflow 1.9-beta-1 git 2.4.0 git-client 1.18.0 Priority: Minor Reporter: James Nord if you have a workflow which uses multiple git repositories the actions and data contributed to the build by the git plugin produce almost unusable visual spam. The tag action does not let you know which repository you are tagging, nor does the build data tell you which repository it is that has the specified hash. Coupled with this you end up with 2 * the number of repos used (plus another 2 if you use workflow from SCM) actions - which simply does not scale. The actions should be refactored so there is one action that can display the data from m
[JIRA] [workflow-plugin] (JENKINS-29754) stage with concurrency :1 can hang forever.
Title: Message Title James Nord commented on JENKINS-29754 Re: stage with concurrency :1 can hang forever. subsequent jobs will build and will not wait for #2 to finish. it is also to be noted that you can not abort/kill #2 with the red "x" on the UI. Running: build Entering stage build Waiting for builds [1] Aborted by James Nord Aborted by James Nord Aborted by James Nord Aborted by James Nord Aborted by James Nord Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29754) stage with concurrency :1 can hang forever.
Title: Message Title
James Nord created an issue
Jenkins / JENKINS-29754
stage with concurrency :1 can hang forever.
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
03/Aug/15 3:29 PM
Environment:
workflow 1.9-beta1
Priority:
Critical
Reporter:
James Nord
create a workflow with the following DSL
stage concurrency: 1, name: 'doit'
node {
sh 'sleep 600'
}
Start a build, then immediately start another build delete the first build by going to job/1/doDelete
expected results the second build that was waiting for the first to finish the stage would progress
actual results the second build is still waiting for the build #1 to finish - and this will never happen.
[JIRA] [mansion-cloud-plugin] (JENKINS-29751) unkillable workflow builds with mansion cloud plugin
Title: Message Title James Nord created an issue Jenkins / JENKINS-29751 unkillable workflow builds with mansion cloud plugin Issue Type: Bug Assignee: Jesse Glick Components: mansion-cloud-plugin, workflow-plugin Created: 03/Aug/15 3:00 PM Environment: workflow 1.9-beta1, jenkins 1.609.1 (Dev@Cloud) Priority: Critical Reporter: James Nord If Jenkins is restarted whilst a workflow is running using slaves from mansion cloud then the result is an unkillable build on the jenkins ui. this is easiest to reproduce cloudbees Dev@Cloud as the mansion cloud is already setup there. 1) create a simple workflow that allocates a node and sleeps for a resonable amount of time. 2) start the build and verify it completes 3) start the build and then restart jenkins. expected results: either when the master comes back up it reconnects to the salve that was running the task and resumes. when the master comes back up it reconnects
[JIRA] [embeddable-build-status-plugin] (JENKINS-29750) ClassCastException ona workflow job
Title: Message Title James Nord created an issue Jenkins / JENKINS-29750 ClassCastException ona workflow job Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: stack.txt Components: embeddable-build-status-plugin, workflow-plugin Created: 03/Aug/15 2:41 PM Environment: workflow 1.9-beta1 Jenkis 1.609.1 Priority: Minor Reporter: James Nord Exception is thrown from the plugin when rendering the build overview page for a workflow job. Jul 31, 2015 3:30:24 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.transientActions in /job/CloudBees%20Jenkins%20Platform/job/all-plugins%20(master)/53/. Reason: java.lang.reflect.InvocationTargetException Caused by: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.jenkinsci.plugins.badge.RunBadgeAction.(RunBadgeAction.java:18) at org.jenkinsci.plugi
[JIRA] [workflow-plugin] (JENKINS-29653) “Generate Groovy” button is not separated from the actual snippet.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29653 “Generate Groovy” button is not separated from the actual snippet. Change By: James Nord The "Generate Groovy" button looks like a tab header rather than a button.!Untitled.png |thumbnail ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29653) “Generate Groovy” button is not separated from the actual snippet.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29653 “Generate Groovy” button is not separated from the actual snippet. Change By: James Nord The "Generate Groovy" button looks like a tab header rather than a button.!Untitled.png |thumbnail ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29653) “Generate Groovy” button is not separated from the actual snippet.
Title: Message Title James Nord created an issue Jenkins / JENKINS-29653 “Generate Groovy” button is not separated from the actual snippet. Issue Type: Bug Assignee: Jesse Glick Attachments: Untitled.png Components: workflow-plugin Created: 27/Jul/15 2:12 PM Priority: Minor Reporter: James Nord The "Generate Groovy" button looks like a tab header rather than a button. Add Comment
[JIRA] [config-file-provider-plugin] (JENKINS-26339) Workflow integration for Config File Provider
Title: Message Title James Nord commented on JENKINS-26339 Re: Workflow integration for Config File Provider Jesse Glick Next LTS has been cut Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29548 don't group both advanced and deprecated together - its not possible to know which is which. Change By: James Nord The snippet generator mixes both deprecated and advanced in a single group.How is a user supposed to know if they should use something as they want something advanced vs don ; ' t use something as it is deprecated.!2015-07-21_21h07_10.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29548 don't group both advanced and deprecated together - its not possible to know which is which. Change By: James Nord The snippet generator mixes both deprecated and advanced in a single group.How is a user supposed to know if they should use something as they want something advanced vs don;t use something as it is deprecated.!2015-07-21_21h07_10.png| daily wtf candidate thumbnail ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29548) don;t group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord created an issue Jenkins / JENKINS-29548 don;t group both advanced and deprecated together - its not possible to know which is which. Issue Type: Bug Assignee: Jesse Glick Attachments: 2015-07-21_21h07_10.png Components: workflow-plugin Created: 21/Jul/15 8:12 PM Priority: Minor Reporter: James Nord The snippet generator mixes both deprecated and advanced in a single group. How is a user supposed to know if they should use something as they want something advanced vs don;t use something as it is deprecated. Add Comment
[JIRA] [workflow-plugin] (JENKINS-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29548 don't group both advanced and deprecated together - its not possible to know which is which. Change By: James Nord Summary: don ; ' t group both advanced and deprecated together - its not possible to know which is which. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29312) not possible to specify which git tool is used in the "git" operation
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29312 not possible to specify which git tool is used in the "git" operation Change By: James Nord Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29312) not possible to specify which git tool is used in the "git" operation
Title: Message Title James Nord edited a comment on JENKINS-29312 Re: not possible to specify which git tool is used in the "git" operation it also appears as there is no possibility to change this with using the generic SCM step is a possible workaround . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-29541) workflow scripts can't use String.substring(int,int)
Title: Message Title
James Nord commented on JENKINS-29541
Re: workflow scripts can't use String.substring(int,int)
the second issue looks like it may be resolved (when using GString) - but I don;t see how this would change the lack of whitelist for {java.lang.String.substring(...)}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-29541) workflow scripts can't use String.substring(int,int)
Title: Message Title
James Nord edited a comment on JENKINS-29541
Re: workflow scripts can't use String.substring(int,int)
the second issue looks like it may be resolved (when using GString) - but I don;t see how this would change the lack of whitelist white list for { { java.lang.String.substring(...)} }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29312) not possible to specify which git tool is used in the "git" operation
Title: Message Title James Nord commented on JENKINS-29312 Re: not possible to specify which git tool is used in the "git" operation it also appears as there is no possibility to change this with the generic SCM step. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29542) example for help for "env" global variable is wrong.
Title: Message Title
James Nord created an issue
Jenkins / JENKINS-29542
example for help for "env" global variable is wrong.
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
21/Jul/15 6:07 PM
Environment:
wf 1.8
Priority:
Minor
Reporter:
James Nord
1) in the workflow job configure page 2) go to "Global variables" 3) select "Env" in the dropdown
the mail example is shown as how to use a groovy variable in the script - but the example does not actually use any groovy variable!
noformat As an example of loading variable values from Groovy:
mail to: 'dev...@acme.com', subject: "Job '' () is waiting for input", body: "Please go to and verify the build" noformat
I'm guessing that something in there should be {$env.somvar}.
[JIRA] [script-security-plugin] (JENKINS-29541) workflow scripts can't use String.substring(int,int)
Title: Message Title James Nord created an issue Jenkins / JENKINS-29541 workflow scripts can't use String.substring(int,int) Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin, workflow-plugin Created: 21/Jul/15 5:42 PM Priority: Major Reporter: James Nord 1.609.1, wf 1.8, secript-scurity 1.14 org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int int same for gstring. org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.codehaus.groovy.runtime.GStringImpl substring java.lang.Integer java.lang.Integer) Add Comment
[JIRA] [core] (JENKINS-29496) Windows service: service can start before required windows services are available.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29496 Windows service: service can start before required windows services are available. Change By: James Nord Summary: Windows service: use "Delayed service can start " as a default start mode for Jenkins master and slaves before required windows services are available. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29496) Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves
Title: Message Title James Nord updated an issue Jenkins / JENKINS-29496 Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves Change By: James Nord Currently the service starts in the default "Automatic" mode, so there can be conflicts with other services like login service, shared directory mappers, etc. " Automatic ( Delayed start ) " could resolve this issue by allowing other services to start before Jenkins master/slave starts the initialization.The change requires https://github.com/kohsuke/winsw/releases/tag/winsw-1.17 at least (not merged into Jenkins core) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29496) Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves
Title: Message Title James Nord commented on JENKINS-29496 Re: Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves Most people probably don't use UNC paths for storage[1] - and then you are impacting the majority of users with a slow startup to fix the minority of users. If you want to fix 80% of the minority without impacting the majority you could just depend on the "workstation" service. Anyone that wants anything more complex can suck it themselves. [1] based on nothing other than gut feeling and finger in the air - and that we still have huge amount of users that run builds on master! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29496) Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves
Title: Message Title James Nord commented on JENKINS-29496 Re: Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves No, Windows will start "delayed" services shortly after starting other ones with automatic start. AFAIK there's no hardcoded timeout. Nope - there is a system wide setting (at least in some versions of Windows) and it defaults to 120 seconds. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\AutoStartDelay There is one well-known use-case with shared directories Another known use case is a Windows event system, which starts as a service. If Jenkins starts before it, we may lose events in monitoring systems There is a potential risk for user jobs, because currently Jenkins may start executing them on slave machines without fully initialized services => undefined behavior even for standard Windows CLI tools Which is why I said you need to install the service with dependencies set, not delayed start. If Jenkins needs service X to be alive it should have a dependency on it to ensure it is started after that service. The result is the service will still start after the services it needs are started, but it will not be artificially delayed but the AutoStartDelay. You need shared directories - add a service dependency on Workstation, you need the event system (you shouldn't), depend on EventLog, you need to make sure antivirus is running add a dependency on WinDefend etc etc... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-29496) Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves
Title: Message Title James Nord commented on JENKINS-29496 Re: Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves this implies that we should not be using winsw to install itself, but Jenkins should install itself ant it needs to tweak the options depending on if the slave/master has been configured with any UNC paths - or that if you use UNC etc etc that you need to update the dependencies with sc config nameOfJenkinsService depend= nameOfServiceAYouDependOn/nameOfServiceAYouDependOn Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29496) Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves
Title: Message Title James Nord commented on JENKINS-29496 Re: Windows service: use "Delayed start" as a default start mode for Jenkins master and slaves The service should not use delayed start as this will slow down the startup of Jenkins. If anything the service dependencies should be set correctly - but how do you know that you need the "Workstation" service only if you are running on a shared home/workspace. Some installations may have disabled this for security. A delayed start by default (IIRC) will keep a salve offline for 2 minutes. AFAICT there is only a global setting for delayed start and changing this will affect services other than Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29312) not possible to specify which git tool is used in the "git" operation
Title: Message Title James Nord created an issue Jenkins / JENKINS-29312 not possible to specify which git tool is used in the "git" operation Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 09/Jul/15 1:26 PM Priority: Major Reporter: James Nord The "git" support in workflow is hard coded to use the "default" git tool. There are cases when you require to use a non default tool - and the workflow does not help here. It should be possible to supply a different git tool to use. Add Comment
[JIRA] [core] (JENKINS-28158) if JENKINS_URL is set to an https adress, then login over an alternate http address not working
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28158 if JENKINS_URL is set to an https adress, then login over an alternate http address not working Change By: James Nord Component/s: core Component/s: active-directory-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-28950) Cucumber Test Result Plugin Fails to parse JSON: Expected BEGIN_ARRAY but was STRING
Title: Message Title James Nord commented on JENKINS-28950 Re: Cucumber Test Result Plugin Fails to parse JSON: Expected BEGIN_ARRAY but was STRING Can you attach the json as a file please. What tool did you use to generate the json? Also 0.1 is very old Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28687) spring version (2.5.x) is ancient and not compatable with many new libraries
Title: Message Title James Nord commented on JENKINS-28687 Re: spring version (2.5.x) is ancient and not compatable with many new libraries Spring trieds to retain backwards compatability. There are a few noteable exceptions, so any upgrade is not without risks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unique-id] (JENKINS-28913) unique-id stores empty ids.
Title: Message Title James Nord started work on JENKINS-28913 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unique-id] (JENKINS-28913) unique-id stores empty ids.
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-28913 unique-id stores empty ids. Change By: James Nord Assignee: recampbell James Nord Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unique-id] (JENKINS-28913) unique-id stores empty ids.
Title: Message Title James Nord created an issue Jenkins / JENKINS-28913 unique-id stores empty ids. Issue Type: Bug Assignee: recampbell Components: unique-id Created: 15/Jun/15 3:57 PM Priority: Blocker Reporter: James Nord WHen the unique id plugin creates an ID for a new job the id persisted to disk is the empty string. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [docker-plugin] (JENKINS-28842) docker-plugin adds JobPropteries to all jobs even if you don't use docker-plugin for that job
Title: Message Title James Nord commented on JENKINS-28842 Re: docker-plugin adds JobPropteries to all jobs even if you don't use docker-plugin for that job this is not an issue with 0.9.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unique-id] (JENKINS-28843) unique id plugin stored the unique value in the job configuration.
Title: Message Title James Nord created an issue Jenkins / JENKINS-28843 unique id plugin stored the unique value in the job configuration. Issue Type: Bug Assignee: James Nord Components: unique-id Created: 10/Jun/15 4:01 PM Priority: Critical Reporter: James Nord The unique-id plugin stores the unique value in a job propterty. This causes issues as Jenkins allows you to copy jobs via the UI, and users are used to copying config.xml to duplicate jobs; both result in jobs with duplicate IDs. Add Comment
[JIRA] [docker-plugin] (JENKINS-28842) docker-plugin adds JobPropteries to all jobs even if you don't use docker-plugin for that job
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28842 docker-plugin adds JobPropteries to all jobs even if you don't use docker-plugin for that job Change By: James Nord Summary: docker-plugin adds JobPropteries to all jobs even if you don't use docker-plugin for that job Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-28842) docker-plugin
Title: Message Title James Nord created an issue Jenkins / JENKINS-28842 docker-plugin Issue Type: Bug Assignee: Kanstantsin Shautsou Components: docker-plugin Created: 10/Jun/15 2:35 PM Environment: docker-plugin 0.8 Jenkins 1.609.1 Priority: Minor Reporter: James Nord The docker-plugin add job properties to Freestyle jobs even if you don't care about using docker-plugin for this job. Adding jobProperties should only be done if the user wants to do something with the job property. This causes issues with plugins that want to migrate jobs to different instances and check what plugins are in use (docker-plugin will be listed as found as its jobProperties will be on all projects where the docker-plugin is installed). Steps to reproduce install docker-plugin restart jenkins create a new FreeStyleJob
[JIRA] [core] (JENKINS-28781) bytecode-compatibility-transformer produces malformed bytecode
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28781 bytecode-compatibility-transformer produces malformed bytecode Change By: James Nord In the case where we see this issue, an [@AdaptField annotation on Queue.Item|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L1753-L1762] was causing transformations in other classes not intended for transformation (in our case, in an elasticsearch class). The result of this transformation was a StackMapFrame verifier error. So there may actually be 2 or 3 bugs that need to be spun out from this :# The bytecode transformer is transforming methods/fields that it should not be transforming.# And one or both of issue tracks the following tracks : #* bytecode-compatibility-transformer doesn't properly support updating of StackMapFrames after manipulation. #* bytecode-compatibility-transformer does support updating of StackMapFrames after manipulation, but Jenkins core is not using that properly. It does look as though bytecode-compatibility-transformer has some support for StackMapFrames. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28781) bytecode-compatibility-transformer produces malformed bytecode
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28781 bytecode-compatibility-transformer produces malformed bytecode Change By: James Nord Summary: bytecode-compatibility-transformer transforming methods/fields it should not be transforming produces malformed bytecode Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28799) bytecode-compatibility-transformer transforming methods/fields it should not be transforming
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28799 bytecode-compatibility-transformer transforming methods/fields it should not be transforming Change By: James Nord In the case where we see this issue, an [@AdaptField annotation on Queue.Item|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L1753-L1762] was causing transformations in other classes not intended for transformation (in our case, in an elasticsearch class). The result of this transformation was a StackMapFrame verifier error. So there may actually be 2 or 3 bugs that need This issue relates to be spun out from this:# The the bytecode transformer is transormer transforming methods/fields classes that it should need not be transforming transformed . # And one or both of the following:#* bytecode-compatibility-transformer doesn't properly support updating of StackMapFrames after manipulation.#* bytecode-compatibility-transformer does support updating of StackMapFrames after manipulation, but Jenkins core is not using that properly.It does look as though bytecode-compatibility-transformer has some support for StackMapFrames. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28799) bytecode-compatibility-transformer transforming methods/fields it should not be transforming
Title: Message Title James Nord created an issue Jenkins / JENKINS-28799 bytecode-compatibility-transformer transforming methods/fields it should not be transforming Issue Type: Bug Assignee: James Nord Components: core Created: 08/Jun/15 11:56 PM Labels: bytecode-compatibility-transformer Priority: Major Reporter: James Nord In the case where we see this issue, an @AdaptField annotation on Queue.Item was causing transformations in other classes not intended for transformation (in our case, in an elasticsearch class). The result of this transformation was a StackMapFrame verifier error. So there may actually be 2 or 3 bugs that need to be spun out from this: The bytecode transformer is transforming methods/fields that it should not be transforming. And one or both of the following: bytecode-compatibility-transformer doesn't properly support updating of StackMapFrames after mani
[JIRA] [core] (JENKINS-28781) bytecode-compatibility-transformer transforming methods/fields it should not be transforming
Title: Message Title James Nord commented on JENKINS-28781 Re: bytecode-compatibility-transformer transforming methods/fields it should not be transforming https://github.com/jenkinsci/bytecode-compatibility-transformer/pull/2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28781) bytecode-compatibility-transformer transforming methods/fields it should not be transforming
Title: Message Title James Nord commented on JENKINS-28781 Re: bytecode-compatibility-transformer transforming methods/fields it should not be transforming unfortunately the binaries for this are not available (unreleased version). Caused by: java.lang.VerifyError: Expecting a stackmap frame at branch target 20 Exception Details: Location: org/elasticsearch/common/settings/ImmutableSettings$Builder.get(Ljava/lang/String;)Ljava/lang/String; @15: ifnull Reason: Expected stackmap frame at this location. Bytecode: 0x000: 2ab4 002a 2bb9 003a 0200 c000 354d 2cc6 0x010: 0005 2cb0 2ab4 002a 2bb8 003f b900 3a02 0x020: 00c0 0035 b0 at org.elasticsearch.common.settings.ImmutableSettings.(ImmutableSettings.java:57) at com.cloudbees.opscenter.elasticsearch.embedded.EmbeddedNode.start(EmbeddedNode.java:94) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28781) bytecode-compatibility-transformer transforming methods/fields it should not be transforming
Title: Message Title James Nord commented on JENKINS-28781 Re: bytecode-compatibility-transformer transforming methods/fields it should not be transforming There are 2 issues that are seemingly at play here. 1) the affected class does not use any of the Jenkins API and should not have been transformed. 2) the transformer is producing a class that is broken. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28781) bytecode-compatibility-transformer transforming methods/fields it should not be transforming
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-28781 bytecode-compatibility-transformer transforming methods/fields it should not be transforming Change By: James Nord Assignee: Kohsuke Kawaguchi James Nord Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28752) DockerTraceabiltyReport marks imageId as nonNull but for certain events its not always possible to obtain it.
Title: Message Title James Nord created an issue Jenkins / JENKINS-28752 DockerTraceabiltyReport marks imageId as nonNull but for certain events its not always possible to obtain it. Issue Type: Bug Assignee: Unassigned Components: docker-traceability-plugin Created: 04/Jun/15 5:11 PM Priority: Minor Reporter: James Nord DockerTraceabilityReport marks getImageId as Nonnull. However in the case a docker container is destroyed it may not be able to obtain this information. The Docker event will contain the containerId and the name of the image it is deployed from. But that image may itself have been removed by the time we request information about it, and so may not be able to retrieve it's details. Add Comment
[JIRA] [support-core-plugin] (JENKINS-28703) add the pinned status of a plugin to the support bundle
Title: Message Title James Nord created an issue Jenkins / JENKINS-28703 add the pinned status of a plugin to the support bundle Issue Type: New Feature Assignee: Steven Christou Components: support-core-plugin Created: 02/Jun/15 10:07 PM Priority: Minor Reporter: James Nord It would be useful to be able to see which plugins are pinned in a support bundle. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28688) UnprotectedRootActions urlname can not start with a '/' but javadoc implies that they must.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28688 UnprotectedRootActions urlname can not start with a '/' but javadoc implies that they must. Change By: James Nord the code in [Jenkins.java ]( | https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java#L3826-L3829 ) ] will append the leading '/' for UnprotectedRootActions, yet the javadoc only exists on Action.java which implies you should add a '/' for actions that are only shown at the root context. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28688) UnprotectedRootActions urlname can not start with a '/' but javadoc implies that they must.
Title: Message Title James Nord created an issue Jenkins / JENKINS-28688 UnprotectedRootActions urlname can not start with a '/' but javadoc implies that they must. Issue Type: Bug Assignee: James Nord Components: core Created: 02/Jun/15 10:52 AM Priority: Major Reporter: James Nord the code in [Jenkins.java](https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Jenkins.java#L3826-L3829) will append the leading '/' for UnprotectedRootActions, yet the javadoc only exists on Action.java which implies you should add a '/' for actions that are only shown at the root context. Add Comment
[JIRA] [core] (JENKINS-28687) spring version (2.5.x) is ancient and not compatable with many new libraries
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28687 spring version (2.5.x) is ancient and not compatable with many new libraries Change By: James Nord Summary: spring version (2.5.x) is ancient and not compatable with many new libraries Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28687) spring version is ancient and not compatable with many new libraries
Title: Message Title James Nord created an issue Jenkins / JENKINS-28687 spring version is ancient and not compatable with many new libraries Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Jun/15 10:05 AM Priority: Minor Reporter: James Nord The spring version 2.5 used in core is very old and this makes it problematic when trying to integrate jenkins with another component, or integrating components within jenkins as most things have moved way passed 2.5 to 4.x. Note - this may also require an upgrade of groovy. Add Comment
[JIRA] [docker-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title James Nord created an issue Jenkins / JENKINS-28643 timestamps in the UI are not correct Issue Type: Bug Assignee: Oleg Nenashev Attachments: dt_screenshot.png Components: docker-traceability-plugin Created: 29/May/15 4:41 PM Priority: Minor Reporter: James Nord see screenshot from submission of events via Docker events hook. Add Comment
[JIRA] [durable-task-plugin] (JENKINS-27419) dos "exit" command not functioning correctly
Title: Message Title James Nord assigned an issue to Jesse Glick Jenkins / JENKINS-27419 dos "exit" command not functioning correctly Change By: James Nord Assignee: James Nord Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-27419) dos "exit" command not functioning correctly
Title: Message Title James Nord commented on JENKINS-27419 Re: dos "exit" command not functioning correctly cmd.exe /? Starts a new instance of the Windows command interpreter /K Carries out the command specified by string but remains > help exit Quits the CMD.EXE program (command interpreter) or the current batch script. EXIT [/B] [exitCode] /B specifies to exit the current batch script instead of CMD.EXE. If executed from outside a batch script, it will quit CMD.EXE basically if you forget to add /b to your dos script (e.g. if you want to terminate early using exit) you will kill the cmd.exe process and Jenkins will sit until the end of days and not realize... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-27869) entered SCM password should be masked in output
Title: Message Title James Nord commented on JENKINS-27869 Re: entered SCM password should be masked in output maven-release-plugin should not by default show the password - so this is an issue with the upstream plugin. Will attempt to see if a workaround is possible Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-27731) Exception while parsing result file
Title: Message Title James Nord commented on JENKINS-27731 Re: Exception while parsing result file "output" should be a string - but you have a number - bug in the tooling you are using - please file upstream. "output": [ 136 ], Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns-plugin] (JENKINS-26461) Refresh test-result and aggregated-failed-tests Jelly references
Title: Message Title James Nord updated an issue Jenkins / JENKINS-26461 Refresh test-result and aggregated-failed-tests Jelly references Change By: James Nord Component/s: cucumber-testresult-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns-plugin] (JENKINS-26461) Refresh test-result and aggregated-failed-tests Jelly references
Title: Message Title James Nord commented on JENKINS-26461 Re: Refresh test-result and aggregated-failed-tests Jelly references cucumber-testresult-plugin does not use the file identified (its some old WIP that is pretty dead) so removing this component. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-28581) support Maven version policies
Title: Message Title James Nord updated an issue Jenkins / JENKINS-28581 support Maven version policies Change By: James Nord Summary: m2release plugin doesn't support Maven version policies Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title James Nord commented on JENKINS-25203 Re: support embedded content in json 1.580 is needed for JENKINS-25280 if you don't care about that it should be possible to back port if you as a dependency on security-144-compat But you should upgrade Jenkins instead �� Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title James Nord commented on JENKINS-25203 Re: support embedded content in json Updated build at https://jenkins.ci.cloudbees.com/job/plugins/job/cucumber-testresult-plugin/54/org.jenkins-ci.plugins$cucumber-testresult-plugin/artifact/org.jenkins-ci.plugins/cucumber-testresult-plugin/0.8-SNAPSHOT/cucumber-testresult-plugin-0.8-SNAPSHOT.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27875) Add ability to skip the default build step triggered by downstream build step such as Jenkins release-plugin
James Nord commented on JENKINS-27875 Add ability to skip the default build step triggered by downstream build step such as Jenkins release-plugin Hi Dan, Unfortunately the code is specific to the maven project type. http://javadoc.jenkins-ci.org/hudson/maven/MavenArgumentInterceptorAction.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27875) Add ability to skip the default build step triggered by downstream build step such as Jenkins release-plugin
James Nord commented on JENKINS-27875 Add ability to skip the default build step triggered by downstream build step such as Jenkins release-plugin Isn't this already solvable by using the Conditional BuildStep plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27875) Add ability to skip the default build step triggered by downstream build step such as Jenkins release-plugin
James Nord commented on JENKINS-27875 Add ability to skip the default build step triggered by downstream build step such as Jenkins release-plugin Note: m2release plugin doesn't have this issue as it doesn't execute maven again, (that is it replaces the maven goals with the release goals, rather than running them up-front.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27888) NPE thrown when scheduling a new Maven release
James Nord resolved JENKINS-27888 as Duplicate NPE thrown when scheduling a new Maven release JENKINS-16043 Change By: James Nord (16/Apr/15 4:20 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27621) Jenkins is not an Item
James Nord
commented on JENKINS-27621
Jenkins is not an Item
it is conveninent to handle in code such that you don't need to do have multiple paths through the code
if (ItemGroup instanceOf Item) { /* do something */}
else if (ItemGroup instanceOf Jenkins) { /* do something else */ }
Item.getFullName should return the empty string or null (depending on if this is nullable), delete could throw an error, or (for bonus points) should remove itself from the OS :-P etc. etc.)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27943) ItemGroupMixin triggers SaveableListener.onChange() on incomplete Object
James Nord created JENKINS-27943 ItemGroupMixin triggers SaveableListener.onChange() on incomplete Object Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/15 7:35 PM Description: The ItemGroupMixin calls save() on a newly created item before it adds the item to the parent ItemGroup - see code. Unfortunately the call to save will trigger SaveableListener.onChange() to be called. The issue here is the Object that gets passed to the SaveableListener will have a parent that knows nothing about this Item. Arguably onChange() should not even be called for the item - as by definition it has not changed - just been born. Note this was observed whilst inspecting code around a proprietary plugin. Project: Jenkins Labels: jenkins Priority: Minor Reporter: James Nord This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-27731) Exception while parsing result file
James Nord commented on JENKINS-27731 Exception while parsing result file The official Gherkin parser is saying your json is not valid. What tool and version did you use to generate this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
James Nord commented on JENKINS-25203 support embedded content in json It needs some testing, you can download the build from https://jenkins.ci.cloudbees.com/job/plugins/job/cucumber-testresult-plugin/53/org.jenkins-ci.plugins$cucumber-testresult-plugin/artifact/org.jenkins-ci.plugins/cucumber-testresult-plugin/0.7-SNAPSHOT/cucumber-testresult-plugin-0.7-SNAPSHOT.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27621) Jenkins is not an Item
James Nord created JENKINS-27621 Jenkins is not an Item Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Mar/15 11:05 AM Description: Due to ItemGroup is not an Item. Which is a PITA when navigating folder structures and wanting to arbitrarily handle cases based on user supplied input. For folders this is OK as a Folder is both an Item and an ItemGroup - but the Jenkins root is an ItemGroup but not an Item, so any generic handling breaks down if you are working at the top level. Project: Jenkins Priority: Minor Reporter: James Nord This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
