Potential Revival of this Codebase

[Jacob-Steele]

Is it at all possible to revive this codebase so a new release can be done or ownership can be passed on to people who will continue to maintain it?

A new release would be great to fix the slowness of tests that fixes #109 implemented

I'd like to look into potentially adding support for Java 17, as well as fix some issues like #143 so we can bump the Jenkins versions up in our tests.

Let me know if I can do anything to help kick this process off.

Thanks,

[deblaci]

Yes it is would be nice, we are waiting for the next release since #109 fixed, we had to release it to own maven repo, but community development would be better.
We have also a stub class what implements some
Jenkins pipeline functionality(env vars, params, retry impl.) what can be incorporated to this project.

Or Are there any fork of this what actively developed?

[Jacob-Steele]

@deblaci I may wait a bit to see if any response comes in from the original authors.

If nothing comes around, I'll try and see if I can get it forked somewhere to add some more contributions to.

[balza]

@Jacob-Steele have you forked the project? If so I like give an hand.

[Jacob-Steele]

@balza No I haven't had a chance to fork this repo and attempt to revive it.

One of the reasons I wanted to attempt to revive this was due to my organization using this project to do heavy lifting in tests related to Jenkins. We were able to commit time to looking at forking and improving this repo. Unfortunately, priorities changed for my org to shift away from focusing on Jenkins to other CI/CD platforms and caused this to fall off our radar.

If anything does come of being forked on this project, I can help contribute towards it, I just don't have the personal time right now to be a key contributor in it.

[slmjy]

My org will also be interested in contributing

[balza]

@awittha do you have any suggestion??

[SaranshIam]

+1 We would like to contribute in maintaining this.

[Gengar003]

Hi, I am @awittha, however, I have left ExpediaGroup and no longer have access to the @awittha account so I can't prove that (nor manage this repository any longer). I also no longer have access to, nor use, Jenkins, so my ability to contribute meaningfully to the codebase is gone for now.

I would recommend forking the repository and all collaborating in the new one, in something not tied to a corporate employee's account... unless some other ExpediaGroup employee happens along to handle the revitalization of the codebase in this repository! (IMO, unlikely....)