[JIRA] (JENKINS-55343) How to use IAM role for authentication with Amazon EC2 Fleet Plugin
Title: Message Title Artem Stasiuk closed an issue as Won't Do Looks like no interest in this feature, closing. Jenkins / JENKINS-55343 How to use IAM role for authentication with Amazon EC2 Fleet Plugin Change By: Artem Stasiuk Status: Open Closed Resolution: Won't Do 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
[JIRA] (JENKINS-59216) LinkageError in ec2 spot fleet while performing jenkins UserRequest
Title: Message Title Artem Stasiuk resolved as Not A Defect thx for comment, closing Jenkins / JENKINS-59216 LinkageError in ec2 spot fleet while performing jenkins UserRequest Change By: Artem Stasiuk Status: Open Resolved Assignee: Chad Schmutzer Artem Stasiuk Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message beca
[JIRA] (JENKINS-59216) LinkageError in ec2 spot fleet while performing jenkins UserRequest
Title: Message Title Artem Stasiuk closed an issue as Not A Defect Jenkins / JENKINS-59216 LinkageError in ec2 spot fleet while performing jenkins UserRequest Change By: Artem Stasiuk Status: Resolved Closed 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.201666.1567572121000.5242.1579883460678%40Atlassian.JIRA.
[JIRA] (JENKINS-54679) SSHLauncher doesn't continue retrying to connect to remote executor
Title: Message Title Artem Stasiuk commented on JENKINS-54679 Re: SSHLauncher doesn't continue retrying to connect to remote executor Hi, is that still valid? 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.195470.1542400069000.5231.1579883280197%40Atlassian.JIRA.
[JIRA] (JENKINS-54679) SSHLauncher doesn't continue retrying to connect to remote executor
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-54679 SSHLauncher doesn't continue retrying to connect to remote executor Change By: Artem Stasiuk Assignee: Chad Schmutzer Artem Stasiuk 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.195470.1542400069000.5227.1579883220364%40Atlassian.JIRA.
[JIRA] (JENKINS-60737) EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave
Title: Message Title Artem Stasiuk updated JENKINS-60737 Jenkins / JENKINS-60737 EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave Change By: Artem Stasiuk Status: Fixed but Unreleased Resolved 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.203990.1578695914000.5224.1579883160499%40Atlassian.JIRA.
[JIRA] (JENKINS-60737) EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave
Title: Message Title Artem Stasiuk updated JENKINS-60737 Jenkins / JENKINS-60737 EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave Change By: Artem Stasiuk Status: Open Fixed but Unreleased Resolution: Not A Defect 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.203990.1578695914000.5222.1579883160468%40Atlassian.JIRA.
[JIRA] (JENKINS-60737) EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave
Title: Message Title Artem Stasiuk commented on JENKINS-60737 Re: EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave Doesn't seem like a bug, looks like builds consume a lot of space, you can try to reduce amount of parallel builds and make sure you checkout only files without repo history https://stackoverflow.com/questions/29368837/copy-a-git-repo-without-history 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.203990.1578695914000.5220.1579883160444%40Atlassian.JIRA.
[JIRA] (JENKINS-60737) EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-60737 EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave Change By: Artem Stasiuk Assignee: Chad Schmutzer Artem Stasiuk 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.203990.1578695914000.5218.1579882980171%40Atlassian.JIRA.
[JIRA] (JENKINS-58621) EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-58621 EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status Change By: Artem Stasiuk Assignee: Chad Schmutzer Artem Stasiuk 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.200787.1563913663000.5215.1579882860641%40Atlassian.JIRA.
[JIRA] (JENKINS-58621) EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status
Title: Message Title Artem Stasiuk commented on JENKINS-58621 Re: EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status One more question on plugin configuration picture, credentials are not configured 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.200787.1563913663000.5212.1579882860535%40Atlassian.JIRA.
[JIRA] (JENKINS-58621) EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status
Title: Message Title Artem Stasiuk commented on JENKINS-58621 Re: EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status Do you see any errors in log? 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.200787.1563913663000.5209.1579882800530%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title
Artem Stasiuk edited a comment on JENKINS-60165
Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels
Just to confirm instance name or agent name is added automatically by Jenkins, so it's not plugin feature. I think I see possible problem {{nonprodslave*.}} is conditional label. Let me try to check that. You should be able to specify just {{nonprodslave}} without conditional {{*.}}
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.203117.1573718238000.2209.1578121380111%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk commented on JENKINS-60165 Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels Just to confirm instance name or agent name is added automatically by Jenkins, so it's not plugin feature. I think I see possible problem nonprodslave*. is conditional label. Let me try to check that. 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.203117.1573718238000.2207.1578121320190%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk commented on JENKINS-60165 Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels For information place where we set Node name https://github.com/jenkinsci/ec2-fleet-plugin/blob/master/src/main/java/com/amazon/jenkins/ec2fleet/EC2FleetCloud.java#L645 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.203117.1573718238000.514.1575490260128%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk commented on JENKINS-60165 Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels Just checked code, plugin doesn't add label to Node name, in fact node name is always just EC2 instance ID, however Jenkins users/plugins are able to change Node name after creation is that possible that you have some additional plugin which does that? 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.203117.1573718238000.309.1575489480153%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk commented on JENKINS-60165 Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels Hi could you please specify version of your EC2 Fleet Plugin, thx 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.203117.1573718238000.303.1575489060321%40Atlassian.JIRA.
[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-60165 EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-343’) after the label. This fails the role assignment by agent labels Change By: Artem Stasiuk Assignee: Chad Schmutzer Artem Stasiuk 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.203117.1573718238000.297.1575488580326%40Atlassian.JIRA.
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Artem Stasiuk commented on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
For the first one can we use: smt like
@Override
public void taskCompleted(Executor executor, Queue.Task task, long durationMS) {
super.taskCompleted(executor, task, durationMS);
if (isOffline() && getOfflineCause() != null) {
System.out.println("Opa, try to resubmit");
Queue.getInstance().schedule(task, 10);
}
}
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.188646.1519349293000.4996.1561064581383%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35426) Additional options for new nodes
Title: Message Title Artem Stasiuk resolved as Fixed All requested features are implemented. Feel free to reopen if you have questions or problems with them. Thx. Jenkins / JENKINS-35426 Additional options for new nodes Change By: Artem Stasiuk Status: Open Resolved Resolution: Fixed 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.171221.1465310252000.18447.1559456100599%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35426) Additional options for new nodes
Title: Message Title Artem Stasiuk commented on JENKINS-35426 Re: Additional options for new nodes Mark Lagendijk feature "Utilize this node as much as possible" vs "Only build jobs with label restrictions matching this node" available from version [1.5.0](https://github.com/jenkinsci/ec2-fleet-plugin/releases/tag/ec2-fleet-1.5.0) 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.171221.1465310252000.18426.1559456040550%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35426) Additional options for new nodes
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-35426 Additional options for new nodes Change By: Artem Stasiuk Assignee: Aleksei Besogonov Artem Stasiuk 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.171221.1465310252000.18437.1559456040708%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk updated JENKINS-35435 Jenkins / JENKINS-35435 Test connection doesn't work Change By: Artem Stasiuk Status: Fixed but Unreleased Resolved 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.171232.146532240.8217.1558491181214%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk updated JENKINS-35435 Fixed and released under ec2 fleet plugin version 1.2.1 Jenkins / JENKINS-35435 Test connection doesn't work Change By: Artem Stasiuk Status: Open Fixed but Unreleased Resolution: Fixed 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.171232.146532240.8215.1558491181157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk commented on JENKINS-35435 Re: Test connection doesn't work PR https://github.com/jenkinsci/ec2-fleet-plugin/pull/72 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.171232.146532240.5771.1558396140688%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-35435 Test connection doesn't work Change By: Artem Stasiuk Assignee: Aleksei Besogonov Artem Stasiuk 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.171232.146532240.5787.1558396140912%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk edited a comment on JENKINS-35435 Re: Test connection doesn't work Fix PR https://github.com/jenkinsci/ec2-fleet-plugin/pull/72 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.171232.146532240.5784.1558396140880%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48696) When an offline node comes online, pending jobs don't get assigned to it
Title: Message Title Artem Stasiuk resolved as Done Thx, close as issue is gone, feel free to reopen if any problems/questions. No code change in plugin assume it was Jenkins/version related. Jenkins / JENKINS-48696 When an offline node comes online, pending jobs don't get assigned to it Change By: Artem Stasiuk Status: Open Resolved Assignee: Artem Stasiuk Resolution: Done 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/jenkins
[JIRA] (JENKINS-45074) spot-fleet plugin deadlocks master when scaling up
Title: Message Title Artem Stasiuk resolved as Fixed Feel free to reopen if you still have problem with it. Jenkins / JENKINS-45074 spot-fleet plugin deadlocks master when scaling up Change By: Artem Stasiuk Status: Open Resolved Resolution: Fixed 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.183167.1498143044000.2130.1557813061502%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45074) spot-fleet plugin deadlocks master when scaling up
Title: Message Title Artem Stasiuk commented on JENKINS-45074 Re: spot-fleet plugin deadlocks master when scaling up Was released under version 1.1.7 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.183167.1498143044000.2122.1557813061244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54679) SSHLauncher doesn't continue retrying to connect to remote executor
Title: Message Title Artem Stasiuk commented on JENKINS-54679 Re: SSHLauncher doesn't continue retrying to connect to remote executor Thx for info, Bert JW Regeer did you fix it in the same way? 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.195470.1542400069000.2118.1557812880200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44138) Add options for node launching strategy
Title: Message Title Artem Stasiuk commented on JENKINS-44138 Re: Add options for node launching strategy Could you please provide a use case for such flexible configuration, this change could take some time, as current impl totally controlled by Jenkins. It defines when scale-up will be run and what amount of executors should be launched. The plugin just controls that no the max will be run. 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.181764.1494315309000.2103.1557811560111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk edited a comment on JENKINS-35435 Re: Test connection doesn't work Current The current version of the plugin is using configured credentials [ here code|[https://github.com/jenkinsci/ec2-fleet-plugin/blob/master/src/main/java/com/amazon/jenkins/ec2fleet/EC2FleetCloud.java#L611]] 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.171232.146532240.2092.1557811380282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk commented on JENKINS-35435 Re: Test connection doesn't work Current version of plugin is using configured credentials 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.171232.146532240.2089.1557811320357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk commented on JENKINS-37123 Re: Support role based access EC2 Spot Fleet supports IAM Roles: EC2 Fleet Plugin supports IAM Role. Manage Jenkins > System Configuration, find Spot Fleet Configuration, if you open AWS Credentials, at the bottom, it has IAM Role Support, which allows the specifying role to assume by the plugin. 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.173201.1470152923000.2076.1557811080316%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk resolved as Done Feel free to reopen if you have questions. Jenkins / JENKINS-37123 Support role based access Change By: Artem Stasiuk Status: Open Resolved Resolution: Done 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.173201.1470152923000.2080.1557811080399%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk edited a comment on JENKINS-37123 Re: Support role based access Similar https://issues.jenkins-ci.org/browse/ JENKINS-55343 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.173201.1470152923000.2072.1557811020329%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk commented on JENKINS-37123 Re: Support role based access Similar https://issues.jenkins-ci.org/browse/JENKINS-55343 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.173201.1470152923000.2068.1557811020279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57188) EC2 fleet machines fail to spin up.
Title: Message Title Artem Stasiuk resolved as Done Thx for update, closed. Jenkins / JENKINS-57188 EC2 fleet machines fail to spin up. Change By: Artem Stasiuk Status: Open Resolved Resolution: Done 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.198941.1556212968000.2065.1557810900382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48696) When an offline node comes online, pending jobs don't get assigned to it
Title: Message Title Artem Stasiuk commented on JENKINS-48696 Re: When an offline node comes online, pending jobs don't get assigned to it Do you still have this issue? 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.187380.1513974343000.2060.1557810780141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55343) How to use IAM role for authentication with Amazon EC2 Fleet Plugin
Title: Message Title Artem Stasiuk edited a comment on JENKINS-55343 Re: How to use IAM role for authentication with Amazon EC2 Fleet Plugin Hi,EC2 Fleet Plugin supports IAM Role. Manage Jenkins > System Configuration, find Spot Fleet Configuration, if you open AWS Credentials, at the bottom, it has IAM Role Support, which allows the specifying role to assume by the plugin. Thx,Artem Is that feature which you are interesting? 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.196437.1545899269000.2058.1557809220124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55343) How to use IAM role for authentication with Amazon EC2 Fleet Plugin
Title: Message Title Artem Stasiuk commented on JENKINS-55343 Re: How to use IAM role for authentication with Amazon EC2 Fleet Plugin Hi, EC2 Fleet Plugin supports IAM Role. Manage Jenkins > System Configuration, find Spot Fleet Configuration, if you open AWS Credentials, at the bottom, it has IAM Role Support, which allows the specifying role to assume by the plugin. Thx, Artem 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.196437.1545899269000.2053.1557809160209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55343) How to use IAM role for authentication with Amazon EC2 Fleet Plugin
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-55343 How to use IAM role for authentication with Amazon EC2 Fleet Plugin Change By: Artem Stasiuk Assignee: Chad Schmutzer Artem Stasiuk 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.196437.1545899269000.2056.1557809160260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35438) Fleet always keeps at least one instance
Title: Message Title Artem Stasiuk commented on JENKINS-35438 Re: Fleet always keeps at least one instance Released under version ec2-fleet-1.1.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.171235.1465324703000.2043.1557808200220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35438) Fleet always keeps at least one instance
Title: Message Title Artem Stasiuk resolved as Fixed Fix already merged, close ticket. Feel free to reopen it if any problem or questions. Jenkins / JENKINS-35438 Fleet always keeps at least one instance Change By: Artem Stasiuk Status: Open Resolved Resolution: Fixed 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.171235.1465324703000.2033.1557808140573%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38477) Can't see status icon in PR
Title: Message Title Artem Stasiuk resolved as Fixed Fixed by PR https://github.com/jenkinsci/github-pr-coverage-status-plugin/pull/2 in version 1.0.9 Jenkins / JENKINS-38477 Can't see status icon in PR Change By: Artem Stasiuk Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit h
[JIRA] (JENKINS-38477) Can't see status icon in PR
Title: Message Title Artem Stasiuk started work on JENKINS-38477 Change By: Artem Stasiuk Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38477) Can't see status icon in PR
Title: Message Title Artem Stasiuk created an issue Jenkins / JENKINS-38477 Can't see status icon in PR Issue Type: Task Assignee: Artem Stasiuk Components: github-pr-coverage-status Created: 2016/Sep/23 9:21 PM Labels: plugin Priority: Major Reporter: Artem Stasiuk Copied from original GitHub https://github.com/terma/github-pr-coverage-status/pull/14 Add Comment
