[JIRA] (JENKINS-52591) Job DSL does not track manual changes correctly
Title: Message Title Artur Szostak commented on JENKINS-52591 Re: Job DSL does not track manual changes correctly No, I have not raised this issue any further, since I do not know the Jenkins development model well enough to know where to send the report and how to structure it to make any sense. The only obvious report I could think of making was this ticket with a reproducible example for job-dsl-plugin. I rely on actual Jenkins developers with far more knowledge about the internals to triage the tickets and redirect them to the appropriate place as necessary. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192434.1531768264000.20707.1557313140209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31866) Attempts to restrict Pipeline jobs from running on master result in job hanging
Title: Message Title Artur Szostak commented on JENKINS-31866 Re: Attempts to restrict Pipeline jobs from running on master result in job hanging Thank you for the warning fix. Looking forward to seeing the warning disappear in some future upgrade of our Jenkins instance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24479) The vSphere cloud will not allow this slave to start at this time.
Title: Message Title Artur Szostak commented on JENKINS-24479 Re: The vSphere cloud will not allow this slave to start at this time. We are using Jenkins 2.121.3 and vsphere-cloud-plugin 2.18. Getting "ERROR: The vSphere cloud will not allow this slave to start at this time." randomly for our Jenkins + vSphere cloud setup. Have a single vSphere cloud configured with about 10 different templates (configured automatically with a Groovy script), each template is limited to a max of 50 instances. The total instance count for the cloud is limited to 100. We see between 5% - 30% VMs do not start properly with the above error message in the log. I would say this shows classic symptoms of a race condition in the plugin / Jenkins code. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51758) Register new vsphere template under vsphere plugin via groovy/jenkinsfile
Title: Message Title
Artur Szostak commented on JENKINS-51758
Re: Register new vsphere template under vsphere plugin via groovy/jenkinsfile
You can do this in a groovy script run within the Jenkins master. You will need to write the code to create new vSphereCloudSlaveTemplate objects and add them to the correct cloud configuration object in the Jenkins instance, e.g. the following pseudo code:
def tmpl = new vSphereCloudSlaveTemplate( ... /* Many parameters to fill, see the source code docs. */ ... )
def clouds = Jenkins.getInstance().clouds
def cloud = findVsphereCloudObject(clouds)
if (cloud.getTemplates().size() == 0) {
// If the cloud had no templates set, then we have to recreate the cloud
// with the new template. This has to be done this way because we
// otherwise get a Java exception if adding to an empty list returned by
// getTemplates().
def cloud_name = 'some_cloud_name'
def max_build_nodes = cloud.getMaxOnlineSlaves()
def max_instances = cloud.getInstanceCap()
def con = cloud.getVsConnectionConfig()
clouds.remove(cloud)
cloud = new vSphereCloud(con, cloud_name, max_build_nodes, max_instances, [tmpl])
clouds.add(cloud)
} else {
cloud.getTemplates().add(tmpl)
}
jenkins.save()
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51758) Register new vsphere template under vsphere plugin via groovy/jenkinsfile
Title: Message Title
Artur Szostak edited a comment on JENKINS-51758
Re: Register new vsphere template under vsphere plugin via groovy/jenkinsfile
You can do this in a groovy script run within the Jenkins master. You will need to write the code to create new vSphereCloudSlaveTemplate objects and add them to the correct cloud configuration object in the Jenkins instance, e.g. the following pseudo code:{code}def tmpl = new vSphereCloudSlaveTemplate( ... /* Many parameters to fill, see the source code docs. */ ... )def clouds = Jenkins.getInstance().cloudsdef cloud = findVsphereCloudObject(clouds)if (cloud.getTemplates().size() == 0) {// If the cloud had no templates set, then we have to recreate the cloud// with the new template. This has to be done this way because we// otherwise get a Java exception if adding to an empty list returned by// getTemplates().def cloud_name = 'some_cloud_name'def max_build_nodes = cloud.getMaxOnlineSlaves()def max_instances = cloud.getInstanceCap()def con = cloud.getVsConnectionConfig()clouds.remove(cloud)cloud = new vSphereCloud(con, cloud_name, max_build_nodes, max_instances, [tmpl])clouds.add(cloud)} else {cloud.getTemplates().add(tmpl)} jenkins Jenkins . getInstance(). save(){code}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53086) vSphere plugin fails to start a VM for pipeline jobs that request a node with no specific label
Title: Message Title Artur Szostak created an issue Jenkins / JENKINS-53086 vSphere plugin fails to start a VM for pipeline jobs that request a node with no specific label Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2018-08-17 08:35 Environment: CentOS 7 Java 8 Priority: Major Reporter: Artur Szostak When a pipeline job requests a node with no label specified a null appears to be passed to the vSphere plugin. One can argue if a null is the appropriate value. However for sure the plugin should be starting any VM template that is configured, because an empty label should match any VM. See the following error message I see in the logs instead: WARNING: provision(null,1): Failed. java.lang.NullPointerException at org.jenkinsci.plugins.vSphereCloud.provision(vSphereCloud.java:334) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:807) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at
[JIRA] (JENKINS-50842) command-launcher terminates the process
Title: Message Title Artur Szostak commented on JENKINS-50842 Re: command-launcher terminates the process As a workaround you can spawn your own watchdog daemon that will not be killed when Jenkins foolishly puts a bullet in your process. You have to make sure the watchdog daemon is not part of the same process group, detach from stdin/stdout etc. Be warned, it will take an annoying period of time to debug this approach and get all the failure modes handled properly. But I have managed to implement this and make it work a while back. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23560) Slave hung in startup phase with missing logging in the GUI
Title: Message Title Artur Szostak closed an issue as Fixed ssh-slaves plugin version 1.10 has been running for over a year on our Jenkins instance with over 50 build slaves. This problem has not occurred since the plugin was updated. Thus I confirm that the fix worked and am closing the ticket. Jenkins / JENKINS-23560 Slave hung in startup phase with missing logging in the GUI Change By: Artur Szostak Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Title: Message Title Artur Szostak closed an issue as Fixed Jenkins / JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Change By: Artur Szostak Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Title: Message Title Artur Szostak resolved as Fixed OK, everyone. I created this ticket and I confirmed that the from v1.4 the plugin fixes the originally reported problem. Reading through the comments again, there is no strong evidence that whatever anyone else is seeing now has anything to do with the original bug post. This ticket is done. If you do not see the same stack trace as in the original post then please create a new ticket. Mixing different problems into the same ticket does not help anyone. Cheers. Jenkins / JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Change By: Artur Szostak Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] [template-workflows-plugin] (JENKINS-17699) Template jobs do not adhere to job permissions
Title: Message Title Artur Szostak commented on JENKINS-17699 Re: Template jobs do not adhere to job permissions No, I did not find a workaround. Honestly, I stopped using that plugin. Sorry to say that it is rather limited and not very good. In the end I went for using http://docs.openstack.org/infra/jenkins-job-builder/. It has its own set of problems, but is much more functional. You could also try pay for the commercial version of Jenkins which comes with a templating facility. However, I do not know how good that is. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copy-project-link-plugin] (JENKINS-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Title: Message Title Artur Szostak closed an issue as Fixed Can confirm the upgrade from v1.1 to v1.4 works. (Jenkins version at time of upgrade was 1.565.1) Jenkins / JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Change By: Artur Szostak Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21217) projects fully loaded on start causing slow startup
Artur Szostak commented on JENKINS-21217 projects fully loaded on start causing slow startup After an upgrade of Jenkins v1.565.1 my startup time dropped down to about 30-40 min from the original 2 hours. However, the startup is still long. In my case it is definitely due to the matrix plugin. After a few exchanges on the mailing lists the conclusion is that this is an I/O bottleneck due to Jenkins being sensitive to I/O operation rate. Others have mention a significant improvement when moving the build logs to solid state disks that can perform orders of magnitude more I/O ops per second. I think to fix this situation one would need to rethink how Jenkins deals with I/O down to the core. 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-23560) Slave hung in startup phase with missing logging in the GUI
Artur Szostak commented on JENKINS-23560 Slave hung in startup phase with missing logging in the GUI This is starting to become a blocker. It is happening regularly (2-3 times a week) and forcing a restart of Jenkins. I have updated to Jenkins version 1.554.3 with no improvement. I think I managed to catch the problem at a slightly earlier moment this time also. After a restart of Jenkins, a number of hours later a job was stuck on one of the build slaves and was aborted. When logging into the machine there was no sign of the Jenkins slave Java process running. However, in the Jenkins GUI the slave appeared to be running or at least starting. About 10 minutes before the stuck job another job ran and failed with the build log following messages: Started by upstream project "admin-validate-slave-configs" build number 456 originally caused by: Started by timer EnvInject - Loading node environment variables. EnvInject - ERROR - SEVERE ERROR occurs: java.lang.InterruptedException Deleting project workspace... Collecting metadata... Metadata collection done. Finished: FAILURE The thread stack dumps that I believe are relevant: "Channel reader thread: ma016213" Id=23008 Group=main WAITING on com.trilead.ssh2.channel.Channel@1d6e8511 at java.lang.Object.wait(Native Method) waiting on com.trilead.ssh2.channel.Channel@1d6e8511 at java.lang.Object.wait(Object.java:503) at com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) at com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:946) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:77) 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.defaultReadFields(ObjectInputStream.java:1990) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1706) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1344) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990) at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:500) at java.lang.Throwable.readObject(Throwable.java:914) at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1893) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) "Executor #0 for ma016213 : executing admin-validate-slave-configs » ma016213 #456 / waiting for hudson.remoting.Channel@21fb7f0a:ma016213" Id=254 Group=main TIMED_WAITING on hudson.remoting.UserRequest@e493bde at java.lang.Object.wait(Native Method) waiting on hudson.remoting.UserRequest@e493bde at
[JIRA] [core] (JENKINS-23560) Slave hung in startup phase with missing logging in the GUI
Artur Szostak commented on JENKINS-23560 Slave hung in startup phase with missing logging in the GUI Additional thread dumps that could be relevant to the previous comment: "Computer.threadPoolForRemoting 144" Id=22726 Group=main WAITING on java.util.concurrent.FutureTask@497a56f6 at sun.misc.Unsafe.park(Native Method) waiting on java.util.concurrent.FutureTask@497a56f6 at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:425) at java.util.concurrent.FutureTask.get(FutureTask.java:187) at java.util.concurrent.AbstractExecutorService.invokeAll(AbstractExecutorService.java:243) at java.util.concurrent.Executors$DelegatedExecutorService.invokeAll(Executors.java:648) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:691) locked hudson.plugins.sshslaves.SSHLauncher@f4631f7 at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Number of locked synchronizers = 1 java.util.concurrent.ThreadPoolExecutor$Worker@451047f5 "Computer.threadPoolForRemoting 744" Id=38276 Group=main BLOCKED on hudson.plugins.sshslaves.SSHLauncher@f4631f7 owned by "Computer.threadPoolForRemoting 144" Id=22726 at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1152) blocked on hudson.plugins.sshslaves.SSHLauncher@f4631f7 at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:547) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Number of locked synchronizers = 1 java.util.concurrent.ThreadPoolExecutor$Worker@3bd8d3ab "Computer.threadPoolForRemoting 823" Id=40700 Group=main BLOCKED on hudson.plugins.sshslaves.SSHLauncher@f4631f7 owned by "Computer.threadPoolForRemoting 144" Id=22726 at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:639) blocked on hudson.plugins.sshslaves.SSHLauncher@f4631f7 at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Number of locked synchronizers = 1 java.util.concurrent.ThreadPoolExecutor$Worker@5f27ca48 "Computer.threadPoolForRemoting 849" Id=41501 Group=main BLOCKED on hudson.plugins.sshslaves.SSHLauncher@f4631f7 owned by "Computer.threadPoolForRemoting 144" Id=22726 at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:639) blocked on hudson.plugins.sshslaves.SSHLauncher@f4631f7 at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Number of locked synchronizers = 1 java.util.concurrent.ThreadPoolExecutor$Worker@36a88ffe 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
[JIRA] [core] (JENKINS-23560) Slave hung in startup phase with missing logging in the GUI
Artur Szostak commented on JENKINS-23560 Slave hung in startup phase with missing logging in the GUI Oh, and the slave is configured with the following settings: Usage = Utilize this slave as much as possible Launch method = Launch slave agents on Unix machines via SSH Port = 22 JVM Options = -Djava.awt.headless=true Availability = Take this slave on-line when in demand and off-line when idle In demand delay = 0 Idel delay = 60 Environment variables is checked with things like ARCH, BUILD_TYPE, CCACHE_DIR, OS, etc set. Prepare job environment is also checked to setup PATH and LD_LIBRARY_PATH (Can't seem to set these two with just "Environment variables" settings) Configured credentials to login to the build account. All other options are default/empty. 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-23560) Slave hung in startup phase with missing logging in the GUI
Artur Szostak commented on JENKINS-23560 Slave hung in startup phase with missing logging in the GUI I think I should adjust one comment in my description: "It seems like Jenkins is hung in the build start phase." = "It seems like Jenkins is hung in the slave start phase." Anyway, nothing interesting in the logs on the slave side since the Jenkins slave JAR never gets started. I dont see any process related to Jenkins on the slave machine. I did notice a similar situation that I was able to dig into a little more. This was related to a physically hung machine that needed a reboot while a Jenkins slave instance was running. It could be related. I sent an email to the developer list to see if anyone could give credibility to my hypothesis. but unfortunately got no reply. I reproduce the email test I sent below with the information I gathered. Perhaps its related since the symptoms were essentially the same. _ Hi, I am trying to debug the following symptom: Jenkins started a slave. The slave died (machine hung, never had a chance to communicate back to master). Jenkins tries to restart it, but is not able to. When trying to restart the slave manually nothing happens. The slave logs are and remain empty with the spinning icon just running. I had a look at the thread dump and saw a number of threads blocked and waiting for the following thread: "Computer.threadPoolForRemoting 14515" Id=577044 Group=main WAITING on com.trilead.ssh2.channel.Channel@76dd2191 at java.lang.Object.wait(Native Method) waiting on com.trilead.ssh2.channel.Channel@76dd2191 at java.lang.Object.wait(Object.java:503) at com.trilead.ssh2.channel.ChannelManager.waitUntilChannelOpen(ChannelManager.java:109) at com.trilead.ssh2.channel.ChannelManager.openSessionChannel(ChannelManager.java:583) at com.trilead.ssh2.Session.init(Session.java:41) at com.trilead.ssh2.Connection.openSession(Connection.java:1129) locked com.trilead.ssh2.Connection@1e553bf at com.trilead.ssh2.SFTPv3Client.init(SFTPv3Client.java:99) at com.trilead.ssh2.SFTPv3Client.init(SFTPv3Client.java:119) at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1160) locked hudson.plugins.sshslaves.SSHLauncher@3c884383 at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:547) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Number of locked synchronizers = 1 java.util.concurrent.ThreadPoolExecutor$Worker@638f4d22 Looking at the code for hudson.plugins.sshslaves.SSHLauncher.java in afterDisconnect I see no hint of code that deals with timeouts. Looking further up the stack I wonder that happens when openSessionChannel tries to make a connection to the slave but it dies on the other side. The code does not look like it times out. If this is the case and whatever is on the other side of the channel that is supposed to respond is also dead, it would seem to me that waitUntilChannelOpen will never return and hang forever. Thus, the hudson.plugins.sshslaves.SSHLauncher lock will never be released and other threads wanting this lock will block forever. i.e. effective deadlock. Can anyone confirm or refute my logic here? This certainly seems it could explain my symptoms. Kind regards. Artur 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-23560) Slave hung in startup phase with missing logging in the GUI
Artur Szostak created JENKINS-23560 Slave hung in startup phase with missing logging in the GUI Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: plugin_list.txt, thread_dump.txt Components: core, ssh-slaves Created: 24/Jun/14 6:24 PM Description: I noticed today a number of jobs stuck in Jenkins. They were waiting for a slave machine to automatically start. However, it was not. It was indicating that the slave was starting but there was nothing in the logs. A manual restart had no effect. I decided to put Jenkins in shutdown mode, stop all running jobs, flush the queues and stop all build slaves. Once there was absolutely no activity on Jenkins I tried to manually start the stuck slave. However, nothing happened again. It seems like Jenkins is hung in the build start phase. I attach my list of plugins and thread dump. Can anyone confirm Jenkins is hung based on the thread dump? Any known workarounds? Environment: Jenkins 1.554.2 Project: Jenkins Priority: Major Reporter: Artur Szostak 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-22261) Link for Manage Old Data fails with a Content Encoding Error error in the browser.
Artur Szostak closed JENKINS-22261 as Fixed Link for Manage Old Data fails with a Content Encoding Error error in the browser. Testing with Jenkins 1.563 no longer produces the symptoms. Change By: Artur Szostak (21/May/14 8:54 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] [copy-project-link] (JENKINS-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Artur Szostak created JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Issue Type: Bug Assignee: Unassigned Components: copy-project-link Created: 26/Mar/14 2:48 PM Description: After upgrading the plugin from version v1.1 to v1.2 and restarting the jenkins instance I no longer see the copy link in the interface and find the following error in the logs: WARNING: Failed to load hudson.plugins.copyProjectLink.CopyFolderActionFactory java.lang.InstantiationException: /opt/jenkins/data/plugins/copy-project-link/WEB-INF/lib/classes.jar might need to be rebuilt: java.lang.ClassNotFoundException: hudson.plugins.copyProjectLink.CopyFolderActionFactory at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:504) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:230) at com.google.inject.spi.Elements.getElements(Elements.java:103) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:230) at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:336) at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2154) at hudson.PluginManager.dynamicLoad(PluginManager.java:431) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1313) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1116) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:701) Caused by: java.lang.ClassNotFoundException: hudson.plugins.copyProjectLink.CopyFolderActionFactory at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:985) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) Environment: Jenkins v1.532.2 Project: Jenkins Priority: Major Reporter: Artur Szostak 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-21217) projects fully loaded on start causing slow startup
Artur Szostak commented on JENKINS-21217 projects fully loaded on start causing slow startup I can confirm the same problem and same kind of stack traces (also with matrix projects) for Jenkins v1.532.2. In my case it takes up to 2 hours to startup. 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-22261) Link for Manage Old Data fails with a Content Encoding Error error in the browser.
Artur Szostak created JENKINS-22261 Link for Manage Old Data fails with a Content Encoding Error error in the browser. Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Mar/14 4:44 PM Description: After an upgrade of Jenkins from 1.518 to 1.532.2 and updating all the plugins I get a notification in the management panel that there is data stored in an older format and/or unreadable data. However, when I click on the "Manage Old Data" link to try and resolve this the web browser indicates that the page is not loadable because of a "Content Encoding Error". In the Jenkins logs I find the stack trace indicated below: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/diska/home/jenkins/install/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.2.jar!/hudson/diagnosis/OldDataMonitor/manage.jelly:35:59: j:forEach java.util.ConcurrentModificationException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) 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 winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [core] (JENKINS-22261) Link for Manage Old Data fails with a Content Encoding Error error in the browser.
Artur Szostak
commented on JENKINS-22261
Link for Manage Old Data fails with a Content Encoding Error error in the browser.
I paste the following information given in an email from Daniel Beck. This could help those who need to work around the problem.
__
To view the problems, try the following in the Script Console:
===
def d = :
d.putAll(Jenkins.instance.getAdministrativeMonitor("OldData").data)
d.each { obj, v -
println obj.class.getName()
println obj.fullName?:obj.fullDisplayName?:obj.displayName?:obj.name
println v
println v.extra
println ''
}
return
===
Sample output:
===
hudson.model.User
Daniel Beck
CannotResolveClassException: hudson.plugins.favorite.user.FavoriteUserProperty, CannotResolveClassException: hudson.plugins.favorite.filter.FavoriteFilter
===
Most of the entries will have an empty line (from 'println v'), this is where a version incompatibility would show up.
Never had that, no idea how it works. If you just disabled a bunch of plugins (like Favorite plugin in the example), you won't have that.
To scrub, try to access http://yourjenkins/administrativeMonitor/OldData/discard manually by editing the URL.
This is what 'Discard Unreadable Data' does, it doesn't even @RequirePOST.
__
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-22261) Link for Manage Old Data fails with a Content Encoding Error error in the browser.
Artur Szostak
edited a comment on JENKINS-22261
Link for Manage Old Data fails with a Content Encoding Error error in the browser.
I paste the following information given in an email from Daniel Beck. This could help those who need to work around the problem.
__
To view the problems, try the following in the Script Console:
===
def d = :
d.putAll(Jenkins.instance.getAdministrativeMonitor("OldData").data)
d.each { obj, v -
println obj.class.getName()
println obj.fullName?:obj.fullDisplayName?:obj.displayName?:obj.name
println v
println v.extra
println ''
}
return
===
Sample output:
===
hudson.model.User
Daniel Beck
CannotResolveClassException: hudson.plugins.favorite.user.FavoriteUserProperty, CannotResolveClassException: hudson.plugins.favorite.filter.FavoriteFilter
===
Most of the entries will have an empty line (from 'println v'), this is where a version incompatibility would show up.
Never had that, no idea how it works. If you just disabled a bunch of plugins (like Favorite plugin in the example), you won't have that.
To scrub, try to access http://yourjenkins/administrativeMonitor/OldData/discard manually by editing the URL.
This is what 'Discard Unreadable Data' does, it doesn't even @RequirePOST.
__
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-5539) Extend Project-based Matrix Authorization Strategy with SCM Configuration option
Artur Szostak commented on JENKINS-5539 Extend Project-based Matrix Authorization Strategy with SCM Configuration option Any progress on a proper solution? 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/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Artur Szostak closed JENKINS-17468 as Fixed NullPointerException in URLTrigger.getFTPResponse during startup Now works with fix applied and explicit setting of user to anonymous. Change By: Artur Szostak (29/Apr/13 1:14 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/groups/opt_out.
[JIRA] [template-workflows] (JENKINS-17699) Template jobs do not adhere to job permissions
Artur Szostak created JENKINS-17699 Template jobs do not adhere to job permissions Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: template-workflows Created: 22/Apr/13 12:57 PM Description: When the "Project-based Matrix Authorization Strategy" is enabled in the global Jenkins configuration and a user Alice does not have "Administer" permissions set under the "Overall" heading, the following is observed: When user Alice creates a new "Template Workflow Job" they are not subsequently able to actually create nor delete any workflows, even though they have modification and configuration permissions for individual jobs. It looks like template workflow jobs do not adhere to job security permissions correctly. This makes the plugin effectively useless in a fully fledged multi user environment. Environment: Jenkins 1.480.3 running on Scientific Linux 5.5 Java runtime 1.6.0_20-b02 Project: Jenkins Priority: Major Reporter: Artur Szostak 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/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Artur Szostak commented on JENKINS-17566 Severe polling error when using script trigger Scripttrigger version is 0.22 EnvInject version is 0.43 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/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Artur Szostak reopened JENKINS-17468 NullPointerException in URLTrigger.getFTPResponse during startup The error message has disappeared but FTP URLs still do not function correctly. Have a look at the attached FTPtestJob.tar.gz job configuration. I expect a build to be triggered at least once, but the URL trigger log always indicates "no change". Change By: Artur Szostak (10/Apr/13 11:21 AM) Resolution: Fixed 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/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Artur Szostak updated JENKINS-17468 NullPointerException in URLTrigger.getFTPResponse during startup Example job showing malfunction. The job should be triggered to build at least once. Change By: Artur Szostak (10/Apr/13 11:22 AM) Attachment: FTPtestJob.tar.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/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Artur Szostak edited a comment on JENKINS-17468 NullPointerException in URLTrigger.getFTPResponse during startup Added example job showing malfunction. The job should be triggered to build at least once. 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/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Artur Szostak created JENKINS-17566 Severe polling error when using script trigger Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: TestJob.tar.gz Components: scripttrigger Created: 10/Apr/13 4:00 PM Description: I find the following in the script trigger logs for the attached test job configuration: ERROR - SEVERE - Polling error null The error disappears when the following tags are removed from the file TestJob/builds/2013-04-10_12-34-47/build.xml: org.jenkinsci.plugins.envinject.EnvInjectPluginAction build class="build" reference="../../.."/ /org.jenkinsci.plugins.envinject.EnvInjectPluginAction Environment: Scientific Linux 5.5 and Ubuntu 10.10 Arch: x86_64 Jenkins 1.480.3 running in standalone with Winstone Project: Jenkins Priority: Major Reporter: Artur Szostak 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/groups/opt_out.
[JIRA] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
Artur Szostak commented on JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option I tried on a different installation of Jenkins (1.480.3 on Ubuntu) and have the same problem. Looking at the file timestamps returned by the FTP server, they do not change. 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/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Artur Szostak created JENKINS-17468 NullPointerException in URLTrigger.getFTPResponse during startup Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 04/Apr/13 9:49 AM Description: The trigger mechanism does not seem to work for FTP URLs. I get the following information shown in the URLTrigger log: URLTrigger - Poll with a URL Polling started on Apr 4, 2013 9:44:47 AM Polling for the job testjob Looking nodes where the poll can be run. Looking for a node to the restricted label master. Polling on master. Failed to poll URL: java.lang.NullPointerException Skipping URLTrigger initialization. Waiting next schedule Polling complete. Took 8 ms. No changes. I also find the following log messages in the jenkins logs: SEVERE: Severe error on trigger startup null java.lang.NullPointerException at org.jenkinsci.plugins.urltrigger.URLTrigger.getFTPResponse(URLTrigger.java:356) at org.jenkinsci.plugins.urltrigger.URLTrigger.start(URLTrigger.java:299) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:97) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) at hudson.model.AbstractProject.submit(AbstractProject.java:1803) at hudson.matrix.MatrixProject.submit(MatrixProject.java:790) at hudson.model.Job.doConfigSubmit(Job.java:993) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:699) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
Artur Szostak created JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: urlscm Created: 04/Apr/13 5:40 PM Description: The URL SCM always triggers a build when using the SCP polling option. The Polling Log only contains the following: Started on Apr 4, 2013 5:32:41 PM Done. Took 1 ms Changes found Thus the URL seems to always be marked by the URL plugin as changed, even when no changes have been made. Environment: Scientific Linux 5.5 Architecture x86_64 Running Jenkins in standalone mode with Winstone Project: Jenkins Priority: Major Reporter: Artur Szostak 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/groups/opt_out.
[JIRA] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
Artur Szostak commented on JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option This happens even when I use HTTP URLs to Jenkins' workspaces, HTTP URLs for lighttpd or FTP URLs for vsftpd. Thats 3 different servers. Seems unlikely that its due to the server. Can you suggest a conclusive way to 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/groups/opt_out.
