Allow to commit to Amazon Elastic Container Service (ECS / Fargate) Plugin for Jenkins

[Sumit Agarwal]

• Link to a plugin you want to adopt: https://plugins.jenkins.io/amazon-ecs/
• Link(s) to pull requests you want to deliver, if applicable: https://github.com/jenkinsci/amazon-ecs-plugin/pull/233
• Your GitHub username/id (e.g. oleg-nenashev for https://github.com/oleg-nenashev/): sumitag
• Your Jenkins infrastructure account id: agarwals

 

Thanks,

Sumit

[Gavin Mogan]

I'm (as someone who doesn't do it often) super nervous about giving access to an amazon plugin, they tend to be installed everywhere.

Have you maintained other plugins in the past? Has the original author replied at all?

Gavin

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAERz7S4TdbHte6Kp3G_a45vGAah7ne7T4wfp9D5uxyCAKtgcZA%40mail.gmail.com.

[Sumit Agarwal]

I completely understand and appreciate your nervousness. I haven’t previously supported plugins and with recent vulnerabilities due to code contributions it’s only fair.

I can use the PR build of the plugin for now to get us going.

I have also reached out to our AWS account team to ask the AWS ECS service team to become maintainers of the plugin.