EC2 Fleet Plugin Adoption

[Brady Shober]

Hi,

 

I would like to adopt a plugin:

 

    Link: https://github.com/jenkinsci/ec2-fleet-plugin

    Pull requests (optional): https://github.com/jenkinsci/ec2-fleet-plugin/pull/462

    Status: abandoned

    GitHub Username: BradyShober

    Jenkins Infrastructure ID: butter1484

    Repository Permission Updater PR: https://github.com/jenkins-infra/repository-permissions-updater/pull/4522

 

This plugin has not had a release in 2 years and I have not seen activity from the maintainers in issues and PRs. The linked PR contains a fix for an issue that was particularly impactful for us that we believe could be impacting other users of the plugin as well and we would like to make the fix available to everyone.

 

Best regards,

Brady Shober

[Basil Crow]

Hi Brady,

Thanks for stepping up to maintain this plugin. Can you please make a
best-effort attempt to reach out to someone at AWS about this? CC'ing
them on this thread should be fine. In the absence of explicit
approval from an existing maintainer, we typically wait for about two
weeks during normal work periods before proceeding with a permissions
request like this.

Once you are onboarded, please ping me, as the plugin is not currently
releasable due to its outdated parent POM.
https://github.com/jenkinsci/ec2-fleet-plugin/pull/405 (which has been
open since 2023) needs to be updated and merged as a prerequisite to
all other work on this plugin. I can help with that once you are
onboarded.

Thanks,
Basil

> --
> 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/ee8e499d-f1e7-422f-8b6b-71a15aabccc1n%40googlegroups.com.

[Brady Shober]

Hi Basil,

I've CCd 2 of the other maintainers on this reply. Our AWS TAM was going to try reaching out to one of the other maintainers internally but we haven't heard back if that was successful or not.

Thanks,

Brady

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/9KviI5BQLho/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpyarbF6uG5wQpLc1UK9URtFMm%3DHETxuKcB%3D7rSXayyjA%40mail.gmail.com.

[Brady Shober]

Hello, just wanted to give a ping here since it has been a bit over two weeks without a response from any of the other maintainers of the plugin.

Thanks,

Brady

[Basil Crow]

Thanks. I approved the repository permissions PR. Once it is merged by
a member of the hosting team, I can invite you to become a member of
the jenkinsci GitHub organization.

> To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/7881096b-7987-4ae8-adde-8f0a64844924n%40googlegroups.com.

[Basil Crow]

Hi Brady,

Looks like you've accepted the GitHub invitation. Welcome aboard!

Now that https://github.com/jenkinsci/ec2-fleet-plugin/pull/405 has
been merged, this plugin can be released manually as documented in
https://www.jenkins.io/doc/developer/publishing/releasing-manually/ —
or alternatively, you can set up automated plugin release as
documented in https://www.jenkins.io/doc/developer/publishing/releasing-cd/
(which is generally easier for new plugin maintainers).

If you are interested, it would be great if someone could update this
plugin to AWS Java SDK v2, as the AWS Java SDK v1 is going out of
support this year. See https://issues.jenkins.io/browse/JENKINS-73652
and its parent epic for more information about that topic and examples
of other AWS Jenkins plugins that have already been migrated to AWS
Java SDK v2.

Basil