Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Jeremy T. Bouse
    @jbouse
    we only just added the JAVA_OPTS env variable to our Java8 build node configuration but that task definition has nearly 17k versions now
    Durga Sreenivas
    @sreeniwas
    Hi all

    I have an issue which is frequently am getting in my jenkins server.
    After creating some users , i was trying to get assign reole from manage jenkins.
    Once I select the Role-based strategy in "Configure global security" immediately am getting error so that could not login in to my server eventhough i have correct username and password.
    I am getting this error " HTTP ERROR 404

    Problem accessing /securityRealm/. Reason: " frequently.
    Can anybody please help me.
    _

    Suryatej Yaramada
    @yrsurya
    I think this is not right group to post for that issue
    There is anothee channel jenkins where you can get help
    This is for ecs-plugin related group
    Durga Sreenivas
    @sreeniwas
    ok but lem me know the right one
    Suryatej Yaramada
    @yrsurya
    Join the chat in jenkinsci/jenkins
    Durga Sreenivas
    @sreeniwas
    As I have launched my jenkins EC2 and getting the problem
    I already joined and sent a request . But nobody giving reply
    Finally feeling happy that someone is giving reply even it is a wrong place.
    Alex Boyd
    @aaboyd
    I just upgraded to the latest version from 1.17 and now I am seeing ECS was unable to assume the role ..., is there a simple fix for this?
    Andreas Sieferlinger
    @webratz
    hmm, that does not sound directly related.
    but there were quite a lot of fixes for things in 1.18 (which has a bug) and 1.19 beta (which works fine, altough its not yet released). so you might want to try the 1.19 beta
    Jeremy T. Bouse
    @jbouse
    Yeah 1.18 has been running much better than earlier versions since 1.15
    @webratz what's the bug in 1.18 you mention?
    Jeremy T. Bouse
    @jbouse
    I've noticed 1.18 has definitely improved the build node state... no longer shows as "suspended" while executing the build but it still appears to be creating a new task definition version even when nothing has changed
    Philipp Garbe
    @pgarbe
    The bug in 1.18 is that in some circumstances, agents couldn't be launched anymore. See the changelog for the details (https://github.com/jenkinsci/amazon-ecs-plugin/blob/master/Changelog.md#119)
    Philipp Garbe
    @pgarbe
    I just released v1.19 of the Jenkins ECS plugin
    Jeremy T. Bouse
    @jbouse
    @pgarbe did 1.19 introduce a breaking change to the ECSCloud prototype?
    Andreas Sieferlinger
    @webratz
    see https://github.com/jenkinsci/amazon-ecs-plugin/blob/master/Changelog.md#119 the slave timeout typo was corrected. so that slightly changed
    Jeremy T. Bouse
    @jbouse
    Anyone using declarative pipelines with amazon-ecs handling your build agent nodes?
    Jeremy T. Bouse
    @jbouse
    it appears that when running declarative pipelines that amazon-ecs plugin doesn't like using agent any but agent none and agent { label 'some-label' } work fine
    Philipp Garbe
    @pgarbe
    Yes, @jbouse that's correct. You've to specify the label to tell which agent should be used as they are created on demand.
    Philipp Garbe
    @pgarbe
    @/all I just released a beta (1.20-beta-2) with support of declarative agent configuration (see example in readme). Looking forward to feedback!
    There are two things that I'm thinking of and I'd be interested what you think:
    • How should values being merged with the parent configuration? Does a value in Jenkinsfile always override the parent one? What about lists? Should it be possible to restrict values (like max cpu or memory)?
    • Internally, the plugin could need some refactoring, so that it's not needed to add new properties of the TaskDefinition in multiple places. But this could be a breaking change as the configuration is not compatible anymore.
    Philipp Garbe
    @pgarbe
    @/all Anyone interested in taking over the maintainer from me?
    Marky Jackson
    @markyjackson-taulia
    @pgarbe Did you ever get a response for this?
    Pietro-G
    @Pietro-G

    it appears that when running declarative pipelines that amazon-ecs plugin doesn't like using agent any but agent none and agent { label 'some-label' } work fine

    Has there been any work-around or explanation why this must be the case?

    Pietro-G
    @Pietro-G

    Currently trying to use the plug in to connect to a AWS Fargate server to sping up a Docker Container Slave and Jenkins will not log in to a Cloud no matter what. It will constantly output ERROR: Cloud does not exist: cloud-default

    Using Jenkins Ver 2.176.1.
    Amazon EC2 Container Service Plug-in Ver 1.20

    Marky Jackson
    @markyjackson-taulia
    Let me try to reproduce this
    Pietro-G
    @Pietro-G
    @markyjackson-taulia Tyvm, i'll stand by, I also documented it here in case I did configure something wrong: jenkinsci/amazon-ecs-plugin#106
    Andreas Sieferlinger
    @webratz
    the agent any thing is known. if i remember correctly that is due to the way jenkins passes these labels to the plugins and isn’t easily fixable
    Pietro-G
    @Pietro-G
    Updated the issue which appears to be independent of using agent any
    Jeremy T. Bouse
    @jbouse
    that is my understanding as well @webratz ... agent none works but agent any does not unless you have other labels available on running agents
    Anyone confirm the behavior if no Template Name is given?
    Marky Jackson
    @markyjackson-taulia
    Looking
    Andrey Devyatkin
    @Andrey9kin
    Is anyone running ECS agents via scripted pipeline? Have a few corner cases where the ability to do so would be very handy but can't wrap my head around how to do that if is it possible at all...
    Andrey Devyatkin
    @Andrey9kin
    @markyjackson-taulia @pgarbe do you have any experience with running ECS agents from scripted pipeline? Or probably should ask if this is possible to start with?
    Marky Jackson
    @markyjackson-taulia
    It is possible but it is ugly. I would have to dig up that code
    Andrey Devyatkin
    @Andrey9kin
    @markyjackson-taulia that would help a lot. Going to wrap ugliness into a shared library so no one won't notice ;)
    Marky Jackson
    @markyjackson-taulia
    Hehe, I will look once I am out of the current meeting
    Andrey Devyatkin
    @Andrey9kin
    Thanks!
    Christian Bongiorno
    @chb0github
    Does anyone have a working pipeline script with ECS? I get the dread: cloud-default error. I even created a cloud call "cloud-default'
    Bernhard Lenz
    @BernhardLenz
    Is there a way to restrict a specific jenkins user a cloud or template? The goal is to have e.g. qa users use different AIM roles than dev users ...
    Christian Bongiorno
    @chb0github
    @BernhardLenz i know you can put permissions on certain nodes but in the case of the ec2 plugin, the nodes are ephemeral. You would need a custom authorizor.
    But maybe you could do this:
    Restrict users to a certain folder. Use the folder properties plugin to inject the template name or label they can use as an env var (that template has your IAM setup for them). Then, the label for their agent is derived at runtime. You are basically holding back the DNA needed to build
    Keep the labels random to thwart guessing. Rotate occasionally
    Not perfect, but it should get you 90% there
    maisumhaider
    @maisumhaider
    Hi all,
    I am running into some issue with the ECS plugin. I am trying to run a task in a cluster with a Auto Scalability group attached as default capacity provider. When I run the jenkins job it is unable to spawn a new instance from ASG. What am I missing ???