profile
viewpoint
Abdul Muqtadir Mohammed imuqtadir AWS United States of America

jenkinsci/ec2-fleet-plugin 68

The EC2 Spot Jenkins plugin launches EC2 Spot instances as worker nodes for Jenkins CI server, automatically scaling the capacity with the load.

imuqtadir/Sentiment-Analysis 6

This Project involves a process of analyzing sentiments about any particular movie using user reviews available on social networking sites like Facebook and Twitter into categories namely, Positive and Negative. The idea behind this was to help user make better judgement about the product by reading only positive reviews or negative reviews related to the product. Sentiment analysis involved extraction and measurement of the sentiment or “attitude” of a review using natural language processing steps such as stemming, stop-words removal and formation of similarity matrix using Stanford NLP libraries.

imuqtadir/Apache-Solr-Wikipedia-and-Related-News-Articles 1

The project aims to provide a customized search engine for Wikipedia Articles and once the user clicks on the Article, a related news is also retrieved using a the description of the article to formulate a search query. Also, relevant facebook post will also be shown

imuqtadir/Android-Messenger 0

This project aims to provide ordering guarantees to five AVD's group messenger. The project guarantees both total ordering as well as FIFO ordering. We store all the messages in the content provider. The different is that when we store the messages and assign sequence numbers, the project mechanism provides total and FIFO ordering guarantees.

imuqtadir/aws-node-termination-handler 0

A Kubernetes Daemonset to gracefully handle EC2 instance shutdown

imuqtadir/aws-simple-ec2-cli-1 0

A CLI tool that simplifies the process of launching, connecting and terminating an EC2 instance.

imuqtadir/Boolean-Search-Engine 0

Project parses the news corpus and retrieves all the relevant information from the article such as Author, Date, Place, Titile etc. by parsing it and indexes these fields in separate indexes. The user when enters his search query, then a boolean query is formulated using AND, OR and NOT and relevant results are retrieved along with snippets. We use Okapi BM25 model for tf-idf in order to rank the documents.

imuqtadir/ec2-fleet-plugin 0

The EC2 Spot Jenkins plugin launches EC2 Spot instances as worker nodes for Jenkins CI server, automatically scaling the capacity with the load.

imuqtadir/Handwritten-Digits-Classification 0

A Multi-Layer Perceptron Neural Network approach for determining hand-written digits along with regularization.

issue commentjenkinsci/ec2-fleet-plugin

Jenkins offlines build slaves with running jobs within scaledown period?

Your understanding regarding Max Idle Minutes Before Scaledown is correct. The plugin will terminate the node only when it has been idle for more than Max Idle Minutes Before Scaledown while considering minimum and maximum cluster size. Is this a recurring issue? Can you share the steps to replicate along with the plugin configurations you have in place so we can dive deeper into this?

ZillaG

comment created time in 4 days

pull request commentjenkinsci/ec2-fleet-plugin

Fix executable resubmission behavior on instance termination

Just adding more details here to highlight the point of contention :

  1. Build is executing on the EC2 instance
  2. The user tries to delete their instance by deleting the agent from Jenkins console
  3. The instance gets removed from Jenkins

Current Scenario: 4. Since the node was intentionally removed from Jenkins. The target capacity is unchanged and user can re-schedule the build if they wish to.

Now with your change: 4. Build gets re-scheduled and Jenkins immediately provisions another EC2 instance and increases the target capacity so that it could execute the re-scheduled build.

I will spend some more time to see why ChannelTermination is not raised in some scenarios to see if we can fix that and talk to few more customers to gather their inputs. Feel free to let me know your thoughts around this.

SrodriguezO

comment created time in 4 days

pull request commentjenkinsci/ec2-fleet-plugin

Fix executable resubmission behavior on instance termination

@SrodriguezO Thanks for the PR and your response. By manually deleting I meant, changing plugin config for scaling down or deleting agent. IIRC this would result in just having SimpleOfflineCause.

Any reason why we didn't include SimpleOfflineCause but removed the condition forChannelTermination? Are there any unintentional exceptions that we will be including as a result of this?

I'm okay with adding this however I will have to run play around with this more and see if there are any side affects to it. Meanwhile can you update the PR with the integ tests AutoResubmitIntegrationTest.

SrodriguezO

comment created time in 5 days

push eventimuqtadir/ec2-fleet-plugin

Mohammed

commit sha 7116acf50e6211ac3c222edf256e1d9687677bfe

[maven-release-plugin] prepare release ec2-fleet-2.1.3

view details

Mohammed

commit sha 89e7478c5f42bc7bbe7f27bcc7e6be2accec4e7d

[maven-release-plugin] prepare for next development iteration

view details

push time in 6 days

pull request commentjenkinsci/ec2-fleet-plugin

Fix executable resubmission behavior on instance termination

When a node gets interrupted unintentionally, it raises OfflineCause.ChannelTermination exception. The job is re-queued using the EC2FleetAutoResubmitComputerLauncher as we resubmit the job when we encounter OfflineCause.ChannelTermination exception. However, this does not remove the EC2 instance from jenkins nodes. EC2FleetCloud nanny then sees that instance is missing in EC2 and removes it from the jenkins nodes. We then encounter hudson.slaves.OfflineCause$SimpleOfflineCause exception.

If you see hudson.slaves.OfflineCause$SimpleOfflineCause exception happen when instance is abruptly terminated, you should ideally see OfflineCause.ChannelTermination exception in above logs. If this is incorrect, please let me know the steps to reproduce it. I have tried multiple ways and this was always the case.

The reason we didn't include hudson.slaves.OfflineCause$SimpleOfflineCause was that the users most often terminate the instance (manually or using plugin configs) to stop the build and they don't want the build to be resubmitted. hudson.slaves.OfflineCause$SimpleOfflineCause is a result of user intentionally terminating the node unlike OfflineCause.ChannelTermination which happens when unexpected interruptions happen.

I would like to know if you have any steps to reproduce this. This would be helpful.

SrodriguezO

comment created time in 6 days

created tagawslabs/aws-simple-ec2-cli

tagv0.5.1

A CLI tool that simplifies the process of launching, connecting and terminating an EC2 instance.

created time in 24 days

push eventawslabs/aws-simple-ec2-cli

Abdul Muqtadir Mohammed

commit sha 46522778c8c67f8dd3b28f8ea1637a91dcac427c

Fix space for DELETE_STACK

view details

push time in 24 days

push eventawslabs/aws-simple-ec2-cli

Abdul Muqtadir Mohammed

commit sha 8262b3c3e3af07c3cffb8439fcb7a086ddd8591f

Add version target

view details

push time in 24 days

delete branch imuqtadir/aws-simple-ec2-cli-1

delete branch : build-binaries

delete time in 24 days

push eventawslabs/aws-simple-ec2-cli

Abdul Muqtadir Mohammed

commit sha b9fa05fba8b54e3025a9d958e0b904cd796e9613

Add script to generate binaries for multiple platform (#5)

view details

push time in 24 days

PR merged awslabs/aws-simple-ec2-cli

Add script to generate binaries for multiple platform

Issue #, if available: Automate creating binaries for multiple platforms

Description of changes: Create make target build-binaries to help create binaries for multiple platform

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+171 -3

0 comment

5 changed files

imuqtadir

pr closed time in 24 days

issue closedawslabs/aws-simple-ec2-cli

Add script to generate binaries for multiple platform

Automate creating binaries for multiple platforms. Create make target build-binaries to help create binaries for multiple platform

closed time in 24 days

imuqtadir

issue openedawslabs/aws-simple-ec2-cli

Add script to generate binaries for multiple platform

Automate creating binaries for multiple platforms. Create make target build-binaries to help create binaries for multiple platform

created time in 24 days

PR opened awslabs/aws-simple-ec2-cli

Add script to generate binaries for multiple platform

Issue #, if available: Automate creating binaries for multiple platforms

Description of changes: Create make target build-binaries to help create binaries for multiple platform

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+171 -3

0 comment

5 changed files

pr created time in 24 days

create barnchimuqtadir/aws-simple-ec2-cli-1

branch : build-binaries

created branch time in 24 days

push eventimuqtadir/aws-simple-ec2-cli-1

Abdul Muqtadir Mohammed

commit sha b82764695cdb58c7755772ecc92ccc29abf14275

Rename THIRD-PARTY-LICENSES.txt to THIRD_PARTY_LICENSES.txt

view details

push time in 24 days

create barnchimuqtadir/aws-simple-ec2-cli

branch : build-binaries

created branch time in 24 days

issue closedjenkinsci/ec2-fleet-plugin

Resubmitted jobs lose their parameters

It looks like build parameters are lost when a job is resubmitted due to SpotFleet killing the host it was running on.

It's kind of uninteresting but, just in case, here is the log: https://gist.github.com/Liath/bba5290f1bf0665ee61d6ccd1fc3020e

The Jenkinsfile of the job is something like this:

pipeline {
  agent {
    label "ec2-fleet"
  }

  parameters {
    string(name: 'template', defaultValue: 'false', description: 'a path')
    string(name: 'stage', defaultValue: 'dev', description: 'environment')
  }

  stages {
    stage('Build') {
      when { expression { params.template != 'false' } }

      steps {
        withAWS(region: 'us-west-2', credentials: 'aws') {
          sh "long-running --stage ${params.stage}' ${params.template}"
        }
      }
    }
  }
}

closed time in 25 days

Liath

issue commentjenkinsci/ec2-fleet-plugin

Resubmitted jobs lose their parameters

I'm closing this for now. Please let us know if this is still the issue and reopen it.

Liath

comment created time in 25 days

push eventimuqtadir/aws-simple-ec2-cli

Abdul Muqtadir Mohammed

commit sha 0885f60e78cefc470adec99359d2baef35c59fb4

Update README.md (#3) Making some minor README changes

view details

Brandon Wagner

commit sha e6db45f30926bdd3c03eac61c9ed1e90514d2eb7

Remove mac ds store files (#4) * remove mac ds store files * fix travis and upgrade go

view details

Abdul Muqtadir Mohammed

commit sha b82764695cdb58c7755772ecc92ccc29abf14275

Rename THIRD-PARTY-LICENSES.txt to THIRD_PARTY_LICENSES.txt

view details

push time in a month

push eventawslabs/aws-simple-ec2-cli

Abdul Muqtadir Mohammed

commit sha b82764695cdb58c7755772ecc92ccc29abf14275

Rename THIRD-PARTY-LICENSES.txt to THIRD_PARTY_LICENSES.txt

view details

push time in a month

created tagimuqtadir/aws-simple-ec2-cli

tagv0.5.0

created time in a month

release imuqtadir/aws-simple-ec2-cli

v0.5.0

released time in a month

PublicEvent

fork imuqtadir/aws-simple-ec2-cli-1

A CLI tool that simplifies the process of launching, connecting and terminating an EC2 instance.

fork in a month

push eventawslabs/aws-simple-ec2-cli

Brandon Wagner

commit sha e6db45f30926bdd3c03eac61c9ed1e90514d2eb7

Remove mac ds store files (#4) * remove mac ds store files * fix travis and upgrade go

view details

push time in a month

PR merged awslabs/aws-simple-ec2-cli

remove mac ds store files

Issue #, if available: N/A

Description of changes:

  • Remove .DS_store files
  • Fix Travis on PR runs
  • Upgrade go to 1.15

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+16 -8

0 comment

8 changed files

bwagner5

pr closed time in a month

PullRequestReviewEvent

created tagawslabs/aws-simple-ec2-cli

tagv0.5.0

A CLI tool that simplifies the process of launching, connecting and terminating an EC2 instance.

created time in a month

release awslabs/aws-simple-ec2-cli

v0.5.0

released time in a month

push eventjenkinsci/ec2-fleet-plugin

Mohammed

commit sha 89e7478c5f42bc7bbe7f27bcc7e6be2accec4e7d

[maven-release-plugin] prepare for next development iteration

view details

push time in a month

created tagjenkinsci/ec2-fleet-plugin

tagec2-fleet-2.1.3

The EC2 Spot Jenkins plugin launches EC2 Spot instances as worker nodes for Jenkins CI server, automatically scaling the capacity with the load.

created time in a month

push eventjenkinsci/ec2-fleet-plugin

Mohammed

commit sha 7116acf50e6211ac3c222edf256e1d9687677bfe

[maven-release-plugin] prepare release ec2-fleet-2.1.3

view details

push time in a month

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha e18c0962270175ed591b467ed665359e7167254d

Upgrade ssh-slave to version 1.23 (#208) More details here: https://issues.jenkins-ci.org/browse/JENKINS-44893

view details

push time in a month

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha e18c0962270175ed591b467ed665359e7167254d

Upgrade ssh-slave to version 1.23 (#208) More details here: https://issues.jenkins-ci.org/browse/JENKINS-44893

view details

push time in a month

PR merged jenkinsci/ec2-fleet-plugin

Upgrade ssh-slave to 1.23

The issue related to class instantiation for TrileadSupport was resolved in ssh-slave 1.23.

More details here: https://issues.jenkins-ci.org/browse/JENKINS-44893

+1 -1

0 comment

1 changed file

imuqtadir

pr closed time in a month

issue closedjenkinsci/ec2-fleet-plugin

ClassNotFoundException: hudson.plugins.sshslaves.verifiers.JenkinsTrilead9VersionSupport

This looks like it's just classes not having been loaded yet, so is just unnecessary noise and happens whenever the instances get terminated/interrupted. There seems to be loading issue with Trilead.

Aug 17, 2020 1:35:30 PM hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager getTrileadSupport
WARNING: Could not create Trilead support class. Using legacy Trilead features
java.lang.ClassNotFoundException: hudson.plugins.sshslaves.verifiers.JenkinsTrilead9VersionSupport
        at org.jenkinsci.maven.plugins.hpi.JettyAndServletApiOnlyClassLoader.findClass(JettyAndServletApiOnlyClassLoader.java:38)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:543)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.createVersion9Instance(TrileadVersionSupportManager.java:52)
        at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.getTrileadSupport(TrileadVersionSupportManager.java:32)
        at hudson.plugins.sshslaves.verifiers.SshHostKeyVerificationStrategy.getPreferredKeyAlgorithms(SshHostKeyVerificationStrategy.java:68)
        at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:796)
        at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:792)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

closed time in a month

imuqtadir

PR opened jenkinsci/ec2-fleet-plugin

Upgrade ssh-slave to 1.23

The issue related to class instantiation for TrileadSupport was resolved in ssh-slave 1.23.

More details here: https://issues.jenkins-ci.org/browse/JENKINS-44893

+1 -1

0 comment

1 changed file

pr created time in a month

create barnchimuqtadir/ec2-fleet-plugin

branch : upgrade-ssh-slave

created branch time in a month

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha b8e8fa1a073c646432615ab3dd403a237e63748e

Fix timeout for integration test (#207)

view details

push time in a month

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha b8e8fa1a073c646432615ab3dd403a237e63748e

Fix timeout for integration test (#207)

view details

push time in a month

PR merged jenkinsci/ec2-fleet-plugin

Fix timeout for integration test

Integration tests were failing intermittently as nodes were terminated by Jenkins due to timeout. Fixing this by breaking sleep into multiple parts

+19 -9

0 comment

1 changed file

imuqtadir

pr closed time in a month

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha f2711076383da3d94fda5d51d5fb9275543397e3

Correct typo

view details

push time in a month

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha 13b629b66892c2c56ffebf48296ec3d9b8271e44

Add comments to explain the timeout

view details

push time in a month

PR opened jenkinsci/ec2-fleet-plugin

Fix timeout for integration test

Integration tests were failing intermittently as nodes were terminated by Jenkins due to timeout. Fixing this by breaking sleep into multiple parts

+19 -7

0 comment

1 changed file

pr created time in a month

create barnchimuqtadir/ec2-fleet-plugin

branch : fix-integ-test

created branch time in a month

issue closedjenkinsci/ec2-fleet-plugin

Jenkins unable to execute jobs on replaced spot instances or scaled instances

Been having this problem of Jenkins master not able to connect to replaced spot instances or new instances added during scale up.

Whenever a spot instance is terminated & replaced, jobs fail to run on the new instance slave spot instance with this error:

hudson.remoting.Channel$CallSiteStackTrace: Remote call to i-09e3xxxxxxxxxxxx Caused: java.io.IOException: Remote call on i-09e3xxxxxx failed

Would appreciate any help in resolving this

closed time in a month

junydania

issue commentjenkinsci/ec2-fleet-plugin

Jenkins unable to execute jobs on replaced spot instances or scaled instances

I'm resolving this for now. Please feel free to reopen when you have additional details.

junydania

comment created time in a month

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha e43a70848b59454bfc0d278f5d4078de0ef09772

Prune excess idle capacity if greater than max (#205)

view details

push time in a month

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha e43a70848b59454bfc0d278f5d4078de0ef09772

Prune excess idle capacity if greater than max (#205)

view details

push time in a month

PR merged jenkinsci/ec2-fleet-plugin

Prune excess idle capacity if greater than max

Excess capacity isn't immediately pruned when max size is decreased or a fleet greater than max allowed was attached to the plugin.

Expected Behavior:

When max is decreased in the fleet plugin settings, the plugin will prune the nodes which are idle. If the nodes are currently busy, they will NOT be pruned and the build would continue. However, once the build is complete and nodes are idle - they will be removed.

+217 -2

0 comment

6 changed files

imuqtadir

pr closed time in a month

issue closedjenkinsci/ec2-fleet-plugin

Excess capacity isn't immediately pruned when max size is decreased in settings

To reproduce:

  1. Create new spot request maually for use in Jenkins
  2. Add fleet to Jenkins via this plugin, scaling from 1-4
  3. (Fleet is added. At some point it scales up to 4 nodes)
  4. Remove fleet; add "new" fleet to Jenkins -- same one -- but now scale from 1-2
  5. (Fleet is added. Remains at 4 nodes indefinitely)
  6. Reboot Jenkins just in case
  7. (Remains at 4 nodes)

Expected behavior:

  • If newly-added fleet is greater in size than the max, automatically scale it down to the max size.
  • i.e. Fleet size immediately becomes 2 nodes

Actual behavior:

  • Fleet remains at the previous max size -- 4 in this case -- even though queue has been empty for 6x the scale-down timeout

Versions

  • Jenkins 2.190.2
  • EC2 Fleet Jenkins Plugin 1.16.1

closed time in a month

ianfixes

issue closedjenkinsci/ec2-fleet-plugin

Have IdleRententionStrategy Integration tests

We need to have only unit tests but no integration tests to test the IdleRententionStrategy. It is important to test idle nodes are terminated as expected.

closed time in a month

imuqtadir

issue openedjenkinsci/ec2-fleet-plugin

Have IdleRententionStrategy Integration tests

We need to have only unit tests but no integration tests to test the IdleRententionStrategy. It is important to test idle nodes are terminated as expected.

created time in a month

PR opened jenkinsci/ec2-fleet-plugin

Prune excess idle capacity if greater than max

Excess capacity isn't immediately pruned when max size is decreased or a fleet greater than max allowed was attached to the plugin.

Expected Behavior:

When max is decreased in the fleet plugin settings, the plugin will prune the nodes which are idle. If the nodes are currently busy, they will NOT be pruned and the build would continue. However, once the build is complete and nodes are idle - they will be removed.

+217 -2

0 comment

6 changed files

pr created time in a month

create barnchimuqtadir/ec2-fleet-plugin

branch : prune-excess-capacity

created branch time in a month

push eventimuqtadir/ec2-fleet-plugin

Mohammed

commit sha d23f57c683bb228ab3e0de69dddafa8190858376

[maven-release-plugin] prepare release ec2-fleet-2.1.2

view details

Mohammed

commit sha e885f7039f548026ea68500571db9df535a79d8a

[maven-release-plugin] prepare for next development iteration

view details

Abdul Muqtadir Mohammed

commit sha 8c5bf2b565ddee7ed8a75c9d1bc24b3b9cae4158

Add maintainer to pom.xml (#203)

view details

push time in a month

issue closedjenkinsci/ec2-fleet-plugin

How do you configure fleet node properties?

When clicking on Configure for a Fleet Cloud node, the following error is thrown:

No page found 'configure-entries.jelly' for class com.amazon.jenkins.ec2fleet.EC2FleetNode

An argument can be made that the user shouldn't be configuring individual nodes, but the node-specific settings (e.g. Tool Locations) do not appear under the Spot Fleet Configuration screen.

closed time in a month

FordyceGarfield

issue commentjenkinsci/ec2-fleet-plugin

How do you configure fleet node properties?

I'm closing the issue as we have not heard back from you. Please feel free to reopen the issue by adding more details.

FordyceGarfield

comment created time in a month

issue openedjenkinsci/ec2-fleet-plugin

ClassNotFoundException: hudson.plugins.sshslaves.verifiers.JenkinsTrilead9VersionSupport

This looks like it's just classes not having been loaded yet, so is just unnecessary noise and happens whenever the instances get terminated/interrupted. There seems to be loading issue with Trilead.

Aug 17, 2020 1:35:30 PM hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager getTrileadSupport
WARNING: Could not create Trilead support class. Using legacy Trilead features
java.lang.ClassNotFoundException: hudson.plugins.sshslaves.verifiers.JenkinsTrilead9VersionSupport
        at org.jenkinsci.maven.plugins.hpi.JettyAndServletApiOnlyClassLoader.findClass(JettyAndServletApiOnlyClassLoader.java:38)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:543)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.createVersion9Instance(TrileadVersionSupportManager.java:52)
        at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.getTrileadSupport(TrileadVersionSupportManager.java:32)
        at hudson.plugins.sshslaves.verifiers.SshHostKeyVerificationStrategy.getPreferredKeyAlgorithms(SshHostKeyVerificationStrategy.java:68)
        at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:796)
        at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:792)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

created time in a month

issue closedjenkinsci/ec2-fleet-plugin

@VackarAfzal . In my case Target capacity and min size works weirdly or please correct me if my understanding is wrong . When I keep the Target capacity in jenkins as 2 and min size as 0 . It immediately sets the target capacity to two in the spot fleet when there is a job which does not require that much . is it supposed to create just one and scale up based on demand ???

@VackarAfzal . In my case Target capacity and min size works weirdly or please correct me if my understanding is wrong . When I keep the Target capacity in jenkins as 2 and min size as 0 . It immediately sets the target capacity to two in the spot fleet when there is a job which does not require that much . is it supposed to create just one and scale up based on demand ???

Originally posted by @ebalakumar in https://github.com/jenkinsci/ec2-fleet-plugin/issues/52#issuecomment-482520557

closed time in a month

ebalakumar

issue commentjenkinsci/ec2-fleet-plugin

Resubmitted jobs lose their parameters

@Liath I tried to replicate this bug. Steps:

  1. Started a parametrized build on instance
  2. The build starts executing
  3. Terminate the instance abruptly
  4. Build gets resubmitted
  5. New instance picks up the build.

However, I do see the parameters were also passed and not lost. I would need more details here for reproducing this bug.

Liath

comment created time in a month

delete branch jenkinsci/ec2-fleet-plugin

delete branch : imuqtadir-maintainer

delete time in a month

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha 8c5bf2b565ddee7ed8a75c9d1bc24b3b9cae4158

Add maintainer to pom.xml (#203)

view details

push time in a month

PR merged jenkinsci/ec2-fleet-plugin

Add maintainer for project

Adding imuqtadir as maintainer for project

+5 -0

0 comment

1 changed file

imuqtadir

pr closed time in a month

PR opened jenkinsci/ec2-fleet-plugin

Add maintainer for project

Adding imuqtadir as maintainer for project

+5 -0

0 comment

1 changed file

pr created time in a month

create barnchjenkinsci/ec2-fleet-plugin

branch : imuqtadir-maintainer

created branch time in a month

delete branch jenkinsci/ec2-fleet-plugin

delete branch : ec2-fleet-2.1.2

delete time in a month

create barnchjenkinsci/ec2-fleet-plugin

branch : ec2-fleet-2.1.2

created branch time in a month

PR opened jenkins-infra/repository-permissions-updater

Add imuqtadir to ec2-fleet-plugin

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

Please add permissions to @imuqtadir for https://github.com/jenkinsci/ec2-fleet-plugin Existing maintainers: @terma <!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

  • [x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+1 -0

0 comment

1 changed file

pr created time in a month

PR opened imuqtadir/repository-permissions-updater

Add imuqtadir to ec2-fleet-plugin

<!-- This PR template only applies to permission changes. Ignore it for changes to the tool updating permissions in Artifactory -->

Description

Please add permissions to @imuqtadir for https://github.com/jenkinsci/ec2-fleet-plugin Existing maintainers: @terma <!-- fill in description here, this will at least be a link to a GitHub repository, and often also links to hosting request, and @mentioning other committers/maintainers as per the checklist below -->

Submitter checklist for adding or changing permissions

<!-- Make sure to implement all relevant entries (see section headers to when they apply) and mark them as checked (by replacing the space between brackets with an "x"). Remove sections that don't apply, e.g. the second and third when adding a new uploader to an existing permissions file. -->

Always

  • [x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

Reviewer checklist (not for requesters!)

  • [ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • [ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
  • [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

+1 -0

0 comment

1 changed file

pr created time in a month

create barnchimuqtadir/repository-permissions-updater

branch : imuqtadir-permissions

created branch time in a month

push eventjenkinsci/ec2-fleet-plugin

Mohammed

commit sha e885f7039f548026ea68500571db9df535a79d8a

[maven-release-plugin] prepare for next development iteration

view details

push time in a month

created tagjenkinsci/ec2-fleet-plugin

tagec2-fleet-2.1.2

The EC2 Spot Jenkins plugin launches EC2 Spot instances as worker nodes for Jenkins CI server, automatically scaling the capacity with the load.

created time in a month

push eventjenkinsci/ec2-fleet-plugin

Mohammed

commit sha d23f57c683bb228ab3e0de69dddafa8190858376

[maven-release-plugin] prepare release ec2-fleet-2.1.2

view details

push time in a month

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha 462cf74ff39b3d3ba53df30c8938ce737648d56d

Add checking AWS Permission using Test Connection button (#202) Allow Test connection button to detect missing AWS Permissions

view details

push time in 2 months

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha 462cf74ff39b3d3ba53df30c8938ce737648d56d

Add checking AWS Permission using Test Connection button (#202) Allow Test connection button to detect missing AWS Permissions

view details

push time in 2 months

PR merged jenkinsci/ec2-fleet-plugin

Add checking AWS Permission using Test Connection button

By clicking 'Test Connections' button, users can verify if they are missing any AWS policies required by the plugin.

+202 -13

0 comment

6 changed files

imuqtadir

pr closed time in 2 months

issue closedjenkinsci/ec2-fleet-plugin

Feature request: Test AWS permissions as part of "test connection"

I had previously submitted a documentation patch related to proper AWS permissions: https://github.com/jenkinsci/ec2-fleet-plugin/pull/56/files

This documentation appears to have been removed from the README.

I think it would be better to provide a check for proper permissions as part of the "Test Connection" button in the plugin configuration. I assume this would be done best by querying the permissions of the user, not by something like attempting to "modify" the spot request to its same values. This way, you have a test not only that the fleet can be used but that the entire plugin will function as expected.

closed time in 2 months

ianfixes

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha 2fd0fad5cd4b33974a675f309f7e6b433b016f2e

Dummy commit to retrigger build due to timeout

view details

push time in 2 months

PR opened jenkinsci/ec2-fleet-plugin

Add checking AWS Permission using Test Connection button

By clicking 'Test Connections' button, users can verify if they are missing any AWS policies required by the plugin.

+203 -13

0 comment

6 changed files

pr created time in 2 months

create barnchimuqtadir/ec2-fleet-plugin

branch : test-connection

created branch time in 2 months

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha 197c8327df96c98c01bba63311654a73061327a5

Add code of conduct (#201)

view details

Abdul Muqtadir Mohammed

commit sha d5e49457d325bd231286e9fb46504765006d2c31

Correct typo for README

view details

push time in 2 months

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha d5e49457d325bd231286e9fb46504765006d2c31

Correct typo for README

view details

push time in 2 months

issue closedjenkinsci/ec2-fleet-plugin

After connection breaks, job is failing and getting resubmitted, though node is back online in some seconds.

Hello.

Not sure, but it looks like in this particular case is slightly different from https://github.com/jenkinsci/ec2-fleet-plugin/issues/121 .

Basically, one of the things which happens from time to time is following:

  1. Node is provisioned
  2. Node gets job
  3. There happens I/O error
  4. build fails and getting resubmitted
  5. Connection restores

So, c.a.j.e.EC2FleetAutoResubmitComputerLauncher#afterDisconnect does resubmit - which is actually good, but it does not count that node is back there in some time.

So what do you think? Should it rather wait for node to come back online, with limited amount of retries, etc or rather current behaviour is proper?

Jenkins ver. 2.191 Plugin ver. 1.10.2

./jenkins.log:2019-09-12 05:32:20.972+0000 [id=5104742]	INFO	h.r.SynchronousCommandTransport$ReaderThread#run: I/O error in channel i-0978b0726c81e4fda
./jenkins.log:2019-09-12 05:32:20.978+0000 [id=5104742]	INFO	c.a.j.e.EC2FleetAutoResubmitComputerLauncher#afterDisconnect: Unexpected FleetCloud i-0978b0726c81e4fda termination,  resubmit
./jenkins.log:2019-09-12 05:32:20.983+0000 [id=5104742]	INFO	c.a.j.e.EC2FleetAutoResubmitComputerLauncher#afterDisconnect: Unexpected FleetCloud i-0978b0726c81e4fda termination, resubmit org.jenkinsci.plugins.workflow.job.WorkflowJob@2dd7fc62[%%%] with actions []
./jenkins.log:2019-09-12 05:32:20.988+0000 [id=5104742]	INFO	c.a.j.e.EC2FleetAutoResubmitComputerLauncher#afterDisconnect: Unexpected FleetCloud i-0978b0726c81e4fda termination, resubmit finished
./jenkins.log:2019-09-12 05:33:05.427+0000 [id=54]	INFO	c.a.j.e.IdleRetentionStrategy#check: Reconnecting to instance: FleetCloud i-0978b0726c81e4fda
./jenkins.log:2019-09-12 05:33:05.427+0000 [id=54]	INFO	hudson.slaves.SlaveComputer#tryReconnect: Attempting to reconnect i-0978b0726c81e4fda
./jenkins.log:[09/12/19 05:33:06] SSH Launch of i-0978b0726c81e4fda on %%% failed in 646 ms
./jenkins.log:2019-09-12 05:33:17.135+0000 [id=48]	INFO	c.a.j.e.IdleRetentionStrategy#check: Reconnecting to instance: FleetCloud i-0978b0726c81e4fda
./jenkins.log:2019-09-12 05:33:17.135+0000 [id=48]	INFO	hudson.slaves.SlaveComputer#tryReconnect: Attempting to reconnect i-0978b0726c81e4fda
./jenkins.log:[09/12/19 05:33:17] SSH Launch of i-0978b0726c81e4fda on %%% failed in 409 ms
./jenkins.log:2019-09-12 05:35:17.110+0000 [id=51]	INFO	c.a.j.e.IdleRetentionStrategy#check: Reconnecting to instance: FleetCloud i-0978b0726c81e4fda
./jenkins.log:2019-09-12 05:35:17.110+0000 [id=51]	INFO	hudson.slaves.SlaveComputer#tryReconnect: Attempting to reconnect i-0978b0726c81e4fda
./jenkins.log:[09/12/19 05:35:20] SSH Launch of i-0978b0726c81e4fda on %%% completed in 3,336 ms

closed time in 2 months

jsmirnov

issue commentjenkinsci/ec2-fleet-plugin

After connection breaks, job is failing and getting resubmitted, though node is back online in some seconds.

I'm hoping the issue is resolved. Please feel free to reopen the issue with the suggested workaround doesn't work well with you.

jsmirnov

comment created time in 2 months

issue commentjenkinsci/ec2-fleet-plugin

Comparison to the Amazon EC2 Plugin?

Yes you are right. EC2 Fleet plugin supports ASG and Spot Fleet and brings all the benefits associated to it whereas EC2 Plugin uses RunInstance EC2 API which requires ad-hoc instances. In EC2 Fleet, the desired capacity of the fleet is calculated by the plugin based on the builds and other settings provided by the users and the fleet target capacity is adjusted based on it. I will keep this issue open to update README with the comparison of both the plugins so that it's helpful to others too.

jakub-bochenski

comment created time in 2 months

delete branch imuqtadir/ec2-fleet-plugin

delete branch : code-of-conduct

delete time in 2 months

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha 197c8327df96c98c01bba63311654a73061327a5

Add code of conduct (#201)

view details

push time in 2 months

PR merged jenkinsci/ec2-fleet-plugin

Add Code of Conduct

Add Amazon code of conduct

+4 -0

0 comment

1 changed file

imuqtadir

pr closed time in 2 months

PR opened jenkinsci/ec2-fleet-plugin

Add Code of Conduct

Add Amazon code of conduct

+4 -0

0 comment

1 changed file

pr created time in 2 months

create barnchimuqtadir/ec2-fleet-plugin

branch : code-of-conduct

created branch time in 2 months

push eventimuqtadir/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha e8795d2b9fef004f55c8eb39152efbd4edc4e5c0

Add CONTRIBUTING.md to project (#200)

view details

push time in 2 months

delete branch imuqtadir/ec2-fleet-plugin

delete branch : contribute-readme

delete time in 2 months

push eventjenkinsci/ec2-fleet-plugin

Abdul Muqtadir Mohammed

commit sha e8795d2b9fef004f55c8eb39152efbd4edc4e5c0

Add CONTRIBUTING.md to project (#200)

view details

push time in 2 months

PR merged jenkinsci/ec2-fleet-plugin

Add CONTRIBUTING.md to project

Added contributing instructions so it's easier for future contributors.

+71 -0

0 comment

1 changed file

imuqtadir

pr closed time in 2 months

issue closedjenkinsci/ec2-fleet-plugin

Publish CONTRIBUTING.md

Publish CONTRIBUTING.md for helping people contribute effectively and easily.

closed time in 2 months

imuqtadir

push eventimuqtadir/ec2-fleet-plugin

Artem Stasiuk

commit sha a2cc9ed1446c3fc92fdb9d980ef6bb99f6f6a4cb

[maven-release-plugin] prepare release ec2-fleet-2.1.1

view details

Artem Stasiuk

commit sha 5a04e20bf90a733dc40713b7e7d69f1209f956de

[maven-release-plugin] prepare for next development iteration

view details

Abdul Muqtadir Mohammed

commit sha 4318796d3af141d21f186f3dc060a2a3b0f65f60

Add AutoScalingGroup client test (#199) * Add tests for AutoScalingGroupFleet * Add tests for AutoScalingGroupFleet Co-authored-by: Mohammed <abdulmh@3c22fb733aef.ant.amazon.com>

view details

push time in 2 months

more