[JIRA] (JENKINS-17116) gracefull job termination
Title: Message Title Matthew Bells commented on JENKINS-17116 Re: gracefull job termination I'm also have problems with this. In particular, our nodes are running Ubuntu 14.04. We are using Jenkins to run some tests as part of the build. There are a few steps where interruption will cause communication failures, leaked temporary files gigabytes in size, and locks that are not undone. Orphaned process is very bad as well, since this could lead to a new build starting communication on the same channel prior to the previous one terminating. Like Martin d'Anjou indicated, we would need a timeout parameter, since the allowed timeout for SIGTERM may be about 300sec, which is probably a lot longer than someone implementing this fix may anticipate. 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] [core] (JENKINS-25652) Relaunch slave agent fails after node changes IP address
Matthew Bells created JENKINS-25652 Relaunch slave agent fails after node changes IP address Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Nov/14 7:33 PM Description: Steps to reproduce Setup Jenkins (computer "jenkins") with a node "foo" on separate computers. Browse to the page: http://jenkins:8080/computer/foo/ Ensure the node is running and Idle. Turn off the node foo computer (without first bringing the Jenkins node offline). Restart the node and have it reconnect to the network with DHCP. Make sure its IP address changed. Refresh the page, note the node is offline. The state may be "This node is being launched.", but the log is empty. Press the "Relaunch slave agent" button. This takes you to the log, which remains empty. Other info The stack trace from Jenkins shows: "Channel reader thread: foo" Id=360 Group=main WAITING on com.trilead.ssh2.channel.Channel@66a77259 at java.lang.Object.wait(Native Method) - waiting on com.trilead.ssh2.channel.Channel@66a77259 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.SFTPv3Client.readBytes(SFTPv3Client.java:215) at com.trilead.ssh2.SFTPv3Client.receiveMessage(SFTPv3Client.java:240) at com.trilead.ssh2.SFTPv3Client.init(SFTPv3Client.java:864) at com.trilead.ssh2.SFTPv3Client.(SFTPv3Client.java:108) at com.trilead.ssh2.SFTPv3Client.(SFTPv3Client.java:119) at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1160) - locked hudson.plugins.sshslaves.SSHLauncher@1cb4fc57 at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:443) at hudson.remoting.Channel.terminate(Channel.java:799) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Workaround Configure the node, add a dummy value (e.g. "relaunch-1" to the description). Save the new configuration. It will now launch. There may be a way to script this too... Environment: Jenkins ver. 1.554.3 Ubuntu 14.04 Project: Jenkins Labels: slave Priority: Minor Reporter: Matthew Bells 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] [nodelabelparameter-plugin] (JENKINS-25622) NodeLabelParameter plugin is missing value parameter for queue jobs
Matthew Bells updated JENKINS-25622 NodeLabelParameter plugin is missing value parameter for queue jobs Change By: Matthew Bells (14/Nov/14 5:50 PM) Summary: NodeLabelParameter plugin is missing value parameter for queue jobs 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] [nodelabelparameter-plugin] (JENKINS-25622) NodeLabelParameter plugin
Matthew Bells
created JENKINS-25622
NodeLabelParameter plugin
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Attachments:
Screenshot-Jenkins_NodeLabel_build_params.png, Screenshot-Jenkins_NodeLabel_build_queue.png
Components:
nodelabelparameter-plugin
Created:
14/Nov/14 5:48 PM
Description:
This plugin will break many APIs and other plugins when there is a job in the queue.
The queue parameter is missing the 'value' entry that is sent from Jenkins through JSON. See output after build.actions below.
- Steps to reproduce
Install Jenkins, install NodeLabelPlugin. (See environment for exact version info)
Create a job that uses the NodeLabelPlugin.
Build with Parameters, and fill in some some parameters (see screenshot).
Take a look at the queue (see screenshot).
Install Python jenkinsapi (using 0.2.16-2):
apt-get install python-jenkinsapi
Type in the following commands:
>>> import jenkinsapi
>>> jenkinsurl='http://localhost:8080'
>>> jobname='MyJob'
>>> jenkins = jenkinsapi.jenkins.Jenkins(jenkinsurl)
>>> queue=jenkins.get_queue()
>>> queued_builds = queue.get_queue_items_for_job(jobname)
>>> build=queued_builds[0]
>>> build.actions
[{'parameters': [{'name': 'job_id', 'value': '0'}, {'name': 'node_label'}, {'name': 'content_id', 'value': ''}, {'name': 'config_id', 'value': ''}]}, {'causes': [{'userName': 'Matt', 'userId': 'mbells', 'shortDescription': 'Started by user Matt'}]}]
>>> for b in queued_builds:
...print (b, b.get_parameters())
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python2.7/dist-packages/jenkinsapi/queue.py", line 97, in get_parameters
return dict([(x['name'], x['value']) for x in parameters])
Environment:
Jenkins ver. 1.554.3
nodelabelparameter plugin ver. 1.5.1
Host OS: Ubuntu 14.04
To get Python api:
Project:
Jenkins
Labels:
nodelabelparameter
Priority:
Major
Reporter:
Matthew Bells
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] (JENKINS-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication
Matthew Bells created JENKINS-24958 UsernameNotFoundException when ActiveDirectory used for API and token authentication Issue Type: Bug Assignee: Unassigned Components: active-directory Created: 01/Oct/14 10:11 PM Description: When a valid username and api-token are used from the Jenkins Python API, the Jenkins server (version 1.582) returns an exception (see stack trace below). Note: When active-directory is not used, the Jenkins API authentication works (tested on Jenkins 1.554.2). - exception stack trace javax.servlet.ServletException: org.acegisecurity.userdetails.UsernameNotFoundException: Authentication was successful but cannot locate the user information for ci_dev_test at jenkins.security.BasicHeaderApiTokenAuthenticator.authenticate(BasicHeaderApiTokenAuthenticator.java:36) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:72) 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:46) 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:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: org.acegisecurity.userdetails.UsernameNotFoundException: Authentication was successful but cannot locate the user information for ci_dev_test at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:273) at hudson.plugins.active_directory.ActiveDirectoryUn
