date:20210126

Re: Jenkins 3.x

2021-01-26 Thread James Nord

> We do not have a fresh new massive story to share. At the same time there
could be a few changes to highlight:

   - Adoption of Configuration-as-Code as a recommended way to manage
   Jenkins.
   - Making emphasis on Jenkins-in-the-cloud applications and packaging,
   with making Docker/Helm/etc. and downstream projects being promoted as
   first class citizens
   - Something else?


There is k8s bits that did not exist in the past now.  The cloud auto
provisioning of agents, some community helm charts (and I think a k8s
operator, but I have never used it as CloudBees has a different
implementation).
There is soon (thanks to a PR) shotly going to be k8s secret support for
both global and secret credentials (so mix C-asC and K8s in one)... (I
should possibly do a blog post on that!)

/James

On Tue, 26 Jan 2021 at 11:26, Oleg Nenashev  wrote:

> Marketing releases are indeed something we could consider. The next LTS
> baseline selection starts this week, with ETA in early April. This release
> will include a number of serious changes, and generally 3.0 might be
> justified from the technical point of view. At the same time, it IMHO
> requires a more fundamental change in Jenkins itself and its usage
> paradigm. For example, in Jenkins 2 we were mostly promoting Jenkins
> Pipeline and a few other related features, not the plugin unbundling as a
> breaking change. If the whole point is about marketing, we need to prepare
> well and to coordinate the rollout with CDF and key vendors so that we have
> a big marketing push.
>
> We do not have a fresh new massive story to share. At the same time there
> could be a few changes to highlight:
>
>- Adoption of Configuration-as-Code as a recommended way to manage
>Jenkins.
>- Making emphasis on Jenkins-in-the-cloud applications and packaging,
>with making Docker/Helm/etc. and downstream projects being promoted as
>first class citizens
>- Something else?
>
> Anyway, I am not sure about taking the next LTS as 3.0. Tables to divs
> story is likely to be a problem for users due to regressions in various
> in-house and not popular plugins which have not been fixed yet. Thanks to
> Tim, Raihaan, Felix and many other contributors for the cleanup, but I
> doubt it will be as smooth as Jenkins 1->2 upgrade for the users.
>
> Best regards,
> Oleg
>
> P.S: If we do a major release, it would be awesome to get the terminology
> cleanup finished at least for the Jenkins core and major plugins. Taking
> our announcements this summer, this is not the topic we should roll over to
> Jenkins 3.
>
>
> On Monday, January 25, 2021 at 6:53:59 PM UTC+1 msi...@cloudbees.com
> wrote:
>
>> That's a good point. I still see people who don't know about pipelines
>> even though they've been around since Jenkins 2.0 IIRC. The updated UI
>> is also less well known.
>>
>> On Fri, Jan 22, 2021 at 9:23 PM Ming Tang  wrote:
>> >
>> > I think the release of Jenkins 3.x is very urgent. Let me put forward
>> another very important reason: companies and users are abandoning Jenkins.
>> Jenkins 2.x has a history of 5 years. In the past 5 years, Jenkins 2.x has
>> many major features and incompatible modifications. The obsolescence,
>> update, and requirements for higher versions of Jenkins core require
>> constant upgrading of Jenkins and modification of the configuration. This
>> is in the view of the end user (administrator) of Jenkins, but it is a toss
>> in the view of the leader. Small versions usually mean small changes. For
>> the leaders of Jenkins administrators, Jenkins 2.x is something that hasn't
>> changed a lot for many years, but it requires labor-intensive maintenance
>> and repeated exploration. The minor version upgrade hides the value of the
>> new version of Jenkins! News organizations do not pay attention to minor
>> version updates, and the leadership does not care about minor version
>> updates. Only the Jenkins administrator knows what Jenkins has updated!
>> Enterprises and users have begun to consider abandoning Jenkins! ! We need
>> to let the outside know that Jenkins is undergoing major changes, not that
>> it has not released a major version for 5 years.
>> >
>> > 在2020年12月3日星期四 UTC+8 上午2:02:20 写道：
>> >>
>> >> Interesting, first I had seen Revapi. Would be worth checking whether
>> >> it can replace japicmp in `jenkinsci/jenkins`, which I introduced as
>> >> part of JEP-227 but had to patch in order to properly handle
>> >> POM/classpath changes (and unfortunately that patch remains
>> >> unevaluated).
>> >
>> > --
>> > 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/9d0ad61c-e63e-47d5-9034-1b648e002198n%40googlegroups.com.
>>
>>
>>
>>
>> --
>> Matt Sicker
>> Senior Software

Re: Hosting requests for similar projects

2021-01-26 Thread Jesse Glick

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

[Event]: cdCON CFP is open

2021-01-26 Thread Alyssa Tong

Hi All,

The Continuous Delivery Foundation is hosting its annual cdCON in June
23-24, 2021 and they are looking for talks on Jenkins, CI CD, etc.  The
(free) registration 
and CFP are open:

   - Early Bird Submission* Deadline: Friday, February 19 by 11:59 PM PST
   - CFP Closes: Friday, March 5 at 11:59 PM PST
   - Submit my talk 

* (5) CFP submissions will be selected and highlighted as Early Bird picks
by the program committee from all talks submitted by the February 19
deadline. Talk submissions not selected as Early Bird picks will still be
considered for the final agenda.

Thnx,
alyssa

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNawQnwFtjxPrbkrftfLRwc9zYSEyDaYP0-cnJsJQkmo8cg%40mail.gmail.com.

Re: Hosting requests for similar projects

2021-01-26 Thread 'Gavin Mogan' via Jenkins Developers

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,  wrote:

> Any other feedback for this?
>
> On Tue, Dec 22, 2020 at 12:01 PM Tim Jacomb  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  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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusGXue9TcCAOpzWT2HNnoGte%3DgwQ61K62GySgm4oAwbDA%40mail.gmail.com.

Re: Has anyone implemented OpenTelemetry or similar observability APIs in Jenkins?

2021-01-26 Thread Matt Sicker

Hey, great to see you again, Cyrille!

This sounds interesting. I'm still not a fan of their enormous
dependency stack, but I'm sure it's sufficient for prototyping. :)

On Tue, Jan 12, 2021 at 2:52 AM 'Cyrille Le Clerc' via Jenkins
Developers  wrote:
>
> Hello Matt,
>
> For Your Information
>
> I'm writing a PoC to instrument Jenkins with OpenTelemetry.
>
> code: https://github.com/cyrille-leclerc/opentelemetry-plugin
>
> My focus for the moment is tracing the execution of jobs with OpenTelemetry 
> distributed traces
>
> I have a glitch for which I am asking for help on 
> https://groups.google.com/g/jenkinsci-dev/c/TEMMId7vzh0
>
> I plan later down the road to instrument:
>
> Jobs with OpenTelemetry metrics and logs
> Jenkins internals with OpenTelemetry metrics and logs
>
> We could also instrument Jenkins HTTP requests as you said
>
> As OpenTelemetry is emerging as the standard for Observability / Monitoring 
> with integrations with most observability technologies, open source and 
> commercial, such as Jaeger, Elastic, Prometheus...), this integration will 
> enable CI monitoring to most Jenkins users.
>
> Cyrille
>
> On Thursday, May 7, 2020 at 12:11:37 AM UTC+2, Matt Sicker wrote:
>>
>> Site: https://opentelemetry.io/
>>
>> This seems like it could be a useful thing to integrate with,
>> particularly for Remoting-related network calls, but it could
>> potentially be extended to other HTTP client type calls and such for
>> richer tracing data. As a Jenkins admin, you'd be able to identify
>> issues in your Jenkins cluster more easily. Implemented properly, it
>> could even provide a way for users to submit traces to help debug
>> issues they find.
>>
>> I looked at their Java library, and it seems to have an absurd amount
>> of dependencies compared to a proper logging library (which has no
>> required dependencies), but the gist of attaching traces and spans to
>> requests/responses is fairly simple to implement.
>>
>> --
>> Matt Sicker
>> Senior Software Engineer, CloudBees
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/296be7c7-f98b-4f80-a3a8-f023ffb118c7o%40googlegroups.com.



-- 
Matt Sicker
Senior Software Engineer, CloudBees

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oxM1tjmFjd_7ht89vzXiq0kq6B0C%2BveAzGR7O%2Be%3DQtxuw%40mail.gmail.com.

Re: Hosting requests for similar projects

2021-01-26 Thread Slide

Any other feedback for this?

On Tue, Dec 22, 2020 at 12:01 PM Tim Jacomb  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  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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVePJo5CNLhd1HJbd71GvOXxsUHQ_K0WKeET-C%2BfdHD70g%40mail.gmail.com.

Re: Jenkins 3.x

2021-01-26 Thread Daniel Beck

The existing 1.x/2.x versioning scheme which only ever increases minor versions 
seems like it reinforces the idea that nothing is happening. Would going with a 
date-based versioning scheme help?

For example YY.nn (year and release, roughly corresponding to week in year), or 
YY.m.nn (year, month, and release). The former would even work (mostly) with 
existing assumptions around version format being 2 parts for weeklies and an 
additional third part for LTS.

Alternatively, we can do what browsers are doing and just make every release a 
top-level release. Given how frequently release this may end up looking silly 
sooner rather than later though. Browsers aren't in the hundreds yet, we've 
done it twice already.


> On 26. Jan 2021, at 12:41, fque...@cloudbees.com  
> wrote:
> 
> I would be 100% behind a change to Jenkins 3 if we do an actual major 
> release. For example, I would just nuke the current navigation system. I 
> think one major pain point is the lack of sane separation of global 
> navigation, local navigation and contextual actions. Redoing the whole 
> sidebar would affect many plugins, but it's the sort of change I'd expect 
> from a v3.
> 
> On Tuesday, January 26, 2021 at 12:25:58 PM UTC+1 Oleg Nenashev wrote:
> Marketing releases are indeed something we could consider. The next LTS 
> baseline selection starts this week, with ETA in early April. This release 
> will include a number of serious changes, and generally 3.0 might be 
> justified from the technical point of view. At the same time, it IMHO 
> requires a more fundamental change in Jenkins itself and its usage paradigm. 
> For example, in Jenkins 2 we were mostly promoting Jenkins Pipeline and a few 
> other related features, not the plugin unbundling as a breaking change. If 
> the whole point is about marketing, we need to prepare well and to coordinate 
> the rollout with CDF and key vendors so that we have a big marketing push.
> 
> We do not have a fresh new massive story to share. At the same time there 
> could be a few changes to highlight:
>   • Adoption of Configuration-as-Code as a recommended way to manage 
> Jenkins.
>   • Making emphasis on Jenkins-in-the-cloud applications and packaging, 
> with making Docker/Helm/etc. and downstream projects being promoted as first 
> class citizens
>   • Something else?
> Anyway, I am not sure about taking the next LTS as 3.0. Tables to divs story 
> is likely to be a problem for users due to regressions in various in-house 
> and not popular plugins which have not been fixed yet. Thanks to Tim, 
> Raihaan, Felix and many other contributors for the cleanup, but I doubt it 
> will be as smooth as Jenkins 1->2 upgrade for the users. 
> 
> Best regards,
> Oleg
> 
> P.S: If we do a major release, it would be awesome to get the terminology 
> cleanup finished at least for the Jenkins core and major plugins. Taking our 
> announcements this summer, this is not the topic we should roll over to 
> Jenkins 3.
> 
> 
> On Monday, January 25, 2021 at 6:53:59 PM UTC+1 msi...@cloudbees.com wrote:
> That's a good point. I still see people who don't know about pipelines 
> even though they've been around since Jenkins 2.0 IIRC. The updated UI 
> is also less well known. 
> 
> On Fri, Jan 22, 2021 at 9:23 PM Ming Tang  wrote: 
> > 
> > I think the release of Jenkins 3.x is very urgent. Let me put forward 
> > another very important reason: companies and users are abandoning Jenkins. 
> > Jenkins 2.x has a history of 5 years. In the past 5 years, Jenkins 2.x has 
> > many major features and incompatible modifications. The obsolescence, 
> > update, and requirements for higher versions of Jenkins core require 
> > constant upgrading of Jenkins and modification of the configuration. This 
> > is in the view of the end user (administrator) of Jenkins, but it is a toss 
> > in the view of the leader. Small versions usually mean small changes. For 
> > the leaders of Jenkins administrators, Jenkins 2.x is something that hasn't 
> > changed a lot for many years, but it requires labor-intensive maintenance 
> > and repeated exploration. The minor version upgrade hides the value of the 
> > new version of Jenkins! News organizations do not pay attention to minor 
> > version updates, and the leadership does not care about minor version 
> > updates. Only the Jenkins administrator knows what Jenkins has updated! 
> > Enterprises and users have begun to consider abandoning Jenkins! ! We need 
> > to let the outside know that Jenkins is undergoing major changes, not that 
> > it has not released a major version for 5 years. 
> > 
> > 在2020年12月3日星期四 UTC+8 上午2:02:20 写道： 
> >> 
> >> Interesting, first I had seen Revapi. Would be worth checking whether 
> >> it can replace japicmp in `jenkinsci/jenkins`, which I introduced as 
> >> part of JEP-227 but had to patch in order to properly handle 
> >> POM/classpath changes (and unfortunately that patch remains 
> >> unevaluated). 
> > 
> > -- 
> >

Re: Jenkins 3.x

2021-01-26 Thread fque...@cloudbees.com

I would be 100% behind a change to Jenkins 3 if we do an actual major 
release. For example, I would just nuke the current navigation system. I 
think one major pain point is the lack of sane separation of global 
navigation, local navigation and contextual actions. Redoing the whole 
sidebar would affect many plugins, but it's the sort of change I'd expect 
from a v3.

On Tuesday, January 26, 2021 at 12:25:58 PM UTC+1 Oleg Nenashev wrote:

> Marketing releases are indeed something we could consider. The next LTS 
> baseline selection starts this week, with ETA in early April. This release 
> will include a number of serious changes, and generally 3.0 might be 
> justified from the technical point of view. At the same time, it IMHO 
> requires a more fundamental change in Jenkins itself and its usage 
> paradigm. For example, in Jenkins 2 we were mostly promoting Jenkins 
> Pipeline and a few other related features, not the plugin unbundling as a 
> breaking change. If the whole point is about marketing, we need to prepare 
> well and to coordinate the rollout with CDF and key vendors so that we have 
> a big marketing push.
>
> We do not have a fresh new massive story to share. At the same time there 
> could be a few changes to highlight:
>
>- Adoption of Configuration-as-Code as a recommended way to manage 
>Jenkins.
>- Making emphasis on Jenkins-in-the-cloud applications and packaging, 
>with making Docker/Helm/etc. and downstream projects being promoted as 
>first class citizens
>- Something else?
>
> Anyway, I am not sure about taking the next LTS as 3.0. Tables to divs 
> story is likely to be a problem for users due to regressions in various 
> in-house and not popular plugins which have not been fixed yet. Thanks to 
> Tim, Raihaan, Felix and many other contributors for the cleanup, but I 
> doubt it will be as smooth as Jenkins 1->2 upgrade for the users. 
>
> Best regards,
> Oleg
>
> P.S: If we do a major release, it would be awesome to get the terminology 
> cleanup finished at least for the Jenkins core and major plugins. Taking 
> our announcements this summer, this is not the topic we should roll over to 
> Jenkins 3.
>
>
> On Monday, January 25, 2021 at 6:53:59 PM UTC+1 msi...@cloudbees.com 
> wrote:
>
>> That's a good point. I still see people who don't know about pipelines 
>> even though they've been around since Jenkins 2.0 IIRC. The updated UI 
>> is also less well known. 
>>
>> On Fri, Jan 22, 2021 at 9:23 PM Ming Tang  wrote: 
>> > 
>> > I think the release of Jenkins 3.x is very urgent. Let me put forward 
>> another very important reason: companies and users are abandoning Jenkins. 
>> Jenkins 2.x has a history of 5 years. In the past 5 years, Jenkins 2.x has 
>> many major features and incompatible modifications. The obsolescence, 
>> update, and requirements for higher versions of Jenkins core require 
>> constant upgrading of Jenkins and modification of the configuration. This 
>> is in the view of the end user (administrator) of Jenkins, but it is a toss 
>> in the view of the leader. Small versions usually mean small changes. For 
>> the leaders of Jenkins administrators, Jenkins 2.x is something that hasn't 
>> changed a lot for many years, but it requires labor-intensive maintenance 
>> and repeated exploration. The minor version upgrade hides the value of the 
>> new version of Jenkins! News organizations do not pay attention to minor 
>> version updates, and the leadership does not care about minor version 
>> updates. Only the Jenkins administrator knows what Jenkins has updated! 
>> Enterprises and users have begun to consider abandoning Jenkins! ! We need 
>> to let the outside know that Jenkins is undergoing major changes, not that 
>> it has not released a major version for 5 years. 
>> > 
>> > 在2020年12月3日星期四 UTC+8 上午2:02:20 写道： 
>> >> 
>> >> Interesting, first I had seen Revapi. Would be worth checking whether 
>> >> it can replace japicmp in `jenkinsci/jenkins`, which I introduced as 
>> >> part of JEP-227 but had to patch in order to properly handle 
>> >> POM/classpath changes (and unfortunately that patch remains 
>> >> unevaluated). 
>> > 
>> > -- 
>> > 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/9d0ad61c-e63e-47d5-9034-1b648e002198n%40googlegroups.com.
>>  
>>
>>
>>
>>
>> -- 
>> Matt Sicker 
>> Senior Software Engineer, CloudBees 
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit

Re: Jenkins 3.x

2021-01-26 Thread Oleg Nenashev

Marketing releases are indeed something we could consider. The next LTS 
baseline selection starts this week, with ETA in early April. This release 
will include a number of serious changes, and generally 3.0 might be 
justified from the technical point of view. At the same time, it IMHO 
requires a more fundamental change in Jenkins itself and its usage 
paradigm. For example, in Jenkins 2 we were mostly promoting Jenkins 
Pipeline and a few other related features, not the plugin unbundling as a 
breaking change. If the whole point is about marketing, we need to prepare 
well and to coordinate the rollout with CDF and key vendors so that we have 
a big marketing push.

We do not have a fresh new massive story to share. At the same time there 
could be a few changes to highlight:

   - Adoption of Configuration-as-Code as a recommended way to manage 
   Jenkins.
   - Making emphasis on Jenkins-in-the-cloud applications and packaging, 
   with making Docker/Helm/etc. and downstream projects being promoted as 
   first class citizens
   - Something else?

Anyway, I am not sure about taking the next LTS as 3.0. Tables to divs 
story is likely to be a problem for users due to regressions in various 
in-house and not popular plugins which have not been fixed yet. Thanks to 
Tim, Raihaan, Felix and many other contributors for the cleanup, but I 
doubt it will be as smooth as Jenkins 1->2 upgrade for the users. 

Best regards,
Oleg

P.S: If we do a major release, it would be awesome to get the terminology 
cleanup finished at least for the Jenkins core and major plugins. Taking 
our announcements this summer, this is not the topic we should roll over to 
Jenkins 3.

On Monday, January 25, 2021 at 6:53:59 PM UTC+1 msi...@cloudbees.com wrote:

> That's a good point. I still see people who don't know about pipelines
> even though they've been around since Jenkins 2.0 IIRC. The updated UI
> is also less well known.
>
> On Fri, Jan 22, 2021 at 9:23 PM Ming Tang  wrote:
> >
> > I think the release of Jenkins 3.x is very urgent. Let me put forward 
> another very important reason: companies and users are abandoning Jenkins. 
> Jenkins 2.x has a history of 5 years. In the past 5 years, Jenkins 2.x has 
> many major features and incompatible modifications. The obsolescence, 
> update, and requirements for higher versions of Jenkins core require 
> constant upgrading of Jenkins and modification of the configuration. This 
> is in the view of the end user (administrator) of Jenkins, but it is a toss 
> in the view of the leader. Small versions usually mean small changes. For 
> the leaders of Jenkins administrators, Jenkins 2.x is something that hasn't 
> changed a lot for many years, but it requires labor-intensive maintenance 
> and repeated exploration. The minor version upgrade hides the value of the 
> new version of Jenkins! News organizations do not pay attention to minor 
> version updates, and the leadership does not care about minor version 
> updates. Only the Jenkins administrator knows what Jenkins has updated! 
> Enterprises and users have begun to consider abandoning Jenkins! ! We need 
> to let the outside know that Jenkins is undergoing major changes, not that 
> it has not released a major version for 5 years.
> >
> > 在2020年12月3日星期四 UTC+8 上午2:02:20 写道：
> >>
> >> Interesting, first I had seen Revapi. Would be worth checking whether
> >> it can replace japicmp in `jenkinsci/jenkins`, which I introduced as
> >> part of JEP-227 but had to patch in order to properly handle
> >> POM/classpath changes (and unfortunately that patch remains
> >> unevaluated).
> >
> > --
> > 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/9d0ad61c-e63e-47d5-9034-1b648e002198n%40googlegroups.com
> .
>
>
>
> -- 
> Matt Sicker
> Senior Software Engineer, CloudBees
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4d5673c0-a69d-489e-a7fe-5a8545ddfccen%40googlegroups.com.

Re: Releasing JCasC support for ghprb-plugin

2021-01-26 Thread Oliver Gondža

CCing the latest appointed maintainer.

On 25/01/2021 18.55, Matt Sicker wrote:

I'd argue that without a maintainer, a plugin would be better off
archived until someone with sufficient interest to maintain it
volunteers.

We have plenty of plugins that are crucial to thousands of users with no
active maintainer. It is far from ideal, but yet the way it is.

I am concerned that if we insist of someone adopting plugins in order to
move some issue forward, we will only encourage people to make reckless
commitments and as a result have more plugins with _inactive_
maintainers appointed (since they would become maintainers to fix an
issue or two, but will not provide long term mainenance) and higher
maintainer fluctuation.

On Fri, Jan 22, 2021 at 3:05 AM ogondza wrote:

I understand it feels strange, though it is the second best thing we can do in
case we lack a maintainer.
On Wednesday, January 6, 2021 at 5:53:37 PM UTC+1 msi...@cloudbees.com wrote:

I'd prefer if this plugin has an actual maintainer. Otherwise, this
also seems like false advertising that the plugin is still supported
by anyone.

On Wed, Jan 6, 2021 at 10:45 AM 'Gavin Mogan' via Jenkins Developers
wrote:

If you do a release and there are new bugs are you going to handle them?

Without a maintainer it seems like deploying to prod and not monitoring
afterwards.

Gavin

On Wed., Jan. 6, 2021, 6:03 a.m. Marky Jackson, wrote:

Same, no objections

On Jan 6, 2021, at 6:01 AM, Mark Waite wrote:

No objections from me.

On Wed, Jan 6, 2021 at 2:18 AM Oliver Gondža wrote:

Hey, there is a long anticipated feature merged in in the plugin[1][2],
but no maintainer appears to be active to cut a release.

Are there any objections if I step in a do the release?

[1] https://github.com/jenkinsci/ghprb-plugin/pull/731
[2] https://issues.jenkins-ci.org/browse/JENKINS-55793
--
oliver

--
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/f3e65b25-477d-a780-ceae-eb8dec945f40%40gmail.com.

--
Matt Sicker
Senior Software Engineer, CloudBees

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/8c9149bf-b71b-4184-a280-2280ad1eeb66n%40googlegroups.com.

--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/a7c72c09-c9c7-2354-9434-03fb49e317fe%40gmail.com.

Re: Jenkins 3.x

Re: Hosting requests for similar projects

[Event]: cdCON CFP is open

Re: Hosting requests for similar projects

Re: Has anyone implemented OpenTelemetry or similar observability APIs in Jenkins?

Re: Hosting requests for similar projects

Re: Jenkins 3.x

Re: Jenkins 3.x

Re: Jenkins 3.x

Re: Releasing JCasC support for ghprb-plugin

10 matches

Site Navigation

Mail list logo

Footer information