Re: [JEP-229] Plugin CD workflow version scheme

['Gavin Mogan' via Jenkins Developers]

So I have next to nothing to add to this as I don't really do plugin dev or
use the cd flow yet but a few thinks I might have picked up over the years.

Afaik Jenkins has never claimed to be semver. Lots of people think plugins
are, but it's probably more often not semver than is semver

Secondly. For CD I believe the version is based on the labels applied to
PRS that get merged. If it's a major or breaking change label, different
bumping behavior vs like chore. I'm not certain though.


On Wed., Mar. 30, 2022, 11:48 a.m. Alex,  wrote:

> I am a user of both Jenkins CloudBees an OSS version. In the last months,
> the Jenkins plugins version scheme changed for a few plugins and the
> experience for Jenkins maintainers to update these plugin with confidence
> regressed.
>
> With the new CD workflow, the version change to `{digit}.{hash}` basically
> telling us that every new version is a major bump and should be treated
> like a breaking change. With such a vast plugin ecosystem and deployment
> that contains 150+  plugins, it is a headache and error-prone experience to
> bump the versions and read every "changelog".
>
> I am not opposed to the continuous delivery and automatic release of every
> commit, I am a big advocate to that approach in OSS and closed-source
> software, however, I think the new jenkins version number is problematic
> and CD should be implemented with a version number such as SemVer
> https://semver.org/
>
> I created
> https://github.com/jenkins-infra/jenkins-maven-cd-action/issues/19 for
> the issue, but I think a better place should exist to discuss JEP-229.
>
> --
> 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/6c870d41-9754-4e14-81d5-b9ff631fde78n%40googlegroups.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_Dut_fe3mdUp%3DGPBephR%3DSwbMRzXHw436chcyEn%3DEX9BRMA%40mail.gmail.com.

[JEP-229] Plugin CD workflow version scheme

[Alex]

I am a user of both Jenkins CloudBees an OSS version. In the last months, 
the Jenkins plugins version scheme changed for a few plugins and the 
experience for Jenkins maintainers to update these plugin with confidence 
regressed.

With the new CD workflow, the version change to `{digit}.{hash}` basically 
telling us that every new version is a major bump and should be treated 
like a breaking change. With such a vast plugin ecosystem and deployment 
that contains 150+  plugins, it is a headache and error-prone experience to 
bump the versions and read every "changelog".

I am not opposed to the continuous delivery and automatic release of every 
commit, I am a big advocate to that approach in OSS and closed-source 
software, however, I think the new jenkins version number is problematic 
and CD should be implemented with a version number such as 
SemVer https://semver.org/ 

I 
created https://github.com/jenkins-infra/jenkins-maven-cd-action/issues/19 
for the issue, but I think a better place should exist to discuss JEP-229.

-- 
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/6c870d41-9754-4e14-81d5-b9ff631fde78n%40googlegroups.com.

Re: Request for maintainer rights - jenkinsci/kubernetes-operator

['Gavin Mogan' via Jenkins Developers]

looks like there's an invite link to their slack on
https://jenkinsci.github.io/kubernetes-operator/

On Tue, Mar 29, 2022 at 4:07 AM Vanio Begic  wrote:
>
> Hi Gavin,
>
> thanks for your response. I was not able to submit my request via the Slack 
> mentioned there since I am unable to access it due to missing permissions.
>
> On Friday, March 25, 2022 at 3:58:51 PM UTC+1 ga...@gavinmogan.com wrote:
>>
>> It would be treated as a plugin for permission models.
>>
>> We(Jenkins) only step in to manage permissions when the plugin in question 
>> is abandoned or up for adoption.
>>
>> The operator seems pretty active although maybe not in the last 30 days.
>>
>> Have you tried reaching out via the slack they mention 
>> https://www.jenkins.io/projects/jenkins-operator/
>>
>> On Fri., Mar. 25, 2022, 7:41 a.m. Jean-Marc Meessen, 
>>  wrote:
>>>
>>> The Kubernetes Operator is not a plugin, if I am not mistaken. So what is 
>>> the process for this?
>>> (didn't find an entry in the Repository Permission Update. Might have 
>>> missed it though)
>>>
>>> Help to guide Vanio further is welcome.
>>>
>>> /- Jmm
>>>
>>> Le ven. 25 mars 2022 à 11:04, Vanio Begic  a écrit :

 Hi Community,

 there is a Jenkins Project in which I have a vested interesst, since I am 
 using it in professional setup. I am currently actively trying to 
 contribute to the project and to keep the community around it alive, but 
 it is becoming very hard as I am unable to properly address issues, pull 
 requests and releases.

 I would like to ask you to promote me to a maintainer so that I can more 
 actively contribute to the project. I have already placed my request with 
 the projet here: 
 https://github.com/jenkinsci/kubernetes-operator/issues/732

 I was asked to forward my request here, which I am now doing.

 --
 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/9df592ec-a5d9-489a-aa7c-63b8ce3c3a53n%40googlegroups.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-de...@googlegroups.com.
>>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CABLvyXy_Jd1beEOyjsRobB5F0aaP412KELtGePGWOXQwdd5CSA%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/fb7e9937-2d8c-4243-a2b3-8fb04a4ca297n%40googlegroups.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_DuvPhkUHCu%3D%2Be8h%2BQp%2BYOncku6s3HM3wqZrdRB0NKRxMMA%40mail.gmail.com.

Re: Reverting JENKINS-20679

[Mark Waite]

+1 from me as well

On Wednesday, March 30, 2022 at 6:00:20 AM UTC-6 Tim wrote:

> +1
>

-- 
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/b516634c-89fb-4d5b-a464-5dfa1d01b012n%40googlegroups.com.

Re: Intellij Stapler Framework Support compatibility

[Ullrich Hafner]

Currently 2022.1 is in beta so I think it would be save to use 2021.1 as 
minimum baseline. Stapler plugin users are developers which typically use 
latest versions rather than outdated versions. So please go ahead and change 
the baseline.

> Am 30.03.2022 um 06:41 schrieb Denys Digtiar :
> 
> I don't have much time to develop this IntelliJ plugin but at least I want to 
> keep doing some maintenance on it.
> 
> It currently raises quite a few deprecation warnings from jetbrain verifiers. 
> Also it cannot support hot reload. And latest gradle build plugin is not 
> easily usable.
> 
> All of above is due to compatibility target of IntelliJ 2016.2. It's rather 
> old. Pre Java 9. I don't think it's of much use at all on latest OS and Java 
> versions. 
> 
> Would anybody be opposed if I bump compatibility to some newer version? Maybe 
> 2020.x or something like that?
> 
> -- 
> 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/CAO%2BCqDg4z5%2BtsvXcsmi9mYwWwAxjA%3Dhgs-WGM6HLTmmPzKtvDw%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/4C9E6759-0E44-40B6-840C-169C3D77E57A%40gmail.com.

Re: Intellij Stapler Framework Support compatibility

[Tim Jacomb]

+100

On Wed, 30 Mar 2022 at 07:36, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> On Wed, Mar 30, 2022 at 6:41 AM Denys Digtiar  wrote:
>
>>
>> Would anybody be opposed if I bump compatibility to some newer version?
>> Maybe 2020.x or something like that?
>>
>> Go for it.
>
>
> As with Jenkins, if you don't update the core, you're probably not
> updating plugins either.
>
> --
> 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/CAMo7PtJmxL6O%2BDN6qaA4eK8ge4d4dFboWS8rX6zH3HV6Zp5L1Q%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-3BicWE0BA9676ePnnuN10xvV9%3DnsHsFqmu7p5iQbej4UmFQ%40mail.gmail.com.

Re: Reverting JENKINS-20679

[Tim Jacomb]

+1

On Wed, 30 Mar 2022 at 07:35, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
>
> On Wed, Mar 30, 2022 at 7:32 AM Basil Crow  wrote:
>
>>
>> > 1. IIRC I've seen plugins requiring Java 11 that just don't declare it.
>> So it's not unused because it isn't needed, but perhaps because plugin
>> authors are unaware of it?
>>
>> I am not familiar with such cases, but I seriously doubt there are
>> enough of them to justify a subsystem of this complexity. If it is
>> really the case that some plugin requires a newer JRE at runtime it
>> can just be documented in the plugin's README rather than with the
>> elaborate and hard-to-maintain subsystem that is in place now.
>>
>> > 2. Will this be replaced by a different system (assuming this is future
>> proof in principle)? Or will plugins be unable to require higher Java
>> versions than what their core baseline requires to run? Or will there be
>> surprises for admins when attempting to install such plugins? I think the
>> core support for this was essentially a warning in plugin manager.
>>
>> Yes the core support for this was essentially a warning in the plugin
>> manager, and no I am not planning on replacing this with something
>> else. Plugins will just have to evolve in lockstep with the minimum
>> Java version required by their core baseline. This is effectively the
>> case in practice everywhere I've looked, and it also seems like a
>> reasonable requirement to me
>>
>
> Makes sense. Worst case is that we change our minds a few years down the
> road and restore this subsystem. And if there's a plugin somewhere that
> uses this after all, it's basically going to be an unused entry in
> the Manifest IIRC.
>
> +1 and thanks for starting this conversation.
>
> (Just in case, I do not think a JEP is needed for what amounts to removal
> of unused code.)
>
> --
> 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/CAMo7PtLefPYhzwK%3DvDQeNGy-vJMN1B9%3DTPrbOQ9zHc0MvmH5ew%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-3Bicd5HB5eZ7Tsi5kFq%3DdL2%3DHURAHs1NJEdRZQXADu5hPNg%40mail.gmail.com.