Question/Feature Request: Full configuration as code

Hi team

I noticed that your plugin does not currently support the configuration-as-code plugin.

Looking at your README.md and at your ECSDeclarativeAgent.java class, I had the impression that this may not even be required, but I was hoping you could help me out.

What I would like to achieve is to configure the build agents cloud 100% scripted. Currently the configuration-as-code plugin is my go-to approach, falling back to groovy on the exception.

Do you have any samples where you configure your build agents as code, instead of manually entering the configuration in the Jenkins web console?

Thanks, I appreciate any help given!

[pbsladek]

@gomesp I use this plugin everyday via jcasc. Happy to help out on any specific issues you are having. Here is one of the slave configs i use. Haven’t tried the lastest, but def works fine with configuration-as-code:1.19 and has for months.

  clouds:
    - ecs: # 4cpu-8gb
        cluster: "arn:aws:ecs:${AWS_REGION}:${AWS_ACCOUNT_ID}:cluster/xxxxxx-${AWS_JENKINS_ENVIRONMENT}-jenkins-ecs-cluster"
        credentialsId: "xxxxxxx_jenkins_xxxxx_credentials"
        jenkinsUrl: ${JENKINS_HOST_URL}
        name: amz2-4cpu-8gb
        regionName: ${AWS_REGION}
        retentionTimeout: 60
        tunnel: "${JENKINS_TUNNEL_URL}:${JENKINS_SLAVE_PORT}"
        templates:
          - assignPublicIp: false
            cpu: 4096
            image: xxxxx/xxxxxxxxxxx
            label: amz2-4cpu-8gb
            launchType: EC2
            memory: 8192
            memoryReservation: 4096
            networkMode: default
            privileged: false
            remoteFSRoot: /home/jenkins
            templateName: amz2-4cpu-8gb

[webratz]

Also quite some of the delay comes from Jenkins weird internal mechanism on when to request agents. This can be changed / optimized with some system params, eg -Dhudson.slaves.NodeProvisioner.initialDelay=0 -Dhudson.slaves.NodeProvisioner.MARGIN=50 -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85