Re: Plug-in adoption

[STEVEN CORREA]

Thank you!

On Thursday, October 26, 2023 at 3:37:35 PM UTC-5 ga...@gavinmogan.com 
wrote:

> i was gonna be snarky and say "warm body"
> honestly the willing to do it goes most of the way, review open issues, 
> close what needs to be closed
> most functionally can be done with basic functions and basic html
> complex stuff you ask for help/advice.
>
> On Thu, Oct 26, 2023 at 1:21 PM Mark Waite  wrote:
>
>> Not much. I am a manager that was a C programmer many years ago.  I have 
>> learned Java and Maven as part of Jenkins plugin maintenance and a little 
>> experience before Jenkins.
>>
>> If you are interested in learning and are willing to learn, you can adopt 
>> a plugin. 
>>
>> Technical questions to the developer list frequently get good answers.  
>> If you'd like others to review your changes,  I am sure we can find people 
>> willing to answer questions and review changes
>>
>> On Thu, Oct 26, 2023, 1:11 PM STEVEN CORREA  wrote:
>>
>>> Hello everyone -
>>>
>>> What is the minimum level of development experience needed to adopt a 
>>> plug-in?
>>>
>>> Regards,
>>> Steve
>>>
>>> -- 
>>> 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/566a1ed2-1118-412c-a67d-d568aaf6df4en%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/CAO49JtHpD5RomKdNUJ6SJ9WOwBAX6SXBRjzboCgzrxizn2SLPQ%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/1456656c-632a-4203-880f-992ac0f2e14an%40googlegroups.com.

Re: Plug-in adoption

['Gavin Mogan' via Jenkins Developers]

i was gonna be snarky and say "warm body"
honestly the willing to do it goes most of the way, review open issues,
close what needs to be closed
most functionally can be done with basic functions and basic html
complex stuff you ask for help/advice.

On Thu, Oct 26, 2023 at 1:21 PM Mark Waite 
wrote:

> Not much. I am a manager that was a C programmer many years ago.  I have
> learned Java and Maven as part of Jenkins plugin maintenance and a little
> experience before Jenkins.
>
> If you are interested in learning and are willing to learn, you can adopt
> a plugin.
>
> Technical questions to the developer list frequently get good answers.  If
> you'd like others to review your changes,  I am sure we can find people
> willing to answer questions and review changes
>
> On Thu, Oct 26, 2023, 1:11 PM STEVEN CORREA  wrote:
>
>> Hello everyone -
>>
>> What is the minimum level of development experience needed to adopt a
>> plug-in?
>>
>> Regards,
>> Steve
>>
>> --
>> 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/566a1ed2-1118-412c-a67d-d568aaf6df4en%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/CAO49JtHpD5RomKdNUJ6SJ9WOwBAX6SXBRjzboCgzrxizn2SLPQ%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_DuuQvqyPzFLqhJiN85sq-1Q6WXCn92xxUEvO2rJMUtwmKw%40mail.gmail.com.

Re: Plug-in adoption

[Mark Waite]

Not much. I am a manager that was a C programmer many years ago.  I have
learned Java and Maven as part of Jenkins plugin maintenance and a little
experience before Jenkins.

If you are interested in learning and are willing to learn, you can adopt a
plugin.

Technical questions to the developer list frequently get good answers.  If
you'd like others to review your changes,  I am sure we can find people
willing to answer questions and review changes

On Thu, Oct 26, 2023, 1:11 PM STEVEN CORREA  wrote:

> Hello everyone -
>
> What is the minimum level of development experience needed to adopt a
> plug-in?
>
> Regards,
> Steve
>
> --
> 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/566a1ed2-1118-412c-a67d-d568aaf6df4en%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/CAO49JtHpD5RomKdNUJ6SJ9WOwBAX6SXBRjzboCgzrxizn2SLPQ%40mail.gmail.com.

Plug-in adoption

[STEVEN CORREA]

Hello everyone -

What is the minimum level of development experience needed to adopt a 
plug-in?

Regards,
Steve

-- 
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/566a1ed2-1118-412c-a67d-d568aaf6df4en%40googlegroups.com.

Re: auto release form branch or manual release of multimodule project

[Basil Crow]

On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek  wrote:
>
> I was fiddling with 
> https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  
> (mostly reset to jenkinsci but it did not did the 
> job.

Just replace  with .

-- 
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/CAFwNDjpysG0nokQ31G5T9joyu9aqGXMpw%2BU60GheWPj%3DYqDPXg%40mail.gmail.com.

Re: Request to adopt AccuRev plugin (up for adoption)

['Alexander Brandes' via Jenkins Developers]

Approved. Welcome aboard :)

> On 26. Oct 2023, at 17:49, Basil Crow  wrote:
> 
> +1, thank you for stepping up to maintain this plugin.
> 
> This plugin's build has not been updated in a long time, so you should
> expect to modernize some portions of the build before being able to do
> a release. See the tutorial here:
> 
> https://www.jenkins.io/doc/developer/tutorial-improve/
> 
> -- 
> 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/CAFwNDjq_qi1yb-JvcZwZK8tYV5T%2BcptJT3QVjv5k_7xgiwd8xw%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/B7CE7F76-D462-46FD-B086-C0B65911A3DC%40notmyfault.dev.

Re: Request to adopt AccuRev plugin (up for adoption)

[Basil Crow]

+1, thank you for stepping up to maintain this plugin.

This plugin's build has not been updated in a long time, so you should
expect to modernize some portions of the build before being able to do
a release. See the tutorial here:

https://www.jenkins.io/doc/developer/tutorial-improve/

-- 
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/CAFwNDjq_qi1yb-JvcZwZK8tYV5T%2BcptJT3QVjv5k_7xgiwd8xw%40mail.gmail.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

On Thursday, October 26, 2023 at 9:29:00 AM UTC-6 Jiri Vanek wrote:

I see. That sounds like correct assumption. Only JDK will become LTS only 
and if only somebody pick it up. So yes, the statement is correct - We can 
be pretty sure that once per 2 years, at last one JDK indeed will be picked 
by any of 
bigger java players. And if so, it is most likely being aligned with 
oracle. 

Thanx for those additional details and sorry for noise. 


Thanks to you as well for being involved and for sharing your concern.
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/f70987ed-29b2-4289-96e6-dfb254d9f5d5n%40googlegroups.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Jiri Vanek]

I'm relying on the statement on the Eclipse Temurin Release Roadmap 
 where it says

 > In addition, every two years since 2021 one feature release will be 
designated as a Long Term Supported (LTS) release. We will support LTS releases 
for at least four years.

Since Eclipse Temurin will support an LTS JDK for at least four years after its 
initial release, I think that the Jenkins project can rely on that.


I see. That sounds like correct assumption. Only JDK will become LTS only and if only somebody pick it up. So yes, the statement is correct - We can be pretty sure that once per 2 years, at last one JDK indeed will be picked  by any of 
bigger java players. And if so, it is most likely being aligned with oracle.


Thanx for those additional details and sorry for noise.


 J.

--
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/5512e4c6-145a-4875-a051-c0e38f36f159%40redhat.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Mark Waite]

On Thursday, October 26, 2023 at 8:12:02 AM UTC-6 Jiri Vanek wrote:

Maybe a small narrowing. 
The LTS every two years means that Oracle java will be following that. And 
that is beyond paywall. 
The usptream openjdk is simply rolling with new jdk every half a year, and 
of it nothing is going to be LTS, unless somone to pick that particular 
repository and keep maintain that, and keep building that (here, eclisdpe 
adoptium will be 
most likely building ever jdk repo which have maintainer). See eg AZUL 
maintaing LTS of JDK13 and few others...


Thanks for the comment Jiri.  Much appreciated.

I'm relying on the statement on the Eclipse Temurin Release Roadmap 
 where it says

> In addition, every two years since 2021 one feature release will be 
designated as a Long Term Supported (LTS) release. We will support LTS 
releases for at least four years.

Since Eclipse Temurin will support an LTS JDK for at least four years after 
its initial release, I think that the Jenkins project can rely on that.

Mark Waite
 

-- 
Jiri Vanek Mgr. 
Principal QA Software Engineer 
Red Hat Inc. 
+420 775 39 01 09 

-- 
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/24879b7a-e2a3-4c32-87c7-62f8e838c3c8n%40googlegroups.com.

Request to adopt AccuRev plugin (up for adoption)

[Alden Pratt]

   
   - Link to a plugin you want to 
   adopt: https://github.com/jenkinsci/accurev-plugin
   - The status of the plugin: up for adoption
   - Link(s) to pull requests you want to deliver:
  - https://github.com/jenkinsci/accurev-plugin/pull/97
  - Your GitHub username/id: AldenPratt
   - Your Jenkins infrastructure account id: prattal
   - The link to the "Repository Permission Updater" 
   PR:  
https://github.com/jenkins-infra/repository-permissions-updater/pull/3589

Requesting permission because this plugin is up for adoption and is 
incompatible with Jenkins v2.414.3

-- 
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/d71e4fe9-02ab-455a-9292-80140fccfcc9n%40googlegroups.com.

Re: Transition to 2+2+2 Java Support for Jenkins

[Jiri Vanek]

Maybe a small narrowing.
The LTS every two years means that Oracle java will be following that. And that 
is beyond paywall.
The usptream openjdk is simply rolling with new jdk every half a year, and of it nothing is going to be LTS, unless somone to pick that particular repository and keep maintain that, and keep building that (here, eclisdpe adoptium will be 
most likely building ever jdk repo which have maintainer). See eg AZUL maintaing LTS of JDK13 and few others...


Where it is likely that other java vendors will pick up the jdk repos, in 
alignment with Oracle LTS support, it is not strictly true. (eg see SAP 
recently dropped jdk11 support, and RH hadc to take it over).

Thanx for bringing this 2+2+2 model up.

J.

On 9/25/23 15:18, Mark Waite wrote:
Java releases are delivered every 6 months with a long term support release every two years as announced in a September 2021 blog post .  The release cadence is 
described in more detail in another blog post .  The OpenJDK project and Eclipse Temurin project both support their long term support releases with security patches for 
six years.



The two year release cadence with a six year support life means that three Java LTS releases are officially supported at any point in time by the OpenJDK project and the Eclipse Temurin project.  Jenkins developers would like to generally 
support two Java LTS releases rather than three LTS releases in order to reduce overhead from supporting Java releases.



In order to limit Java support to two LTS releases, I propose that the Jenkins project adopt a “2+2+2” model where a new Java LTS release is supported for two years, then becomes the minimum required Java version for two years, then is 
unsupported for two years.  In the last two years, new Jenkins releases will not run on that oldest supported Java version.



A diagram 
is
 provided to describe the transition from our current model to the “2+2+2” model.

The diagram shows that as part of the transition, Java 17 will be the minimum required Java version for only 12 months and Java 21 will be the minimum required version for only 18 months.  Java 25 and later will be the minimum required 
version for 24 months.



The “2+2+2” pattern balances the needs of large scale Jenkins users for 
predictability and stability and the needs of Jenkins developers for less 
maintenance overhead.


After a week or two of discussion in the Jenkins developer mailing list and the 
Jenkins user mailing list, I plan to submit this as a Jenkins Enhancement 
Proposal.

More details are available in the Google Doc 
.

Thanks,
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/2f4e2751-6765-4973-8a05-48d0a7fce8e5n%40googlegroups.com 
.


--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09

--
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/515af80f-6cc3-41ca-ba69-8e50ab77ee0b%40redhat.com.

Re: auto release form branch or manual release of multimodule project

[Jiri Vanek]

Right.

I think I'm lacking imagination how to use them then.
I was fiddling with 
https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  (mostly reset to 
jenkinsci but it did not did the job.
If you have a stronger kick to  me, please share!

TYVM!
 J.

On 10/26/23 15:05, 'Daniel Beck' via Jenkins Developers wrote:



On Thu, Oct 26, 2023 at 2:51 PM Jiri Vanek mailto:jva...@redhat.com>> wrote:

[ERROR]  jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is 
not a valid repository name


Looks like the attributes in https://github.com/jenkinsci/archetypes/blob/8203c822c89145f74d077c4895fd691c7d61c893/empty-plugin/src/main/resources/archetype-resources/pom.xml#L24 
 could fix this?


--
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/CAMo7Pt%2BSUkgtZpw_8D7-dFRpqyxO9A%3D17oY94NXt%3DzytjvitxA%40mail.gmail.com 
.


--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09

--
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/39cc0589-3ab1-439e-8185-5af02aaeed15%40redhat.com.

Re: auto release form branch or manual release of multimodule project

['Daniel Beck' via Jenkins Developers]

On Thu, Oct 26, 2023 at 2:51 PM Jiri Vanek  wrote:

> [ERROR]  jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is
> not a valid repository name
>

Looks like the attributes in
https://github.com/jenkinsci/archetypes/blob/8203c822c89145f74d077c4895fd691c7d61c893/empty-plugin/src/main/resources/archetype-resources/pom.xml#L24
could fix this?

-- 
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/CAMo7Pt%2BSUkgtZpw_8D7-dFRpqyxO9A%3D17oY94NXt%3DzytjvitxA%40mail.gmail.com.

Re: auto release form branch or manual release of multimodule project

[Jiri Vanek]

> On 10/26/23 14:03, Ullrich Hafner wrote:

I think the incremental tools do not work with multi-module projects. I always 
cd to my plugin folder and start mvn release from there.


Hello! Thanx a lot! that would work, and also it is what I tried. There must be 
some misconfiguration, or I had missed anything, because  when running
 $ cd report-jtreg-plugin  # top level project as cloned form 
https://github.com/jenkinsci/report-jtreg-plugin/
 $ mvn clean install   # all passes
 $ cd report-jtreg-plugin  # the submodule with plugin
 $ mvn release:prepare
... dies :
[INFO] Executing: /bin/sh -c cd 
'/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin' && 'git' 'commit' 
'--verbose' '-F' '/tmp/maven-scm-1232529661.commit'
[INFO] Working directory: 
/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin
[INFO] Executing: /bin/sh -c cd 
'/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin' && 'git' 
'symbolic-ref' 'HEAD'
[INFO] Working directory: 
/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin
[INFO] Executing: /bin/sh -c cd '/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin' && 'git' 'push' 'g...@github.com:jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin' 
'refs/heads/chartjs-1-rebasedToRefactored:refs/heads/chartjs-1-rebasedToRefactored'

[INFO] Working directory: 
/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin
...
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: remote error:
[ERROR]  jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is not a 
valid repository name
[ERROR] Visit https://support.github.com/ for help
[ERROR]


Where indeed, the 
g...@github.com:jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is 
nonsese (should be jsut 
g...@github.com:jenkinsci/report-jtreg-plugin-plugin.git)

TYVM!

 J.





Am 26.10.2023 um 12:10 schrieb Jiri Vanek :

Hello!

I have a plugin - https://github.com/jenkinsci/report-jtreg-plugin/ -  where 
main branch is aligned with future, prototypeJS-less  jenkins, and so it have 
another branch, which is compatible with current live jenkinses.
In this setup, I was able to do the only live version of this plugin - 2.1. 
IIRC, I had released this one via `mvn release:prepare release:perform`
Recently, we had heavily refactored the plugin, so ti is now multi-module maven 
plugin, with lib, plugin (with bundled lib), and two standalone services which 
depends on lib, and - if manually started - can comunicate with plugin. The 
release here, of course counts only with the hpi plugin.

Today I wished to release 2.3 but I underestimated it, and (after quite a 
struggling), only top level pom.xml got uploaded to artifactory.
However, the commits to master, seems to be (via GHactions autorelease) 
correctly propagated to artifactory as incremental per-merge binaries, 
including lib, plugin and also both services.
So,encouraged by this, I had manually pushed to  not-main branch, and tagged, 
and hoped that incremntalify will pick it up and  release. Nope.

I guess best would be to setup incrementalify to release only from my non-main 
branch (until prototypejs-less jenkins reaches LTS), is ti possible?
If not, any hint on how can I manually release, or jsut upload, binaries from 
the branch to artifactory?


Thanx!
  J.




--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09

--
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/3527668e-9cf3-4f91-834c-5270b1a6d7ea%40redhat.com.




--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09

--
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/872d6b3b-2399-4c08-813b-9dfd2ac3c9a6%40redhat.com.

Re: [ci.jenkins.io] Update of the Digital Ocean Kubernetes clusters to 1.26

[Damien Duportal]

The operation is now finished and was successful.

Le jeu. 26 oct. 2023 à 13:12, Damien Duportal  a
écrit :

> Hello dear all!
>
> The Jenkins Infra. team will perform an upgrade of the DigitalOcean
> Kubernetes clusters from 1.25 to 1.26 is scheduled the Thursday 26 October
> 2023 at 12:00 (noon) UTC.
>
> No visible impact is expected on ci.jenkins.io as the container agent
> workloads will be taken over by the AWS EKS cluster instead of Digital
> Ocean starting at 11:00 UTC.
>
> More details in
> https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1780857936
> .
>
>
> For the infra team,
>
>
> Damien DUPORTAL
>

-- 
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/CA%2BAiRi8OikBZ2yaZapw4-Ehry0XQ-2oNgmstRfx%3DSGspKX1-UQ%40mail.gmail.com.

Re: auto release form branch or manual release of multimodule project

[Ullrich Hafner]

I think the incremental tools do not work with multi-module projects. I always 
cd to my plugin folder and start mvn release from there.

> Am 26.10.2023 um 12:10 schrieb Jiri Vanek :
> 
> Hello!
> 
> I have a plugin - https://github.com/jenkinsci/report-jtreg-plugin/ -  where 
> main branch is aligned with future, prototypeJS-less  jenkins, and so it have 
> another branch, which is compatible with current live jenkinses.
> In this setup, I was able to do the only live version of this plugin - 2.1. 
> IIRC, I had released this one via `mvn release:prepare release:perform`
> Recently, we had heavily refactored the plugin, so ti is now multi-module 
> maven plugin, with lib, plugin (with bundled lib), and two standalone 
> services which depends on lib, and - if manually started - can comunicate 
> with plugin. The release here, of course counts only with the hpi plugin.
> 
> Today I wished to release 2.3 but I underestimated it, and (after quite a 
> struggling), only top level pom.xml got uploaded to artifactory.
> However, the commits to master, seems to be (via GHactions autorelease) 
> correctly propagated to artifactory as incremental per-merge binaries, 
> including lib, plugin and also both services.
> So,encouraged by this, I had manually pushed to  not-main branch, and tagged, 
> and hoped that incremntalify will pick it up and  release. Nope.
> 
> I guess best would be to setup incrementalify to release only from my 
> non-main branch (until prototypejs-less jenkins reaches LTS), is ti possible?
> If not, any hint on how can I manually release, or jsut upload, binaries from 
> the branch to artifactory?
> 
> 
> Thanx!
>  J.
> 
> 
> 
> 
> -- 
> Jiri Vanek Mgr.
> Principal QA Software Engineer
> Red Hat Inc.
> +420 775 39 01 09
> 
> -- 
> 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/3527668e-9cf3-4f91-834c-5270b1a6d7ea%40redhat.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/FB5D50EB-F5F1-43F2-8659-6D8DEBC0C466%40gmail.com.

[ci.jenkins.io] Update of the Digital Ocean Kubernetes clusters to 1.26

[Damien Duportal]

Hello dear all!

The Jenkins Infra. team will perform an upgrade of the DigitalOcean
Kubernetes clusters from 1.25 to 1.26 is scheduled the Thursday 26 October
2023 at 12:00 (noon) UTC.

No visible impact is expected on ci.jenkins.io as the container agent
workloads will be taken over by the AWS EKS cluster instead of Digital
Ocean starting at 11:00 UTC.

More details in
https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1780857936
.


For the infra team,


Damien DUPORTAL

-- 
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/CA%2BAiRi_md%2BMAp7NR0X01tELzjUOazjKd2YHhc9YoKNucSrux%3Dw%40mail.gmail.com.

auto release form branch or manual release of multimodule project

[Jiri Vanek]

Hello!

I have a plugin - https://github.com/jenkinsci/report-jtreg-plugin/ -  where 
main branch is aligned with future, prototypeJS-less  jenkins, and so it have 
another branch, which is compatible with current live jenkinses.
In this setup, I was able to do the only live version of this plugin - 2.1. 
IIRC, I had released this one via `mvn release:prepare release:perform`
Recently, we had heavily refactored the plugin, so ti is now multi-module maven plugin, with lib, plugin (with bundled lib), and two standalone services which depends on lib, and - if manually started - can comunicate with plugin. The 
release here, of course counts only with the hpi plugin.


Today I wished to release 2.3 but I underestimated it, and (after quite a 
struggling), only top level pom.xml got uploaded to artifactory.
However, the commits to master, seems to be (via GHactions autorelease) 
correctly propagated to artifactory as incremental per-merge binaries, 
including lib, plugin and also both services.
So,encouraged by this, I had manually pushed to  not-main branch, and tagged, 
and hoped that incremntalify will pick it up and  release. Nope.

I guess best would be to setup incrementalify to release only from my non-main 
branch (until prototypejs-less jenkins reaches LTS), is ti possible?
If not, any hint on how can I manually release, or jsut upload, binaries from 
the branch to artifactory?


Thanx!
  J.




--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09

--
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/3527668e-9cf3-4f91-834c-5270b1a6d7ea%40redhat.com.