Hosting requests for similar projects

[slide]

Hi Everyone,

Currently we have two hosting requests open (https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1048 and https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1046) for CLI tools that interact with Jenkins. I would like to get some feedback on ideas on how to move forward on these requests. They were filed nearly the same day and from my understanding provide similar features. I am not against hosting both, but would really rather have people work on one solution to make it better. 

Let me know what you think.

Regards,

Alex

--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcy%3D75a2vRdK6Vv_NVfp%2Bn%2BhoHg8LykhxvKXZ-XVNySNQ%40mail.gmail.com.

agree would be great if they could be merged

and also the jenkins core (and winstone) CLI enhanced with a more modern CLI library

On Tue, 22 Dec 2020 at 18:13, Slide <[hidden email]> wrote:

Hi Everyone,

Currently we have two hosting requests open (https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1048 and https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1046) for CLI tools that interact with Jenkins. I would like to get some feedback on ideas on how to move forward on these requests. They were filed nearly the same day and from my understanding provide similar features. I am not against hosting both, but would really rather have people work on one solution to make it better. 

Let me know what you think.

Regards,

Alex

--

Website: http://earl-of-code.com

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcy%3D75a2vRdK6Vv_NVfp%2Bn%2BhoHg8LykhxvKXZ-XVNySNQ%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biei4Dh4aii0m7KPDtAQ9B8rmuFzVDpsGW3JqLQBoQed%2BA%40mail.gmail.com.

[slide]

Any other feedback for this? 

On Tue, Dec 22, 2020 at 12:01 PM Tim Jacomb <[hidden email]> wrote:

agree would be great if they could be merged

and also the jenkins core (and winstone) CLI enhanced with a more modern CLI library

On Tue, 22 Dec 2020 at 18:13, Slide <[hidden email]> wrote:

Hi Everyone,

Currently we have two hosting requests open (https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1048 and https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1046) for CLI tools that interact with Jenkins. I would like to get some feedback on ideas on how to move forward on these requests. They were filed nearly the same day and from my understanding provide similar features. I am not against hosting both, but would really rather have people work on one solution to make it better. 

Let me know what you think.

Regards,

Alex

--

Website: http://earl-of-code.com

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcy%3D75a2vRdK6Vv_NVfp%2Bn%2BhoHg8LykhxvKXZ-XVNySNQ%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biei4Dh4aii0m7KPDtAQ9B8rmuFzVDpsGW3JqLQBoQed%2BA%40mail.gmail.com.

--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVePJo5CNLhd1HJbd71GvOXxsUHQ_K0WKeET-C%2BfdHD70g%40mail.gmail.com.

[Gavin Mogan]

I thought I replied to this a while ago. Apologies. 

I'm also not in favor of having two split projects. It's just confusing for end users and more likely to be abandoned with only a single maintainer.

My vote is either arbitrarily pick one, or get them to decide which they want to use as the main repo and co maintain it

On Tue., Jan. 26, 2021, 8:43 a.m. Slide, <[hidden email]> wrote:

Any other feedback for this? 

On Tue, Dec 22, 2020 at 12:01 PM Tim Jacomb <[hidden email]> wrote:

agree would be great if they could be merged

and also the jenkins core (and winstone) CLI enhanced with a more modern CLI library

On Tue, 22 Dec 2020 at 18:13, Slide <[hidden email]> wrote:

Hi Everyone,

Currently we have two hosting requests open (https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1048 and https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1046) for CLI tools that interact with Jenkins. I would like to get some feedback on ideas on how to move forward on these requests. They were filed nearly the same day and from my understanding provide similar features. I am not against hosting both, but would really rather have people work on one solution to make it better. 

Let me know what you think.

Regards,

Alex

--

Website: http://earl-of-code.com

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcy%3D75a2vRdK6Vv_NVfp%2Bn%2BhoHg8LykhxvKXZ-XVNySNQ%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biei4Dh4aii0m7KPDtAQ9B8rmuFzVDpsGW3JqLQBoQed%2BA%40mail.gmail.com.

--

Website: http://earl-of-code.com

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVePJo5CNLhd1HJbd71GvOXxsUHQ_K0WKeET-C%2BfdHD70g%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusGXue9TcCAOpzWT2HNnoGte%3DgwQ61K62GySgm4oAwbDA%40mail.gmail.com.

[Jesse Glick-4]

Since Jenkins already has a built-in extensible CLI, we could simply reject both `HOSTING` requests. For non-plugin repositories I see no compelling advantage to in-org hosting.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0kFCOvqvG%2Btt0_-efD46aYqN6DWKeii08vWsBb8Yhong%40mail.gmail.com.