Re: Interested to become a Maintainer

[Mohammed Abdullah]

Thanks for the warm welcome Gavin, Mark and Jmm. I will go through all the 
videos and docs, I am sure I will find my answers in there, thanks for 
sharing. 

I have submitted my PR2409 
 , 
hopefully it will get approved soon and I will remove the "up for adoption 
tag"

Also, Mark, last month I saw your talk at the Contributor Summit 
,  it is a phenomenal way of 
getting people interested (me included)! :)

On Wednesday, February 23, 2022 at 3:03:27 PM UTC+5:30 Jean-Marc Meessen 
wrote:

> Hello Mohammed,
>
> Thank you for stepping forward to adopt this plugin: it deserves indeed 
> some attention and care. And it is a good way to learn about Jenkins.
> The description of the plugin adoption process is here: 
> https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/  
>
> Don't hesitate to ask for help here (adoption, coding, etc).
>
> > "*but thought it would be better to get more information before doing 
> anything*"
> Do you have a particular doubt you would like to have clarifications on?
>
> /- Jmm
>
> Le mar. 22 févr. 2022 à 21:40, Mark Waite  a écrit :
>
>>
>>
>> On Tuesday, February 22, 2022 at 1:06:50 PM UTC-7 you wrote:
>>
>>> Hi All,
>>>
>>>   I have been a Jenkins Admin and User for more than 5 years now. I 
>>> would love to contribute to better the tool and part of this journey.
>>>
>>>   I came across the "Adopt a Plugin" initiative a couple of years ago 
>>> but my lack of knowledge in development kept me at bay. 
>>>
>>>   I have decided to give it a shot now, I would like to start with a 
>>> plugin which I think I can handle and go on from there.
>>>
>>> *DETAILS AS REQUESTED:*
>>> 1. https://plugins.jenkins.io/global-post-script/
>>> 2. It is up for Adoption
>>> 3. All open tickets for this one
>>> 4. https://github.com/mhmdabdh
>>> 5. abie_in
>>> 6. Well I tried to create a pull request on (
>>> /permissions/plugin-global-post-script.yml 
>>> )
>>>  
>>> but thought it would be better to get more information before doing 
>>> anything.
>>>
>>>
>> Thanks so much for adopting a plugin!  Create the pull request to adopt 
>> the plugin.  That's the best way to get started.
>>
>> If you're interested in a series of steps to consider, try the "Contributing 
>> to Open Source" 
>> 
>>  
>> document.  It includes text descriptions of steps and links to a five part 
>> video series:
>>
>>- 
>>
>>Part 1  - Choosing your 
>>plugin, update the parent pom, update Jenkins base version
>>- 
>>
>>Part 2  - Spotbugs, 
>>incremental builds, dependency updates, and release drafter
>>- 
>>
>>Part 3  - Migrate 
>>docs to GitHub, add a “report an issue” link, interactive testing
>>- 
>>
>>Part 4  - Enable 
>>continuous delivery, plugin bill of materials
>>- 
>>
>>Part 5  - Topics 
>>and labels on repositories, resolving security scan reports
>>
>> Many of the topics in the document are not covered in the video series.  
>> If you find mistakes in the document, please suggest corrections so that we 
>> can include the corrections in the pull request that will eventually be 
>> completed on www.jenkins.io.
>>
>> Mark Waite 
>>
>> -- 
>> 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/f31ba744-a691-43ef-868f-b73cdd4dd803n%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/2937513e-2737-4b69-a13f-20d849018e19n%40googlegroups.com.

Re: Linux installers for Jenkins 2.332.1 LTS

[Basil Crow]

While the System V init code from 2.333 and earlier is the least
likely to surprise us, it remains full of long-standing bugs
(including JENKINS-65809) and depends on third-party daemonization
packages, one of which is not available at all in Fedora EPEL 9. This
code has caused and continues to cause significant pain for users, and
this pain has increased in recent Debian and Red Hat-based
distributions. In my opinion, this code has outlived its usefulness.

The systemd-based packaging first introduced in 2.335 has been
shipping for two weeks without issue. This code fixes a number of
long-standing bugs and improves integration between Jenkins and the
service manager. It also eliminates a number of fragile shell scripts
in favor of a declarative service configuration file. This should
prove easier to support in the unlikely case that there are issues.
Migration from the old configuration format is fully automated and has
been tested in a variety of configurations.

The System V init code from 2.334 is a compromise between these
choices that, in my opinion, would please nobody. True, it addresses
the biggest deficiencies of the old implementation, including
JENKINS-65809 and the Fedora EPEL 9 issue. Yet, it has been tested the
least (only one week) and retains a number of existing issues. Because
of its reliance on fragile shell scripts, this code is difficult to
support. If there are issues with it, the arduous task of supporting
users would end up being throwaway work, as the entire implementation
has changed in later releases with the introduction of systemd
support.

For these reasons, my vote is to backport the systemd code to 2.332.1
LTS. Although this does not meet the usual criteria for backports, I
believe that the benefits mentioned above outweigh the risks.

-- 
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/CAFwNDjrU5iM_6Cx4DXPBh2rUqYKSst%3DhemBGKaBLkyoVA%2B6ymA%40mail.gmail.com.

Re: Automated plugin release failing on 'check interesting categories' step

[Alex]

I got it working by exchanging the GitHub token in the workflow with a PAT: 
https://github.com/jenkinsci/purge-build-queue-plugin/commit/3e0e709bf62ec15a84d5bf4e2e81a98ace7b79bf

I guess, GitHub either changed or broke something (both I'm currently 
unaware of), because the regular GH token suffices and grants read/write 
perms to all scopes, unless you change the workflow permission to read only 
for content, but that doesn't apply here. 
Alex schrieb am Donnerstag, 24. Februar 2022 um 23:57:39 UTC+1:

> To amend my comment on the dark-theme-plugin PR, I got the action somewhat 
> of working by wiping the additional drafts and keeping one that covers all.
> I'm using release-drafter via GitHub actions outside of Jenkins too and 
> have repositories with several drafts with different entries, so I'm not 
> sure whether that is an actual issue with CD or GH actions/release-drafter 
> itself.
> However, I didn't make it as far as Tim, because the "release" step fails 
> with a 403 on deployment for me. That failure creates a new draft and we're 
> basically back at step one.
>
>
> timja...@gmail.com schrieb am Donnerstag, 24. Februar 2022 um 23:18:30 
> UTC+1:
>
>> We were just discussing this here:
>>
>> https://github.com/jenkinsci/dark-theme-plugin/pull/170#issuecomment-1050263227
>>
>> By using a manual trigger to bypass the interesting category check and 
>> publishing the release notes myself I was able to get the release out
>>
>> On Thu, 24 Feb 2022 at 22:06, José Lamas Ríos  wrote:
>>
>>> Maybe unrelated but I've just noticed that the release draft 
>>> 
>>>  
>>> that was just created and is listed as the most recent one but shows a Dec 
>>> 10 2021 date...
>>>
>>> There is in fact another release 
>>>  on that 
>>> date that is not in draft state but (probably due to some error on my part) 
>>> got published while keeping the 'next' tag / name.
>>>
>>> I'll later try renaming or deleting the old release and check if that 
>>> fixes the problem. 
>>>
>>>
>>>
>>>
>>> On Thursday, February 24, 2022 at 6:52:46 PM UTC-3 José Lamas Ríos wrote:
>>>
 Hi, 

 I'm having problems with the automated release workflow for 
 genexus-plugin .

 For instance, this CD run at 
 https://github.com/jenkinsci/genexus-plugin/runs/5325279945

 After the successful build it gets to create the release draft, but 
 then seems to fail at finding it with an interesting category, so the 
 release is not fired.

 The draft release was created at 
 https://github.com/jenkinsci/genexus-plugin/releases/tag/untagged-1934fa52b049ad8ace3d
  
 and running these commands on my terminal does seem to work:

 McJLR:~jlr$ RESULT=$(gh api /repos/jenkinsci/genexus-plugin/releases | 
 jq -e -r '.[] | select(.draft == true and .name == "next") | .body' | 
 egrep 
 "$INTERESTING_CATEGORIES" || echo 'failed')

 McJLR:~ jlr$ echo $RESULT

 ##  Bug fixes


 Any ideas?

 Thanks in advance,




 -- 
>>> 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/c742b7c1-e2e2-456a-a6ab-d2a56f76fb36n%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/badbb90d-1358-48c4-809a-0462c08c9c00n%40googlegroups.com.

Re: Linux installers for Jenkins 2.332.1 LTS

[Mark Waite]

On Thursday, February 24, 2022 at 3:20:52 PM UTC-7 Mark Waite wrote:

> I propose that we use the systemd Linux installers for Jenkins 2.332.1.
>
> The Linux installers for Jenkins 2.335 and Jenkins 2.336 weekly releases 
> use systemd instead of System V init.  They include migration steps that 
> read the existing System V init script settings and convert them to systemd 
> override configuration settings.
>
> The systemd service has been the default and preferred system and service 
> manager on most Linux distributions for many years.  Jenkins use of systemd 
> unifies the service management method across all three of our Linux 
> installers and allows us to describe configuration actions for Debian, Red 
> Hat, and SUSE installers with a single set of instructions.
>
> The systemd implementation resolves the following known issues with the 
> installers:
>
>- JENKINS-41218 -  Switch Linux installers from System V init to 
>systemd
>- JENKINS-65809 -  Restart the Jenkins service after plugin updates on 
>Debian 11 (bullseye)
>- JENKINS-56219 -  Restart systemd service when the controller exits 
>unexpectedly
>- JENKINS-31656 - Return zero from RPM init script on successful stop
>- JENKINS-67487 -  Correctly report startup result on Amazon Linux 2 
>installed with the rpm package
>- JENKINS-67404 - Do not fail startup with timeout on systems with 
>slow DNS resolution
>
> We prefer to introduce infrastructure changes like this one on the first 
> release in an LTS series and we like to have some experience with the 
> change in weekly before the LTS release.
>
> If we choose to not use systemd for the 2.332.1 release, then the current 
> configuration of the 2.332.1 Linux installer will use the Linux installer 
> from 2.334.  That installer is a variant of the System V Linux installer 
> but without the requirement for the `daemon` program on Debian or the 
> `daemonize` program on Red Hat and SUSE.  It was only available in one 
> weekly release before it was superseded by the installer based on systemd.
>
> Our choices are:
>
>1. Use systemd installer from 2.335 and 2.336 in 2.332.1
>2. Use System V init installer from 2.334 (no dependency on daemon 
>program)
>3. Use System V init installer from 2.333 and earlier
>
> We'll need additional documentation for managing services with systemd.  
> Basil Crow and I are willing to work on that documentation.
>
> We'll need entries in the upgrade guide for the systemd transition.  I'm 
> willing to work on that with Basil's help.
>
> Comments and concerns are welcomed,
>

I missed another impact if we choose to use the systemd installer.  There 
changes in the 2.335 Jenkins weekly to support the systemd notify system.  
Those changes would need to be included in the 2.332.1 backports for 
Jenkins core.  Pull requests 
are https://github.com/jenkinsci/jenkins/pull/6228 
and https://github.com/jenkinsci/jenkins/pull/6237
 

> Mark Waite
>

-- 
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/12d1d622-0dac-4902-8c9d-b7f3a19615bdn%40googlegroups.com.

Re: Automated plugin release failing on 'check interesting categories' step

[Alex]

To amend my comment on the dark-theme-plugin PR, I got the action somewhat 
of working by wiping the additional drafts and keeping one that covers all.
I'm using release-drafter via GitHub actions outside of Jenkins too and 
have repositories with several drafts with different entries, so I'm not 
sure whether that is an actual issue with CD or GH actions/release-drafter 
itself.
However, I didn't make it as far as Tim, because the "release" step fails 
with a 403 on deployment for me. That failure creates a new draft and we're 
basically back at step one.


timja...@gmail.com schrieb am Donnerstag, 24. Februar 2022 um 23:18:30 
UTC+1:

> We were just discussing this here:
>
> https://github.com/jenkinsci/dark-theme-plugin/pull/170#issuecomment-1050263227
>
> By using a manual trigger to bypass the interesting category check and 
> publishing the release notes myself I was able to get the release out
>
> On Thu, 24 Feb 2022 at 22:06, José Lamas Ríos  wrote:
>
>> Maybe unrelated but I've just noticed that the release draft 
>> 
>>  
>> that was just created and is listed as the most recent one but shows a Dec 
>> 10 2021 date...
>>
>> There is in fact another release 
>>  on that 
>> date that is not in draft state but (probably due to some error on my part) 
>> got published while keeping the 'next' tag / name.
>>
>> I'll later try renaming or deleting the old release and check if that 
>> fixes the problem. 
>>
>>
>>
>>
>> On Thursday, February 24, 2022 at 6:52:46 PM UTC-3 José Lamas Ríos wrote:
>>
>>> Hi, 
>>>
>>> I'm having problems with the automated release workflow for 
>>> genexus-plugin .
>>>
>>> For instance, this CD run at 
>>> https://github.com/jenkinsci/genexus-plugin/runs/5325279945
>>>
>>> After the successful build it gets to create the release draft, but then 
>>> seems to fail at finding it with an interesting category, so the release is 
>>> not fired.
>>>
>>> The draft release was created at 
>>> https://github.com/jenkinsci/genexus-plugin/releases/tag/untagged-1934fa52b049ad8ace3d
>>>  
>>> and running these commands on my terminal does seem to work:
>>>
>>> McJLR:~jlr$ RESULT=$(gh api /repos/jenkinsci/genexus-plugin/releases | 
>>> jq -e -r '.[] | select(.draft == true and .name == "next") | .body' | egrep 
>>> "$INTERESTING_CATEGORIES" || echo 'failed')
>>>
>>> McJLR:~ jlr$ echo $RESULT
>>>
>>> ##  Bug fixes
>>>
>>>
>>> Any ideas?
>>>
>>> Thanks in advance,
>>>
>>>
>>>
>>>
>>> -- 
>> 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/c742b7c1-e2e2-456a-a6ab-d2a56f76fb36n%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/08c4d988-48c9-4332-b649-0c38d8596412n%40googlegroups.com.

Re: Governance meeting Feb 23, 2022

['Jesse Glick' via Jenkins Developers]

On Wed, Feb 23, 2022 at 6:46 PM Slide  wrote:

> Windows installers have issues with versions like this


Interesting. In general native packagings may have to process the version
number to follow specific conventions or restrictions.

The product version is already mangled to support LTS releases, it might
> get confusing as to what version is installed if we have to mangle more.


Indeed a native package version ought to at least visually include the true
(Maven) version.

-- 
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/CANfRfr1ivR9LXjmrJdGfkDpPGSueXLX4TimBKmF9%3DNXme-UtKg%40mail.gmail.com.

Re: Governance meeting Feb 23, 2022

['Gavin Mogan' via Jenkins Developers]

Technical limitations is why we talked about at a high level, and
looking to create a JEP first

> Or format as a date, like 2022.02.23, so we can issue up to one release a 
> day. Or drop MRP and use CD versions…

how would lts work? 2022.02.23.1? I think that'll confuse a lot of
version parsers.

Maybe we should go IPV6 when that happens (cause 4 periods = IPv4
..okay I'll see myself out)

> ProductVersion Property is defined as [0-255].[0-255].[0-65535] ( 8,8,16 
> signed bit respectively) File Version is defined as 
> [0-65535].[0-65535].[0-65535].[0-65535] ( 16,16,16,16 signed bit... )
22.03.01 would still work then,  as would 22.03.01.1 since the .1
would be just fileversion? I don't know?

On Wed, Feb 23, 2022 at 3:46 PM Slide  wrote:
>>>
>>>
>>> Version number to yearly?
>>>
>>> Starting in with 23.01 being the first week of the year 2023
>>>
>>> Harder to skip/reissue/etc a release
>>
>> Or format as a date, like 2022.02.23, so we can issue up to one release a 
>> day. Or drop MRP and use CD versions…
>
>
> Windows installers have issues with versions like this, there are limits on 
> how high the major/minor/build version can go.
>
> FileVersions and ProductVersions are unrelated. ProductVersion is shown in 
> Add/Remove Programs ( Programs and Features ) and is mainly used during Major 
> Upgrade scenarios to decide what should happen.
>
> ProductVersion Property is defined as [0-255].[0-255].[0-65535] ( 8,8,16 
> signed bit respectively) File Version is defined as 
> [0-65535].[0-65535].[0-65535].[0-65535] ( 16,16,16,16 signed bit... )
>
>
> The product version is already mangled to support LTS releases, it might get 
> confusing as to what version is installed if we have to mangle more.
>
> --
> 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/CAPiUgVc1HtMoz32xGzaKix8Hh5Ce3SZzGy%3DGxJHbqy_tezEuzw%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_Duvdr4vnsKiRt%3DG0vR6Q3zSGGdqG%2BOZe79ScSNb-qexfOg%40mail.gmail.com.

Linux installers for Jenkins 2.332.1 LTS

[Mark Waite]

I propose that we use the systemd Linux installers for Jenkins 2.332.1.

The Linux installers for Jenkins 2.335 and Jenkins 2.336 weekly releases 
use systemd instead of System V init.  They include migration steps that 
read the existing System V init script settings and convert them to systemd 
override configuration settings.

The systemd service has been the default and preferred system and service 
manager on most Linux distributions for many years.  Jenkins use of systemd 
unifies the service management method across all three of our Linux 
installers and allows us to describe configuration actions for Debian, Red 
Hat, and SUSE installers with a single set of instructions.

The systemd implementation resolves the following known issues with the 
installers:

   - JENKINS-41218 -  Switch Linux installers from System V init to systemd
   - JENKINS-65809 -  Restart the Jenkins service after plugin updates on 
   Debian 11 (bullseye)
   - JENKINS-56219 -  Restart systemd service when the controller exits 
   unexpectedly
   - JENKINS-31656 - Return zero from RPM init script on successful stop
   - JENKINS-67487 -  Correctly report startup result on Amazon Linux 2 
   installed with the rpm package
   - JENKINS-67404 - Do not fail startup with timeout on systems with slow 
   DNS resolution

We prefer to introduce infrastructure changes like this one on the first 
release in an LTS series and we like to have some experience with the 
change in weekly before the LTS release.

If we choose to not use systemd for the 2.332.1 release, then the current 
configuration of the 2.332.1 Linux installer will use the Linux installer 
from 2.334.  That installer is a variant of the System V Linux installer 
but without the requirement for the `daemon` program on Debian or the 
`daemonize` program on Red Hat and SUSE.  It was only available in one 
weekly release before it was superseded by the installer based on systemd.

Our choices are:

   1. Use systemd installer from 2.335 and 2.336 in 2.332.1
   2. Use System V init installer from 2.334 (no dependency on daemon 
   program)
   3. Use System V init installer from 2.333 and earlier

We'll need additional documentation for managing services with systemd.  
Basil Crow and I are willing to work on that documentation.

We'll need entries in the upgrade guide for the systemd transition.  I'm 
willing to work on that with Basil's help.

Comments and concerns are welcomed,
Mark Waite

-- 
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/45c8299c-831a-41b5-9fcf-2ff4ff6491e7n%40googlegroups.com.

Re: Automated plugin release failing on 'check interesting categories' step

[Tim Jacomb]

We were just discussing this here:
https://github.com/jenkinsci/dark-theme-plugin/pull/170#issuecomment-1050263227

By using a manual trigger to bypass the interesting category check and
publishing the release notes myself I was able to get the release out

On Thu, 24 Feb 2022 at 22:06, José Lamas Ríos  wrote:

> Maybe unrelated but I've just noticed that the release draft
> 
> that was just created and is listed as the most recent one but shows a Dec
> 10 2021 date...
>
> There is in fact another release
>  on that
> date that is not in draft state but (probably due to some error on my part)
> got published while keeping the 'next' tag / name.
>
> I'll later try renaming or deleting the old release and check if that
> fixes the problem.
>
>
>
>
> On Thursday, February 24, 2022 at 6:52:46 PM UTC-3 José Lamas Ríos wrote:
>
>> Hi,
>>
>> I'm having problems with the automated release workflow for
>> genexus-plugin .
>>
>> For instance, this CD run at
>> https://github.com/jenkinsci/genexus-plugin/runs/5325279945
>>
>> After the successful build it gets to create the release draft, but then
>> seems to fail at finding it with an interesting category, so the release is
>> not fired.
>>
>> The draft release was created at
>> https://github.com/jenkinsci/genexus-plugin/releases/tag/untagged-1934fa52b049ad8ace3d
>> and running these commands on my terminal does seem to work:
>>
>> McJLR:~jlr$ RESULT=$(gh api /repos/jenkinsci/genexus-plugin/releases | jq
>> -e -r '.[] | select(.draft == true and .name == "next") | .body' | egrep
>> "$INTERESTING_CATEGORIES" || echo 'failed')
>>
>> McJLR:~ jlr$ echo $RESULT
>>
>> ##  Bug fixes
>>
>>
>> Any ideas?
>>
>> Thanks in advance,
>>
>>
>>
>>
>> --
> 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/c742b7c1-e2e2-456a-a6ab-d2a56f76fb36n%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/CAH-3BifGXQWeFtwr-PievtCgyPKaruhEpXTpcDGHg%2B4ezUdhRg%40mail.gmail.com.

Re: Automated plugin release failing on 'check interesting categories' step

[José Lamas Ríos]

Maybe unrelated but I've just noticed that the release draft 

 
that was just created and is listed as the most recent one but shows a Dec 
10 2021 date...

There is in fact another release 
 on that 
date that is not in draft state but (probably due to some error on my part) 
got published while keeping the 'next' tag / name.

I'll later try renaming or deleting the old release and check if that fixes 
the problem. 




On Thursday, February 24, 2022 at 6:52:46 PM UTC-3 José Lamas Ríos wrote:

> Hi, 
>
> I'm having problems with the automated release workflow for genexus-plugin 
> .
>
> For instance, this CD run at 
> https://github.com/jenkinsci/genexus-plugin/runs/5325279945
>
> After the successful build it gets to create the release draft, but then 
> seems to fail at finding it with an interesting category, so the release is 
> not fired.
>
> The draft release was created at 
> https://github.com/jenkinsci/genexus-plugin/releases/tag/untagged-1934fa52b049ad8ace3d
>  
> and running these commands on my terminal does seem to work:
>
> McJLR:~jlr$ RESULT=$(gh api /repos/jenkinsci/genexus-plugin/releases | jq 
> -e -r '.[] | select(.draft == true and .name == "next") | .body' | egrep 
> "$INTERESTING_CATEGORIES" || echo 'failed')
>
> McJLR:~ jlr$ echo $RESULT
>
> ##  Bug fixes
>
>
> Any ideas?
>
> Thanks in advance,
>
>
>
>
>

-- 
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/c742b7c1-e2e2-456a-a6ab-d2a56f76fb36n%40googlegroups.com.

Automated plugin release failing on 'check interesting categories' step

[José Lamas Ríos]

Hi, 

I'm having problems with the automated release workflow for genexus-plugin 
.

For instance, this CD run at 
https://github.com/jenkinsci/genexus-plugin/runs/5325279945

After the successful build it gets to create the release draft, but then 
seems to fail at finding it with an interesting category, so the release is 
not fired.

The draft release was created 
at 
https://github.com/jenkinsci/genexus-plugin/releases/tag/untagged-1934fa52b049ad8ace3d
 
and running these commands on my terminal does seem to work:

McJLR:~jlr$ RESULT=$(gh api /repos/jenkinsci/genexus-plugin/releases | jq 
-e -r '.[] | select(.draft == true and .name == "next") | .body' | egrep 
"$INTERESTING_CATEGORIES" || echo 'failed')

McJLR:~ jlr$ echo $RESULT

##  Bug fixes


Any ideas?

Thanks in advance,




-- 
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/00fd5ecb-518c-43a1-85a5-39398a49effcn%40googlegroups.com.

Re: regarding enabling automated plugin release for extended-choice-parameter plugin

[vimil saju]

Thanks Tim, this helps a lot.

Thanks
Vimil

On Thu, Feb 24, 2022 at 10:47 AM Tim Jacomb  wrote:

> Should work now, I can confirm secrets are there too
>
> On Thu, 24 Feb 2022 at 18:44, vimil saju  wrote:
>
>> Hi Gavin,
>> The link I put in the email was incorrect but the issue is still present.
>> https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions
>> still gives a  404. I think I need admin access to that repo to see the
>> settings for the plugin repo. Could you let me know how I can get admin
>> access?
>>
>> Thanks
>> Vimil
>>
>> On Thu, Feb 24, 2022 at 9:16 AM 'Gavin Mogan' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>> the link you posted to the mailing list goes to "your-plugin" not
>>> "extended-choice-parameter-plugin", is that intentional?
>>>
>>> On Thu, Feb 24, 2022 at 9:03 AM vimil saju  wrote:
>>> >
>>> > Hi,
>>> > I am trying to enable automated plugin release for
>>> extended-choice-parameter plugin. I am following the document
>>> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ but I am
>>> stuck on step 3.
>>> >
>>> > step 3 says to check
>>> https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions
>>> >
>>> > however I am getting a 404 when accessing that url.
>>> >
>>> > Any help regarding this would be appreciated
>>> >
>>> > Thanks
>>> > Vimil
>>> >
>>> > --
>>> > 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/CAFyP1Djfmn3PqAx0CeP371k5gCoL6TYW0azcHhSSTBMMrQCKRg%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_DuvbUHm-3%2Bb5gOFngfsTyav5vng0AFPkDm17tW%2BBX0Bvkw%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/CAFyP1Dgxi3DPTJV6p3VSWdSvZgYBWZw%3DS%2BV5SNRzS2qt2E6vhw%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-3BicbWv874poiHo5BYQXP%3DLbzBp1Eimy%2BAqnspTv9wq%3DwGw%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/CAFyP1DiLTLGhdrfceGmO7kDU3xcRGZ548xhxn%3D9-xzdBMfPgmA%40mail.gmail.com.

Re: regarding enabling automated plugin release for extended-choice-parameter plugin

[Tim Jacomb]

Should work now, I can confirm secrets are there too

On Thu, 24 Feb 2022 at 18:44, vimil saju  wrote:

> Hi Gavin,
> The link I put in the email was incorrect but the issue is still present.
> https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions
> still gives a  404. I think I need admin access to that repo to see the
> settings for the plugin repo. Could you let me know how I can get admin
> access?
>
> Thanks
> Vimil
>
> On Thu, Feb 24, 2022 at 9:16 AM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> the link you posted to the mailing list goes to "your-plugin" not
>> "extended-choice-parameter-plugin", is that intentional?
>>
>> On Thu, Feb 24, 2022 at 9:03 AM vimil saju  wrote:
>> >
>> > Hi,
>> > I am trying to enable automated plugin release for
>> extended-choice-parameter plugin. I am following the document
>> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ but I am
>> stuck on step 3.
>> >
>> > step 3 says to check
>> https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions
>> >
>> > however I am getting a 404 when accessing that url.
>> >
>> > Any help regarding this would be appreciated
>> >
>> > Thanks
>> > Vimil
>> >
>> > --
>> > 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/CAFyP1Djfmn3PqAx0CeP371k5gCoL6TYW0azcHhSSTBMMrQCKRg%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_DuvbUHm-3%2Bb5gOFngfsTyav5vng0AFPkDm17tW%2BBX0Bvkw%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/CAFyP1Dgxi3DPTJV6p3VSWdSvZgYBWZw%3DS%2BV5SNRzS2qt2E6vhw%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-3BicbWv874poiHo5BYQXP%3DLbzBp1Eimy%2BAqnspTv9wq%3DwGw%40mail.gmail.com.

Re: regarding enabling automated plugin release for extended-choice-parameter plugin

[vimil saju]

Hi Gavin,
The link I put in the email was incorrect but the issue is still present.
https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions
still gives a  404. I think I need admin access to that repo to see the
settings for the plugin repo. Could you let me know how I can get admin
access?

Thanks
Vimil

On Thu, Feb 24, 2022 at 9:16 AM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> the link you posted to the mailing list goes to "your-plugin" not
> "extended-choice-parameter-plugin", is that intentional?
>
> On Thu, Feb 24, 2022 at 9:03 AM vimil saju  wrote:
> >
> > Hi,
> > I am trying to enable automated plugin release for
> extended-choice-parameter plugin. I am following the document
> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ but I am
> stuck on step 3.
> >
> > step 3 says to check
> https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions
> >
> > however I am getting a 404 when accessing that url.
> >
> > Any help regarding this would be appreciated
> >
> > Thanks
> > Vimil
> >
> > --
> > 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/CAFyP1Djfmn3PqAx0CeP371k5gCoL6TYW0azcHhSSTBMMrQCKRg%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_DuvbUHm-3%2Bb5gOFngfsTyav5vng0AFPkDm17tW%2BBX0Bvkw%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/CAFyP1Dgxi3DPTJV6p3VSWdSvZgYBWZw%3DS%2BV5SNRzS2qt2E6vhw%40mail.gmail.com.

Re: regarding enabling automated plugin release for extended-choice-parameter plugin

['Gavin Mogan' via Jenkins Developers]

the link you posted to the mailing list goes to "your-plugin" not
"extended-choice-parameter-plugin", is that intentional?

On Thu, Feb 24, 2022 at 9:03 AM vimil saju  wrote:
>
> Hi,
> I am trying to enable automated plugin release for extended-choice-parameter 
> plugin. I am following the document 
> https://www.jenkins.io/doc/developer/publishing/releasing-cd/ but I am stuck 
> on step 3.
>
> step 3 says to check  
> https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions
>
> however I am getting a 404 when accessing that url.
>
> Any help regarding this would be appreciated
>
> Thanks
> Vimil
>
> --
> 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/CAFyP1Djfmn3PqAx0CeP371k5gCoL6TYW0azcHhSSTBMMrQCKRg%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_DuvbUHm-3%2Bb5gOFngfsTyav5vng0AFPkDm17tW%2BBX0Bvkw%40mail.gmail.com.

regarding enabling automated plugin release for extended-choice-parameter plugin

[vimil saju]

Hi,
I am trying to enable automated plugin release for
extended-choice-parameter plugin. I am following the document
https://www.jenkins.io/doc/developer/publishing/releasing-cd/ but I am
stuck on step 3.

step 3 says to check
https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions


however I am getting a 404 when accessing that url.

Any help regarding this would be appreciated

Thanks
Vimil

-- 
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/CAFyP1Djfmn3PqAx0CeP371k5gCoL6TYW0azcHhSSTBMMrQCKRg%40mail.gmail.com.

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Mark Waite]

On Thursday, February 24, 2022 at 8:54:40 AM UTC-7 Jesse Glick wrote:

> On Thu, Feb 24, 2022 at 8:42 AM Mark Waite wrote:
>
>> more exploring of potential issues related to the transition.
>>>
>>
> My main concern is about bugs, like JENKINS-59910 which no one seems to be 
> evaluating. If stuff works when run on 8 and does not work when run on 11 
> then users will not accept the upgrade.
>

Agreed.  I think that a detailed review of reported bugs is the right thing 
to do.

-- 
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/3f555bcc-c2f5-4ff9-afe0-64f884248fbbn%40googlegroups.com.

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

['Jesse Glick' via Jenkins Developers]

On Thu, Feb 24, 2022 at 8:42 AM Mark Waite 
wrote:

> more exploring of potential issues related to the transition.
>>
>
My main concern is about bugs, like JENKINS-59910 which no one seems to be
evaluating. If stuff works when run on 8 and does not work when run on 11
then users will not accept the upgrade.

-- 
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/CANfRfr2_vAA6m3BiW1MzvQdx5dq-rHi0gxeiJcEV2Gd6grRdWQ%40mail.gmail.com.

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Mark Waite]

On Friday, February 18, 2022 at 1:53:10 PM UTC-7 Tim Jacomb wrote:

> Hello
>
> https://jenkins.io/jep/236 has been integrated.
>
> Please have a read and share any thoughts.
>
> Any thoughts on us continuing as Basil suggested with the June 14 date for 
> LTS?
>
> and a weekly in the near future?
>
>
I'm not comfortable that we've reviewed the work to be done thoroughly 
enough yet.  I'd like another 2 weeks to do more exploring of potential 
issues related to the transition.

I opened a (premature) conversation in the Jenkins governance meeting 
asking if this is the time to change from major number 2 to major number 
3.  That would be similar to the way that Jetty changed from 9 to 10 when 
they began requiring Java 11 and would be similar to the way that Eclipse 
JGit switched from 5 to 6 when they began requiring Java 11.  I don't know 
if that is a common pattern in other projects, but I've seen that pattern 
in a few projects.

Mark Waite
 

-- 
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/4e4e8947-c6cc-4d00-bb33-fe421409b7f2n%40googlegroups.com.