[JIRA] [p4-plugin] (JENKINS-26956) perforce timeout option in the plugin
arazauci created JENKINS-26956 perforce timeout option in the plugin Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 13/Feb/15 4:22 PM Description: sometimes, we that our jobs hangs forever because there are some communication issues with perforce. It could be networking issues, p4 servers issues, etc. It would be very helpful to have some timeout option in the P4 SCM section so that the job can be exit out with abort state Project: Jenkins Priority: Major Reporter: arazauci 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-26851) Sometimes EC2 slaves come online with no labels
arazauci created JENKINS-26851 Sometimes EC2 slaves come online with no labels Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 08/Feb/15 10:32 AM Description: I am using only one ami in my configuration. I am spinning up 250+ slaves at any given time. I notice that under high load, about 5% of the EC2 slaves come online with no label. All my jobs are tied to label so a slave without label is a waste of resource and money on AWS. Environment: plugin version: 1.25 Project: Jenkins Priority: Major Reporter: arazauci 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-26852) Better exception handling when terminating EC2 slave
arazauci created JENKINS-26852 Better exception handling when terminating EC2 slave Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 08/Feb/15 10:39 AM Description: If using the 'idle termination time' setting, jenkins throws the following error in /var/log/jenkins/jenkins.log when the instance is terminated Feb 08, 2015 2:32:12 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Ubuntu-UI-Slave (i-1fbbf6ee) 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(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source) at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInputStream.init(Unknown Source) at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) If are you looking at logs for other issues, this ends up creating a lot of noise and makes debugging quite difficult. Environment: plugin version: 1.25 Project: Jenkins Priority: Major Reporter: arazauci 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] [digitalocean-plugin] (JENKINS-26352) Cannot create Jenkins slaves
arazauci
created JENKINS-26352
Cannot create Jenkins slaves
Issue Type:
Bug
Assignee:
Unassigned
Components:
digitalocean-plugin
Created:
09/Jan/15 9:30 AM
Description:
The plugin is not able to create jenkins slave. The jenkins logs show the following exception message (hidding some of my details)
com.myjeeva.digitalocean.exception.RequestUnsuccessfulException: DigitalOcean API request unsuccessful, possible reason colud be incorrect values https://api.digitalocean.com/droplets/new/?client_id=xxapi_key=name=jenkins_ea8482b1-665c-4d5b-805d-a5bbe35c50c3region_id=3ssh_key_ids=xxximage_id=xxxsize_id=63.
DigitalOcean support says that the plugin has invalid values for host name
As for the API call itself, it appears that your hostname in the call contains invalid characters:
{"status":"ERROR","error_message":"Name Only valid hostname characters are allowed. (a-z, A-Z, 0-9, . and -)","message":"Name Only valid hostname characters are allowed. (a-z, A-Z, 0-9, . and -)"}
Please try again using another hostname.
Project:
Jenkins
Priority:
Blocker
Reporter:
arazauci
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-25385) Jenkins EC2 plugin is not able to launch Windows Slaves in AWS
arazauci
commented on JENKINS-25385
Jenkins EC2 plugin is not able to launch Windows Slaves in AWS
@kohsuke
I can manually telnet into the windows ec2 instance. However, Jenkins cannot seem to add it as a slave. I see the following error in the winrm logger
Request:
POST http://xxx.xxx.xx.xx:5985/wsman
?xml version="1.0" encoding="UTF-8"?
env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:rsp="http://schemas.microsoft.com/wbem/wsman/1/windows/shell" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns="http://schemas.microsoft.com/wbem/wsman/1/wsman.xsd"env:Headera:Tohttp://xxx.xxx.xx.xx:5985/wsman/a:Toa:ReplyToa:Address mustUnderstand="true"http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/a:Address/a:ReplyTow:MaxEnvelopeSize mustUnderstand="true"153600/w:MaxEnvelopeSizea:MessageIDuuid:AC60C672-A7F9-4283-B161-17B5A37A9F63/a:MessageIDw:Locale mustUnderstand="false" xml:lang="en-US"/p:DataLocale mustUnderstand="false" xml:lang="en-US"/w:OperationTimeoutPT60S/w:OperationTimeouta:Action mustUnderstand="true"http://schemas.xmlsoap.org/ws/2004/09/transfer/Create/a:Actionw:ResourceURI mustUnderstand="true"http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd/w:ResourceURIw:OptionSetw:Option Name="WINRS_NOPROFILE"FALSE/w:Optionw:Option Name="WINRS_CODEPAGE"437/w:Option/w:OptionSet/env:Headerenv:Bodyrsp:Shellrsp:InputStreamsstdin/rsp:InputStreamsrsp:OutputStreamsstdout stderr/rsp:OutputStreams/rsp:Shell/env:Body/env:Envelope
Dec 05, 2014 8:46:40 PM SEVERE hudson.plugins.ec2.win.winrm.WinRMClient sendRequest
I/O Exception in HTTP POST
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:178)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at hudson.plugins.ec2.win.winrm.WinRMClient.sendRequest(WinRMClient.java:244)
at hudson.plugins.ec2.win.winrm.WinRMClient.sendRequest(WinRMClient.java:215)
at hudson.plugins.ec2.win.winrm.WinRMClient.openShell(WinRMClient.java:94)
at hudson.plugins.ec2.win.winrm.WinRM.ping(WinRM.java:29)
at hudson.plugins.ec2.win.WinConnection.ping(WinConnection.java:117)
at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:118)
at hudson.plugins.ec2.win.EC2WindowsLauncher.launch(EC2WindowsLauncher.java:29)
at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:101)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:241)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
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:745)
I did what Tomasz suggested
2) In WinRMClient.buildHTTPClient() I've removed unregister for AuthPolicy.SPNEGO and added unregister for KERBEROS, DIGEST and NTLM. Before this change there was exception about unsupported auth method, but it was getting lost somewhere in the code flow.
private DefaultHttpClient buildHTTPClient()
{
DefaultHttpClient httpclient = new DefaultHttpClient();
//httpclient.getAuthSchemes().unregister(AuthPolicy.SPNEGO);
httpclient.getAuthSchemes().unregister(AuthPolicy.KERBEROS);
httpclient.getAuthSchemes().unregister(AuthPolicy.DIGEST);
[JIRA] [ec2-plugin] (JENKINS-25837) ec2 plugins fails to launch new ec2 slaves if previous launch attempt had errors
arazauci created JENKINS-25837 ec2 plugins fails to launch new ec2 slaves if previous launch attempt had errors Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 30/Nov/14 9:27 PM Description: I notice that the ec2 plugin fails to launch new ec2 instances/slave if the previous one had some errors. I kicked off 100+ jobs all tied to the same ami and noticed that build queue did not move for hours. I could see that some of the nodes were in offline status with the following log just before slave Ubuntu-UI-Slave (i-4a38xxx) gets launched ... executing pre-launch scripts ... Node Ubuntu-UI-Slave (i-4a38xxx)(i-4a38xxx) is still stopping, waiting 5s Node Ubuntu-UI-Slave (i-4a38xxx)(i-4a38xxx) is still stopping, waiting 5s Node Ubuntu-UI-Slave (i-4a38xxx)(i-4a38xxx) is terminated or terminating, aborting launch These instances showed as 'terminated' on aws due to some error. The side effect was that jenkins was not able to provision any new slaves till the offline slaves were manually cleared/deleted. The plugin should be able to delete such instances automatically. Project: Jenkins Priority: Blocker Reporter: arazauci 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-25832) Launch multiple slaves in parallel for jobs with same node label
arazauci
created JENKINS-25832
Launch multiple slaves in parallel for jobs with same node label
Issue Type:
New Feature
Assignee:
Francis Upton
Components:
ec2-plugin
Created:
29/Nov/14 10:52 AM
Description:
I use build flow plugin to kick off 200+ jobs. Each of these jobs has the same label. During this scenario, 200+ jobs are queued up. The ec2 plugin seems to process one job at time and this is a painfully slow process.
It seems that the AWS JAVA SDK allows for launching multiple ec2 instances. Can the ec2 plugin detect the number of jobs with the same label in the queue, and then launch that many ec2 instances in parallel?
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/ec2/model/RunInstancesRequest.html#RunInstancesRequest%28java.lang.String,%20java.lang.Integer,%20java.lang.Integer%29
private EC2AbstractSlave provisionOndemand(TaskListener listener) throws AmazonClientException, IOException {
PrintStream logger = listener.getLogger();
AmazonEC2 ec2 = getParent().connect();
try {
String msg = "Launching " + ami + " for template " + description;
logger.println(msg);
LOGGER.info(msg);
KeyPair keyPair = getKeyPair(ec2);
RunInstancesRequest riRequest = new RunInstancesRequest(ami, 1, 1);
Project:
Jenkins
Priority:
Critical
Reporter:
arazauci
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-20742) EC2 plugin does not delete slaves that failed to start
arazauci commented on JENKINS-20742 EC2 plugin does not delete slaves that failed to start +1 $500 from for anyone who fixes this annoying 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-20742) EC2 plugin does not delete slaves that failed to start
arazauci edited a comment on JENKINS-20742 EC2 plugin does not delete slaves that failed to start +1 $500 from me for anyone who fixes this annoying 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-20742) EC2 plugin does not delete slaves that failed to start
arazauci edited a comment on JENKINS-20742 EC2 plugin does not delete slaves that failed to start +1 $500 from me for anyone who fixes this annoying issue https://freedomsponsors.org/issue/412/ec2-plugin-does-not-delete-slaves-that-failed-to-start?alert=SPONSOR#sponsors 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-8618) would like to use one instance per build
arazauci commented on JENKINS-8618 would like to use one instance per build +1 $500 for whoever fixes this https://freedomsponsors.org/issue/594/would-like-to-use-one-instance-per-build?alert=SPONSOR# 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] [jclouds-jenkins] (JENKINS-20921) Spinning up Windows instances via Jenkins+jclouds on OpenStack
arazauci commented on JENKINS-20921 Spinning up Windows instances via Jenkins+jclouds on OpenStack Hi Johan, This is a bit of a hack but will work. If you install cygwin/openssh in the base windows image, you should be able to use the jcloud or ec2 slave plugin to bring up windows slaves. Here is a good article on how to setup cygwin/openssh on windwos http://ist.uwaterloo.ca/~kscully/CygwinSSHD_W2K3.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
