[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title Jakub Bochenski commented on JENKINS-60288 Re: Installator is broken on Alpine That is not practical if you need to support builds using different JDK versions. Replying "don't use the plugin" to a bug request isn't very helpful. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.203279.1574785565000.21010.1588589520112%40Atlassian.JIRA.
[JIRA] (JENKINS-53579) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Jakub Bochenski edited a comment on JENKINS-53579 Re: Asynchronous cleanup not removing renamed workspace directories on slaves > I would expect Jenkins to establish a permission mapping between its euid and container's root. Can you suggest a technical solution to this. It would be useful but I see no robust and easy way to do it EDIT: my argument is same as https://issues.jenkins-ci.org/browse/JENKINS-53579?focusedCommentId=374472=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-374472 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.194059.1536919955000.12558.1587050280998%40Atlassian.JIRA.
[JIRA] (JENKINS-53579) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Jakub Bochenski commented on JENKINS-53579 Re: Asynchronous cleanup not removing renamed workspace directories on slaves > I would expect Jenkins to establish a permission mapping between its euid and container's root. Can you suggest a technical solution to this. It would be useful but I see no robust and easy way to do it Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.194059.1536919955000.12509.1587050160568%40Atlassian.JIRA.
[JIRA] (JENKINS-61853) Broken links to pull requests
Title: Message Title Jakub Bochenski commented on JENKINS-61853 Re: Broken links to pull requests This works for me with plugin version 1.17 and formatter 1.8 on Jenkins ver. 2.204.5 Without a way to reproduce there isn't much I can do to help. Maybe you are actually using a different markup formatter? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205716.158643871.8913.1586512920119%40Atlassian.JIRA.
[JIRA] (JENKINS-61853) Broken links to pull requests
Title: Message Title Jakub Bochenski closed an issue as Not A Defect This is caused by the upgraded markup formatter https://github.com/jenkinsci/antisamy-markup-formatter-plugin/releases/tag/antisamy-markup-formatter-2.0 Jenkins / JENKINS-61853 Broken links to pull requests Change By: Jakub Bochenski Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart I was able to resolve my problem in the same way as described in https://issues.jenkins-ci.org/browse/JENKINS-61370?focusedCommentId=388247=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-388247 The swallowing of useful error output is a big issue that should be improved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199745.1559315049000.8061.1586345460372%40Atlassian.JIRA.
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title Jakub Bochenski commented on JENKINS-39977 Re: Support for bitbucket-branch-source-plugin For reference it's in the api viewer at plugin/job-dsl/api-viewer/index.html#path/javaposse.jobdsl.dsl.jobs.OrganizationFolderJob.organizations-bitbucket Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.176601.1479914431000.3685.158520245%40Atlassian.JIRA.
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title Jakub Bochenski commented on JENKINS-39977 Re: Support for bitbucket-branch-source-plugin So where can I find a list of traits? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.176601.1479914431000.3671.1585666500400%40Atlassian.JIRA.
[JIRA] (JENKINS-61370) EC2 instances are terminated during launch
Title: Message Title Jakub Bochenski commented on JENKINS-61370 Re: EC2 instances are terminated during launch After changing to "SSH process" connection method I was able to see additional errors, which are swallowed by the Trilead java connector. Exception in thread "main" java.nio.file.AccessDeniedException: /opt/jenkins at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:211 Turns out that if you mount a block device in user-data script it can sometimes not be available when the master SSH connection comes in. The solution seems to be to use the init-script instead. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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
[JIRA] (JENKINS-61735) Add STAGE_NAME and NODE_NAME to environment parameters
Title: Message Title Jakub Bochenski commented on JENKINS-61735 Re: Add STAGE_NAME and NODE_NAME to environment parameters I'm not sure what do you mean by "parent build" in the context of Jenkins pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205563.1585515231000.2855.1585579680116%40Atlassian.JIRA.
[JIRA] (JENKINS-59110) Logstash plugin: Not working for Pipeline jobs when 'Enabled Globally'
Title: Message Title Jakub Bochenski commented on JENKINS-59110 Re: Logstash plugin: Not working for Pipeline jobs when 'Enabled Globally' Sorry, I don't have time to work on this ATM. If anybody want's to send a PR I'll be happy to assist and review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.201535.1566943198000.1272.1585315680165%40Atlassian.JIRA.
[JIRA] (JENKINS-61698) Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61698
Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime
Change By:
Jakub Bochenski
When trying to provision a new agent You can enter double comma into the plugin would start and then terminate an EC2 instance several times before succeeding in the end block devices field (E . I have no explanation for this behavior g . Might be related to JENKINS {{/dev/xvdb=:20,,/dev/sdf=snap - 61343Might 1234}} . It will be because accepted, later the plugin somehow allocates "2 computer(s)" even though the instance cap is 1. will fail with: {code}Mar 06 26 , 2020 3: 05 55 : 22 57 PM INFO SEVERE hudson. plugins triggers . ec2.EC2Cloud log SafeTimerTask run bootstrap() Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@1bbf83bc failed Mar 06, 2020 3 java.lang.ArrayIndexOutOfBoundsException : 05:22 PM INFO 1 at hudson.plugins.ec2. EC2Cloud logGetting keypair util . DeviceMappingParser . parse(DeviceMappingParser . Mar 06, 2020 3 java : 05:22 PM INFO 45) at hudson.plugins.ec2. EC2Cloud logUsing private key j4a-ec2-ssh-key SlaveTemplate.setupCustomDeviceMapping ( SHA-1 fingerprint a7 SlaveTemplate.java : b4:70:08:35:11:e3:cf:4b:f5:92:57:b8:02:7f:c6:8e:54:52:02 904 ) Mar 06, 2020 3:05:22 PM INFO at hudson.plugins.ec2. EC2Cloud logAuthenticating as adminMar 06, 2020 3 SlaveTemplate.setupBlockDeviceMappings(SlaveTemplate.java : 05:22 PM INFO 1070) at hudson. slaves plugins . NodeProvisioner lambda$update$6EC2 ( ec2 ) - ec2 (ami-028d96c69234f9d1a) provisioning successfully completed . We have now 2 computer SlaveTemplate.provisionOndemand ( s SlaveTemplate.java:607 ) Mar 06, 2020 3:05:22 PM INFO at hudson.plugins.ec2. EC2Cloud logConnecting to 10 SlaveTemplate . 20 provisionOndemand(SlaveTemplate . 4.41 on port 22, with timeout 1.Mar 06, 2020 3 java : 05:29 PM INFO 585) at hudson.plugins.ec2. EC2Cloud logConnected via SSH SlaveTemplate . Mar 06, 2020 3 provision(SlaveTemplate.java : 05:29 PM INFO 540) at hudson.plugins.ec2.EC2Cloud logconnect fresh as rootMar 06, 2020 3 .getNewOrExistingAvailableSlave(EC2Cloud.java : 05:29 PM INFO 589) at hudson.plugins.ec2.EC2Cloud logConnecting to 10 . 20 provision(EC2Cloud . 4 java:615) at com . 41 on port 22, with timeout 1 cloudbees . Mar 06, 2020 3:05:30 PM INFO hudson jenkins .plugins. ec2 amazonecs . EC2Cloud logConnected via SSH ECSProvisioningStrategy . Mar 06, 2020 3 apply(ECSProvisioningStrategy.java : 05:30 PM INFO 58) at hudson. plugins slaves . ec2 NodeProvisioner . EC2Cloud logCreating tmp directory update ( /tmp NodeProvisioner.java:332 ) if it does not exist Mar 06, 2020 3:05:30 PM INFO at hudson. plugins slaves . ec2 NodeProvisioner . EC2Cloud logVerifying: access$900(NodeProvisioner. java -fullversionMar 06, 2020 3 : 05:30 PM INFO 63) at hudson. plugins slaves . ec2 NodeProvisioner$NodeProvisionerInvoker . EC2Cloud logVerifying doRun(NodeProvisioner.java : which scp 819) Mar 06, 2020
[JIRA] (JENKINS-61698) Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-61698 Configuration accepts invalid values -- ArrayIndexOutOfBoundsException during runtime Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-26 16:07 Environment: Jenkins ver. 2.204.2 ec2 plugin 1.49.1 Priority: Major Reporter: Jakub Bochenski When trying to provision a new agent the plugin would start and then terminate an EC2 instance several times before succeeding in the end. I have no explanation for this behavior. Might be related to JENKINS-61343 Might be because the plugin somehow allocates "2 computer(s)" even though the instance cap is 1. Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log bootstrap() Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Getting keypair... Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Using private key j4a-ec2-ssh-key (SHA-1 fingerprint a7:b4:70:08:35:11:e3:cf:4b:f5:92:57:b8:02:7f:c6:8e:54:52:02) Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Authenticating as admin Mar 06, 2020 3:05:22 PM INFO hudson.slaves.NodeProvisioner lambda$update$6 EC2 (ec2) - ec2 (ami-028d96c69234f9d1a) provisioning successfully completed. We have now 2 computer(s) Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2.EC2Cloud log Connecting to 10.20.4.41 on port 22, with timeout 1. Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2.EC2Cloud log Connected via SSH. Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2.EC2Cloud log connect fresh as root Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2.EC2Cloud log
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Jakub Bochenski commented on JENKINS-57513 Re: Split the large databound constructors into databound setters Can you please leave the old constructors in place. I'm already using groovys scripts to configure the plugin. Splitting out into setters is a welcome change, but it sucks to have to update your scripts for a new release. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199415.1558053245000.7986.1584371940280%40Atlassian.JIRA.
[JIRA] (JENKINS-60424) logstash-plugin does not work with ElasticSearch 7
Title: Message Title Jakub Bochenski commented on JENKINS-60424 Re: logstash-plugin does not work with ElasticSearch 7 Hi, I don't use ES7 so I don't plan to work on this feature. If you would like to submit a PR I can help with review though Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.203496.1575996102000.5196.1583929320153%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Raihaan Shouhell I have filled a separate issue about the agents dying during launch as it happens independently of this issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199745.1559315049000.708.1583509020181%40Atlassian.JIRA.
[JIRA] (JENKINS-61370) EC2 instances are terminated during launch
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61370
EC2 instances are terminated during launch
Change By:
Jakub Bochenski
I'm seeing this in When trying to provision a new agent the logs every 10 minutes. The monitor thread starts plugin would start and then dies terminate an EC2 instance several times before succeeding in the end . 10 minutes later it repeats I have no explanation for this behavior . Might be related to JENKINS-61343 Might be because the plugin somehow allocates "2 computer(s)" even though the instance cap is 1. {code}Mar 05 06 , 2020 10 3 : 54 05 : 35 AM 22 PM INFO hudson. model plugins . AsyncPeriodicWork lambda$doRun$0 ec2.EC2Cloud log Started EC2 alive slaves monitor bootstrap() Mar 05 06 , 2020 10 3 : 54 05 : 35 AM SEVERE 22 PM INFO hudson. init plugins . impl ec2 . InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException EC2Cloud log A thread (EC2 alive slaves monitor thread/10354) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code Getting keypair . java . lang . NullPointerException at Mar 06, 2020 3:05:22 PM INFO hudson.plugins.ec2. util.MinimumInstanceChecker.lambda$countQueueItemsForAgentTemplate$8(MinimumInstanceChecker.java:67) EC2Cloud log at java.util.stream.ReferencePipeline$2$1.accept Using private key j4a-ec2-ssh-key ( ReferencePipeline.java SHA-1 fingerprint a7 : 174 b4:70:08:35:11:e3:cf:4b:f5:92:57:b8:02:7f:c6:8e:54:52:02 ) at java.util.stream.ReferencePipeline$ Mar 06, 2020 3 $1.accept(ReferencePipeline.java : 193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java 05 : 1382) at java 22 PM INFO hudson . util plugins . stream ec2 . AbstractPipeline.copyInto(AbstractPipeline.java:482) EC2Cloud log at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java Authenticating as adminMar 06, 2020 3:05:22 PM INFO hudson . util slaves . stream.ReduceOps NodeProvisioner lambda $ ReduceOp.evaluateSequential update$6EC2 ( ReduceOps.java:708 ec2 ) at java.util.stream.AbstractPipeline.evaluate - ec2 ( AbstractPipeline.java:234 ami-028d96c69234f9d1a ) at java provisioning successfully completed . util.stream.LongPipeline.reduce We have now 2 computer ( LongPipeline.java:461 s ) at java Mar 06, 2020 3:05:22 PM INFO hudson . util plugins . stream ec2 . LongPipeline.sum(LongPipeline.java:419) EC2Cloud log at java Connecting to 10 . util 20 . stream 4 . ReferencePipeline 41 on port 22, with timeout 1 . count(ReferencePipeline.java:593) at Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2. util EC2Cloud logConnected via SSH . MinimumInstanceChecker.countQueueItemsForAgentTemplate(MinimumInstanceChecker.java:68) at Mar 06, 2020 3:05:29 PM INFO hudson.plugins.ec2. util.MinimumInstanceChecker.lambda$null$11(MinimumInstanceChecker.java:87) EC2Cloud log at java.util.ArrayList.forEach(ArrayList.java:1257) at
[JIRA] (JENKINS-61370) EC2 instances are terminated during launch
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-61370 EC2 instances are terminated during launch Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-06 15:34 Environment: Jenkins ver. 2.204.2 ec2 plugin 1.49.1 Priority: Major Reporter: Jakub Bochenski I'm seeing this in the logs every 10 minutes. The monitor thread starts and then dies. 10 minutes later it repeats. Mar 05, 2020 10:54:35 AM INFO hudson.model.AsyncPeriodicWork lambda$doRun$0 Started EC2 alive slaves monitor Mar 05, 2020 10:54:35 AM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException A thread (EC2 alive slaves monitor thread/10354) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at hudson.plugins.ec2.util.MinimumInstanceChecker.lambda$countQueueItemsForAgentTemplate$8(MinimumInstanceChecker.java:67) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but { { code} string.replace('\n','\\n') {code } } works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6825.1583419800228%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like { { code} string.replaceAll('\n','\n\\' ) {code } } to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {code}string.replace('\n','\\n'){code} works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6827.1583419800288%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \ n')}} works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6821.1583419740312%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \ n')}} works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6823.1583419740338%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \ n')}} works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6819.1583419740284%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \\ n')}} works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6815.1583419680331%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\\ \ n')}} works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6817.1583419680370%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\ n \\ n ' )}} to escape it manually EDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\n')}} works
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6813.1583419680289%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\\\ \ n' )}} to escape it manually
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6792.1583418480262%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent } '''{code}You have to add sth like {{string.replaceAll('\n','n' )}} to escape it manually
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6788.1583418420345%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent } ''' } {code}You have to add sth like {{string.replaceAll('\n','n' )}} to escape it manually
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.204938.1583418355000.6790.1583418420377%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2020-03-05 14:25
Priority:
Major
Reporter:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:
environmentVariables {
env 'config', '''multiline
content
'''
You have to add sth like string.replaceAll('\n','n' ) to escape it manually
Add Comment
[JIRA] (JENKINS-61343) EC2 alive slaves monitor thread died unexpectedly
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-61343 EC2 alive slaves monitor thread died unexpectedly Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-05 11:20 Environment: Jenkins ver. 2.204.2 ec2 plugin 1.49.1 Priority: Major Reporter: Jakub Bochenski I'm seeing this in the logs every 10 minutes. The monitor thread starts and then dies. 10 minutes later it repeats. Mar 05, 2020 10:54:35 AM INFO hudson.model.AsyncPeriodicWork lambda$doRun$0 Started EC2 alive slaves monitor Mar 05, 2020 10:54:35 AM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException A thread (EC2 alive slaves monitor thread/10354) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at hudson.plugins.ec2.util.MinimumInstanceChecker.lambda$countQueueItemsForAgentTemplate$8(MinimumInstanceChecker.java:67) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1ec2 plugin 1.43, 1.44, 1.45 , 1.49.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199745.1559315049000.6721.1583407080708%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1 , 2.204.2 ec2 plugin 1.43, 1.44, 1.45, 1.49.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.199745.1559315049000.6723.1583407080729%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Do you have any logs from the retention strategy. I see in your logs that the instances were stopped but I'm not certain why. I'm not sure what you mean. I have pasted all of the Jenkins log output here already. Do you want me to enable DEBUG level logging for some components? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.199745.1559315049000.6933.1582715160463%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
{ code quote }Do you have any logs from the retention strategy. I see in your logs that the instances were stopped but I'm not certain why.{ code quote }I'm not sure what you mean. I have pasted all of the Jenkins log output here already. Do you want me to enable DEBUG level logging for some components?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.199745.1559315049000.6939.1582715160542%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart I tried this a few more times. So far it's reproducible 100% (which is in a way good) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.199745.1559315049000.6410.1582646100205%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
Actually I've noticed another problematic thing. After I manually terminate the instance the plugin will spawn 4 new instances that will get terminated immediatelly before finally getting the fifth one up. I thought it's was a fluke at first but it seems to be reproducible consistently.Log: https://gist.github.com/jakub-bochenski/c24b1f8e24e7be77aa2522df2c8caaed It seems the plugin just terminates the instance for no reason:{code}Feb 25, 2020 3:18:30 PM INFO hudson.plugins.ec2.EC2Cloud logLaunching remoting agent (via Trilead SSH2 Connection): java -jar /tmp/remoting.jar -workDir /opt/jenkinsFeb 25, 2020 3:18:32 PM INFO hudson.plugins.ec2.EC2OndemandSlave terminateTerminated EC2 instance (terminated): i-046afc69c32c1acddFeb 25, 2020 3:18:32 PM INFO hudson.plugins.ec2.EC2OndemandSlave terminateRemoved EC2 instance from jenkins master: i-046afc69c32c1acdd{code}Also notice this, despite instance cap=1{code}Feb 25, 2020 3:18:21 PM INFO hudson.slaves.NodeProvisioner lambda$update$6EC2 (ec2) - ec2 (ami-028d96c69234f9d1a) provisioning successfully completed. We have now 2 computer(s){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Actually I've noticed another problematic thing. After I manually terminate the instance the plugin will spawn 4 new instances that will get terminated immediatelly before finally getting the fifth one up. I thought it's was a fluke at first but it seems to be reproducible consistently. Log: https://gist.github.com/jakub-bochenski/c24b1f8e24e7be77aa2522df2c8caaed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.199745.1559315049000.6363.1582644900210%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this).I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2.I was able to reproduce this with just: - start Jenkins master instance - trigger job that will ask for the EC2-powered agent - wait for job to finish and stop Jenkins - start Jenkins again - trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance againThe log output looks like this: {code}Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfigConfiguring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}{code}After I terminate the instance manually in EC2 Console the log is {code}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Considering launchingFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDeviceAMI had xvdaFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice{DeleteOnTermination: true,SnapshotId: snap-040ff84a8c849bc15,VolumeSize: 8,VolumeType: gp2,Encrypted: false}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.TerminateFeb 25, 2020 3:18:02 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this).I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2.I was able to reproduce this with just: - start Jenkins master instance - trigger job that will ask for the EC2-powered agent - wait for job to finish and stop Jenkins - start Jenkins again - trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance againThe log output looks like this: {code}Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfigConfiguring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}{code} After I terminate the instance manually in EC2 Console the log is {code}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Considering launchingFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDeviceAMI had xvdaFeb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice{DeleteOnTermination: true,SnapshotId: snap-040ff84a8c849bc15,VolumeSize: 8,VolumeType: gp2,Encrypted: false}Feb 25, 2020 3:18:01 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.TerminateFeb 25, 2020 3:18:02 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart BTW I didn't think about it earlier, but shouldn't the plugin actually terminate the EC2 instance on Jenkins shutdown? Otherwise it could stay there indefinatly indefinitely Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.199745.1559315049000.6344.1582643820566%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart BTW I didn't think about it earlier, but shouldn't the plugin actually terminate the EC2 instance on shutdown? Otherwise it could stay there indefinatly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.199745.1559315049000.6342.1582643820476%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this).I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2.I was able to reproduce this with just: - start Jenkins master instance - trigger job that will ask for the EC2-powered agent - wait for job to finish and stop Jenkins - start Jenkins again - trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance againThe log output looks like this: {code} Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfigConfiguring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsFeb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}{code}
Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski commented on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
We have only 1 cloud active, you can find the groovy script to configure it above (I have disabled to ECS cloud to test this). I'm on version 1.49.1 of plugin and Jenkins ver. 2.204.2. I was able to reproduce this with just:
start Jenkins master instance
trigger job that will ask for the EC2-powered agent
wait for job to finish and stop Jenkins
start Jenkins again
trigger job that will ask for the EC2-powered agent, now it won't be able to hook the running instance again
The log output looks like this:
Feb 25, 2020 2:55:21 PM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Feb 25, 2020 2:55:21 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: ew1-internal-proxy.services-ci-infra-services.fsapi.com Proxy Port: 8080
Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0
Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}
Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Feb 25, 2020 2:55:22 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0
Feb 25, 2020 2:55:22 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}
Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Feb 25, 2020 2:55:31 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0
Feb 25, 2020 2:55:31 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-028d96c69234f9d1a', labels='docker docker-bakery'}
[JIRA] (JENKINS-61200) Missing authentication when downloading Avatar
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-61200
Missing authentication when downloading Avatar
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-branch-source-plugin
Created:
2020-02-24 14:30
Priority:
Major
Reporter:
Jakub Bochenski
I'm seeing those errors in the log, I expect the credentials are valid since other functions of the plugin work
Feb 24, 2020 2:27:18 PM INFO com.cloudbees.jenkins.plugins.bitbucket.BitbucketTeamMetadataAction$BitbucketAvatarCacheSource fetch
IOException: I/O error when accessing URL: /rest/api/1.0/projects/J4A/avatar.png
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: .
HttpResponseProxy{HTTP/1.1 401 [Server: nginx/1.6.2, Date: Mon, 24 Feb 2020 14:27:18 GMT, Content-Type: application/json;charset=UTF-8, Transfer-Encoding: chunked, Connection: keep-alive, X-AREQUESTID: @16SCIDTx987x473696093x3, X-ASEN: SEN-9755481, WWW-Authenticate: Basic realm="Atlassian Bitbucket", Vary: Accept-Encoding] org.apache.http.client.entity.DecompressingEntity@7fe95b62}
at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getImageRequest(BitbucketServerAPIClient.java:877)
at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getTeamAvatar(BitbucketServerAPIClient.java:728)
Caused: java.io.IOException: I/O error when accessing URL: /rest/api/1.0/projects/J4A/avatar.png
at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getTeamAvatar(BitbucketServerAPIClient.java:733)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketTeamMetadataAction$BitbucketAvatarCacheSource.fetch(BitbucketTeamMetadataAction.java:80)
at
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart We are still seeing issues with spawning instances after restart. Do you plan to work on resolving this? FABRIZIO MANFREDIRaihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.199745.1559315049000.5353.1582550760205%40Atlassian.JIRA.
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-60288
Installator is broken on Alpine
Change By:
Jakub Bochenski
The installer does not throw an error but the resulting installation is not usable unusable . Sample output from trying to run this on a {{jenkinsci/slave:alpine}} with the docker-plugin{code}Running as SYSTEM[EnvInject] - Loading node environment variables.Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadoptERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from masterAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.io.FileNotFoundException: /var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at java.io.FileInputStream.(FileInputStream.java:93) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) at java.net.URL.openStream(URL.java:1045) at hudson.FilePath$Unpack.invoke(FilePath.java:949) at hudson.FilePath$Unpack.invoke(FilePath.java:943) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3050) at
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-60288
Installator is broken on Alpine
Change By:
Jakub Bochenski
The installer does not throw an error but the resulting installation is not usable. Sample output from trying to run this on a {{jenkinsci/slave:alpine}} with the docker-plugin{code}Running as SYSTEM[EnvInject] - Loading node environment variables.Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadoptERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from masterAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.io.FileNotFoundException: /var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at java.io.FileInputStream.(FileInputStream.java:93) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) at java.net.URL.openStream(URL.java:1045) at hudson.FilePath$Unpack.invoke(FilePath.java:949) at hudson.FilePath$Unpack.invoke(FilePath.java:943) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3050) at
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-60288 Installator is broken on Alpine Issue Type: Bug Assignee: Mads Mohr Christensen Components: adoptopenjdk-plugin Created: 2019-11-26 16:26 Priority: Major Reporter: Jakub Bochenski The installer does not throw an error but the resulting installation is not usable. Sample output from trying to run this on a jenkinsci/slave: alpine with docker-plugin Running as SYSTEM [EnvInject] - Loading node environment variables. Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadopt ERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from master Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-60288
Installator is broken on Alpine
Change By:
Jakub Bochenski
The installer does not throw an error but the resulting installation is not usable. Sample output from trying to run this on a {{jenkinsci/slave: alpine}} with the docker-plugin{code}Running as SYSTEM[EnvInject] - Loading node environment variables.Installing AdoptOpenJDK to /home/jenkins/tools/hudson.model.JDK/jdkadoptERROR: Failed to download file:/var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip from agent; will retry from masterAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-006z72dcdzrtj at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:913) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:846) at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111) at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:134) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.io.FileNotFoundException: /var/lib/jenkins/caches/adoptopenjdk/LINUX/amd64/jdk-11.0.5+10.zip (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at java.io.FileInputStream.(FileInputStream.java:93) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) at java.net.URL.openStream(URL.java:1045) at hudson.FilePath$Unpack.invoke(FilePath.java:949) at hudson.FilePath$Unpack.invoke(FilePath.java:943) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3050) at
[JIRA] (JENKINS-59941) Env vars with '.' in the name fail sending to ElasticSearch
Title: Message Title Jakub Bochenski assigned an issue to Unassigned Jenkins / JENKINS-59941 Env vars with '.' in the name fail sending to ElasticSearch Change By: Jakub Bochenski Assignee: Jakub Bochenski Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202745.1572038185000.2667.1572200400169%40Atlassian.JIRA.
[JIRA] (JENKINS-59941) Env vars with '.' in the name fail sending to ElasticSearch
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-59941 Env vars with '.' in the name fail sending to ElasticSearch Thanks for the report William Brode A workaround would be to put logstash in front of your EC and use de_dot filter. I would be reluctant to add this as default behavior because you can use the ES REST API to also send to Logstash REST. I think it could be added as optional behavior. I don't indtend to work on this myself since I find the de_dot workaround sufficient. There is already an abadoned PR trying to solve this issue here: https://github.com/jenkinsci/logstash-plugin/pull/21/files If you want to pick it up I can offer some advice and reviews Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202745.1572038185000.2665.1572200280209%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski resolved as Fixed Released as v. 1.14 Jenkins / JENKINS-59833 Stash Pull Request Builder Multiple PR in single build Change By: Jakub Bochenski Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski commented on JENKINS-59833 Re: Stash Pull Request Builder Multiple PR in single build FTR you could also use the incremental builds https://jenkins.io/blog/2018/05/15/incremental-deployment/ I deploy Jenkins from a docker container it's much more convinient to just add a line like :incrementals;org.jenkins-ci.plugins;VERSION Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202568.1571346229000.18276.1571834880619%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski commented on JENKINS-59833 Re: Stash Pull Request Builder Multiple PR in single build Upkar Rai did you actually check if the fix works for you? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202568.1571346229000.13126.1571747520248%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski commented on JENKINS-59833 Re: Stash Pull Request Builder Multiple PR in single build Upkar Rai can you please check if the incremental build fixes the issue for you? It should be available soonish, once https://ci.jenkins.io/job/Plugins/job/stash-pullrequest-builder-plugin/job/PR-151/ completes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202568.1571346229000.11627.1571654640450%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski started work on JENKINS-59833 Change By: Jakub Bochenski Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202568.1571346229000.11633.1571654640629%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski assigned an issue to Pavel Roskin Jenkins / JENKINS-59833 Stash Pull Request Builder Multiple PR in single build Change By: Jakub Bochenski Assignee: Pavel Roskin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202568.1571346229000.11630.1571654640529%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski commented on JENKINS-59833 Re: Stash Pull Request Builder Multiple PR in single build I don't expect I'll find time to investigate this any time soon. If you can investigate the issue and file a PR I'll be happy to review it (that's what "experimental support" is about) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202568.1571346229000.10313.1571395980159%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski assigned an issue to Unassigned Jenkins / JENKINS-59833 Stash Pull Request Builder Multiple PR in single build Change By: Jakub Bochenski Assignee: Jakub Bochenski Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202568.1571346229000.10311.1571395800155%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
I'm still seeing issues in 1. 46 45 . The instance is in {{running}} state but plugin can't see t be able to connect it. I can't test it on 1.46 because of JENKINS-59564 {code}Sep 30, 2019 9:32:03 AM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Considering launchingSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDeviceAMI had xvdaSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice{DeleteOnTermination: true,SnapshotId: snap-0f2d5ab1c6f918116,VolumeSize: 8,VolumeType: gp2,Encrypted: false,}Sep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.TerminateSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Looking for existing instances with describe-instance: {Filters: [{Name: image-id,Values: [ami-02769bd03e603e42f]}, {Name: instance-type,Values: [t3.micro]}, {Name: key-name,Values: [j4a-bochja]}, {Name: subnet-id,Values: [subnet-0a167eb56a247e891]}, {Name: instance.group-id,Values: [sg-0a4f5e5ac5bb602e4]}, {Name: tag:Name,Values: [ew1-j4a-jenkins-slave-ec2]}, {Name: tag:DeploymentName,Values: [ew1-j4a]}, {Name: tag:CostCenter,Values: [31505]}, {Name: tag:DeploymentType,Values: [dev]}, {Name: tag:DeploymentGroup,Values: [ew1-j4a]}, {Name: tag:jenkins_server_url,Values: [https://acme.com/]}, {Name: tag:jenkins_slave_type,Values: [demand_ec2 (ami-02769bd03e603e42f)]}],InstanceIds: [],}Sep 30, 2019 9:32:05 AM INFO hudson.plugins.ec2.CloudHelper getInstanceUnexpected number of reservations reported by EC2 for instance id 'i-0571c7e8c36a6b783', expected 1 result, found []. Instance seems to be dead.Sep 30, 2019 9:32:05 AM WARNING hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Exception during provisioningcom.amazonaws.AmazonClientException: Unexpected number of reservations reported by EC2 for instance id 'i-0571c7e8c36a6b783', expected 1 result, found []. Instance seems to be dead. at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:54) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(CloudHelper.java:25) at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:566) at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:165) at hudson.plugins.ec2.EC2OndemandSlave.(EC2OndemandSlave.java:56) at hudson.plugins.ec2.SlaveTemplate.newOndemandSlave(SlaveTemplate.java:1104) at hudson.plugins.ec2.SlaveTemplate.toSlaves(SlaveTemplate.java:773) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:745) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:585) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:540) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:589) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:615) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
I'm still seeing issues in 1.46. The instance is in {{running}} state but plugin can't see t be able to connect it.{code}Sep 30, 2019 9:32:03 AM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 unitsSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Considering launchingSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDeviceAMI had xvdaSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice{DeleteOnTermination: true,SnapshotId: snap-0f2d5ab1c6f918116,VolumeSize: 8,VolumeType: gp2,Encrypted: false,}Sep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.TerminateSep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Looking for existing instances with describe-instance: {Filters: [{Name: image-id,Values: [ami-02769bd03e603e42f]}, {Name: instance-type,Values: [t3.micro]}, {Name: key-name,Values: [j4a-bochja]}, {Name: subnet-id,Values: [subnet-0a167eb56a247e891]}, {Name: instance.group-id,Values: [sg-0a4f5e5ac5bb602e4]}, {Name: tag:Name,Values: [ew1-j4a-jenkins-slave-ec2]}, {Name: tag:DeploymentName,Values: [ew1-j4a]}, {Name: tag: Contact,Values: [production-cloud-un...@f-secure.com]}, {Name: tag: CostCenter,Values: [31505]}, {Name: tag:DeploymentType,Values: [dev]}, {Name: tag:DeploymentGroup,Values: [ew1-j4a]}, {Name: tag:jenkins_server_url,Values: [https:// mastermaster acme . j4a.infra-dev-services.fsapi. com/]}, {Name: tag:jenkins_slave_type,Values: [demand_ec2 (ami-02769bd03e603e42f)]}],InstanceIds: [],}Sep 30, 2019 9:32:05 AM INFO hudson.plugins.ec2.CloudHelper getInstanceUnexpected number of reservations reported by EC2 for instance id 'i-0571c7e8c36a6b783', expected 1 result, found []. Instance seems to be dead.Sep 30, 2019 9:32:05 AM WARNING hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Exception during provisioningcom.amazonaws.AmazonClientException: Unexpected number of reservations reported by EC2 for instance id 'i-0571c7e8c36a6b783', expected 1 result, found []. Instance seems to be dead. at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:54) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(CloudHelper.java:25) at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:566) at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:165) at hudson.plugins.ec2.EC2OndemandSlave.(EC2OndemandSlave.java:56) at hudson.plugins.ec2.SlaveTemplate.newOndemandSlave(SlaveTemplate.java:1104) at hudson.plugins.ec2.SlaveTemplate.toSlaves(SlaveTemplate.java:773) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:745) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:585) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:540) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:589) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:615) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski commented on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
I'm still seeing issues in 1.46. The instance is in running state but plugin can't see t be able to connect it.
Sep 30, 2019 9:32:03 AM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Sep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
SlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Considering launching
Sep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice
AMI had xvda
Sep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice
{DeleteOnTermination: true,SnapshotId: snap-0f2d5ab1c6f918116,VolumeSize: 8,VolumeType: gp2,Encrypted: false,}
Sep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
SlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate
Sep 30, 2019 9:32:04 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
SlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Looking for existing instances with describe-instance: {Filters: [{Name: image-id,Values: [ami-02769bd03e603e42f]}, {Name: instance-type,Values: [t3.micro]}, {Name: key-name,Values: [j4a-bochja]}, {Name: subnet-id,Values: [subnet-0a167eb56a247e891]}, {Name: instance.group-id,Values: [sg-0a4f5e5ac5bb602e4]}, {Name: tag:Name,Values: [ew1-j4a-jenkins-slave-ec2]}, {Name: tag:DeploymentName,Values: [ew1-j4a]}, {Name: tag:Contact,Values: [production-cloud-un...@f-secure.com]}, {Name: tag:CostCenter,Values: [31505]}, {Name: tag:DeploymentType,Values: [dev]}, {Name: tag:DeploymentGroup,Values: [ew1-j4a]}, {Name: tag:jenkins_server_url,Values: [https://mastermaster.j4a.infra-dev-services.fsapi.com/]}, {Name: tag:jenkins_slave_type,Values: [demand_ec2 (ami-02769bd03e603e42f)]}],InstanceIds: [],}
Sep 30, 2019 9:32:05 AM INFO hudson.plugins.ec2.CloudHelper getInstance
Unexpected number of reservations reported by EC2 for instance id 'i-0571c7e8c36a6b783', expected 1 result, found []. Instance seems to be dead.
Sep 30, 2019 9:32:05 AM WARNING hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-02769bd03e603e42f', labels='docker docker-bakery'}. Exception during provisioning
com.amazonaws.AmazonClientException: Unexpected number of reservations reported by EC2 for instance id 'i-0571c7e8c36a6b783', expected 1 result, found []. Instance seems to be dead.
at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:54)
at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(CloudHelper.java:25)
at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:566)
at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:165)
at hudson.plugins.ec2.EC2OndemandSlave.(EC2OndemandSlave.java:56)
at hudson.plugins.ec2.SlaveTemplate.newOndemandSlave(SlaveTemplate.java:1104)
at hudson.plugins.ec2.SlaveTemplate.toSlaves(SlaveTemplate.java:773)
at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:745)
at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:585)
at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:540)
at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:589)
at
[JIRA] (JENKINS-59564) Network interfaces and an instance-level subnet ID may not be specified on the same request
Title: Message Title Jakub Bochenski commented on JENKINS-59564 Re: Network interfaces and an instance-level subnet ID may not be specified on the same request I'm guessing this might be related to https://issues.jenkins-ci.org/browse/JENKINS-58578 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202199.1569599527000.6850.1569599760152%40Atlassian.JIRA.
[JIRA] (JENKINS-59564) Network interfaces and an instance-level subnet ID may not be specified on the same request
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-59564
Network interfaces and an instance-level subnet ID may not be specified on the same request
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-09-27 15:52
Environment:
ec2 plugin 1.46
Priority:
Critical
Reporter:
Jakub Bochenski
After upgrading to 1.46 the plugin can no longer spawn instances. I get the above error from AWS. This works correctly when I downgrade to 1.45. My plugin configuration is
final cloud = new AmazonEC2Cloud(
'ec2',
false,
'',
config.ec2_region,
config.ec2_ssh_key,
config.ec2_instance_cap,
[
new SlaveTemplate(
config.ec2_ami_id,
'',
null,
config.ec2_security_groups,
'/opt/jenkins',
InstanceType.fromValue(config.ec2_instance_type),
false,
config.ec2_label,
Node.Mode.NORMAL,
"ec2 (${config.ec2_ami_id})",
'',
'/tmp',
'''#!/bin/bash -xe
mkfs.ext4 /dev/nvme1n1
mkdir -p /opt/jenkins
mount /dev/nvme1n1 /opt/jenkins
chown -R admin:admin /opt/jenkins
service docker stop
mkdir -p /opt/jenkins/docker/lib
mv /var/lib/docker
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Is there a way to reproduce this consistently from your end? Also what is the number of instances that get run in your setup? It happens quite often after restart but I have no way to reproduce it 100%. Maybe the fact that the instance counting logic sees the EC2 machine (since it says there is no capacity), but the attaching node can't connect it for some reason would be a hint? lso what is the number of instances that get run in your setup? I'm not sure if I understand. The instance cap is 1 so we have at most 1 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.7226.1567692660525%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Raihaan Shouhell I've provided the full configuration via a groovy script above. What else do you need? 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.199745.1559315049000.4160.1567417020226%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1ec2 plugin 1.43, 1.44 , 1.45 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.199745.1559315049000.1009.1565601840446%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart FABRIZIO MANFREDI the same problem is happening with 1.45 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.199745.1559315049000.1007.1565601840419%40Atlassian.JIRA.
[JIRA] (JENKINS-58849) Logstash plugin: requires insecure "mask-passwords"
Title: Message Title Jakub Bochenski commented on JENKINS-58849 Re: Logstash plugin: requires insecure "mask-passwords" Please try upgrading the plugin to latest version, as old versions depended on mask-passwords 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.201164.1565189042000.10048.1565196120097%40Atlassian.JIRA.
[JIRA] (JENKINS-58849) Logstash plugin: requires insecure "mask-passwords"
Title: Message Title Jakub Bochenski closed an issue as Cannot Reproduce The dependency you link to is only used in test (as can be seen by it's scope). I fail to see why it would be a problem. Please reopen if I'm missing something Jenkins / JENKINS-58849 Logstash plugin: requires insecure "mask-passwords" Change By: Jakub Bochenski Status: Open Closed Resolution: Cannot Reproduce 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.201164.1565189042000.9875.1565190900232%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart > I believe I found the problem, I trying to put in the 1.44.2 that should be release in a couple of days. FABRIZIO MANFREDI it's been a month now and I can't see any new releases after 1.44.1. Any updates? 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.199745.1559315049000.7892.1565011860566%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart > One more question what do you mean with orphaned, stop state or no longer in the jenkins interface ? It's not available as an agent in jenkins. It's still in running state when I check the status in AWS console> Did you apply the all the IAM role requested specify in the ec2 plugin page ? I believe I did, since this is a random error it doesn't happen every time . E.g. the instances get terminated after idle timeout 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.199745.1559315049000.2317.1562330340401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart > One more question what do you mean with orphaned, stop state or no longer in the jenkins interface ? It's not available as an agent in jenkins. It's still in running state when I check the status in AWS console > Did you apply the all the IAM role requested specify in the ec2 plugin page ? I believe I did, since this is a random error it doesn't happen every time 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.199745.1559315049000.2314.1562330220119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart [~thoulen][~raihaan] I know this is OSS and there are is not SLA. Still could you tell me if I and when I can expect any assistance from you . ? 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.199745.1559315049000.1830.1562247420130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart FABRIZIO MANFREDIRaihaan Shouhell I know this is OSS and there are is not SLA. Still could you tell me if I and when I can expect any assistance from you. 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.199745.1559315049000.1828.1562247360241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1ec2 plugin 1.43, 1.44 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.199745.1559315049000.10656.1561638300177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart I double checked this. If I'm at cap = 1 with 1 orphaned instance and increase the cap to 2 then the plugin will spawn a new instance. If I'm at cap = 2 with 2 orphaned instances and terminate one of the instances manually then the plugin will reconnect the other 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.10552.1561637520111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Above looks like maybe there is some "off by one" error, when the plugin won't attempt to re-connect instances if it's at instance cap 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.199745.1559315049000.10543.1561635660112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski commented on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
I'm now getting this situation with instance cap = 2. I have two matching instances on EC2, both are active. Plugin is looping with above message, with no agents available for the builds. Now when I terminated one of the instances an interesting thing happened. Jenkins was able to pick up the other instance and reconnect it
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0
Jun 27, 2019 11:35:07 AM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}
Jun 27, 2019 11:35:16 AM INFO hudson.plugins.ec2.EC2Cloud provision
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units
Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Considering launching
Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice
AMI had xvda
Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice
{DeleteOnTermination: true,SnapshotId: snap-0b70f104d64ae4a48,VolumeSize: 8,VolumeType: gp2,Encrypted: false,}
Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate
Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Looking for existing instances with describe-instance: {Filters: SNAP
Jun 27, 2019 11:35:18 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. checkInstance: i-0e454aea630ccb88f. true - Instance is not connected to Jenkins
Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Can you try with 2 ? If I reproduce the issue with instance cap = 1, then increase the cap to 2 I will get a new agent spawned (but only 1) Now trying to reproduce this with 2 instances getting orphaned. I also tried setting instance cap on slave template to 2 (it was blank before) – doesn't seem to help 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.199745.1559315049000.10524.1561632480494%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58215) Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-58215 Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean) Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1Timestamper 1.9AnsiColor 0.6.2Pipeline: Declarative 1.3.9 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.200275.1561560107000.9726.1561564500875%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
This is happening at least since 1.43 and it just happened on 1.44I have only one EC2 cloud configured, but I also have an ECS cloud (they use separate agent labels).This is our cloud configuration done via groovy script:{code}final cloud = new AmazonEC2Cloud('ec2',false,config.ec2_access_key,config.ec2_region,config.ec2_ssh_key,config.ec2_instance_cap,[new SlaveTemplate( config.ec2_ami_id, '', null, config.ec2_security_groups, '/tmp', InstanceType.fromValue(config.ec2_instance_type), false, config.ec2_label, Node.Mode.NORMAL, "ec2 (${config.ec2_ami_id})", '', '/tmp', '', '1', config.ec2_remote_user, new UnixData(null, null, null, null), '', false, config.ec2_subnet_id, [ Name: ' ew1-j4a-jenkins-slave-ec2 acme ', CostCenter: '31505', DeploymentGroup: 'ew1-j4a', DeploymentName: 'ew1-j4a', DeploymentType: 'dev', Contact : ' production-cloud-unity acme @ f-secure acme .com', // FIXME don't hard-code the region, parametrize ].collect{ new EC2Tag(it.key,it.value) }, '30', false, '', config.ec2_arn_role, true, false, false, '1800', false, '', false, false, false, false)],config.ec2_arn_role,''){code}
Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
This is happening at least since 1.43 and it just happened on 1.44 I have only one EC2 cloud configured, but I also have an ECS cloud (they use separate agent labels). This is our cloud configuration done via groovy script:{code}final cloud = new AmazonEC2Cloud('ec2',false,config.ec2_access_key,config.ec2_region,config.ec2_ssh_key,config.ec2_instance_cap,[new SlaveTemplate( config.ec2_ami_id, '', null, config.ec2_security_groups, '/tmp', InstanceType.fromValue(config.ec2_instance_type), false, config.ec2_label, Node.Mode.NORMAL, "ec2 (${config.ec2_ami_id})", '', '/tmp', '', '1', config.ec2_remote_user, new UnixData(null, null, null, null), '', false, config.ec2_subnet_id, [ Name: 'ew1-j4a-jenkins-slave-ec2', CostCenter: '31505', DeploymentGroup: 'ew1-j4a', DeploymentName: 'ew1-j4a', DeploymentType: 'dev', Contact : 'production-cloud-un...@f-secure.com', // FIXME don't hard-code the region, parametrize ].collect{ new EC2Tag(it.key,it.value) }, '30', false, '', config.ec2_arn_role, true, false, false, '1800', false, '', false, false, false, false)],config.ec2_arn_role,''){code}
Add Comment
This message
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski commented on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
This is happening at least since 1.43 and it just happened on 1.44 This is our cloud configuration done via groovy script:
final cloud = new AmazonEC2Cloud(
'ec2',
false,
config.ec2_access_key,
config.ec2_region,
config.ec2_ssh_key,
config.ec2_instance_cap,
[
new SlaveTemplate(
config.ec2_ami_id,
'',
null,
config.ec2_security_groups,
'/tmp',
InstanceType.fromValue(config.ec2_instance_type),
false,
config.ec2_label,
Node.Mode.NORMAL,
"ec2 (${config.ec2_ami_id})",
'',
'/tmp',
'',
'1',
config.ec2_remote_user,
new UnixData(null, null, null, null),
'',
false,
config.ec2_subnet_id,
[
Name: 'ew1-j4a-jenkins-slave-ec2',
CostCenter: '31505',
DeploymentGroup: 'ew1-j4a',
DeploymentName: 'ew1-j4a',
DeploymentType: 'dev',
Contact : 'production-cloud-un...@f-secure.com',
// FIXME don't hard-code the region, parametrize
].collect{ new EC2Tag(it.key,it.value) },
'30',
false,
'',
config.ec2_arn_role,
true,
false,
false,
'1800',
false,
'',
false,
false,
false,
false
)],
config.ec2_arn_role,
''
)
Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-57795
Orphaned EC2 instances after Jenkins restart
Change By:
Jakub Bochenski
Sometimes after a Jenkins restart the plugin won't be able to spawn more agents.The plugin will just loop on this:{code}SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Attempting to provision slave needed by excess workload of 1 unitsMay 31, 2019 2:23:53 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Cannot provision - no capacity for instances: 0May 31, 2019 2:23:53 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}{code}If I go to the EC2 console and terminate the instance manually the plugin will spawn a new one and use it.It seems like there is some mismatch in the plugin logic. The part responsible for calculating the number of instances and checking the cap sees the EC2 instance. However the part responsible for picking up running EC2 instances doesn't seem to be able to find it.We use a single subnet, security group and vpc (I've seen some reports about this causing problems). It seems the problems do not occur when I do a {{/safeRestart}} but they do if I use e.g. "restart Jenkins when no jobs are running" form the Update Center. We use instanceCap = 1 setting as we are testing the plugin, this might make this problem more visible than with a higher cap.
Add Comment
This message was sent by
[JIRA] (JENKINS-58215) Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Title: Message Title Jakub Bochenski commented on JENKINS-58215 Re: Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean) Devin NusbaumJesse Glick maybe this is related to the ConsoleAnnotator change? 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.200275.1561560107000.9509.1561560360113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58215) Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-58215
Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Change By:
Jakub Bochenski
The next timestamp after a coloured line appears with the same color as the line and is not formatted. !Screenshot_20190626_164002.png! Relevant parts of Jenkinsfile{code}pipeline {options {withAWS(region: 'eu-west-1', roleAccount: acme, credentials: 'acme')timeout(time: 20, unit: 'MINUTES')timestamps()ansiColor('xterm')}stage('Build') { // build goes before tests to force updating the parent image steps {sh '''#!/bin/sh -euxdocker build --pull --tag "$GIT_COMMIT" .'''}}}{code}
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.200275.1561560107000.9507.1561560180135%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58215) Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-58215
Coloring breaks timestamp output in Declarative Pipeline (NOT Blueocean)
Issue Type:
Bug
Assignee:
Andrew Bayer
Attachments:
Screenshot_20190626_164002.png
Components:
ansicolor-plugin, pipeline-model-definition-plugin, timestamper-plugin
Created:
2019-06-26 14:41
Priority:
Minor
Reporter:
Jakub Bochenski
The next timestamp after a coloured line appears with the same color as the line and is not formatted.Relevant parts of Jenkinsfile
pipeline {
options {
withAWS(region: 'eu-west-1', roleAccount: acme, credentials: 'acme')
timeout(time: 20, unit: 'MINUTES')
timestamps()
ansiColor('xterm')
}
stage('Build') {
// build goes before tests to force updating the parent image
steps {
sh '''#!/bin/sh -eux
docker build --pull --tag "$GIT_COMMIT" .
'''
}
}
}
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Raihaan Shouhell maybe you would care to respond? 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.199745.1559315049000.9470.1561557420193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title Jakub Bochenski commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Is this a duplicate of JENKINS-58163 ? 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.200248.1561491352000.9462.1561557063651%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20353) EC2 plugin forgets about some instances it launched when Jenkins restarts
Title: Message Title Jakub Bochenski reopened an issue I have this happening after almost every restart, see JENKINS-57795 Jenkins / JENKINS-20353 EC2 plugin forgets about some instances it launched when Jenkins restarts Change By: Jakub Bochenski Resolution: Cannot Reproduce Status: Closed Reopened 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.151873.1383169757000.8391.1561470420944%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart FABRIZIO MANFREDI it would be nice to at least get some pointers on how to debug this further or work around it 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.199745.1559315049000.8387.1561470180140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57956) Cancel outdated jobs not working properly with multiple jobs ont the same pull request
Title: Message Title Jakub Bochenski commented on JENKINS-57956 Re: Cancel outdated jobs not working properly with multiple jobs ont the same pull request Bartlomiej Poleszak the repository you mention is abandoned and outside of control of the jenkins project. Please feel free to re-submit the PR to the official repository at https://github.com/jenkinsci/stash-pullrequest-builder-plugin This functionality has been moved to StashRepository. We also require some basic unit test coverage for new changes 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.199937.1560252872000.25204.1560263880531%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56683) Declarative Pipeline: set the build result when tests fail without a script block
Title: Message Title Jakub Bochenski resolved as Duplicate That's great. I think we can resolve this issue now Jenkins / JENKINS-56683 Declarative Pipeline: set the build result when tests fail without a script block Change By: Jakub Bochenski Status: Open Resolved Resolution: Duplicate 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.198320.1553265541000.17669.1559318040323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-57795
Orphaned EC2 instances after Jenkins restart
Change By:
Jakub Bochenski
Sometimes after a Jenkins restart the plugin won't be able to spawn more agents.The plugin will just loop on this:{code}SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Attempting to provision slave needed by excess workload of 1 unitsMay 31, 2019 2:23:53 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Cannot provision - no capacity for instances: 0May 31, 2019 2:23:53 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}{code}If I go to the EC2 console and terminate the instance manually the plugin will spawn a new one and use it.It seems like there is some mismatch in the plugin logic. The part responsible for calculating the number of instances and checking the cap sees the EC2 instance. However the part responsible for picking up running EC2 instances doesn't seem to be able to find it.We use a single subnet, security group and vpc (I've seen some reports about this causing problems).It seems the problems do not occur when I do a ` {{ /safeRestart ` }} but they do if I use e.g. "restart Jenkins when no jobs are running" form the Update Center. We use instanceCap = 1 setting as we are testing the plugin, this might make this problem more visible than with a higher cap.
Add Comment
This message was
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-57795
Orphaned EC2 instances after Jenkins restart
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-05-31 15:04
Priority:
Critical
Reporter:
Jakub Bochenski
Sometimes after a Jenkins restart the plugin won't be able to spawn more agents. The plugin will just loop on this:
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Attempting to provision slave needed by excess workload of 1 units
May 31, 2019 2:23:53 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlave
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}. Cannot provision - no capacity for instances: 0
May 31, 2019 2:23:53 PM WARNING hudson.plugins.ec2.EC2Cloud provision
Can't raise nodes for SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker'}
If I go to the EC2 console and terminate the instance manually the plugin will spawn a new one and use it. It seems like there is some mismatch in the plugin logic. The part responsible for calculating the number of instances and checking the cap sees the EC2 instance. However the part responsible for picking up running EC2 instances doesn't seem to be able to find it. We use a single subnet, security group and vpc (I've seen some reports about this causing problems). It seems the problems do not occur when I do a `/safeRestart` but they do if I use e.g. "restart Jenkins when no jobs are running" form the Update Center. We use instanceCap = 1 setting as we are testing the plugin, this might make this problem more visible than with a higher cap.
[JIRA] (JENKINS-56683) Declarative Pipeline: set the build result when tests fail without a script block
Title: Message Title Jakub Bochenski commented on JENKINS-56683 Re: Declarative Pipeline: set the build result when tests fail without a script block Devin Nusbaum does the new `unstable` step solve this? I think it still requires a `script` block, right? 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.198320.1553265541000.17612.1559314680125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Jakub Bochenski commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin Kinnaird McQuade thanks for sharing your workaround. I think you'll agree that having credentials plugin support would make be better than jumping all those hoops? 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.198606.1554663571000.17576.1559313000115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Jakub Bochenski commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin Also if you want to use JCasC it will force you to enter the ssh key in plaintext in JCasC yaml 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.198606.1554663571000.16580.1559220780116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
