[JIRA] [core] (JENKINS-26870) java.io.IOException on LogRotator
Daniel Beck commented on JENKINS-26870 java.io.IOException on LogRotator This looks like your build data migration in 1.597 failed (JENKINS-26519). 1.599 will contain a fix related to that, so you should probably upgrade as soon as that gets released. 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-26528) build.delete() should throw if build is marked as "keep forever"
Orgad Shaneh commented on JENKINS-26528 build.delete() should throw if build is marked as "keep forever" I'd expect the web UI to warn the user, then clear the flag and delete the build, rather than the delete() function itself ignoring it. 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-26870) java.io.IOException on LogRotator
Daniel Beck assigned JENKINS-26870 to Jesse Glick java.io.IOException on LogRotator Assigning to jglick in case there's more to this that a straightforward failure to migrate the data. Change By: Daniel Beck (10/Feb/15 8:05 AM) Assignee: Jesse Glick 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-26528) build.delete() should throw if build is marked as "keep forever"
Daniel Beck reopened JENKINS-26528 build.delete() should throw if build is marked as "keep forever" Right, that would be possible as well. Change By: Daniel Beck (10/Feb/15 8:11 AM) Resolution: Won't Fix Status: Resolved Reopened 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-26528) build.delete() should throw if build is marked as "keep forever"
Daniel Beck updated JENKINS-26528 build.delete() should throw if build is marked as "keep forever" Change By: Daniel Beck (10/Feb/15 8:11 AM) Status: Reopened Open 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] [ws-cleanup-plugin] (JENKINS-18137) null value for project workspace location
Oliver Gondža resolved JENKINS-18137 as Incomplete null value for project workspace location Closing as incomplete, please open new issue with exception attached. Change By: Oliver Gondža (10/Feb/15 8:27 AM) Status: Open Resolved Assignee: Lucie Votypkova Oliver Gondža Resolution: Incomplete 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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Bert Jan Schrijver commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel https://issues.jenkins-ci.org/browse/JENKINS-14332 helped for me. 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] [ec2-plugin] (JENKINS-23705) EC2 slave disconnects on longer running builds
Bert Jan Schrijver commented on JENKINS-23705 EC2 slave disconnects on longer running builds We tried the suggested solution from https://issues.jenkins-ci.org/browse/JENKINS-14332 and downgraded the kernel on the master from 3.14.23-22.44.amzn1.x86_64 to 3.4.73-64.112.amzn1.x86_64. I've been throwing builds at it like crazy for the last hour but haven't seen any disconnects anymore. I'll keep a eye on things and post an update here later. So far, the kernel downgrade seems to fix the issues for us. 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-14332) Repeated channel/timeout errors from Jenkins slave
Bert Jan Schrijver commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Same thing for us: Amazon Linux master with EC2 slaves plugin and Amazon Linux slaves. Builds were randomly hanging and slaves were timing out. We downgraded the kernel on the master this morning from 3.14.23-22.44.amzn1.x86_64 to 3.4.73-64.112.amzn1.x86_64 and haven't seen any issues since. I'll report back later. 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-14332) Repeated channel/timeout errors from Jenkins slave
Bert Jan Schrijver edited a comment on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Same thing for us: Amazon Linux master with EC2 slaves plugin and Amazon Linux slaves. Builds were randomly hanging and slaves were timing out. We downgraded the kernel on the master this morning from 3.14.23-22.44.amzn1.x86_64 to 3.4.73-64.112.amzn1.x86_64 and haven't seen any issues since. Slaves are still running 3.14 kernel (3.14.27-25.47.amzn1.x86_64). I'll report back later. 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] [junit-plugin] (JENKINS-26153) JUnit missing builds
Gergely Pilisi commented on JENKINS-26153 JUnit missing builds Hi, any update on this? The workaround is working, however I need the original graph if possible. Please give me some feedback. Thank you! 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Karl Theil commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 this is an other issue im confronted with too: https://issues.jenkins-ci.org/browse/JENKINS-26318 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-23914) Invalid element added to in job causing NPE on job load
Martin Heinzerling commented on JENKINS-23914 Invalid element added to in job causing NPE on job load Still an issue with 1.598. Beside Trigger and GitSCM, and }} are also deleted. And is set to default. Pushing a backup with jenkins_cli update-job is working fine. After restoring a working version I tried making the same changes as before but I couldn't reproduce the bug anymore. 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] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
Per Arnold Blaasmo commented on JENKINS-26303 Not compatible with Subversion plugin 2.5 I have tested you plugin fix, and it works now. 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] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
Per Arnold Blaasmo edited a comment on JENKINS-26303 Not compatible with Subversion plugin 2.5 I have tested your plugin fix, and it works now. 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] [workflow-plugin] (JENKINS-26874) Restricting build execution cause does not work
Timur Batyrshin created JENKINS-26874 Restricting build execution cause does not work Issue Type: Bug Assignee: Jesse Glick Attachments: skitch.png Components: workflow-plugin Created: 10/Feb/15 9:37 AM Description: Restricting build execution cause does not work for workflow jobs (I think I'm using Job Restrictions Plugin for that, see attachment). There are simply no log lines for that and the jobs starts when started manually as well. Project: Jenkins Priority: Minor Reporter: Timur Batyrshin 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] [clearcase-ucm-plugin] (JENKINS-26875) CCUCM Deliver read-only component (case 12580)
Mads Nielsen created JENKINS-26875 CCUCM Deliver read-only component (case 12580) Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 10/Feb/15 9:50 AM Project: Jenkins Priority: Minor Reporter: Mads Nielsen 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-5318) Allow default view at user level
Andreas Galek commented on JENKINS-5318 Allow default view at user level This would be a great extension in Jenkins if every user could configure his start view. 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] [p4-plugin] (JENKINS-26713) P4Jenkins - Modifying Cilentspec Root
Paul Allen commented on JENKINS-26713 P4Jenkins - Modifying Cilentspec Root This might seem strange, but the output is correct. The first line 'in workspace c:\trees\nodes\rsmsnbuild121' is reported by Jenkins. I have no control over the text, it is also true as this is where Jenkins will execute the build. However, as I no longer modify the clients root for Static workspaces the sync command can run anywhere on the machine. As long as the files end up where Jenkins needs them (c:\trees\nodes\rsmsnbuild121), you can use Perforce to sync files to other parts of the system. I have seen a few customers use this trick to sync, compilers, build tools, IDE's, etc... outside of the build area. 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] [multijob-plugin] (JENKINS-26876) Option to mark a phase as non-blocking / asynchron phase
lx last created JENKINS-26876 Option to mark a phase as non-blocking / asynchron phase Issue Type: New Feature Assignee: Unassigned Components: multijob-plugin Created: 10/Feb/15 10:26 AM Description: Have a option like the "disable job" option to mark a phase/job as e.g. non-blocking asynchron non-waiting This phase/job is executed in normal manner of the pipeline but does not block the execution cycle of the surrounding multijob. For example: A multijob M with three phases: Phase 1: A Phase 2: B Phase 3: C + D M has several post-builds (with conditions). B,C,D are multijobs itself. C is a multijob containing jobs (e.g. maintenance jobs), which can take very long. This job can be executed asynchron, so that the surrounding multijob M can finish an execute it's post builds and a result can be generated. The result of C is not important for the result of M, but should be shown within the pipeline of M. Project: Jenkins Labels: plugin jenkins multi-job configuration Priority: Minor Reporter: lx last 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] [multijob-plugin] (JENKINS-26876) Option to mark a phase/job as non-blocking/asynchron
lx last updated JENKINS-26876 Option to mark a phase/job as non-blocking/asynchron Change By: lx last (10/Feb/15 10:28 AM) Summary: Option to mark a phase /job as non-blocking / asynchron phase 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] [promoted-builds-plugin] (JENKINS-10068) Ability to remove a Promotion on a promoted build
dmeibusch commented on JENKINS-10068 Ability to remove a Promotion on a promoted build @AnneTheAgile This sounds great! In our workflow flows, the reversing of a promotion is not important. Important would be removing the build as the linkage for any promotion based URL (this is key for out build pipelines) removing the visual indications (icon 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] [promoted-builds-plugin] (JENKINS-10068) Ability to remove a Promotion on a promoted build
dmeibusch edited a comment on JENKINS-10068 Ability to remove a Promotion on a promoted build @AnneTheAgile This sounds great! In our workflows, the reversing the actions of a promotion is not so important. Important would be: removing the build in the links via any promotion based URL (this is key for our build pipelines) removing the visual indications (icon 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] [promoted-builds-plugin] (JENKINS-10068) Ability to remove a Promotion on a promoted build
dmeibusch edited a comment on JENKINS-10068 Ability to remove a Promotion on a promoted build @AnneTheAgile This sounds great! In our workflow flows, the reversing of a promotion is not important. Important would be removing the build in the links via any promotion based URL (this is key for our build pipelines) removing the visual indications (icon 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] [gerrit-trigger-plugin] (JENKINS-24575) The instance of extension class should not be kept
rin_ne closed JENKINS-24575 as Fixed The instance of extension class should not be kept Change By: rin_ne (10/Feb/15 11:22 AM) Status: Resolved Closed 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] [gerrit-trigger-plugin] (JENKINS-24099) Connection to Gerrit is always established on bootup
rin_ne closed JENKINS-24099 as Fixed Connection to Gerrit is always established on bootup Change By: rin_ne (10/Feb/15 11:23 AM) Status: Resolved Closed 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] [gerrit-trigger-plugin] (JENKINS-24074) Cannot review for build completed to default Gerrit via REST API
rin_ne closed JENKINS-24074 as Fixed Cannot review for build completed to default Gerrit via REST API Change By: rin_ne (10/Feb/15 11:23 AM) Status: Resolved Closed 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] [gerrit-trigger-plugin] (JENKINS-24012) Messages in RabbitMQ's queue was consumed but unacknowledged
rin_ne closed JENKINS-24012 as Fixed Messages in RabbitMQ's queue was consumed but unacknowledged Change By: rin_ne (10/Feb/15 11:23 AM) Status: Resolved Closed 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] [gerrit-trigger-plugin] (JENKINS-22813) Warning when clean install and restart
rin_ne closed JENKINS-22813 as Fixed Warning when clean install and restart Change By: rin_ne (10/Feb/15 11:25 AM) Status: Resolved Closed 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] [gerrit-trigger-plugin] (JENKINS-23421) Parameter value should be always displayed as human-readable
rin_ne closed JENKINS-23421 as Fixed Parameter value should be always displayed as human-readable Change By: rin_ne (10/Feb/15 11:24 AM) Status: Resolved Closed 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] [gerrit-trigger-plugin] (JENKINS-23189) REST related configuration is lost when copy server
rin_ne closed JENKINS-23189 as Fixed REST related configuration is lost when copy server Change By: rin_ne (10/Feb/15 11:24 AM) Status: Resolved Closed 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] [gerrit-trigger-plugin] (JENKINS-22814) Some infomations are logged from constructor on startup
rin_ne closed JENKINS-22814 as Fixed Some infomations are logged from constructor on startup Change By: rin_ne (10/Feb/15 11:24 AM) Status: Resolved Closed 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-26739) Executors are dying since 1.597 - related to the directory layout change?
Thomas Müller commented on JENKINS-26739 Executors are dying since 1.597 - related to the directory layout change? okay - quite period doesn't help ... feel like a bit less - but we are not that acive at the moment. Any further ideas on this? THX 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] [remoting] (JENKINS-26855) Unreachable objects "remoting.Channel" can not garbage collect
denger tung edited a comment on JENKINS-26855 Unreachable objects "remoting.Channel" can not garbage collect Many warning log in tomcat: 10, 2015 2:38:09 hudson.node_monitors.AbstractNodeMonitorDescriptor$Record waring: Previous Architecture monitoring activity still in progress. Interrupting 10, 2015 2:38:09 hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor waring: Failed to monitor oped-slave-08-argus-cp185 for Clock Difference hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:549) at hudson.remoting.Request.callAsync(Request.java:204) at hudson.remoting.Channel.callAsync(Channel.java:778) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280) Caused by: java.nio.channels.AsynchronousCloseException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:412) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:35) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.InputStream.read(InputStream.java:101) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 10, 2015 2:38:09 hudson.node_monitors.AbstractNodeMonitorDescriptor$Record waring: Previous Clock Difference monitoring activity still in progress. Interrupting 10, 2015 2:38:09 hudson.node_monitors.AbstractNodeMonitorDescriptor$Record 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] [parameterized-trigger-plugin] (JENKINS-26877) Manual trigger ignores properties file if the build node doesn't exists anymore
hcguersoy created JENKINS-26877 Manual trigger ignores properties file if the build node doesn't exists anymore Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 10/Feb/15 11:34 AM Description: Our builds are running in slaves based running in 'on demand' docker containers (using jenkins docker plugin). This means, after a build this slave is thrown away and is not available anymore. Now, I've a pipeline consisting of Job A and B. In a post build action I have configured a 'Build other projects (manual step)' action. In this action, I gather build parameters from a properties file and trigger Job B. Now, then I trigger the Job B after the successful build of A, nothing happens but I got a large stacktrace in log (see below). Then I switch to "Trigger parameterized build on otherprojects' then everything is OK, the same if I don't build Job A on a volatile slave. The log: Feb 09, 2015 6:13:05 PM WARNING org.kohsuke.stapler.HttpResponseRenderer$Default handleJavaScriptProxyMethodCall call to /$stapler/bound/7b4683aa-8e6e-4cd8-a6b2-725176bbc2e7/triggerManualBuild failed java.lang.NullPointerException at hudson.plugins.parameterizedtrigger.FileBuildParameters.extractAllValues(FileBuildParameters.java:112) at hudson.plugins.parameterizedtrigger.FileBuildParameters.getAction(FileBuildParameters.java:102) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.triggerBuild(BuildPipelineView.java:570) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.triggerManualBuild(BuildPipelineView.java:465) 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:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$_javascript_ProxyMethodDispatcher.doDispatch(MetaClass.java:470) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:812) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:198) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.sec
[JIRA] [gerrit-trigger-plugin] (JENKINS-26878) Wrong report to Gerrit
Pol Dellaiera created JENKINS-26878 Wrong report to Gerrit Issue Type: Bug Assignee: rsandell Attachments: Change I205aa7cf- Update. - s-eci-versn.easme Code Review 2015-02-10 13-13-03.png, Gerrit Trigger Plugin Configuration [Jenkins] 2015-02-10 13-13-31.png, Gerrit Trigger Plugin Configuration [Jenkins] 2015-02-10 13-13-49.png, Log [Jenkins] 2015-02-10 13-17-36.png, Log [Jenkins] 2015-02-10 13-17-50.png, Sandbox #227 Console [Jenkins] 2015-02-10 13-09-42.png Components: gerrit-trigger-plugin Created: 10/Feb/15 12:18 PM Description: Hi, Since a couple of days, Jenkins (1.598) is not reporting back to gerrit when a build is successful. We were using Gerrit 2.9.4 and we though that the problem was there, so, this morning, we've upgraded to Gerrit 2.10, but it's still the same. I'm attaching some screenshots of the build, the result in Gerrit, and the configuration of Gerrit-trigger. If you need more information, just let me know. Project: Jenkins Priority: Major Reporter: Pol Dellaiera 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] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Horst Krause commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I submitted pull request #304. https://github.com/jenkinsci/git-plugin/pull/304 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-11851) More options for default parameters
Hannes Kogler commented on JENKINS-11851 More options for default parameters I am searching for years now for such a feature! As I see it, this would improve the usability of parameterized builds a lot, because you save much time of users who don't need to change and even don't need to know about any of the parameters. I cannot imagine that an option to hide predefined parameters would be so much effort to implement... 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Nela Kolundzija commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module For me the same still the error occurs randomly on different machines and different build steps. I'm working with latest version of Jenkins 1.598. Any suggestion? thnx! 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] [subversion-plugin] (JENKINS-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch commented on JENKINS-26866 jenkins java.io.ioexception remote file operation failed Thanks Daniel. Sorry, I am doing my best to get this resolved, because I have left our build system in an unknown state - even though the jobs are all running successfully - while I am away on holiday, during a fairly important milestone for our project. Needless to say, for any conscientious person, that makes me feel ill. Anyway, apparently I haven't managed to provide the Jenkins version. My initial installation of Jenkins on this server was via the download link for Fedora on the Jenkins site here: http://pkg.jenkins-ci.org/redhat/ Then I have updated via the web interface to the running Master server. I am fairly confident that means I am running 1.598. Please tell me how I check. 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-22853) SEVERE: Trying to unexport an object that's already unexported
Nela Kolundzija edited a comment on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported still happening for me even with the latest version of jenkins 1.598. java.lang.IllegalStateException: Invalid object ID 1078 iota=1079 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Palio3_Ctrl_Builds_Phonak_CH01WW7441(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy92.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1078 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@7d0fdd32 created at at hudson.remoting.Command.(Command.java:6
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Nela Kolundzija commented on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported still happening for me even with latest version of jenkins 1.598. java.lang.IllegalStateException: Invalid object ID 1078 iota=1079 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Palio3_Ctrl_Builds_Phonak_CH01WW7441(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy92.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1078 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@7d0fdd32 created at at hudson.remoting.Command.(Command.java:67) a
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Nela Kolundzija edited a comment on JENKINS-23271 Intermittent Invalid Object ID in remoting module For me the same still the error occurs randomly on different machines and different build steps. I'm working with latest version of Jenkins 1.598. Any suggestion? thnx! java.lang.IllegalStateException: Invalid object ID 1078 iota=1079 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Palio3_Ctrl_Builds_Phonak_CH01WW7441(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy92.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1078 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remot
[JIRA] [core] (JENKINS-26780) Auto-installer for JDK no longer works
Daniel Beck
commented on JENKINS-26780
Auto-installer for JDK no longer works
FWIW I experienced something similar (mixup of various client downloaded DownloadService files) on Oct 28 2014 and Feb 10 2015. It's annoying as hell.
For me, the fix once this happens is:
Manage Jenkins, Script Console:
hudson.model.DownloadService.signatureCheck = false
hudson.model.DownloadService.Downloadable.all().each { it.updateNow() }
hudson.model.DownloadService.signatureCheck = true
return
Then go to Manage Jenkins, Configure Jenkins, and make sure that all tool installers point to the correct versions. Change and save if necessary.
It may even be necessary to verify that all tools on all slaves are actually correct, e.g. there may be a Maven in the folder containing auto-installed Ant binaries.
A possible solution would be to disable browser downloads of update center metadata (Manage Jenkins, Configure Jenkins, Download Preferences, disable Use browser). This may actually result in Jenkins not receiving any updates to tool versions though (not sure about that).
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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Nela Kolundzija edited a comment on JENKINS-23271 Intermittent Invalid Object ID in remoting module For me the same still the error occurs randomly on different machines and different build steps. I'm working with latest version of Jenkins 1.598 and Java8u31. Any suggestion? thnx! java.lang.IllegalStateException: Invalid object ID 1078 iota=1079 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Palio3_Ctrl_Builds_Phonak_CH01WW7441(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy92.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1078 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Nela Kolundzija edited a comment on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported still happening for me even with the latest version of jenkins 1.598 and Java8u31 java.lang.IllegalStateException: Invalid object ID 1078 iota=1079 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) at ..remote call to Palio3_Ctrl_Builds_Phonak_CH01WW7441(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy92.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #1078 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Released at Tue Feb 10 13:21:05 CET 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@7d0fdd32 created at at hudson.remoting.Command.(C
[JIRA] [compress-artifacts-plugin] (JENKINS-26858) java.net.URISyntaxException when special chars are used in filename
Oliver Gondža stopped work on JENKINS-26858 java.net.URISyntaxException when special chars are used in filename Change By: Oliver Gondža (10/Feb/15 2:06 PM) Status: In Progress Open 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] [compress-artifacts-plugin] (JENKINS-26858) java.net.URISyntaxException when special chars are used in filename
Oliver Gondža commented on JENKINS-26858 java.net.URISyntaxException when special chars are used in filename Fix proposed: https://github.com/jenkinsci/compress-artifacts-plugin/pull/2 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] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Daniel Spilker resolved JENKINS-17222 as Fixed Add ability to specify more than one location when using the svn method Will be released in 1.30. Change By: Daniel Spilker (10/Feb/15 2:19 PM) Status: In Progress Resolved Assignee: Chris Dore Daniel Spilker Resolution: Fixed 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] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported
Daniel Spilker resolved JENKINS-17513 as Fixed For SVN only one workspaceupdater is supported Will be released in 1.30. Change By: Daniel Spilker (10/Feb/15 2:20 PM) Status: In Progress Resolved Resolution: Fixed 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] [dashboard-view-plugin] (JENKINS-26879) Job Statistics portlet slow to load with many jobs and builds
Matthew Sawin created JENKINS-26879 Job Statistics portlet slow to load with many jobs and builds Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view-plugin Created: 10/Feb/15 2:48 PM Description: The Job Statistics portlet takes a long time to initially load with 100+ jobs and 1000+ builds each. Thread dump shows the stack trace is mostly spent in RunList.size() which is being called in StatJobs.HealthStatus.getHealthStatus(). This forces every build to be loaded from disk when, looking at the code, all it needs to do is check if the list is empty. "Handling GET /view/ServersDashboard/ from 192.168.70.40 : RequestHandlerThread10 View/index.jelly Dashboard/main.jelly StatJobs/portlet.jelly StatJobs/statjobs.jelly" Id=59 Group=main RUNNABLE at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:272) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) locked java.io.BufferedInputStream@7bb58e96 at java.io.FilterInputStream.read(FilterInputStream.java:83) at java.io.PushbackInputStream.read(PushbackInputStream.java:139) at com.thoughtworks.xstream.core.util.XmlHeaderAwareReader.getHeader(XmlHeaderAwareReader.java:79) at com.thoughtworks.xstream.core.util.XmlHeaderAwareReader.(XmlHeaderAwareReader.java:61) at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65) at hudson.XmlFile.unmarshal(XmlFile.java:163) at hudson.model.Run.reload(Run.java:321) at hudson.model.Run.(Run.java:309) at hudson.model.AbstractBuild.(AbstractBuild.java:178) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:38) at sun.reflect.GeneratedConstructorAccessor70.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at jenkins.model.lazy.LazyBuildMixIn.loadBuild(LazyBuildMixIn.java:158) at jenkins.model.lazy.LazyBuildMixIn$1.create(LazyBuildMixIn.java:135) at hudson.model.RunMap.retrieve(RunMap.java:220) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:465) locked hudson.model.RunMap@4ca4594d at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:448) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:356) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:332) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:74) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.size(RunList.java:108) at hudson.plugins.view.dashboard.stats.StatJobs$HealthStatus.getHealthStatus(StatJobs.java:54) at hudson.plugins.view.dashboard.stats.StatJobs.getJobStat(StatJobs.java:104) Even after the initial load, subsequent requests still take several seconds due to complete traversal of every build for every job. "Handling GET / from 192.168.70.53 : RequestHandlerThread20 View/index.jelly Dashboard/main.jelly StatJobs/portlet.jelly StatJobs/statjobs.jelly" Id=69 Group=main RUNNABLE at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:332) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:74) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.size(RunList.java:108) at hudson.plugins.view.dashboard.stats.StatJobs$HealthStatus.getHealthStatus(StatJobs.java:54) at hudson.plugins.view.dashboard.stats.StatJobs.getJobStat(StatJobs.java:104) Environment: Jenkins 1.598, Dashboard View 2.9.4
[JIRA] [promoted-builds-plugin] (JENKINS-26880) 'Restrict where this promotion process can be run' doesn't work for new groovy process
Pawel Grzegrzolka
created JENKINS-26880
'Restrict where this promotion process can be run' doesn't work for new groovy process
Issue Type:
Bug
Assignee:
Unassigned
Components:
promoted-builds-plugin
Created:
10/Feb/15 2:54 PM
Description:
I'm using 'Restrict where this promotion precess can be run' option together with 'Execute system groovy script' as an action.
The script executes on the specific host, but when I create a groovy process:
cmd = ("ipconfig /all").execute()
cmd.consumeProcessOutput(out, err)
cmd.waitFor()
println out
println err
The new created process is running on the Jenkins host, not on the required node.
Environment:
promoted builds plugin: 2.17
Jenkins: 1.583
Groovy: groovy-2.4.0-beta-2
host: Windows 2013R2 Server
Project:
Jenkins
Priority:
Minor
Reporter:
Pawel Grzegrzolka
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] [groovy-plugin] (JENKINS-26880) 'Restrict where this promotion process can be run' doesn't work for new groovy process
Pawel Grzegrzolka
updated JENKINS-26880
'Restrict where this promotion process can be run' doesn't work for new groovy process
Change By:
Pawel Grzegrzolka
(10/Feb/15 3:09 PM)
Description:
I'm using 'Restrict where this
promotion precess
process
can be run' option together with 'Execute system groovy script' as an action. The script executes on the specific host, but when I create a groovy process:{noformat} cmd = ("ipconfig /all").execute()cmd.consumeProcessOutput(out, err)cmd.waitFor()println outprintln err{noformat}The new created process is running on the Jenkins host, not on the required node.
Component/s:
groovy-plugin
Component/s:
promoted-builds-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] [groovy-plugin] (JENKINS-26880) 'Restrict where this promotion process can be run' doesn't work for new groovy process
Pawel Grzegrzolka updated JENKINS-26880 'Restrict where this promotion process can be run' doesn't work for new groovy process Change By: Pawel Grzegrzolka (10/Feb/15 3:11 PM) Environment: Hudson Groovy builder: 1.20 promoted builds plugin: 2.17Jenkins: 1.583Groovy: groovy-2.4.0-beta-2host: Windows 2013R2 Server 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-14332) Repeated channel/timeout errors from Jenkins slave
Jonathan Langevin commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave I'm on Amazon EC2 w/ Ubuntu 14.04.1 LTS. I've downgraded the kernel (manually) to 3.4. wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.105-quantal/linux-headers-3.4.105-0304105-generic_3.4.105-0304105.201412012335_amd64.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.105-quantal/linux-headers-3.4.105-0304105_3.4.105-0304105.201412012335_all.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.105-quantal/linux-image-3.4.105-0304105-generic_3.4.105-0304105.201412012335_amd64.deb dpkg -i linux-* Once I had the 3.4 kernel installed, I had to make it the default kernel on boot, so I followed the instructions here: http://statusq.org/archives/2012/10/24/4584/ I'm trying out some builds now to see how Jenkins behaves... 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] [active-directory-plugin] (JENKINS-26846) Abot Aborsi Cytotec Misoprostol, 087831810789
Larry Shatzer, Jr. updated JENKINS-26846 Abot Aborsi Cytotec Misoprostol, 087831810789 Change By: Larry Shatzer, Jr. (10/Feb/15 3:56 PM) Environment: Untuk Pemesanan/Konsultasi Hubungi *Hotline/Sms : 0878 3181 0789 Description: Untuk Pemesanan/Konsultasi Hubungi *Hotline/Sms : 0878 3181 0789 Banyak kejadian seperti keluarga yang sudah merencanakan dengan matang tentang kehamilan nya kelak dengan melihat tanggal yang biasanya wanita mengalami menstruasi, oleh karena itu jangan pernah menyepelakan tentang hal-hal yang dapat menyebabkan kehamilan bila ingin mempunyai dan ingin membina keluarga berencana.Oleh karena itu disini kami menyediakan obat telat datang bulan aman dan terbukti ampuh untuk mengatasi terlambat datang bulan bila mana anda tidak atau belum menghendaki anak yang akan lahir kelak.Obat telat bulan bisa menjadi solusi sebagai cara menggugurkan kandungan dengan aman dan tanpa efek samping, ingat bila anda ingin membina keluarga berencana namun terjadi hamil saat anda lupa menghitung tanggal, ataupun meminum obat KB sebagai pencegah hamil, oleh karena itu kami sarankan anda segera mengkonsumsi obat telat bulan yang satu ini, karena sangat aman dan terbukti 100% dipakai kebanyakan kalangan , khususnya yang ingin membina keluarga berencana. Priority: Major Trivial Labels: jenkins URL: https://aborsisehat.wordpress.com/ 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] [active-directory-plugin] (JENKINS-26846) Abot Aborsi Cytotec Misoprostol, 087831810789
Larry Shatzer, Jr. closed JENKINS-26846 as Fixed Abot Aborsi Cytotec Misoprostol, 087831810789 Change By: Larry Shatzer, Jr. (10/Feb/15 3:56 PM) Status: Reopened Closed Resolution: Fixed 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] [active-directory-plugin] (JENKINS-26846) Abot Aborsi Cytotec Misoprostol, 087831810789
Larry Shatzer, Jr. reopened JENKINS-26846 Abot Aborsi Cytotec Misoprostol, 087831810789 Change By: Larry Shatzer, Jr. (10/Feb/15 3:55 PM) Resolution: Not A Defect Status: Closed Reopened Assignee: Klinik Sehat Larry Shatzer, Jr. 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] [active-directory-plugin] (JENKINS-26846) Abot Aborsi Cytotec Misoprostol, 087831810789
Larry Shatzer, Jr. closed JENKINS-26846 as Not A Defect Abot Aborsi Cytotec Misoprostol, 087831810789 Change By: Larry Shatzer, Jr. (10/Feb/15 3:55 PM) Status: Open Closed Resolution: Not A Defect 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] [bazaar-plugin] (JENKINS-25746) Obat Penyubur Sperma Semenax Alami
Larry Shatzer, Jr. closed JENKINS-25746 as Fixed Obat Penyubur Sperma Semenax Alami Change By: Larry Shatzer, Jr. (10/Feb/15 3:57 PM) Status: Resolved Closed 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus D'Souza edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! See attached ErrorConsole.png. Hopefully this makes sense to you? Update - based on the console, I manually ran the buildHistory/ajax call which seems to be the last thing that is called when this error pops-up and there's a stack trace alright! java.lang.Exception: Missing the 'n' HTTP header at hudson.widgets.HistoryWidget.doAjax(HistoryWidget.java:161) at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source) 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:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(Diagnostic
[JIRA] [bazaar-plugin] (JENKINS-25746) Obat Penyubur Sperma Semenax Alami
Larry Shatzer, Jr. updated JENKINS-25746 Obat Penyubur Sperma Semenax Alami Change By: Larry Shatzer, Jr. (10/Feb/15 3:57 PM) Description: Anda Mengalami Sperma Encer / Air Mani kurang subur dengan cara menyembuhkan sperma yang tidak subur dengan secara alami menggunakasexual characteristicsbat herbal / Obat Penyubur Sperma terbaik ini maka anda tidak perlu bingung lagi untuk mencari solusi pengobatan sperma tidak subur hanya dengan menggunakan obat penyubur sperma herbal, sperma yasexual characteristicstidak subur akan kembali routine obat ini mujarab yang paling ampuh, karena dengan cara cepat mengobati sperma tidak subur menggunakan obat herbal ini maka anda akan sembuh juga dari berbagai macam penyakit. Mengapa bisa demikian? Karena obat penyubur sperma ini adalah obat herbal multi khasiat yang berguna juga untuk mengobati berbagai macam penyakit, oleh karena itu maka jangan tunggu lama lagi, segeralah sembuhkan penyakit sperma anda yang tidak subur dengan menggunakan obat penyubur sperma yang mujarab dan ampuh ini.Menderita sperma encer? Ejakulasi dini? Tidak bisa ereksi? Susah punya keturunan? Menderita virgit? Sperma Susah keluar? Dan mandul? Segeralah sembuhkan hanya dengan menggunakan obat herbal terbaik yang aman dan alami untuk mengobati berbagai macam penyakit.Apa saja faktor penyebab sperma tidak subur?Ada banyak faktor penyebab yang bisa menimbulkan ketidak suburan pada sperma diantaranya:Pola Hidup /Gaya hidup yang tidak sehatKegemukan / ObesitasMinim / Kurang olahragaStressTerlalu aktif secara seksual pada usia diniMerokok, mengkonsumsi alkohol dan narkobaBerendan di air panas dengan waktu lebih dari 15 menitRadiasi ponsel dan lapotRadang testisKanker testisKecelakaan yang bisa menimbulkan gangguan pada sistem reproduksiItulah beberapa faktor penyebabsexual characteristicserma tidak subur maka dari itu kita harus mengetahui dan mencegah terjadinya sperma tidak subur sexual characteristics.Mempunyai keturunan adalah keinginan semua manusia, namun jika anda menderita susah punya keturunan, maka segeralah sembuhkan hanya dengan tricajus obat sperma tidak subur yang muujarab, alami, aman, terpercaya dan bebas dari efek samping.Bagaimana cara mengatasi sperma tidak subur? Apakah pencerita sperma tidak subur masih sexual characteristicsa punya keturunan?Untuk anda yang menderita sperma tidak subur maka tidak perlu mengeluh, karensexual characteristicsetiap masalah juga pasti ada solusinya, dan jika anda sedang mencari solusi pengobatan untuk sperma tidak subur maka segeralah atasi dengan menggunakan tricaju obat herbal untuk pengobatan sperma tidak subur.Tips Pengganti Obat Penyubur Sperma Secara Alami secara Perlakuan :Anda ingin meningkatkan peluang memiliki anak atau hanya sekadar ingin ejakulasi dengan tingkat sperma dan air mani yang tinggi? Sperma yang banyak merupakan satu tanda sistem reproduksi yang sehat. Tidak diragukan memiliki air mani dan sperma yang lebih banyak menghasilkan orgasme lebih lama, termasuk meningkatnya hasrat seks. Jika Anda ingin menyirami pasangan dengan cinta sekaligus menjadi seorang calon ayah, inilah beberapa tips untuk memperbaiki dan meningkatkan jumlah sperma:Berhenti merokokJika Anda seorang perokok saat ini, berhentilah. Selain menyebabkan napas tak sedap, merokok juga dapat memengaruhi jumlah sperma. Penelitian menujukan perokok memiliki jumlah sperma lebih kecil dibanding pria yang tidak merokok.Hindari memakai celana ketat dan panasTestis perlu memiliki suhu lebih sejuk dibanding bagian tubuh lain karena itu memakai celana dalam atau celana panjang ketat akan mengakibatkan suhu di sekitarnya panas. Sedapat mungkin usahakan tidak mengenakan celana dalam sewaktu tidur untuk menjaga suhu tetap sejuk.Mulailah makanan makanan yang tepatDiyakini atau tidak, pola makan akan memengaruhi produksi sperma. Cobalah makan makanan rendah lemak, berprotein tinggi, sayuran dan seluruh jenis padi-padian yang baik bagi kesehatan.Kurangi hubungan intim dan masturbasiBanyak pria mengeluhkan air mani mereka sedikit dan encer. Semakin banyak ejakulasi, semakin berkurang kekentalalan air mani tersebut. Jika Anda melakukan hubungan intim setiap hari atau lebih buruk lagi masturbasi akan berpengaruh
[JIRA] [_test] (JENKINS-26847) Obat Telat Bulan Gastrul/Misoprostol cytotec, 087831810789
Larry Shatzer, Jr. updated JENKINS-26847 Obat Telat Bulan Gastrul/Misoprostol cytotec, 087831810789 Change By: Larry Shatzer, Jr. (10/Feb/15 3:56 PM) Environment: Obat Aborsi, Obat Telat Bulan, Obat Penggugur Janin, Obat Penggugur Kandungan, Obat Pelancar Haid, Obat Cytotec, Obat Gastrul Description: Untuk Pemesanan/Konsultasi Hubungi *Hotline/Sms : 087831810789Menggugurkan kandungan adalah keputusan yang amat sulit, Apabila Anda tidak bisa membicarakan aborsi ini atau tidak ada pilihan lain untuk berdiskusi dengan dokter atau pelayan kesehatan. Untuk mengatasi masalah ini saya saya sarankan anda untuk membicarakannya dengan teman baik atau anggota keluarga.Bicarakanlah situasi ini, keputusan anda dan tata cara aborsi dengan orang tua atau orang dewasa lain yang anda percayaCara menggugurkan kandungan paling aman untuk usia 1 minggu atau 1 – 5 bulan, baik bagi wanita untuk melakukan pengguguran kandungan ( aborsi ) sendiri sampai dengan usia kehamilan minggu ke-12 adalah dengan meminum 2 obat Gastrul Mifepristone ( juga dikenal dengan nama pil abortus, RU 486, Mifegyn, Mifeprex ), dan Misoprostol juga dikenal dengan nama Cytotec, Arthrotec, Oxaprost, Cyprostol, Mibetec, Prostokos or Misotrol.Cara aborsi non medis atau obat penggugur kandungan ini telah memberi tingkat keberhasilan lebih dari 97%. Dan bila Anda tinggal di negara yang tidak menyediakan akses pelayanan aborsi yang aman dan anda ingin menggugurkan kandungan dengan obat-obat Mifepristone dan Misoprostol ini adalah cara yang tepat untuk mengatasi masalah anda. Labels: jenkins URL: https://aborsisehat.wordpress.com/2015/02/06/gastrul-obat-penggugur-kandungan/ 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] [_test] (JENKINS-26847) Obat Telat Bulan Gastrul/Misoprostol cytotec, 087831810789
Larry Shatzer, Jr. closed JENKINS-26847 as Not A Defect Obat Telat Bulan Gastrul/Misoprostol cytotec, 087831810789 Change By: Larry Shatzer, Jr. (10/Feb/15 3:56 PM) Status: Open Closed Resolution: Not A Defect 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus D'Souza edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! See attached ErrorConsole.png. Hopefully this makes sense to you? 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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=lshatzer&avatarId=10826";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=lshatzer";
style="color:#355564;">Larry Shatzer, Jr.
deleted https://issues.jenkins-ci.org/images/icons/task.gif";
height="16" width="16" border="0" align="absmiddle" alt="Task"> JENKINS-25746
Obat Penyubur
Sperma Semenax Alami
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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=lshatzer&avatarId=10826";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=lshatzer";
style="color:#355564;">Larry Shatzer, Jr.
deleted https://issues.jenkins-ci.org/images/icons/improvement.gif"; height="16"
width="16" border="0" align="absmiddle" alt="Improvement"> JENKINS-19420
Jual Celana
Obat Sakit Untuk Hernia
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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=lshatzer&avatarId=10826";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=lshatzer";
style="color:#355564;">Larry Shatzer, Jr.
deleted https://issues.jenkins-ci.org/images/icons/bug.gif";
height="16" width="16" border="0" align="absmiddle" alt="Bug"> JENKINS-26872
Test
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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=lshatzer&avatarId=10826";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=lshatzer";
style="color:#355564;">Larry Shatzer, Jr.
deleted https://issues.jenkins-ci.org/images/icons/newfeature.gif"; height="16"
width="16" border="0" align="absmiddle" alt="New Feature"> JENKINS-26846
Abot Aborsi
Cytotec Misoprostol, 087831810789
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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=lshatzer&avatarId=10826";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=lshatzer";
style="color:#355564;">Larry Shatzer, Jr.
deleted https://issues.jenkins-ci.org/images/icons/newfeature.gif"; height="16"
width="16" border="0" align="absmiddle" alt="New Feature"> JENKINS-26847
Obat Telat
Bulan Gastrul/Misoprostol cytotec, 087831810789
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] [extreme-notification-plugin] (JENKINS-26881) Doesn't send any notifications to webhook
Hrusikesh Panda created JENKINS-26881 Doesn't send any notifications to webhook Issue Type: Bug Assignee: Bruno Meneguello Components: extreme-notification-plugin Created: 10/Feb/15 4:05 PM Description: After installing the plugin and configuring a webhook URL ( I used a requestb.in URL), I fired a job. However, no notifications came through. I tried increasing the timeout, changing from all events to selected but no luck. Environment: Jenkins ver. 1.586 Project: Jenkins Labels: configuration Priority: Major Reporter: Hrusikesh Panda 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] [p4-plugin] (JENKINS-26814) P4-Plugin - Changes page not limited to defined Workspace view
Matthew Smith closed JENKINS-26814 as Fixed P4-Plugin - Changes page not limited to defined Workspace view Turns out the way our in house build scripts are stored, integrated, and synched is causing this issue - Closing as the plugin appears to be correctly displaying changes to the workspace, the workspace is just set up poorly. It would still be nice to able to tell the view to ignore certain folders on the Jenkins side - But for now I can just fix up my mappings in P4. Change By: Matthew Smith (10/Feb/15 4:10 PM) Resolution: Fixed Status: Open Closed 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] [build-pipeline-plugin] (JENKINS-26882) Memory leak in build pipeline plugin
Boris Goykhman created JENKINS-26882 Memory leak in build pipeline plugin Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-02-10 at 11.11.35 AM.png Components: build-pipeline-plugin Created: 10/Feb/15 4:15 PM Description: We have a Jenkins instance that is heavily utilizing Build Pipeline plugin. On a weekly or bi-weekly basis, Jenkins runs out of memory. Taking a heapdump and analyzing it for leak suspects indicated that build pipeline plugin is a culprit. Below are tables from leak suspects report taken from the heapdump: Label Number of Objects Used Heap Size Retained Heap Size au.com.centrumsystems.hudson.plugin.buildpipeline.BuildForm 7,126,445 285,057,800 1,881,469,128 – java.util.HashMap$Entry 6,535,640 209,140,480 1,669,522,544 Total: 2 entries 13,662,085 494,198,280 3,550,991,672 Given the fact that the JVM runs on 8G of heapspace, total size of objects related to build pipeline plugin occupies nearly half of that. Big difference between retained and used heap sizes shows that heap space is not being freed fast enough. I'm also attaching a screenshot of heap dump histogram for a more complete picture. Version of Jenkins: 1.588 Version of build pipeline plugin: 1.4.5 Project: Jenkins Labels: jenkins plugin build-pipeline-plugin Priority: Major Reporter: Boris Goykhman 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-26639) JClouds failing after upgrade to 1.598
Chris Manson commented on JENKINS-26639 JClouds failing after upgrade to 1.598 So what is the resolution to this then? What can we do to get this up and running again? 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Alex Earl updated JENKINS-23271 Intermittent Invalid Object ID in remoting module Upping this to critical because it's killing lots of my builds. Change By: Alex Earl (10/Feb/15 4:47 PM) Priority: Major Critical 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] [maven-plugin] (JENKINS-959) hudson deploys maven artifact even if test has failed
chirs damour commented on JENKINS-959 hudson deploys maven artifact even if test has failed +infinite. this is a silly decision that is not immediately apparent to people that know maven but don't know jenkins 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
martinfr62 commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Seeing same issue, restarting jenkins from the web browser cleared the issue, so clearly some sort of issue in the ec2 plugin itself, not an issue with the date on the instance hosting jenkins. My guess - the request object used to talk to amazon is not being created for every request, rather is being cached and reused. Thus it 'ages out' and is unusable after some period of time. Will take a look at the source code later today to see if I can find the issue. 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
martinfr62 edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Seeing same issue, restarting jenkins from the web browser cleared the issue, so clearly some sort of issue in the ec2 plugin itself, not an issue with the date on the instance hosting jenkins. 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] [build-publisher-plugin] (JENKINS-14372) Can't publish to public server with CSRF security option
Dave Hunt commented on JENKINS-14372 Can't publish to public server with CSRF security option I just discovered this today. Are there any plans to fix 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] [core] (JENKINS-26780) Auto-installer for JDK no longer works
Immo Huneke commented on JENKINS-26780 Auto-installer for JDK no longer works Thanks for the last comment. Interesting that this happened simultaneously on two different installations, one of which has NEVER had a JDK installed previously. We only noticed the problem because we wanted to build a Java application for the first time. I checked the access log but I am unsure what to look for. We have Apache access logs showing every call to the Jenkins URL from outside the box, but of course if it's internally calling itself on port 8080 then this will be invisible. Besides, I have just noticed that the log doesn't go back far enough - I'll have to see the archived ones. Will update this comment if I find anything significant. 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] [gitlab-plugin] (JENKINS-26641) "Filter branches" is empty
Aruna Gunasekera commented on JENKINS-26641 "Filter branches" is empty I am having the same problem, Which token do you need to use? 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-26780) Auto-installer for JDK no longer works
Immo Huneke updated JENKINS-26780 Auto-installer for JDK no longer works Change By: Immo Huneke (10/Feb/15 5:12 PM) Attachment: jenkins.log-20150209.gz 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-26780) Auto-installer for JDK no longer works
Immo Huneke edited a comment on JENKINS-26780 Auto-installer for JDK no longer works Thanks for the last comment. Interesting that this happened simultaneously on two different installations, one of which has NEVER had a JDK installed previously. We only noticed the problem because we wanted to build a Java application for the first time. I checked the access log but I am unsure what to look for. We have Apache access logs showing every call to the Jenkins URL from outside the box, but of course if it's internally calling itself on port 8080 then this will be invisible. However, I have discovered the relevant archived Jenkins log and attach this for information. I won't try the script approach described above - we have a workaround. 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] [warnings-plugin] (JENKINS-26113) REST api needed to get individual warnings values, not combined ones
Morne Joubert commented on JENKINS-26113 REST api needed to get individual warnings values, not combined ones i can't seem to get the list of warnings actions. I can see them in the debugger in the transientActions Vector but the values are protected 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-26780) Auto-installer for JDK no longer works
Immo Huneke updated JENKINS-26780 Auto-installer for JDK no longer works Change By: Immo Huneke (10/Feb/15 5:20 PM) Attachment: access_jenkins.zip 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-26780) Auto-installer for JDK no longer works
Immo Huneke edited a comment on JENKINS-26780 Auto-installer for JDK no longer works Thanks for the last comment. Interesting that this happened simultaneously on two different installations, one of which has NEVER had a JDK installed previously. We only noticed the problem because we wanted to build a Java application for the first time. I checked the access log but I am unsure what to look for. We have Apache access logs showing every call to the Jenkins URL from outside the box, but of course if it's internally calling itself on port 8080 then this will be invisible. However, I have discovered the relevant archived Jenkins log and attach this for information, together with the filtered Apache access log (showing just accesses to /jenkins.*) for the relevant date range. There are a number of calls to /jenkins/descriptorByName/hudson.tools.JDKInstaller/checkId and similar URLs in the file. I won't try the script approach described above - we have a workaround of manually adding the JDK installer file to the cache. 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] [gerrit-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
Eugene Korekin commented on JENKINS-26865 Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin In fact we have two options turned on: 'Exclude No Code Change' and 'Exclude Trivial Rebase'. For now I don't know which one of two leads to this behaviour. But in any case problem is: matrix children jobs is cancelled by gerrit-trigger while matrix parent isn't. Then it aborts cause it can't find child jobs. Gerrit is 2.8.4-15-g6dc8444 in our case. 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Ximon Eighteen
commented on JENKINS-26854
EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
To be clear, I have a working (well seems to work, I must admit it's not thoroughly tested yet) solution, but I'm not sure if it's wise for others to use. My solution is the pull request here, with the following tiny modification:
└─(.../scratch/ximon-ec2-plugin)─> git diff
diff --git a/src/main/java/hudson/plugins/ec2/EC2Cloud.java b/src/main/java/hudson/plugins/ec2/EC2Cloud.java
index 8891999..7feed81 100644
--- a/src/main/java/hudson/plugins/ec2/EC2Cloud.java
+++ b/src/main/java/hudson/plugins/ec2/EC2Cloud.java
@@ -476,6 +476,7 @@ public abstract class EC2Cloud extends Cloud {
public synchronized static AmazonEC2 connect(AWSCredentialsProvider credentialsProvider, URL endpoint) {
awsCredentialsProvider = credentialsProvider;
ClientConfiguration config = new ClientConfiguration();
+config.setSignerOverride("QueryStringSignerType");
ProxyConfiguration proxyConfig = Jenkins.getInstance().proxy;
Proxy proxy = proxyConfig == null ? Proxy.NO_PROXY : proxyConfig.createProxy(endpoint.getHost());
if (! proxy.equals(Proxy.NO_PROXY) && proxy.address() instanceof InetSocketAddress) {
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] [safe-restart] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Tommy McNeely created JENKINS-26883 SEVERE: Restarting VM as requested by username Issue Type: Bug Assignee: Unassigned Components: safe-restart Created: 10/Feb/15 5:26 PM Description: While managing modules, I am offered a "restart" button, but when I click it, it logs this message: Feb 10, 2015 10:00:46 AM jenkins.model.Jenkins$23 run SEVERE: Restarting VM as requested by username The "log level" should be changed to "INFO" or "NOTICE" rather than "SEVERE" as SEVERE should be reserved for "really bad things" such as crashes or something that is actually severe ~tommy Environment: CentOS 6.6 x86_64, jenkins-1.580.3-1.1.noarch, java-1.7.0-openjdk-1.7.0.75-2.5.4.0.el6_6.x86_64 Project: Jenkins Priority: Minor Reporter: Tommy McNeely 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] [gerrit-trigger-plugin] (JENKINS-26878) Wrong report to Gerrit
Pol Dellaiera resolved JENKINS-26878 as Fixed Wrong report to Gerrit Re-installed Jenkins and everything is working again. What a mess ! Change By: Pol Dellaiera (10/Feb/15 5:28 PM) Status: Open Resolved Resolution: Fixed 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] [ssh-slaves-plugin] (JENKINS-26884) Slave disconnect should be graceful during restart
Tommy McNeely updated JENKINS-26884 Slave disconnect should be graceful during restart Change By: Tommy McNeely (10/Feb/15 5:31 PM) Summary: Slave disconnect should be *nicer* graceful during restart 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] [ssh-slaves-plugin] (JENKINS-26884) Slave disconnect should be *nicer* during restart
Tommy McNeely created JENKINS-26884 Slave disconnect should be *nicer* during restart Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 10/Feb/15 5:31 PM Description: While managing modules, I am offered a "restart" button, but when I click it, it logs this message: Feb 10, 2015 10:00:46 AM jenkins.model.Jenkins$23 run SEVERE: Restarting VM as requested by username Feb 10, 2015 10:00:46 AM hudson.plugins.sshslaves.PluginImpl closeRegisteredConnections INFO: Forcing connection to ft-dbadmin:22 closed. Feb 10, 2015 10:00:46 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel ft-dbadmin java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) The restart process should "gracefully" close slave connections, as to not cause the "SEVERE" I/O errors. ~tommy Environment: CentOS 6.6 x86_64, jenkins-1.580.3-1.1.noarch, java-1.7.0-openjdk-1.7.0.75-2.5.4.0.el6_6.x86_64 Project: Jenkins Priority: Minor Reporter: Tommy McNeely 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] [gitlab-plugin] (JENKINS-26641) "Filter branches" is empty
Alex Earl commented on JENKINS-26641 "Filter branches" is empty You need to use a token which has been added to the project in Gitlab, e.g. for a user with access to the project. 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-26885) (all files in zip) link generates a zip archive that doesn't maintain permissions
Josh Davidson created JENKINS-26885 (all files in zip) link generates a zip archive that doesn't maintain permissions Issue Type: Bug Assignee: Unassigned Components: core Created: 10/Feb/15 6:18 PM Description: When using a the option to download all artifacts as a zip on a Linux job, the resulting archive doesn't maintain the permissions of the original file. A couple years ago, this used to work. It first broke for us when we upgrade to a 1.5x LTS release. We've recently switched to latest (1.598) and it is still broke. Here is an example from directory in a slave's workspace that is part of the archived artifacts: ls -l | head -4 total 42288 -rwxr-xr-x 1 goesrjen goesrsw74575 Feb 10 10:01 CreateSizes -rwxr-xr-x 1 goesrjen goesrsw 832 Apr 2 2014 create-workspace rw-rr- 1 goesrjen goesrsw 25816831 Jan 26 20:19 GroundServiceApp.jar When I download all artifacts as a zip, this is what is in the directory after extraction: ls -l | head -4 total 42288 rw-rr- 1 davidsj2 goesrsw74575 Feb 10 10:01 CreateSizes rw-rr- 1 davidsj2 goesrsw 832 Apr 2 2014 create-workspace rw-rr- 1 davidsj2 goesrsw 25816831 Jan 26 20:19 GroundServiceApp.jar If I manually "zip -r .zip " on the slave, and then unzip everything is fine, so it has something to do with how Jenkins is creating the zip file. Environment: Linux RHEL6 x86-64 Project: Jenkins Labels: archive Priority: Minor Reporter: Josh Davidson 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-26885) (all files in zip) link generates a zip archive that doesn't maintain permissions
Josh Davidson
updated JENKINS-26885
(all files in zip) link generates a zip archive that doesn't maintain permissions
Change By:
Josh Davidson
(10/Feb/15 6:20 PM)
Description:
When using a the option to download all artifacts as a zip on a Linux job, the resulting archive doesn't maintain the permissions of the original file. A couple years ago, this used to work. It first broke for us when we upgrade to a 1.5x LTS release. We've recently switched to latest (1.598) and it is still broke.Here is an example from directory in a slave's workspace that is part of the archived artifacts:
{code}
ls -l | head -4total 42288-rwxr-xr-x 1 goesrjen goesrsw74575 Feb 10 10:01 CreateSizes-rwxr-xr-x 1 goesrjen goesrsw 832 Apr 2 2014 create-workspace-rw-r--r-- 1 goesrjen goesrsw 25816831 Jan 26 20:19 GroundServiceApp.jar
{code}
When I download all artifacts as a zip, this is what is in the directory after extraction:
{code}
ls -l | head -4total 42288-rw-r--r-- 1 davidsj2 goesrsw74575 Feb 10 10:01 CreateSizes-rw-r--r-- 1 davidsj2 goesrsw 832 Apr 2 2014 create-workspace-rw-r--r-- 1 davidsj2 goesrsw 25816831 Jan 26 20:19 GroundServiceApp.jar
{code}
If I manually "zip -r .zip " on the slave, and then unzip everything is fine, so it has something to do with how Jenkins is creating the zip file.
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-26639) JClouds failing after upgrade to 1.598
Daniel Beck commented on JENKINS-26639 JClouds failing after upgrade to 1.598 Wait for 1.599 to be released, and upgrade. This will work, until another attempt to upgrade Guice is made. 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-26883) SEVERE: Restarting VM as requested by username
Daniel Beck updated JENKINS-26883 SEVERE: Restarting VM as requested by username Change By: Daniel Beck (10/Feb/15 6:32 PM) Component/s: core Component/s: safe-restart 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-26883) SEVERE: Restarting VM as requested by username
Daniel Beck updated JENKINS-26883 SEVERE: Restarting VM as requested by username Change By: Daniel Beck (10/Feb/15 6:33 PM) Issue Type: Bug Improvement 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-26884) Slave disconnect should be graceful during restart
Daniel Beck updated JENKINS-26884 Slave disconnect should be graceful during restart Applies to all slave types. Change By: Daniel Beck (10/Feb/15 6:37 PM) Component/s: ssh-slaves-plugin Component/s: core Assignee: Kohsuke Kawaguchi 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-26885) (all files in zip) link generates a zip archive that doesn't maintain permissions
Daniel Beck commented on JENKINS-26885 (all files in zip) link generates a zip archive that doesn't maintain permissions If I manually "zip -r .zip " on the slave, and then unzip everything is fine, so it has something to do with how Jenkins is creating the zip file. Build artifacts are stored on the master. 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.
