[JIRA] (JENKINS-59510) Unable to use User scoped credentials in Matrix Job
Title: Message Title Manuel Cardenas updated an issue Jenkins / JENKINS-59510 Unable to use User scoped credentials in Matrix Job Change By: Manuel Cardenas * Create a Matrix Job. * Define Credentials parameter. * Define Credentials binding AWS access key and secret.Try to pass a user scoped credential as parameter , assign the parameter to the binding and use it in the job. It will not work. The same setup works for a freestyle job.It would be great if the user scoped credential could work in a matrix job. 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.202132.1569329832000.4211.1569329940323%40Atlassian.JIRA.
[JIRA] (JENKINS-59510) Unable to use User scoped credentials in Matrix Job
Title: Message Title Manuel Cardenas created an issue Jenkins / JENKINS-59510 Unable to use User scoped credentials in Matrix Job Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 2019-09-24 12:57 Environment: Jenkins 2.164.x matrix-project 1.14 Credentials binding 1.18 Credentials 2.1.18 Priority: Minor Reporter: Manuel Cardenas Create a Matrix Job. Define Credentials parameter. Define Credentials binding AWS access key and secret. Try to pass a user scoped credential as parameter and use it in the job. It will not work. The same setup works for a freestyle job. It would be great if the user scoped credential could work in a matrix job. Add Comment
[JIRA] (JENKINS-58787) Be able to create a job posting config.xml - Or improve docs
Title: Message Title Manuel Cardenas created an issue Jenkins / JENKINS-58787 Be able to create a job posting config.xml - Or improve docs Issue Type: Improvement Assignee: Janario Oliveira Components: http-request-plugin Created: 2019-08-02 14:41 Priority: Minor Reporter: Manuel Cardenas I want to be able to create jobs just by posting config.xml to the jenkins instance using the httprequest step def response = httpRequest authentication: 'JENKINS', customHeaders: [[maskValue: false, name: 'Content-type', value: 'application/xml']], ignoreSslErrors: true, outputFile: 'config.xml', responseHandle: "STRING", url: 'http://localhost:8080/job/FOLDER/job/template/config.xml', validResponseCodes: '100:399' def myxml= "'"+response.content+"'" def response1 = httpRequest authentication: 'JENKINS', customHeaders: [[maskValue: false, name: 'Content-Type', value: 'TEXT_PLAIN'], [maskValue: false, name: 'requestBody', value: myxml], [maskValue: false, name: 'consoleLogResponseBody', value: 'true'], [maskValue: false, name: 'authentication', value: 'BASIC'] ], httpMode: 'POST', ignoreSslErrors: true, url: "http://localhost:8080/createItem?name=new_job" Or def response = httpRequest authentication: 'JENKINS', customHeaders: [[maskValue: false, name: 'Content-type', value: 'application/xml']], ignoreSslErrors: true, outputFile: 'config.xml', responseHandle: "STRING", url: 'http://localhost:8080/job/FOLDER/job/template/config.xml', validResponseCodes: '100:399' def myxml=
[JIRA] (JENKINS-57820) When running a build in a Windows agent we get an FRM-92120 error
Title: Message Title Manuel Cardenas created an issue Jenkins / JENKINS-57820 When running a build in a Windows agent we get an FRM-92120 error Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-06-03 12:23 Priority: Minor Reporter: Manuel Cardenas Jenkins version 2.89.4.2 maven-plugin:3.1.2 'Maven Integration plugin' The error reported was that the maven job fails (simple mvn clean test) with an applet error coming from Forms server. FRM-92120 - https://community.oracle.com/thread/170365 The job is being built in an agent which is running in a windows machine. The agent process has been launched from an interactive session using an administrator command prompt. When you run the same command out of the agent process, directly from the windows agent workspace, the job is successfully built. When you run the `mvn clean test` command from a shell step in that agent, the job is built successfully. There are no traces of any other errors in the agent logs, or in the event logs for Application, System or Security at Windows level. Any further debugging steps would be appreciated. The valid workaround at this point is not using the plugin, but I would like to understand why.
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title Manuel Cardenas commented on JENKINS-55070 Re: "Jenkins.instance is missing" error when restarting Jenkins Devin Nusbaum are you aware of any potential workaround for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title Manuel Cardenas commented on JENKINS-55070 Re: "Jenkins.instance is missing" error when restarting Jenkins Thank you for your analysis Wadeck Follonier, we will try to dig a little bit more on what is happening as it is preventing us from applying a security upgrade. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title
Manuel Cardenas edited a comment on JENKINS-55070
Re: "Jenkins.instance is missing" error when restarting Jenkins
[~danielbeck] , we have seen this issue in a non windows installation, Centos 7.x * OpenJDK 64-Bit Server VM 25.161-b14 The complete context: We are upgrading Jenkins from 2.138.3.1 to 2.138.4.3 using a war file. Once that we use the new war file, the service is not able to start. We can see the trace below. {code:java}Dec 11, 2018 3:22:10 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /login java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) ... ec Dec 11, 2018 3:22:42 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /tcpSlaveAgentListener/ java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:58) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:531) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title
Manuel Cardenas edited a comment on JENKINS-55070
Re: "Jenkins.instance is missing" error when restarting Jenkins
[~danielbeck] , we have seen this issue in a non windows installation, Centos 7.x * OpenJDK 64-Bit Server VM 25.161-b14 {code:java}Dec 11, 2018 3:22:10 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /login java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) ...ec 11, 2018 3:22:42 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /tcpSlaveAgentListener/ java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:58) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:531) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) at
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title Manuel Cardenas commented on JENKINS-55070 Re: "Jenkins.instance is missing" error when restarting Jenkins Daniel Beck , we have seen this issue in a non windows installation, Centos 7.x Dec 11, 2018 3:22:10 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /login java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) ... ec 11, 2018 3:22:42 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /tcpSlaveAgentListener/ java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:58) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:531) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at
[JIRA] (JENKINS-54205) Blue Ocean Editor modifies a declarative Jenkinsfile without warning
Title: Message Title
Manuel Cardenas created an issue
Jenkins / JENKINS-54205
Blue Ocean Editor modifies a declarative Jenkinsfile without warning
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-pipeline-editor-plugin
Created:
2018-10-23 13:18
Priority:
Major
Reporter:
Manuel Cardenas
@Library('bitwiseman-shared@blog/declarative/notifications') _
pipeline {
...
If you open a BO editor page or you modify the pipeline using BO interface, the annotation gets removed. Is this an expected behavior? Interestingly, if you put that code directly in the GitHub repo, it will work, but if you edit the code using the BO UI the code gets removed. https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-editor/src/main/js/services/PipelineValidator.js#L83 We should be able to warn users about this modification. That would happen not only with shared libraries but with anything outside the pipeline block.
[JIRA] (JENKINS-37385) Powershell plugin does not seem to support dot sourcing
Title: Message Title Manuel Cardenas commented on JENKINS-37385 Re: Powershell plugin does not seem to support dot sourcing Mathew Miehling would it be possible for you to confirm this? If so, could you close the issue? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42757) Wrong changelog displayed when using two repositories
Title: Message Title Manuel Cardenas closed an issue as Fixed It does not show once that you upgrade git-branch-source to 1.10.1 Jenkins / JENKINS-42757 Wrong changelog displayed when using two repositories Change By: Manuel Cardenas Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42757) Wrong changelog displayed when using two repositories
Title: Message Title Manuel Cardenas commented on JENKINS-42757 Re: Wrong changelog displayed when using two repositories I've found that once that you upgrade git-branch-source to version 1.10.1 the problem does not persist. Thus, I think that we can close the issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42757) Wrong changelog displayed when using two repositories
Title: Message Title
Manuel Cardenas commented on JENKINS-42757
Re: Wrong changelog displayed when using two repositories
I have used this vanilla Jenkinsfile in Repo A, the Jenkinsfile performs a simple checkout on Repo B.
stage 'Dev'
node () {
checkout([$class: 'GitSCM', branches: [[name: '*/master']],
doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [],
userRemoteConfigs: [[url: 'Put a valid GithubRepo here where you can do a checkout']]])
sh 'ls -lrt' //easy command to have the job executed successfully
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42757) Wrong changelog displayed when using two repositories
Title: Message Title Manuel Cardenas created an issue Jenkins / JENKINS-42757 Wrong changelog displayed when using two repositories Issue Type: Bug Assignee: Mark Waite Components: git-plugin, pipeline Created: 2017/Mar/14 3:02 PM Environment: Jenkins LTS 2.19.4 git:2.5.3 workflow-aggregator:2.4 Labels: pipeline Priority: Major Reporter: Manuel Cardenas Given two repositories: Repo A: containing Jenkinsfile that defines the build pipeline Repo B: containing an application that is built using Jenkinsfile existing in repo A. Once that you run the pipeline job that uses the Jenkinsfile in repo A to checkout the application in repo B and build it, the results for the execution of the pipeline show the changelog for the repo A, not for repo B. Add Comment
[JIRA] (JENKINS-41426) EC2- Keeps sending stop signal to a manually stopped instance
Title: Message Title Manuel Cardenas updated an issue Jenkins / JENKINS-41426 EC2- Keeps sending stop signal to a manually stopped instance Change By: Manuel Cardenas When using EC2 plugin to stop (not terminate) slave instances after a certain amount of idle time, if you stop manually one of those slaves before the stop signal is sent, you can see in the logs messages like the following one:```INFO h.p.ec2.EC2RetentionStrategy#internalCheck: Idle timeout of [XXX] after 82 idle minutes INFO h.plugins.ec2.EC2AbstractSlave#idleTimeout: EC2 instance idle time expired: [XXX-ID] INFO h.plugins.ec2.EC2AbstractSlave#stop: EC2 instance stop request sent for [XXX-ID]``` The plugin keeps sending the stop signal even if the instance is already stopped. This message fill the logs. Any way to remove it? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-41426) EC2- Keeps sending stop signal to a manually stopped instance
Title: Message Title Manuel Cardenas created an issue Jenkins / JENKINS-41426 EC2- Keeps sending stop signal to a manually stopped instance Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2017/Jan/25 1:48 PM Environment: * Jenkins 2.19.4.2 * Java Version: 1.8.0_111 * ec2:1.36 'Amazon EC2 plugin' Priority: Minor Reporter: Manuel Cardenas When using EC2 plugin to stop (not terminate) slave instances after a certain amount of idle time, if you stop manually one of those slaves you can see in the logs messages like the following one: ``` INFO h.p.ec2.EC2RetentionStrategy#internalCheck: Idle timeout of [XXX] after 82 idle minutes INFO h.plugins.ec2.EC2AbstractSlave#idleTimeout: EC2 instance idle time expired: [XXX-ID] INFO h.plugins.ec2.EC2AbstractSlave#stop: EC2 instance stop request sent for [XXX-ID] ``` This message fill the logs. Any way to remove it? Add Comment
