Operation on LDAP and public ACP (arm64 migration of workloads on publick8s)

[Damien Duportal]

Hi dear contributors,

The Jenkins infra team is starting a planned operation on publick8s to
migrate to arm64.

Expect LDAP restarts (e.g. no authentication on *.jenkins.io) and outage on
ACP (repo.azure.jenkins.io: the ci.jenkins.io jobs should switch to
repo.jenkins-ci.org temporarily).

For the Jenkins 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%2BAiRi8N7%3DBjm4qnHv48Rf5OZmijCyT9s1fonO2p1Hy0puDGBg%40mail.gmail.com.

Re: [Jenkins infrastructure][2024-07-04] Unavailable authentication and websites for Kubernetes 1.28 upgrade

[Damien Duportal]

The operation is finished. It was successful.

All services are now operational.

Damien Duportal

Le jeu. 4 juil. 2024 à 08:38, Damien Duportal  a
écrit :

> Hello dear Jenkins contributors,
>
> The Jenkins infrastructure team is starting a Kubernetes 1.28 upgrade on
> the Jenkins Infrastructure public cluster.
>
> We expect disruption on the centralized authentication (ci.jenkins.io,
> repo.jenkins-ci.org, etc.) during the operation.
>
> Other public-facing services (Plugin Health score, Public reports, wiki,
> etc.) are expected to be either slower or disrupted during the operation.
>
> You may follow status.jenkins.io page for changes.
>
> More details in
> https://github.com/jenkins-infra/helpdesk/issues/4144#issuecomment-2196274746
>
> For the Jenkins 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%2BAiRi9jXvPp2eyc395RC5R%3D-RjkZ_sxu5BD2ONhBwrD7ErqWQ%40mail.gmail.com.

[Jenkins infrastructure][2024-07-04] Unavailable authentication and websites for Kubernetes 1.28 upgrade

[Damien Duportal]

Hello dear Jenkins contributors,

The Jenkins infrastructure team is starting a Kubernetes 1.28 upgrade on
the Jenkins Infrastructure public cluster.

We expect disruption on the centralized authentication (ci.jenkins.io,
repo.jenkins-ci.org, etc.) during the operation.

Other public-facing services (Plugin Health score, Public reports, wiki,
etc.) are expected to be either slower or disrupted during the operation.

You may follow status.jenkins.io page for changes.

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

For the Jenkins 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%2BAiRi8i%2BLH_bEMVt3T5XU%2BmQ%3DuO%3DKko__NqjSjAM7vWEJkWFw%40mail.gmail.com.

[ci.jenkins.io] Maven 3.9.8 general availability

[Damien Duportal]

Hi dear contributors,

The Jenkins Infra team is pleased to announce that Maven 3.9.8 
<https://maven.apache.org/docs/3.9.8/release-notes.html> is now available 
and the default all agents and build tools of ci.jenkins.io.

Note that Jenkins Core itself is now using Maven 3.9.8 since yesterday 
weekly release.

Please check https://github.com/jenkins-infra/helpdesk/issues/4150 for 
details.

Damien DUPORTAL, for the Jenkins Infra team

-- 
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/dd306298-b1c2-423e-96b9-cb6692e723f8n%40googlegroups.com.

[ci.jenkins.io] Maven 3.9.7 general availability

[Damien Duportal]

Hi dear contributors,

The Jenkins Infra team is pleased to announce that Maven 3.9.7 is now 
available and the default all agents and build tools of ci.jenkins.io.

Ref. https://github.com/jenkins-infra/helpdesk/issues/4109 for details

Damien DUPORTAL, for the Jenkins Infra team

-- 
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/53807a16-33f4-4fa5-b386-b0a1fd6c7928n%40googlegroups.com.

[ci.jenkins.io] Changing Kubernetes agents from (AWS + DigitalOcean) to Azure

[Damien Duportal]

Hi dear contributors!

For information, the Jenkins infra team will perform an operation on
ci.jenkins.io to use Azure instead of AWS + DigitalOcean to run Kubernetes
Linux container agents.

In addition, this operation increases the amount of memory from 8Gb  to 12
Gb for your builds and features new powerful CPUs + local disks.

If you see any issue in your (Linux containers) build in the upcoming days,
please let us know by answering this email or opening an issue in the
github.com/jenkins-infra/helpdesk project.

The whole topic is described in
https://github.com/jenkins-infra/helpdesk/issues/3954 if you are interested
in the motivations and details.

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-yL%3DAq8vngcZB8d2e8%3DWGuYqTo_MJEZEyWxexoiP9Gjg%40mail.gmail.com.

Kubernetes 1.27 upgrade for public cluster

[Damien Duportal]

Hello dear contributors!

The Jenkins infra team will perform a Kubernetes upgrade to 1.27 on the
public cluster today, 19 March at 08:30UTC.

As described in
https://status.jenkins.io/issues/2024-19-03-maintenance-az-publick8s-1-27/,
we mainly  expect downtime on LDAP with authentication unavailable for 10
to 15 minutes during restart(s).

Damien DUPORTAL for the Jenkins infra team

-- 
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_jF3VbSZOSN-%3DzmJkQt5M_KLf3o7No%2BqBN2SSNr2%3DcEA%40mail.gmail.com.

Re: [get(mirrors).jenkins.io] Maintenance today with partial disruptions on download mirrors

[Damien Duportal]

Operation is no finished and was successull

Le ven. 26 janv. 2024 à 13:05, Damien Duportal 
a écrit :

> Hello dear contributors,
>
> As per
> https://status.jenkins.io/issues/2024-01-26-get.jenkins.io-migration/, we
> are starting a maintenance on the Jenkins download mirrors which may have
> (limited) impact on your workflows if you download plugins or binaries from
> get.jenkins.io.
>
> We'll keep you up to date.
>
> Damien Duportal, for the Jenkins Infra team
>

-- 
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_%3DoF4%2BtTq6zxx9k53ds2FVc8eovxmBLoX2s-J1hifMNA%40mail.gmail.com.

[get(mirrors).jenkins.io] Maintenance today with partial disruptions on download mirrors

[Damien Duportal]

Hello dear contributors,

As per https://status.jenkins.io/issues/2024-01-26-get.jenkins.io-migration/,
we are starting a maintenance on the Jenkins download mirrors which may
have (limited) impact on your workflows if you download plugins or binaries
from get.jenkins.io.

We'll keep you up to date.

Damien Duportal, for the Jenkins Infra team

-- 
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-np_Yv2VrNb6b9ZWmHP5AZHzDwcFGOFi7j-bjs2K5dHw%40mail.gmail.com.

Re: [ci.jenkins.io] Maintenance with full downtime today

[Damien Duportal]

Operation is finished and ci.jenkins.io is operating succesfully.

Le jeu. 25 janv. 2024 à 14:44, Damien Duportal 
a écrit :

> Update : operation still in progress. No blockers, but we are slower than
> expected.
>
> Le jeu. 25 janv. 2024 à 12:20, Damien Duportal 
> a écrit :
>
>> Hi dear contributors,
>>
>> The Jenkins Infra team will perform a maintenance on ci.jenkins.io
>> starting at 12:30pm (noon time) UTC today with full downtime.
>>
>>
>> The goal is to move the service to a new VM in another Azure subscription
>> where we have credits to pay for the resources (instead of having a billing
>> with the current VM).
>>
>> More details in https://github.com/jenkins-infra/helpdesk/issues/3913.
>>
>> We expect 1 hour of downtime, but we will send an email to let you know 1
>> hour after the beginning (or if we finished earlier).
>>
>> 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%2BAiRi8F%3DYy3UD%3DSVB0hKkJ6TSBeomFBt1fLX1D4BfzCnHiaWw%40mail.gmail.com.

Re: [ci.jenkins.io] Maintenance with full downtime today

[Damien Duportal]

Update : operation still in progress. No blockers, but we are slower than
expected.

Le jeu. 25 janv. 2024 à 12:20, Damien Duportal 
a écrit :

> Hi dear contributors,
>
> The Jenkins Infra team will perform a maintenance on ci.jenkins.io
> starting at 12:30pm (noon time) UTC today with full downtime.
>
>
> The goal is to move the service to a new VM in another Azure subscription
> where we have credits to pay for the resources (instead of having a billing
> with the current VM).
>
> More details in https://github.com/jenkins-infra/helpdesk/issues/3913.
>
> We expect 1 hour of downtime, but we will send an email to let you know 1
> hour after the beginning (or if we finished earlier).
>
> 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%2BAiRi9etG5Nxxdt0u8zCasGZie11HwoxbchNNHt64rnn_%3DBKw%40mail.gmail.com.

[ci.jenkins.io] Maintenance with full downtime today

[Damien Duportal]

Hi dear contributors,

The Jenkins Infra team will perform a maintenance on ci.jenkins.io starting
at 12:30pm (noon time) UTC today with full downtime.


The goal is to move the service to a new VM in another Azure subscription
where we have credits to pay for the resources (instead of having a billing
with the current VM).

More details in https://github.com/jenkins-infra/helpdesk/issues/3913.

We expect 1 hour of downtime, but we will send an email to let you know 1
hour after the beginning (or if we finished earlier).

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%2BAiRi8S5htdssLMjSh0tOL4vj9Zv9Ke0ypy2LhSmABO3L_NmA%40mail.gmail.com.

Re: LDAP maintenance today (2024-01-19) at 08:45am UTC

[Damien DUPORTAL]

Operation finished ✅ Le 19 janv. 2024 à 09:42, Damien Duportal  a écrit :Hello all!The Jenkins infra team will perform an operation on the LDAP today (2024-01-19) at 08:45am UTC.No authentication will be possible during this operation (which requires at least one LDAP restart) on issues.jenkins.io, ci.jenkins.io, repo.jenkins-ci.org, etc.See https://status.jenkins.io/issues/2024-01-19-ldap-maintenance/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/965EFB68-E57B-41EC-90F7-736AF94C6F16%40gmail.com.

LDAP maintenance today (2024-01-19) at 08:45am UTC

[Damien Duportal]

Hello all!

The Jenkins infra team will perform an operation on the LDAP today
(2024-01-19) at 08:45am UTC.

No authentication will be possible during this operation (which requires at
least one LDAP restart) on issues.jenkins.io, ci.jenkins.io,
repo.jenkins-ci.org, etc.

See https://status.jenkins.io/issues/2024-01-19-ldap-maintenance/


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-iC7ztqqd-hUOkDJh_8evEmnr%3DUFopWD_LthXPHOGwCA%40mail.gmail.com.

Re: [Jenkins Infra] Upgrade of Kubernetes 1.26 in Azure

[Damien Duportal]

The upgrade operation is now finished.

It went successfully, with a measured 6 min outage on the LDAP and 2 min on
the incremental publisher.

The platform is now in nominal condition.

Damien

Le jeu. 9 nov. 2023 à 12:24, Damien Duportal  a
écrit :

> As per https://status.jenkins.io/, the Jenkins infrastructure team is
> running a cluster upgrade of AKS to Kubernetes 1.26.
>
> We are starting the upgrade now: expect outages with the log-in/log-out on
> all "*.jenkins.io" services during the next hour due to LDAP restart.
>
> The incremental publisher service is also in the operation scope: please
> avoid releasing incremental plugin versions and trigger a new PR build
> (with an empty commit) once the operation is finished to successfully
> publish your incremental releases.
>
> Stéphane and Damien, for the Jenkins Infra team
>

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

[Jenkins Infra] Upgrade of Kubernetes 1.26 in Azure

[Damien Duportal]

As per https://status.jenkins.io/, the Jenkins infrastructure team is
running a cluster upgrade of AKS to Kubernetes 1.26.

We are starting the upgrade now: expect outages with the log-in/log-out on
all "*.jenkins.io" services during the next hour due to LDAP restart.

The incremental publisher service is also in the operation scope: please
avoid releasing incremental plugin versions and trigger a new PR build
(with an empty commit) once the operation is finished to successfully
publish your incremental releases.

Stéphane and Damien, for the Jenkins Infra team

-- 
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%2BAiRi9KExXkWaPdbq0PcUXkbHbvq4QrTLq%2B144f0CUXd3BjBA%40mail.gmail.com.

Re: [ci.jenkins.io] Upgrade of Kubernetes 1.26 in AWS EKS: no BOM builds

[Damien Duportal]

The operation finished after 1h45 with success. ci.jenkins.io builds are
back to normal.

Le lun. 6 nov. 2023 à 15:47, Damien Duportal  a
écrit :

> Hi dear developers,
>
> The Jenkins infra team will perform a Kubernetes upgrade on the AWS EKS
> clusters used by ci.jenkins.io for agents, today (Monday 6 Nov.) at 14h00
> UTC.
>
> No BOM builds are possible (and will be put in the queue) during the
> operation.
> Plugins builds will be handled by DigitalOcean cloud agent or by VMs.
>
> More details in
> https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1794913444
>
> Damien, for the infra team
>

-- 
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%2BAiRi8UK_io3MUdtHd-yd0PRir0u2u1wvsnJiaHvW778g9%3DHQ%40mail.gmail.com.

Re: [ci.jenkins.io] Upgrade of Kubernetes 1.26 in AWS EKS: no BOM builds

[Damien Duportal]

My apologies: it's is 15h00 UTC (winter time got me confused)

Le lundi 6 novembre 2023 à 15:47:19 UTC+1, Damien Duportal a écrit :

> Hi dear developers,
>
> The Jenkins infra team will perform a Kubernetes upgrade on the AWS EKS 
> clusters used by ci.jenkins.io for agents, today (Monday 6 Nov.) at 14h00 
> UTC.
>
> No BOM builds are possible (and will be put in the queue) during the 
> operation.
> Plugins builds will be handled by DigitalOcean cloud agent or by VMs.
>
> More details in 
> https://github.com/jenkins-infra/helpdesk/issues/3683#issuecomment-1794913444
>
> Damien, for the infra team
>

-- 
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/24747348-7c8a-4937-a0da-b5a799ed2cd1n%40googlegroups.com.

[ci.jenkins.io] Upgrade of Kubernetes 1.26 in AWS EKS: no BOM builds

[Damien Duportal]

Hi dear developers,

The Jenkins infra team will perform a Kubernetes upgrade on the AWS EKS
clusters used by ci.jenkins.io for agents, today (Monday 6 Nov.) at 14h00
UTC.

No BOM builds are possible (and will be put in the queue) during the
operation.
Plugins builds will be handled by DigitalOcean cloud agent or by VMs.

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

Damien, for the infra team

-- 
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_u3V7qbsA2U8KS4siFMwUjEdpWVS8Z8Ej-MW3BLdkVwA%40mail.gmail.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.

[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.

Re: Backporting for LTS 2.414.3 has started

[Damien Duportal]

PR for cherry pick created, please check carefully folks: 
https://github.com/jenkinsci/packaging/pull/439

Le mercredi 18 octobre 2023 à 13:01:01 UTC+2, Mark Waite a écrit :

> On Wednesday, October 18, 2023 at 2:09:37 AM UTC-6 Alexander Brandes wrote:
>
> Packaging happens from the versioned stable-2.414 branch.
>
> There's a stable- branch for every recent LTS release.
>
>
> You're right.  I'm not sure how I made the mistake of not seeing that 
> branch, but I clearly did not see it in the session where Kevin and I were 
> investigating.  
>
> Unfortunately, I'm not available to create the cherry pick commit because 
> I need to leave for the airport.
>
> I'm +1 for the cherry-pick, but also have no problem if the curl based 
> instructions remain so that we don't disrupt today's release.
>
> 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/64506dcf-718d-4d3b-9c2a-f9ec3d664e35n%40googlegroups.com.

[ci.jenkins.io] General availability of Maven 3.9.5

[Damien Duportal]

Hello dear contributors,

As described in https://github.com/jenkins-infra/helpdesk/issues/3776, 
Maven 3.9.5 is now generally available as the default Maven in 
ci.jenkins.io (and other controllers).

As usual, if you have any problem due to this upgrade, please raise your 
voice on this email thread or by raising an issue.


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/92dfe543-9bbd-46e3-b411-96fd1a0a335cn%40googlegroups.com.

Re: Proposal: Kris Stern to join the release team

[Damien Duportal]

Kris did a lot of of work and committed to the past year of release really 
often!

They are invaluable contributor to the Jenkins project.

+1 From me!

Damien Duportal

Le mardi 26 septembre 2023 à 18:28:28 UTC+2, Alexander Brandes a écrit :

> Hey everyone,
>
> I would like to propose Kris Stern (@krisstern 
> <https://github.com/krisstern>) to join the release team.
>
> I have assisted them during their past releases 
> <https://groups.google.com/g/jenkinsci-dev/search?q=release%20lead%20kris%20stern>
>  
> as lead and would welcome an addition to the release team on GitHub.
>
> They have signed an ICLA too.
>
> Best,
>
> Alex
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f2cdf809-c63a-485a-beff-91ed705be8dfn%40googlegroups.com.

[repo.jenkins-ci.org] Stop mirroring/caching Apache Central ("repo1")

[Damien Duportal]

Hello dear contributors,

As part of the Artifactory bandwidth reduction project (request from JFrog 
who is the sponsor of the repo.jenkins-ci.org Artifactory instance), we'll 
stop mirroring and caching the Apache Central (sometimes referred as 
"repo1") this Thursday September 7 2023.

More details in 
https://github.com/jenkins-infra/helpdesk/issues/3599#issuecomment-1708490449 
if you are interested.

We expect no impacts as the previous brownout operations showed Maven falls 
back as expected to the Apache Central instead when needed.

For the Jenkins 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/ab76d5d5-c449-43d6-a5a1-c8e91127372dn%40googlegroups.com.

Re: [ci.jenkins.io] Artifactory configuration update - brownout

[Damien Duportal]

Brownout is now finished, everything is back to previous state.

We'll report back results in the issue.

Le lundi 4 septembre 2023 à 16:01:22 UTC+2, Damien Duportal a écrit :

> Hello dear contributors,
>
> a quick reminder that we are currently in a "brownout" state on 
> ci.jenkins.io regarding Artifactory configuration as described in 
> https://status.jenkins.io/issues/2023-09-04-artifactory-central-brownount/
> .
>
>
> TL;DR; we removed the "Apache Central" mirrors from repo.jenkins-ci.org 
> for a 3-4 hours today. We expect no disruptions but some weird Maven 
> dependency magic could behave unexpectedly: if you see dependency 
> resolution failure on your builds, please let us know!
>
>
> 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/4258446c-061f-42fa-aa4f-74f749e46707n%40googlegroups.com.

[ci.jenkins.io] Artifactory configuration update - brownout

[Damien Duportal]

Hello dear contributors,

a quick reminder that we are currently in a "brownout" state on 
ci.jenkins.io regarding Artifactory configuration as described in 
https://status.jenkins.io/issues/2023-09-04-artifactory-central-brownount/.


TL;DR; we removed the "Apache Central" mirrors from repo.jenkins-ci.org for 
a 3-4 hours today. We expect no disruptions but some weird Maven dependency 
magic could behave unexpectedly: if you see dependency resolution failure 
on your builds, please let us know!


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/3b3d0a3d-1e71-4d78-8c05-461890b26ac5n%40googlegroups.com.

[ci.jenkins.io] Updated Maven settings.xml

[Damien Duportal]

Hi dear contributors,

for information, as part of the bandwidth reduction effort in our 
Artifactory instance (ref. 
https://github.com/jenkins-infra/helpdesk/issues/3599), the Jenkins infra 
team have deployed an updated `settings.xml` for the ci.jenkins.io agents.

This updated version features a new default profile which sets up the list 
of "pluginRepositories" as you can see in 
https://github.com/jenkins-infra/jenkins-infra/pull/3041/files.

There should be no impact BUT as usual if anything unusual happens in your 
build (in the dependency resolutions phases), please let us now by opening 
a new issue in github.com/jenkins-infra/helpdesk!

Cheers

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/aa349b81-dde5-4376-9e04-832dd0f7ca2an%40googlegroups.com.

[Jenkins Infrastructure] Upgrade of (.*)ci.jenkins.io to JDK17

[Damien Duportal]

Hello dear contributors,

For information, the Jenkins infrastructrue team will operate the 
"trusted,.ci", "cert.ci" and "ci" jenkins.io controllers to switch from 
JDK11 to JDK17 for both controller and agents JVMs.

At least 2 restarts per controller is expected. We expect no more issues 
(as described in https://github.com/jenkins-infra/helpdesk/issues/3072) 
because agents have been updated for JDK17. However we can never rule out a 
mistake or a forgotten agent template so we let you know: if you see any 
JDK related message in your build please let us know!

For the Jenkins infrastructure 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/f12ff15f-a7cb-446d-9d5e-5aa94a902afen%40googlegroups.com.

CD release of Plugins fixed

[Damien Duportal]

Hello dear contributors,

As per https://github.com/jenkins-infra/helpdesk/issues/3714, the CD 
release of plugins was broken since the past 2 days.

This email is to let you know that it is fixed an you can trigger your 
plugin releases again.

Thanks @Tim Jacomb for reporting and triaging during the week end!

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/4cd817ec-ee61-4d6c-b255-4bf647d56177n%40googlegroups.com.

[ci.jenkins.io] JDK21 availability

[Damien Duportal]

Hello dear developers!

Thanks to the work of our dear SRE Stéphane Merle (helped by Bruno 
Verachten and Mark Waite), we are announcing the availability of the JDK21 
prerelease in ci.jenkins.io.

You can now either specify the "21" JDK in your buildPlugin() pipeline 
library, specify a "maven-21" label to get a Linux native container agent 
with JDK21 or specify the Jenkins tool "jdk21".

You can follow up the last step and/or report any problem (native 
"maven-21-windows" agent template is work in progress) in 
https://github.com/jenkins-infra/helpdesk/issues/3709.

For the Jenkins 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/fb1eb389-3b55-425c-afe4-4036a6991dc7n%40googlegroups.com.

[ci.jenkins.io] General availability of Maven 3.9.4

[Damien Duportal]

Hi folks,

As per https://github.com/jenkins-infra/helpdesk/issues/3708, Maven 3.9.4 
is now deployed to the platform and is the default Maven version.

Feel free to contact us if this upgrade is doing any harm on your plugins 
or projects.

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/57a1fb04-636b-44b8-b651-9062fac558fbn%40googlegroups.com.

Re: Artifactory(repo.jenkins-ci.org) Brownout of "repo1" mirrors at 14h30 UTC today, 2nd August 2023

[Damien Duportal]

Brownout is now finished : we'll add our conclusions in 
https://github.com/jenkins-infra/helpdesk/issues/3599.

Le mercredi 2 août 2023 à 12:25:25 UTC+2, Damien Duportal a écrit :

> Hello dear contributors!
>
> As part of the joint effort to decrease the outbound bandwidth on our 
> Artifactory instance repo.jenkins-ci.org, the infrastructure team will 
> perform a 1 hour brownout today at 14h30 UTC: any Maven central (referenced 
> as "repo1" / "maven-repo1") will be disabled to ensure that any builds 
> (your machines, ci.jenkins.io, GitHub actions, etc.) falls back to the 
> internal Maven "central".
>
> More details in 
> https://github.com/jenkins-infra/helpdesk/issues/3599#issuecomment-1653881431
>

-- 
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/a49ae826-58ca-431b-a912-b3f1d184e40an%40googlegroups.com.

Artifactory(repo.jenkins-ci.org) Brownout of "repo1" mirrors at 14h30 UTC today, 2nd August 2023

[Damien Duportal]

Hello dear contributors!

As part of the joint effort to decrease the outbound bandwidth on our 
Artifactory instance repo.jenkins-ci.org, the infrastructure team will 
perform a 1 hour brownout today at 14h30 UTC: any Maven central (referenced 
as "repo1" / "maven-repo1") will be disabled to ensure that any builds 
(your machines, ci.jenkins.io, GitHub actions, etc.) falls back to the 
internal Maven "central".

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

-- 
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/1b6c75a3-b353-4d23-969b-7c073422e596n%40googlegroups.com.

Re: [ci.jenkins.io] Operation today (4th of July) with downtime

[Damien Duportal]

The operation is now finished and the migration is complete.

You can resume usual work with ci.jenkins.io.

If you have any problem (including a pipeline runtime error such as "No 
such DSL method '' found among steps <...>"), please comment in 
https://github.com/jenkins-infra/helpdesk/issues/3535 
.

Damien

Le mardi 4 juillet 2023 à 19:42:09 UTC+2, Damien Duportal a écrit :

> Update:
>
> The ci.jenkins.io's JENKINS_HOME seems to be in bad shape, leading to 
> slow transfer rate. The copy is done with consistency checks which set the 
> ETA to the 5th of July.
>
> Sorry for the inconvenience, let's wait until the data transfer is 
> properly finished.
>
>
>
> Le mardi 4 juillet 2023 à 17:11:37 UTC+2, Damien Duportal a écrit :
>
>> The first part of the operation (Kubernetes upgrade) is now finished (as 
>> per 
>> https://github.com/jenkins-infra/helpdesk/issues/3582#issuecomment-1603056198
>> ).
>>
>> The next operation (with a full downtime) is starting.
>>
>> Le mardi 4 juillet 2023 à 14:40:28 UTC+2, Damien Duportal a écrit :
>>
>>> Hello dear contributors!
>>>
>>> As explained in 
>>> https://status.jenkins.io/issues/2023-07-04-ci-maintenance/, we'll 
>>> operate ci.jenkins.io for 2 majors changes.
>>>
>>> Expect a minor disruption from 13:00 UTC until 14:30 UTC with no BOM 
>>> builds and the agent workload forced to Digital Ocean and Azure (as AWS 
>>> agents will be disabled).
>>>
>>> Then a full downtime is expected starting at 14:30 UTC until operation 
>>> is finished.
>>>
>>> Please answer to this email thread if you have an emergency that would 
>>> collide with these operations.
>>>
>>> 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/da5e1090-b9a0-4e94-8947-00fde97cceaen%40googlegroups.com.

Re: [ci.jenkins.io] Operation today (4th of July) with downtime

[Damien Duportal]

Update:

The ci.jenkins.io's JENKINS_HOME seems to be in bad shape, leading to slow 
transfer rate. The copy is done with consistency checks which set the ETA 
to the 5th of July.

Sorry for the inconvenience, let's wait until the data transfer is properly 
finished.



Le mardi 4 juillet 2023 à 17:11:37 UTC+2, Damien Duportal a écrit :

> The first part of the operation (Kubernetes upgrade) is now finished (as 
> per 
> https://github.com/jenkins-infra/helpdesk/issues/3582#issuecomment-1603056198
> ).
>
> The next operation (with a full downtime) is starting.
>
> Le mardi 4 juillet 2023 à 14:40:28 UTC+2, Damien Duportal a écrit :
>
>> Hello dear contributors!
>>
>> As explained in 
>> https://status.jenkins.io/issues/2023-07-04-ci-maintenance/, we'll 
>> operate ci.jenkins.io for 2 majors changes.
>>
>> Expect a minor disruption from 13:00 UTC until 14:30 UTC with no BOM 
>> builds and the agent workload forced to Digital Ocean and Azure (as AWS 
>> agents will be disabled).
>>
>> Then a full downtime is expected starting at 14:30 UTC until operation is 
>> finished.
>>
>> Please answer to this email thread if you have an emergency that would 
>> collide with these operations.
>>
>> 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/d5ddbc1c-9a60-48fd-bb96-2ae850293eedn%40googlegroups.com.

Re: [ci.jenkins.io] Operation today (4th of July) with downtime

[Damien Duportal]

The first part of the operation (Kubernetes upgrade) is now finished (as 
per 
https://github.com/jenkins-infra/helpdesk/issues/3582#issuecomment-1603056198).

The next operation (with a full downtime) is starting.

Le mardi 4 juillet 2023 à 14:40:28 UTC+2, Damien Duportal a écrit :

> Hello dear contributors!
>
> As explained in 
> https://status.jenkins.io/issues/2023-07-04-ci-maintenance/, we'll 
> operate ci.jenkins.io for 2 majors changes.
>
> Expect a minor disruption from 13:00 UTC until 14:30 UTC with no BOM 
> builds and the agent workload forced to Digital Ocean and Azure (as AWS 
> agents will be disabled).
>
> Then a full downtime is expected starting at 14:30 UTC until operation is 
> finished.
>
> Please answer to this email thread if you have an emergency that would 
> collide with these operations.
>
> 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/9ac9bb75-90d6-40db-91d4-54bd022ed3fen%40googlegroups.com.

[ci.jenkins.io] Operation today (4th of July) with downtime

[Damien Duportal]

Hello dear contributors!

As explained in 
https://status.jenkins.io/issues/2023-07-04-ci-maintenance/, we'll operate 
ci.jenkins.io for 2 majors changes.

Expect a minor disruption from 13:00 UTC until 14:30 UTC with no BOM builds 
and the agent workload forced to Digital Ocean and Azure (as AWS agents 
will be disabled).

Then a full downtime is expected starting at 14:30 UTC until operation is 
finished.

Please answer to this email thread if you have an emergency that would 
collide with these operations.

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/fbb1edca-61f7-4c7b-82a0-d22254894507n%40googlegroups.com.

Re: [Artifactory - repo.jenkins-ci.org] Operating the jgit mirror repository

[Damien Duportal]

Operation is now finished, everything is back to normal.

Have a nice day folks!

Le jeudi 8 juin 2023 à 14:31:50 UTC+2, Damien Duportal a écrit :

> Hello dear developers,
>
> For information, we're going to operate on the jgit mirrored repository 
> for the next hour as per 
> https://status.jenkins.io/issues/2023-06-08-artifactory-operation/.
>
> No outage is expected at first sight, but we want to cover a lot of 
> different cases so better keep you informed.
>
> As usual any error related to dependency download with jgit, either on 
> ci.jenkins.io our your machines should be reported as answer to this 
> email thread on in the jenkins-infra/helpdesk GitHub issues tracker.
>
> Damien DUPORTAL for the infra team
>

-- 
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/8cda8794-a0ae-4a89-a1db-11f3f468aca3n%40googlegroups.com.

[Artifactory - repo.jenkins-ci.org] Operating the jgit mirror repository

[Damien Duportal]

Hello dear developers,

For information, we're going to operate on the jgit mirrored repository for 
the next hour as per 
https://status.jenkins.io/issues/2023-06-08-artifactory-operation/.

No outage is expected at first sight, but we want to cover a lot of 
different cases so better keep you informed.

As usual any error related to dependency download with jgit, either on 
ci.jenkins.io our your machines should be reported as answer to this email 
thread on in the jenkins-infra/helpdesk GitHub issues tracker.

Damien DUPORTAL for the infra team

-- 
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/1e8c6823-11fc-4a32-a8c9-df472560b0b0n%40googlegroups.com.

Re: [Infrastructure] No plugin new release visible today (migration of trusted.ci.jenkins.io to Azure)

[Damien Duportal]

The operation is now finished:

- Update Center is running successully and have published any plugin 
released since 13 hours ago
- Repository Permission Updater ran successfully and new plugin releases 
were confirmed successful
- All the other jobs in trusted.ci.jenkins.io were verified with success.

Le vendredi 2 juin 2023 à 10:13:53 UTC+2, Damien Duportal a écrit :

> Hi dear developers,
>
> The Jenkins Infrastructure is going to migrate the (private) service 
> trusted.ci.jenkins.io from AWS to Azure today, starting at 08h30 UTC.
>
> During the whole migration, there won't be any update of the Update Center 
> neither Repository Permission Updated update: if you have released a plugin 
> today, or plan to do it, you might want to wait for the end of this 
> operation.
>
> More details in https://github.com/jenkins-infra/helpdesk/issues/3486.
>
> As usual, do not hesitate to answer to this email thread or open an issue 
> on github.com/jenkins-infra/helpdesk if you run into any trouble.
>
> 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/37a5b921-8f8b-4c61-ac80-10124f0f7f3cn%40googlegroups.com.

[Infrastructure] No plugin new release visible today (migration of trusted.ci.jenkins.io to Azure)

[Damien Duportal]

Hi dear developers,

The Jenkins Infrastructure is going to migrate the (private) service 
trusted.ci.jenkins.io from AWS to Azure today, starting at 08h30 UTC.

During the whole migration, there won't be any update of the Update Center 
neither Repository Permission Updated update: if you have released a plugin 
today, or plan to do it, you might want to wait for the end of this 
operation.

More details in https://github.com/jenkins-infra/helpdesk/issues/3486.

As usual, do not hesitate to answer to this email thread or open an issue 
on github.com/jenkins-infra/helpdesk if you run into any trouble.

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/f8d5e09c-5bf7-4503-8488-cade10a381b5n%40googlegroups.com.

Re: [ci.jenkins.io] Migration of the Incremental Publisher in a new cluster

[Damien Duportal]

Migration is finished, no downtime detected

Le vendredi 26 mai 2023 à 18:27:49 UTC+2, Damien Duportal a écrit :

> Hello dear contributors!
>
> The Jenkins Infra team is going to migrate the Incremental Publisher to a 
> new cluster as per 
> https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1564632990
> .
>
> No downtime expected but if things goes wrong, the publication of the 
> incremental artifacts in the ci.jenkins.io could fail between 16h30 and 
> 17h00 UTC today.
>
>
> 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/b8a0b422-2668-4da5-97b4-6f45cee9c5den%40googlegroups.com.

Re: Maven 3.9.2: ready to roll?

[Damien Duportal]

Thanks! Maven 3.9.2 has been generally released in the infrastructure

Le mardi 23 mai 2023 à 17:59:43 UTC+2, m...@basilcrow.com a écrit :

> +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/b625de11-70da-4a3c-a231-0cf1a8d57f5bn%40googlegroups.com.

[ci.jenkins.io] Migration of the Incremental Publisher in a new cluster

[Damien Duportal]

Hello dear contributors!

The Jenkins Infra team is going to migrate the Incremental Publisher to a 
new cluster as per 
https://github.com/jenkins-infra/helpdesk/issues/3351#issuecomment-1564632990.

No downtime expected but if things goes wrong, the publication of the 
incremental artifacts in the ci.jenkins.io could fail between 16h30 and 
17h00 UTC today.


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/bc3237d6-196d-4a31-aa62-720b755ae4c3n%40googlegroups.com.

Maven 3.9.2: ready to roll?

[Damien Duportal]

Hello dear maintainers,

Is there any objection against the deployment of Maven 3.9.2 in the Jenkins 
infrastructure?


For the Jenkins 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/79cf9a35-7396-49e8-aab7-abd1c36eef8fn%40googlegroups.com.

[ci.jenkins.io] "higmem" agent size decrease

[Damien Duportal]

Hello dear contributors,

The Jenkins infrastructure team is going to change the size of the 
"highmem" VM agents on ci.jenkins.io.

We are working on controlloing the spendings in clouds and these expansive 
machines are under used as described in 
https://github.com/jenkins-infra/helpdesk/issues/3551#issuecomment-1526009746.

As usual, if you have any issue related to this change, you can either 
raise your concern in this email thread and/or open an helpdesk issues with 
metrics or links to elements helping us to justify a rollback or another 
kind of fix.

Cheers,

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/43563ca7-096a-4771-9e98-b0e9e8a77fben%40googlegroups.com.

Re: Alex Brandes as a copy editor

[Damien Duportal]

LGTM

Le jeudi 13 avril 2023 à 19:37:36 UTC+2, alytong13 a écrit :

> apologies. Meant to say  sounds good to me.
>
> Thnx,
> alyssa
>
> On Thu, Apr 13, 2023 at 10:36 AM Alyssa Tong  wrote:
>
>>  sounds 
>>
>> On Thu, Apr 13, 2023 at 10:08 AM 'Kevin Martens' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> +1 from me for sure!
>>>
>>> On Thu, Apr 13, 2023 at 1:06 PM Mark Waite  wrote:
>>>
 Proposed to add Alex Brandes (NtoMyFault) as a copy editor in 
 jenkins.io repository.  Already has merge permissions and has already 
 submitted 90 pull requests and has reviewed 150.

 Approved?

 -- 
 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/8240e6f8-01cb-41ba-b589-93fbe6f3780bn%40googlegroups.com
  
 
 .

>>>
>>>
>>> -- 
>>> Kevin Martens
>>> Technical Content Developer
>>> CloudBees, Inc.
>>>
>>>
>>> E: kmar...@cloudbees.com
>>>
>>> Pronouns: He/Him/His
>>>
>>> -- 
>>> 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/CAP92yNf_DexKjge4C555F11fbpOTAJFmmTy2F0j0XGdFEt1irQ%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/e81d3cd3-65f9-4f8c-9fad-286a2ede29d5n%40googlegroups.com.

[ci.jenkins.io] Linux agents bumped to Ubuntu 22.04

[Damien Duportal]

As part of the Jenkins Infrastructure Ubuntu 22.04 Upgrade
<https://github.com/jenkins-infra/helpdesk/issues/2982> campaign,  the
Jenkins Infrastucture is going to rollout a new major version of the agent
templates on ci.jenkins.io.

The changelog can be found in
https://github.com/jenkins-infra/packer-images/releases/tag/1.0.0 and it
mainly features update from Ubuntu 20.04 to Ubuntu 22.04.

We do not expect any breakage unless if you are running pipeline relying on
the operating system version or on specific packages versions.

As usual, any issue with the infrastructure can be reported in
https://github.com/jenkins-infra/helpdesk if you have any problem.

For the infrastructure 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-Cp_qu6wdaPn-%3DD_PfF%3D8u0KuksFQE%2B0EVTOkKKOiycw%40mail.gmail.com.

ci.jenkins.io: rollout of Maven 3.9.1

[Damien Duportal]

Hello dear contributors!

Ths email to let you know that today, the Jenkins infrastructure team 
deployed a new version of Maven to ci.jenkins.io agents (and on the whole 
infrastructure), instead of Maven 3.9.0.

If you see any issue, please comment in 
https://github.com/jenkins-infra/helpdesk/issues/3482.

Thanks!

Damien Duportal, for the Jenkins Infra team

-- 
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/b7361d2c-2056-4c18-af5d-38833d30c29fn%40googlegroups.com.

Re: Maintenance on the infrastructure: 07 of March 2023 (LDAP restart)

[Damien Duportal]

Maintenance is now finished, all services are working.

Le mardi 7 mars 2023 à 12:42:02 UTC+1, Damien Duportal a écrit :

> Hello dear contributors !
>
> Today (07 March 2023) at 13:00 UTC, the Jenkins infrastructure team will 
> perform a maintenance on one of the production Kubernetes cluster.
>
> The most important impact is the service ldap.jenkins.io which will be 
> restarted as part of the operation: during this restart operation, 
> authentication on ci.jenkins.io, JIRA (issues.jenkins.io), 
> repo.jenkins-ci.org and any other controllers won't be possible.
>
> This restart should take 1 to 5 minute, and should happen between 13:00 
> UTC and 13:30 UTC.
>
>
> - For more details on the impacts (in status.jenkins.io): 
> https://status.jenkins.io/issues/2023-03-07-maintenance-prodpublick8s-sp/
> - For more details on the operation (in the Jenkins Infra helpdesk): 
> https://github.com/jenkins-infra/helpdesk/issues/3433
>
> For the Jenkins Infrastructure 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/98177041-d20b-4b9a-a61b-9854c2ceda23n%40googlegroups.com.

Maintenance on the infrastructure: 07 of March 2023 (LDAP restart)

[Damien Duportal]

Hello dear contributors !

Today (07 March 2023) at 13:00 UTC, the Jenkins infrastructure team will
perform a maintenance on one of the production Kubernetes cluster.

The most important impact is the service ldap.jenkins.io which will be
restarted as part of the operation: during this restart operation,
authentication on ci.jenkins.io, JIRA (issues.jenkins.io),
repo.jenkins-ci.org and any other controllers won't be possible.

This restart should take 1 to 5 minute, and should happen between 13:00 UTC
and 13:30 UTC.


- For more details on the impacts (in status.jenkins.io):
https://status.jenkins.io/issues/2023-03-07-maintenance-prodpublick8s-sp/
- For more details on the operation (in the Jenkins Infra helpdesk):
https://github.com/jenkins-infra/helpdesk/issues/3433

For the Jenkins Infrastructure 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%2BAiRi9RiB7oOm1vNOE2N4qeEN-WYW7nKvPwjge3-jzfM8u9LA%40mail.gmail.com.

Re: Jenkins Infra: Operation (upgrade) on all the Kubernetes clusters

[Damien Duportal]

The operation is finished and was successfull.

We saw a 2 min outage on ldap.jenkins.io while it was restarting, but no 
other impacts.

Thanks for the understanding.

Damien DUPORTAL, for the Jenkins Infra team

Le mercredi 22 février 2023 à 16:33:14 UTC+1, Damien Duportal a écrit :

> Hello dear Jenkins contributors,
>
> The Jenkins infrastructure team is operating all the Kubernetes clusters 
> to get them upgraded.
>
> The operation is planned:
>
> - Today (Wednesday 22 of February 2023) for Digital Ocean and Amazon 
> clusters. Expected impacts are:
>   > ci.jenkins.io build queue might grow until the upgrades are finished.
>   > The builds on ci.jenkins.io might be slowed down due to the caching 
> proxy rolling upgrade. We do not expect breakage (as the service is 
> replicated twice on each cloud) but it is the first operation on this 
> service.
>
> - Tomorrow (Thursday 23 of February 2023) for the Azure clusters (private 
> and publics). Expected impacts are:
>   > All the preview for *.jenkins.io websites will be either failing or 
> slowed down during the upgrade
>   > Unavailability of the LDAP (ldap.jenkins.io) during the restart + 
> slower response times on the other services (accounts.jenkins.io, 
> plugins.jenkins.io components, bots, private controllers)
>
>
> If you are curious, the following GitHub issue tracks the work: 
> https://github.com/jenkins-infra/helpdesk/issues/3387.
> The operation is also advertised on https://status.jenkins.io .
>
> If you have any problem related to this change, please open an issue on 
> https://github.com/jenkins-infra/helpdesk.
>
> Cheers,
>
> Damien DUPORTA, for the Jenkins Infra team
>

-- 
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/88917c97-d2ce-4b86-8203-410c6854188dn%40googlegroups.com.

Jenkins Infra: Operation (upgrade) on all the Kubernetes clusters

[Damien Duportal]

Hello dear Jenkins contributors,

The Jenkins infrastructure team is operating all the Kubernetes clusters to get 
them upgraded.

The operation is planned:

- Today (Wednesday 22 of February 2023) for Digital Ocean and Amazon clusters. 
Expected impacts are:
  > ci.jenkins.io  build queue might grow until the 
upgrades are finished.
  > The builds on ci.jenkins.io  might be slowed down 
due to the caching proxy rolling upgrade. We do not expect breakage (as the 
service is replicated twice on each cloud) but it is the first operation on 
this service.

- Tomorrow (Thursday 23 of February 2023) for the Azure clusters (private and 
publics). Expected impacts are:
  > All the preview for *.jenkins.io  websites will be 
either failing or slowed down during the upgrade
  > Unavailability of the LDAP (ldap.jenkins.io ) 
during the restart + slower response times on the other services 
(accounts.jenkins.io , plugins.jenkins.io 
 components, bots, private controllers)


If you are curious, the following GitHub issue tracks the work: 
https://github.com/jenkins-infra/helpdesk/issues/3387.
The operation is also advertised on https://status.jenkins.io 
 .

If you have any problem related to this change, please open an issue on 
https://github.com/jenkins-infra/helpdesk.

Cheers,

Damien DUPORTA, for the Jenkins Infra team

-- 
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/82513E4D-A5AF-417D-8705-25D6E21A82DE%40gmail.com.

Re: [Event]: FOSDEM'23

[Damien Duportal]

Hello folks, 

Just to let you know that the dinner will take place in the "Restaurant 
Persia" (Rue des Chapeliers 30, 1000 Bruxelles, Belgium - 
https://goo.gl/maps/a9KjqY6HMBK85Bz4A ).

We have a reservation at the name "Jenkins" for 10 people for 20:00 (was 
19:00 but I've moved it one hour later).
No problem if you join us later.

You can call me any time if you have any problem: +33.6.50.83.37.76 (SMS, 
Signal, calls) / +32.4.72.97.20.06 (SMS, calls).

Cheers,

Damien


Le dimanche 29 janvier 2023 à 15:43:10 UTC+1, Oleg Nenashev a écrit :

> Hi all,
>
> Just a quick update, we also want to have a Jenkins dinner on February 
> 4th, 19:00
> If you are interested in joining, please respond here: 
> https://forms.gle/v1E6dF6cusWBXjJs9
>
> Best regards,
> Oleg Nenashev
>
> On Thursday, January 5, 2023 at 8:43:48 PM UTC+1 alytong13 wrote:
>
>> Hi All,
>>
>> Happy New Year!
>>
>> We are a few short weeks away from FOSDEM'23 . 
>> Jenkins will have a stand at the conference and we are looking for 
>> volunteers to join us.
>>
>> The planning gdoc is HERE 
>> 
>>  
>> so if you're planning on attending FOSDEM and would like to participate in 
>> Jenkins activities pls sign up in the doc.
>>
>> Got suggestions? Pls add to the doc as well.
>>
>> BR,
>> 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/1a0e0b38-0bb6-4c36-aeb6-972e9b764300n%40googlegroups.com.

Re: Maintenance with downtime of JFrog Artifactory (repo.jenkins-ci.org) 18 of December of 2022

[Damien Duportal]

Dear developers,

the maintenance was done successfully. All the infrastructure is back to 
normal.

ci.jenkins.io is back online and processing the build queue since 14:10 UTC 
(was 973 build). 92 builds are left in the queue: expect 30min of work 
before being fully operationnal.

For the infra team,
Damien DUPORTAL

Le lundi 12 décembre 2022 à 16:52:09 UTC+1, Damien Duportal a écrit :

> Good suggestion, thanks Daniel!
>
> We've updated the issue and status.jenkins.io with this
> Le vendredi 9 décembre 2022 à 18:36:34 UTC+1, db...@cloudbees.com a 
> écrit :
>
>> On Fri, Dec 9, 2022 at 4:55 PM Damien Duportal  
>> wrote:
>>
>>> - No artifacts can be downloaded (failing builds on your machines as 
>>> well as builds on ci.jenkins.io)
>>>
>>
>> Could you put ci.j.io into quiet down mode for the time to prevent 
>> builds failing for infra reasons?
>>
>

-- 
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/3e5505ea-48ca-482d-abc0-5ac26b72835fn%40googlegroups.com.

Re: Maintenance with downtime of JFrog Artifactory (repo.jenkins-ci.org) 18 of December of 2022

[Damien Duportal]

Good suggestion, thanks Daniel!

We've updated the issue and status.jenkins.io with this
Le vendredi 9 décembre 2022 à 18:36:34 UTC+1, db...@cloudbees.com a écrit :

> On Fri, Dec 9, 2022 at 4:55 PM Damien Duportal  
> wrote:
>
>> - No artifacts can be downloaded (failing builds on your machines as well 
>> as builds on ci.jenkins.io)
>>
>
> Could you put ci.j.io into quiet down mode for the time to prevent builds 
> failing for infra reasons?
>

-- 
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/ea2b446b-a5bd-4d9d-8deb-a878c41380edn%40googlegroups.com.

Maintenance with downtime of JFrog Artifactory (repo.jenkins-ci.org) 18 of December of 2022

[Damien Duportal]

Hello dear contributors,

A maintenance of the JFrog Artifactory is planned for the Sunday 18 of 
December.

Expect a full downtime for roughly 6 hours (exact time window is not fixed 
yet).

During the maintenance:

- No release can be done
- No artifacts can be downloaded (failing builds on your machines as well 
as builds on ci.jenkins.io)


The infrastructure issue (with more details) is available here: 
https://github.com/jenkins-infra/helpdesk/issues/3288.

The status.jenkins.io website is up to date, and expect a blog post as 
additional communication in the upcoming hours.

Feel free to ask any question to the infra team!

Damien Duportal, for the Infra team

-- 
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/dbe3422d-a928-4ddf-ba4f-b820e318b82dn%40googlegroups.com.

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

[Damien Duportal]

+1

Le mercredi 7 décembre 2022 à 15:49:42 UTC+1, bma...@gmail.com a écrit :

> +1.
>
> At least such a move will make it very explicit for any new plugin that 
> only Maven really has /production/ support for Jenkins plugin dev.
>
> I think that we should still "allow" new plugins to use Gradle if they 
> wish so. But then they'll be very well aware that they got to be ready for 
> a lot of pain and much meta-work around the tooling itself for developing 
> their plugins.
> Which right now might be overlooked by new developers joining the 
> community and thinking that choosing one or another is simply a matter of 
> taste and habits.
>
> Le mer. 7 déc. 2022 à 15:19, Basil Crow  a écrit :
>
>> +1
>>
>> On Wed, Dec 7, 2022 at 2:20 AM Alexander Brandes  
>> wrote:
>> >
>> > Hey everyone,
>> >
>> > the Gradle JPI plugin lacks fundamental support of the jenkins.io 
>> infrastructure.
>> > There's no support for automated releases (CD, JEP-229), missing 
>> metadata for the plugin page and a few other limitations, which don't make 
>> it a great experience using it.
>> >
>> > Additionally, worth to note, the components mentioned above aren't new. 
>> People are proactively switching away from Gradle to Maven for better 
>> support and acceptance of our tooling, see ivy-plugin/49 for example.
>> >
>> > For the reasons stated, I would like to propose, that new plugin 
>> hosting requests use Maven, to have better toolchain support.
>> > I would be ready to lift this restriction again if the JPI plugin 
>> developers provide the same scope of tools like we have for Maven.
>> >
>> > Best,
>> > Alexander Brandes, for the hosting team
>> >
>> > --
>> > 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/bb8f56d3-727b-481a-9132-17bf5eddbbcdn%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/CAFwNDjq9xnyvJFoB33n07jORm7Hw6fSBf8FY5ho5FdGMDAiKug%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/5f43f822-37e4-45e2-85a2-3c60840ffcdfn%40googlegroups.com.

Re: JDK19 is now available on ci.jenkins.io

[Damien Duportal]

> Given this is the first time (I think) that a non-LTS JDK is provided, 
what are the plans around supporting this? 

We did not have any plan as we did not thought that much. Interesting point!

> Will it be removed once JDK 20 exists?

I guess yes. That would break pipelines using JDK19 though. Would that make 
sense to provide a support policy in the infra that would explain we follow 
the JDK lifecycles? 

Also, would that make sense to, instead, provide a "jdk-edge" that would be 
always the latest non LTS JDK instead (intermediate status: if there are no 
version AND it's name edge, we make it explicit that it could break at any 
time)?
Le jeudi 8 décembre 2022 à 17:09:34 UTC+1, db...@cloudbees.com a écrit :

> On Thu, Dec 8, 2022 at 11:02 AM 'Stephane Merle' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> Hello dear developers,
>>
>> I’m happy to announce that in order to allow contributors to prepare the 
>> future of Jenkins by working in advance with new JDK, we’ve added JDK19 on 
>> ci.jenkins.io.
>>
>
> Given this is the first time (I think) that a non-LTS JDK is provided, 
> what are the plans around supporting this? Will it be removed once JDK 20 
> exists? Once JDK 21 (next LTS) exists? Will it be supported indefinitely?
>

-- 
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/ba7929ca-ae1e-4619-a31b-4b01be0068a3n%40googlegroups.com.

Re: Next baseline shift

[Damien Duportal]

As explained by Jesse in 
https://github.com/jenkins-infra/pipeline-library/pull/541#issuecomment-1342884874,
 
changing the default of buildPlugin() could create problems. I'll close the 
PR as there is no value in changing the default as it.

The archetypes used to generate a new plugin project are already up to 
date: there is a documentation effort to be done that would be much more 
valuable (I heard that some documentation contributors are going to propose 
help) which make sense.

Eventually, once the documentation is up to date, we could add a message 
when "buildPlugin()" is called without argument, recomending to list 
explicit configurations.


Le mercredi 7 décembre 2022 à 16:51:06 UTC+1, Damien Duportal a écrit :

> Prepared the draft PR for "buildPlugin()": 
> https://github.com/jenkins-infra/pipeline-library/pull/541
>
> Le jeudi 1 décembre 2022 à 19:16:40 UTC+1, m...@basilcrow.com a écrit :
>
>> I released the first tranche of PRs in 4.52 
>> <https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.52>. Next 
>> week I will take a look at migrating from Jetty 9 to Jetty 10 in the plugin 
>> build toolchain.
>>
>

-- 
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/face200b-1265-4e42-9194-eb2a46f00916n%40googlegroups.com.

Re: Next baseline shift

[Damien Duportal]

Prepared the draft PR for "buildPlugin()": 
https://github.com/jenkins-infra/pipeline-library/pull/541

Le jeudi 1 décembre 2022 à 19:16:40 UTC+1, m...@basilcrow.com a écrit :

> I released the first tranche of PRs in 4.52 
> . Next 
> week I will take a look at migrating from Jetty 9 to Jetty 10 in the plugin 
> build toolchain.
>

-- 
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/bd858e25-590e-4dc8-8c01-d271c41052d1n%40googlegroups.com.

Deleting Community (Azure) Functions and Infra (Azure) Functions

[Damien Duportal]

Hello dear contributors and former contributors.

This thread is a call for help about the infra.

As described in https://github.com/jenkins-infra/helpdesk/issues/3258, we are 
cleaning up unused resources on the Azure cloud and are wondering if it is ok 
to delete the Azure functions that seems unused.
Also, as per 
https://github.com/jenkins-infra/helpdesk/issues/3258#issuecomment-1339179136 
<https://github.com/jenkins-infra/helpdesk/issues/3258#issuecomment-1339179136>,
 we do not see any usage of these functions anymore, so we want to proceed to 
deletion.

If you have any memory of these functions and their usages and feel like we 
should not delete them in Azure, please net us know by answering to this email.

Without any blocker, we’ll proceed to delete these cloud resources in 7 days 
(aka. the 13th of December).

Thanks in advance for your time and knowledge sharing!

Damien Duportal, for the infra team

-- 
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/9D519A28-C923-4E18-BC62-B5D63B4FBCDB%40gmail.com.

Re: Next baseline shift

[Damien Duportal]

+1 for me on the proposal to require a 2.361 baseline. I'm in favor of a 
late 2022 (after 2.375.1 of course) as the end of year is usually spent on 
low activity so it will let plugin maintainer some time to discover and fix 
any issues caused by this change.

> Independently of that, we can consider switching the default JDK for 
ci.jenkins.io `buildPlugin` from 8 to 11. 

I volunteer to make this change in the form of a draft PR to the 
jenkins-infra/pipeline-library until we are ready to go.


Damien

Le mardi 29 novembre 2022 à 10:19:10 UTC+1, ullrich...@gmail.com a écrit :

> +1 from me as well (after release of 2.375.1)
>
> > Am 28.11.2022 um 19:50 schrieb Basil Crow :
> > 
> > Historically we have supported old baselines for a long time in the
> > build toolchain. The current build toolchain supports baselines as far
> > back as 2.249. This provides a high degree of flexibility for plugin
> > maintainers and ultimately end users.
> > 
> > Sustaining this level of compatibility across complex transitions like
> > the move to Java 11 and Jetty 10 comes at significant build toolchain
> > complexity, either in the form of conditional logic in a single-branch
> > build toolchain scheme (the current status quo) or in the form of
> > multiple branches (a hypothetical scenario). For example, the test
> > harness needs to support Java 8 in order to support 2.249, the need to
> > support Java 8 means the test harness cannot move to Jetty 10 (which
> > requires Java 11), and the test harness' continued use of Jetty 9
> > requires core to retain support both Jetty 9 and 10 (even though only
> > Jetty 10 is used in production use cases). Similarly, conditional
> > logic is required to set the Maven compiler release version to 11 for
> > plugins when newer baselines are in use, and even then that
> > conditional logic tends to trip up IDEs.
> > 
> > For these reasons, it is desirable to require a baseline of 2.361 or
> > later (and therefore Java 11) for plugins in the build toolchain
> > sooner rather than later. The advantage is that this allows us to
> > simplify and clean up conditional logic that is increasingly becoming
> > less relevant and a maintenance burden. The disadvantage of requiring
> > a baseline of 2.361 or later for plugins in late 2022 or early 2023
> > (as opposed to our usual timeline of e.g. late 2023 or early 2024) is
> > that it is more of an imposition on plugin maintainers and users of
> > older LTS lines. I believe that the advantages outweigh the
> > disadvantages and that we should do this sooner rather than later,
> > ideally in late 2022.
> > 
> > If the consensus is that we are OK with requiring a baseline of 2.361
> > or later for plugins in late 2022 (i.e., after the release of 2.375.x
> > LTS) or early 2023 (i.e., after the release of the next major LTS line
> > after 2.375), then I explicitly commit to implement the change in the
> > plugin parent POM (e.g., with regard to Java 8), test harness (e.g.,
> > with regard to Unicode properties files), HPI plugin (e.g., with
> > regard to the Maven compiler release version), core (e.g., with regard
> > to Jetty 9), annotation indexer, symbol annotation library, version
> > number library, and access modifier library, noting in the release
> > notes for all eight (8) components that this is a breaking change for
> > plugin maintainers and that plugin maintainers must use a baseline of
> > 2.361 or later when upgrading to the latest build toolchain.
> > 
> > If you are in favor of requiring a baseline of 2.361 or later for
> > plugins in late 2022 or early 2023 and with me implementing this
> > transition in the manner described, please reply with your timeline
> > preference (either late 2022 or early 2023). If you are in favor of
> > maintaining a stable branch of the abovementioned eight (8) components
> > for older LTS lines, please reply stating whether you are willing to
> > do the implementation and release work (noting that I explicitly
> > decline to do this implementation and release work). If you are in
> > favor of any other proposal, please reply stating the alternative
> > proposal and whether you are willing to do the implementation work.
> > 
> > Thanks,
> > Basil
> > 
> > -- 
> > 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/CAFwNDjo4AV%3DuY-f1R%3DjTFTfwe-m8TdxONt4Ly7yhU3JpPTJj6w%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 

Permission Request for the community Google Document "Jenkins Social Media Covers / Artwork"

[Damien Duportal]

Hello there,

Both Bruno Verachten (gount...@gmail.com) and I (damien.dupor...@gmail.com) 
would like to get write access to the Community Google Document named "Jenkins 
Social Media Covers / Artwork" 
(https://docs.google.com/presentation/d/1Q1PgNnRTgzBpVRXPqQo3PudzCa2eoc6_1_NRjFRMLrU/edit#slide=id.g876094df05_0_11
 
) in order to be able to update and generate social media covers when we 
upload SIG meeting videos to Youtube (at least).

Cheers,

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/3ecb19a9-a6ee-4e99-a1a4-1e2e9605c6b0n%40googlegroups.com.

Re: JDK 11.0.17+8

[Damien Duportal]

For information, we have triggered the deployment of these new JDK11 and 
JDK17 versions in https://github.com/jenkins-infra/jenkins-infra/pull/2463 
for agents, and https://github.com/jenkins-infra/jenkins-infra/pull/2455 + 
https://github.com/jenkins-infra/jenkins-infra/pull/2456 for 
ci.jenkins.io's tools.

We're going to open an issue to track the work on providing a "edge 
version" of these tools. Thanks a lot!

Le jeudi 27 octobre 2022 à 16:54:07 UTC+2, m...@basilcrow.com a écrit :

> You are welcome. Java 17.0.5 does not seem to contain any fixes that
> are relevant to Jenkins. Adding 11.0.17 and 17.0.5 as JDK tools on
> ci.jenkins.io might help as you test the upgrade but would likely not
> be of much use once the upgrade has been completed. However, I could
> think of a use case for a permanent JDK tool for the bleeding edge
> version of Java (e.g., Java 18 yesterday, Java 19 today, or Java 20
> tomorrow): setting up some CI build (not on the critical path) to run
> speculative tests of Jenkins core or plugin builds on the latest Java
> runtime to proactively discover new issues as soon as they are
> introduced.
>

-- 
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/240920b3-e4ed-4ba1-8d25-4a31b5920efen%40googlegroups.com.

Re: JDK 11.0.17+8

[Damien Duportal]

First of all, thanks a lot Basil for this thorough check and feedback!

Second, we are adding JDK17 17.0.5+8 to this deadline (just popped in our 
system).

Finally, if it helps, we can totally add these 2 new JDK as tools in 
ci.jenkins.io, with a new such as 'jdk11-next' and 'jdk17-next' to allow 
easy testing for BOM or any other project: does that make sense?


Damien

Le mercredi 26 octobre 2022 à 18:26:32 UTC+2, m...@basilcrow.com a écrit :

> Checking the release notes at
> https://www.oracle.com/java/technologies/javase/11-0-17-relnotes.html
> I see 11.0.17 contains fixes for JDK-8231454 and JDK-8268773, which
> are relevant to Jenkins. The update of tzdata will also resolve
> JENKINS-69635. The fix for JDK-8231454 was already worked around in
> Pipeline: Groovy and Script Security, and I manually stepped through
> the workaround code on 11.0.17 to verify that it was harmless (though
> unnecessary) on an 11.0.17 JVM with the fix for JDK-8231454. The fix
> for JDK-8268773 should not be needed as of recent versions of
> Remoting. I ran my local development Jenkins controller on 11.0.17 and
> did not experience any problems running various job types
> interactively. I also ran the following test suites on 11.0.17
> successfully:
>
> - Jenkins core smoke tests
> - Pipeline: Groovy
> - Script Security
> - Remoting
>
> A quick perusal of
> https://mail.openjdk.org/pipermail/jdk-updates-dev/2022-October/ does
> not appear to show any major regressions in the past week since the
> release took place, unlike 11.0.16 (where
> https://mail.openjdk.org/pipermail/jdk-updates-dev/2022-August/016460.html
> was being actively discussed).
>
> Based on the above, I do not anticipate any problems with the C2 JIT
> compiler, the metaspace, or container awareness for cgroups v2 (which
> are the three categories where we experienced issues with 11.0.16). If
> it is feasible without too much effort to run the BOM test suite
> against 11.0.17 before our agents are upgraded, I think that would be
> safest. But if that is not practical, I think it would be fine to
> upgrade our agents and merely monitor core and BOM builds afterward to
> ensure no new failures are introduced.
>

-- 
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/bf0bac12-ec85-492d-b7bc-9777388a9e16n%40googlegroups.com.

Re: Request for access to YouTube account

[Damien Duportal]

+1 for me!

Bruno's work on the SIG is clearly an indicator of the trust we can put.
I'm also convinced that he'll have plenty of idea to 
documente/describe/improve the SIG publication process

Le mercredi 26 octobre 2022 à 15:07:33 UTC+2, ullrich...@gmail.com a écrit :

> +1
>
> Am 26.10.2022 um 14:42 schrieb timja...@gmail.com :
>
> +1
>
> On Wednesday, 26 October 2022 at 13:18:13 UTC+1 goun...@gmail.com wrote:
>
>> Hi group,
>>
>> I sometimes run the Platform SIG meeting (like 
>> https://www.youtube.com/watch?v=R2322YxIciQ) and would like to be able 
>> to post the resulting video to YouTube when Mark is on PTO for example.
>> Therefore I'm asking the authorization to be granted access to the 
>> Youtube account/channel (to upload the recording to the channel).
>>
>> Best wishes,
>>
>> Bruno Verachten
>>
>
> -- 
> 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/77f08589-693b-46cd-96e4-cb665587b9a9n%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/e95988eb-5cb5-498f-bfea-27c23753cd27n%40googlegroups.com.

JDK 11.0.17+8

[Damien Duportal]

Hello dear contributors,

The Jenkins Infrastructure team received automatic notification of a new 
JDK11 version: 11.0.17+8 (changelog at 
https://foojay.io/java-11/?version=11.0.17=102022=component).

Our usual process is to upgrade the JDK on the next update of the agent 
templates for ci.jenkins.io. 

However last time we bumped the JDK, it created regressions and unexpected 
work on some Jenkins Core change requests (not mentioning thet 11.0.16 line 
had to be patched because of memory issues to 11.0.16.1).

In order to avoid as much disruption as posible, we are seeking your 
feedbacks on this upgrade.

Here is the timeline proposal: 

We would want to upgrade the JDK11 on the ci.jenkins.io agents for the 
Thursday 03 of November (The next LTS release is the 2nd).

Is there any voice against this timeline for change?

Thanks in advance

Damien, for the infrastructure team

-- 
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/585dada5-fb24-4fc1-ae98-ba9ba149a3dcn%40googlegroups.com.

Re: Marking plugins for adoption

[Damien Duportal]

That looks a sane change. Worst case, any developer could still claim back 
their maintainership if someone adopt their plugin.

Thanks for this work Adrien!

Le vendredi 21 octobre 2022 à 10:33:33 UTC+2, Adrien Lecharpentier a écrit :

> Hello,
>
> while I was updating some permissions I had on plugins deployment to 
> Artifactory, I noticed that a lot of plugins have no developers listed. 
> This means that no one is maintaining them.
>
> So I proposed 
> https://github.com/jenkins-infra/repository-permissions-updater/pull/2891 
> to automatically mark plugins with no developers as up for adoption. 
>
> Currently, 104 plugins are mark as such, and only 92 are labelled with way 
> in the update center. However, I detect at least 327 plugins with no 
> developers. Probably more but some permission files have no `github` info.
>
> It could be seen as harsh but I think it is just fair to users and us. 
>
> What do you think? 
> -- Adrien
>

-- 
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/f3ddf9e9-a05d-47ba-9f90-28d8eec0e86an%40googlegroups.com.

[ci.jenkins.io] Agent template update

[Damien Duportal]

Hello dear developers,

We just updated the agent templates on ci.jenkins.io (Linux VMs, Linux 
Containers and Windows VMs) to ensure that the 2 `git` CVEs 
https://github.com/git/git/security/advisories/GHSA-3wp6-j8xr-qw85 and 
https://github.com/git/git/security/advisories/GHSA-rjr6-wcq6-83p6 are 
fixed in our build environments (more details on 
https://github.blog/2022-10-18-git-security-vulnerabilities-announced/).

It also includes the changes listed in 
https://github.com/jenkins-infra/packer-images/releases/tag/0.45.0 . Most 
notable  are:

- Git to 2.38.1 (to fix CVEs)
- JDK11 bumped to 11.0.16.1+1
- JDK17 bumped to 17.0.4.1+1


Please also note that Docker 20.10.20 
(https://docs.docker.com/engine/release-notes/#201020) is also in the 
party, as well on all of our machines.

For the Jenkins Infra,

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/7cd5079f-58c2-44a8-900e-62fd73ec6be6n%40googlegroups.com.

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

[Damien Duportal]

+1

Alex involvement on the project speaks for itself!

Le lundi 17 octobre 2022 à 19:33:09 UTC+2, ga...@gavinmogan.com a écrit :

> Nobody on the governance meeting was against it
>
> On Mon, Oct 17, 2022 at 10:14 AM Oleg Nenashev  
> wrote:
>
>> +1, thanks for all contributions @NotMyFault!
>>
>> P.S: On behalf of the exclusive weekly release trainwreck club, please 
>> make sure to tweet "Not my fault" the first time you break the weekly 
>> release :P 
>>
>>
>> On Saturday, October 15, 2022 at 7:58:15 PM UTC+2 adrien.lec...@gmail.com 
>> wrote:
>>
>>> of course +1.
>>>
>>>
>>> Le sam. 15 oct. 2022 à 18:31, Alexander Brandes  a 
>>> écrit :
>>>
 Thanks everyone, I'd be very happy to join the core team :)

 On Friday, 14 October 2022 at 13:48:48 UTC+2 hle...@cloudbees.com 
 wrote:

> +1
>
> On Fri, Oct 14, 2022 at 1:18 PM James Nord  wrote:
>
>> +1
>>
>> On Thu, 13 Oct 2022 at 20:16, Pedro Amaral  
>> wrote:
>>
>>> +1
>>>
>>> On Thu, Oct 13, 2022 at 10:12 AM 'Kevin Martens' via Jenkins 
>>> Developers  wrote:
>>>
 +1 from me too!

 On Thu, Oct 13, 2022 at 5:52 AM 'Olblak' via Jenkins Developers <
 jenkin...@googlegroups.com> wrote:

> +1  :) 
>
> On Thu, Oct 13, 2022, at 11:39 AM, 'Stephane Merle' via Jenkins 
> Developers wrote:
>
> +1 for me too
> good luck Alexander
>
> On Thu, Oct 13, 2022 at 9:44 AM 'Daniel Beck' via Jenkins 
> Developers  wrote:
>
>
>
> On Thu, Oct 13, 2022 at 9:11 AM Tim Jacomb  
> wrote:
>
> I would like to propose Alexander Brandes (@NotMyFault 
> ) to join the Jenkins Core team.
>
>
> +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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJFQvvfqtNixCGOk34quz7Fm_bu0as_QNOVxX%2BXY5jvwA%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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO%2B-N1qxoBRFwKk4%3DJdVY%2B_gns%2BCaMd8J_DC9xuWnRqzEfYDZA%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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/b67d978b-bc39-4cb4-a2a3-3ad69cdf621c%40app.fastmail.com
>  
> 
> .
>


 -- 
 Kevin Martens
 Technical Content Developer
 CloudBees, Inc.


 E: kmar...@cloudbees.com

 Pronouns: He/Him/His

 -- 
 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/CAP92yNdJ5WrfjJith1bzawZiEsEJw%2BhG4SDv6GxLhVHT6fmjGA%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-de...@googlegroups.com.
>>> To view this discussion on the 

Re: [ci.jenkins.io] ACI (Windows containers) builds are queued

[Damien Duportal]

Service is now back in full healthy state and all the queued builds had 
been process.

Le mardi 18 octobre 2022 à 18:17:40 UTC+2, Damien Duportal a écrit :

> Please note that the Linux containers are now also impacted. We are on it.
>
> Le mardi 18 octobre 2022 à 18:05:09 UTC+2, Damien Duportal a écrit :
>
>> Hello dear developers,
>>
>> The Jenkins Infra team is working on the ACI templates: as a result, the 
>> builds are currently queued. We should unblock in ~1h, no build should be 
>> lost.
>>
>> Damien 
>>
>

-- 
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/4f72be1e-9062-4273-8a4d-6b0a14d558abn%40googlegroups.com.

Re: [ci.jenkins.io] ACI (Windows containers) builds are queued

[Damien Duportal]

Please note that the Linux containers are now also impacted. We are on it.

Le mardi 18 octobre 2022 à 18:05:09 UTC+2, Damien Duportal a écrit :

> Hello dear developers,
>
> The Jenkins Infra team is working on the ACI templates: as a result, the 
> builds are currently queued. We should unblock in ~1h, no build should be 
> lost.
>
> Damien 
>

-- 
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/9ecba128-e929-4938-b316-1292090c2f1en%40googlegroups.com.

[ci.jenkins.io] ACI (Windows containers) builds are queued

[Damien Duportal]

Hello dear developers,

The Jenkins Infra team is working on the ACI templates: as a result, the 
builds are currently queued. We should unblock in ~1h, no build should be 
lost.

Damien 

-- 
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/b0f41d2e-7946-4e61-a3a3-a984dc92a275n%40googlegroups.com.

[ci.jenkins.io] New agent template version (Linux/Windows) with Git 2.38.0

[Damien Duportal]

Hello dear developers!

The Jenkins Infra team is deploying 
(https://github.com/jenkins-infra/jenkins-infra/pull/2429) a new agent 
template model which features Git v2.38.0 (as per 
https://github.com/jenkins-infra/packer-images/releases/tag/0.44.0).

If you see any issue with your build that looks related to this Git version 
bump, please open an issue in https://github.com/jenkins-infra/helpdesk or 
answer to this email with a link to the failing build and a bit of context, 
so we could rollback quickly the change if it blocks anything.

For the Jenkins 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/ad121f23-b89c-49d2-92e3-d98860bf7eb2n%40googlegroups.com.

Re: pipeline-graph-view-plugin on infra.ci.jenkins.io

[Damien Duportal]

+ 1 Let's go !

Le vendredi 16 septembre 2022 à 19:42:06 UTC+2, mc.ca...@gmail.com a écrit :

> +1
>
> On Friday, 16 September 2022 at 19:40:01 UTC+2 Mark Waite wrote:
>
>> +1 from me.  It's working very well on my instance.  All the rendering 
>> issues that I had seen before are resolved.
>>
>> On Friday, September 16, 2022 at 11:33:42 AM UTC-6 timja...@gmail.com 
>> wrote:
>>
>>> +1
>>>
>>> On Fri, 16 Sep 2022 at 18:01, 'Herve Le Meur' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
 Hello,

 https://github.com/jenkinsci/pipeline-graph-view-plugin/ has received 
 a lot of updates lately, and we would like to install it on 
 infra.ci.jenkins.io in order to test it and make feedback.

 Any objections?

 Regards and great weekend all,

 Hervé for the Jenkins Infra Team

 -- 
 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/CAL-LwjxKhxKeRpXEe0e7vY1xDLAozE21Wocpe2E%3DuvWfcE_GJw%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/6c13dd9b-6816-45e8-9a9a-5f0d476e57bfn%40googlegroups.com.

Re: Improvement and change of image for linux jnlp-maven agents

[Damien Duportal]

Thanks Basil for opening 
https://github.com/jenkins-infra/helpdesk/issues/3130 following this 
operation.

We have rolled-out a fix to ensure that your agent running as linux 
containers are now using the C.UTF-8 locale (instead of ANSI) which was a 
regression.

More news tomorrow, but this specific problem should be fixed for the 
uypcoming 24 hours.

Thanks for your patience and contributions.

Cheers,

Damien


Le jeudi 15 septembre 2022 à 08:43:49 UTC+2, sme...@cloudbees.com a écrit :

>
> Hi all,
> in the process of unification of the images used for the agents within 
> ci.jenkins.io we plan to change the images used for the linux container 
> agents jnlp-maven-8/11/17 tomorrow Thursday 15 of September around 12:00am 
> UTC. Do not hesitate to open an helpdesk issue here 
> https://github.com/jenkins-infra/helpdesk/issues/ in case you find out 
> that something goes wrong.
> Thanks for your help.
>
> Stéphane MERLE for the SRE team.
>
> -- 
> Stéphane MERLE
> Staff SRE
>

-- 
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/36719ca3-8de9-4e17-85b8-c05f09bd7439n%40googlegroups.com.

Re: Failing Windows build on ci.jenkins.io

[Damien Duportal]

Thanks Basil for restarting the build!

After a quick check, there was no issue on the infrastructure.

But the build reached the timeout of 1 hour (default for plugins as per 
https://github.com/jenkins-infra/pipeline-library/blob/master/vars/buildPlugin.groovy#L13)
 
which stopped the build.

The underlying infrastructure is a Windows Container (with Maven 3.8.4 and 
a JDK8) running in Azure Container Instance services: it seems that the 
baseline performance for this service is having a lot of differences 
between 2 identical tasks (can 2x faster!) which explains the timeout. The 
infrastructure team is studying how to improve this situation, thanks for 
raising this concern.

Damien, for the Infra team



Le mardi 23 août 2022 à 00:23:42 UTC+2, m...@basilcrow.com a écrit :

> I restarted your build at
>
> https://ci.jenkins.io/job/Plugins/job/pipeline-utility-steps-plugin/job/PR-162/2/
> and the second build ran to completion (with a test failure in your
> new test).
>

-- 
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/bd7e087f-4cce-4f26-b386-94ebbfb16b85n%40googlegroups.com.

[ci.jenkins.io] Update of the VM agent templates

[Damien Duportal]

Hello dear contributors,

This email to inform you that the Jenkins Infra team is going to update the 
template of the agents on ci.jenkins.io of type "Virtual Machine" (both 
Azure VMs and Amazon EC2).

The changelog is available there: 
https://github.com/jenkins-infra/packer-images/releases/tag/0.39.0

Cheers,

Damien, for the infra team

-- 
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/1b1a35c2-2a6b-49d5-9c2f-7dcc600f9b5fn%40googlegroups.com.

[ci.jenkins.io] Update of the agent tools - 04/05 Aug. 2022

[Damien Duportal]

Hello dear contributors and maintainers!

For information, the infra-team is updating the tooling of the agents on 
ci.jenkins.io.

Main changes are located around JDK upgrade:

- Yesterday, we bumped JDK 11 to the latest 11.0.16+8 and JDK 17 to latest 
17.0.4+8.
- Today, we'll bump the JDK8 to the latest 8u345-b01

(Less important, but the azure CLI, the gh CLI, docker-compose CLI and the 
remoting protocol are also upgraded).

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/50fa7ac3-6101-42ce-ae10-0d29ad7fe2edn%40googlegroups.com.

ci.jenkins.io: performing maintenance operations

[Damien Duportal]

Hello dear contributors,

The Jenkins Infra team is going to perform a set of maintenance operations 
on ci.jenkins.io, as described on status.jenkins.io .

Expect Controller restart and some build to fail.

Sorry for the inconvenience,

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/0cbc518a-7f4f-4310-b5c3-0a2274aa1e1dn%40googlegroups.com.

Re: Is there interest for GitHub issues in core components?

[Damien Duportal]

>> The barrier to entry on Jira is a lot higher than on GitHub, many people 
struggle to report issues. 

>I do not think the barrier to entry on Jira is prohibitively high. As 
others have noted, reporting issues requires a certain degree of due 
diligence, including writing steps to reproduce, expected results, and 
actual results. 

Reporting issues with due diligence is absolutely not related to GitHub or 
JIRA. Both provides mecanisms (templates, etc.) to help on this area but 
both can be used and abused to report weird messages.

Using JIRA means "keep the same people and put an entry barrier": that is 
how we felt for the use case of the infra. By moving to GitHub we lost the 
"strictness" described by Basil (EPIC, links beetween issue with associated 
causality such as "blocked by", etc.).
In our case, loosing this "strictness" was clearly an annoyance, but 
compared to the sudden participation it was clearly worth the change.

As a Jenkins user, I think it took me 6 years before being able even start 
thinking about opening an issue. The mental energy that it consume only for 
"creating the account + understand that there is one project for core & ALL 
plugins + being able to search if an issue already exist + understanding 
this body syntax which is its own" (not mentioning what could go wrong 
along: account issue, permission issue, JIRA suddenly loosing message 
content" is HIGH.
So most of the time, I did not even started the process otherwise I was 
driven crazy and unable to have the "due diligence" because it was 
exhausting.

For the infra project, going back is not an option unless we would want to 
remove any willingness for people to contribute or open issues.

> If we expect and even encourage that most plugins switch to GitHub for 
issue tracking, so that we expect Jira (Cloud) to be used mainly for core 
and associated components and tools (plus the `SECURITY` project), does 
that change the calculus? There would still be plenty of people creating an 
account just to report some sort of core bug (or a bug which they cannot 
easily map to a particular plugin), but probably not tens of thousands of 
them.

Really smart idea!
Le vendredi 1 juillet 2022 à 17:07:53 UTC+2, Jesse Glick a écrit :

> On Fri, Jul 1, 2022 at 3:22 AM 'Daniel Beck' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> we have 130k users in Jira. While many are probably not legitimate users 
>> of Jira […or] haven't been logged in in years
>>
>
> If we expect and even encourage that most plugins switch to GitHub for 
> issue tracking, so that we expect Jira (Cloud) to be used mainly for core 
> and associated components and tools (plus the `SECURITY` project), does 
> that change the calculus? There would still be plenty of people creating an 
> account just to report some sort of core bug (or a bug which they cannot 
> easily map to a particular plugin), but probably not tens of thousands of 
> them.
>

-- 
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/4b7b8879-a262-4324-b3de-92ae3227843bn%40googlegroups.com.

Re: New member of jenkins.io triage team

[Damien Duportal]

+1 for me as well

Le mercredi 6 juillet 2022 à 07:58:26 UTC+2, timja...@gmail.com a écrit :

> +1
>
> On Wed, 6 Jul 2022 at 06:50, 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> No objections by me.
>>
>> On Tue, Jul 5, 2022 at 2:01 PM Mark Waite  wrote:
>> >
>> > Kevin Martens has been running Jenkins Docs office hours (Europe) and 
>> contributing to Jenkins documentation.  I'd like to add him to the 
>> jenkins.io triage team in preparation for him eventually becoming a copy 
>> editor.
>> >
>> > The process that has been outlined previously is that we first assign 
>> people to the triage team, then mentor them for a time.  Once there is a 
>> pattern of contributed reviews, then the docs officer or the contributor 
>> proposes that they be added to the copy editors team.
>> >
>> > I propose that the following regular attendees at Docs office hours be 
>> added to the jenkins.io triage team:
>> >
>> > Kevin Martens  - Changelog and upgrade guide for 2.346.1, Docs office 
>> hours (Europe) leader, screenshot update pull requests, helped with docs 
>> projects in She Code Africa Contributnon
>> >
>> > During the mentoring period, he will need to submit an individual 
>> contributor license agreement and become a member of the jenkins-infra 
>> organization.  Once the mentoring period is complete and the ICLA's have 
>> been submitted, we'll propose that he be made a copy editor.
>> >
>> > 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/d4a01ebe-d437-4ef1-bb29-33170f249674n%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/CAG%3D_Dus_Gg%2BTykcPYDk8bHhhdfryg0-sv0pHvD2%3DqEspBUZQ9w%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/b2ddf151-16c2-4efa-b28f-93cb4d63e902n%40googlegroups.com.

Re: Experiencing high response time from repo.jenkins-ci.org

[Damien Duportal]

The outage finished roughly 2 hours after its started yesterday. JFrog 
identified a few slow request but nothing obvious.

Our monitoring confirms that repo.jenkins-ci.org has been acting normal 
since monday 08h00am UTC: no more slowness.

Cheers

Damien

Le lundi 4 juillet 2022 à 09:18:34 UTC+2, Damien Duportal a écrit :

> Good Monday dear contributors friends!
>
> The Jenkins infrastructure monitoring detected an unusual response time 
> since today ~06h00am UTC.
>
> You should expect slow download of dependencies from repo.jenkins-ci.org, 
> on bot h your environments and also on ci.jenkins.io.
>
> We are keeping status.jenkins.io up-to-date with latest information we'll 
> receive from JFrog.
>
> The Jenkins Infra Team
>

-- 
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/bba0d3a8-3b11-4455-b440-00d0533fc776n%40googlegroups.com.

Experiencing high response time from repo.jenkins-ci.org

[Damien Duportal]

Good Monday dear contributors friends!

The Jenkins infrastructure monitoring detected an unusual response time 
since today ~06h00am UTC.

You should expect slow download of dependencies from repo.jenkins-ci.org, 
on bot h your environments and also on ci.jenkins.io.

We are keeping status.jenkins.io up-to-date with latest information we'll 
receive from JFrog.

The Jenkins Infra Team

-- 
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/1a5ff4f2-0b8b-4594-b419-43688743bea6n%40googlegroups.com.

Re: Proposal: Jenkins Core PR reviewers team

[Damien Duportal]

+1 for me as well (with the hat of infra officer)

Le lundi 20 juin 2022 à 11:19:47 UTC+2, mc.ca...@gmail.com a écrit :

> Follow up to my initial message, I would like to join both teams, the core 
> maintainer and reviewer one, where the latter would only be for review 
> requests, as I'm already inheriting these permissions as release team 
> member.
>
> Cheers
>
> On Sunday, 19 June 2022 at 21:44:12 UTC+2 Mark Waite wrote:
>
>> +1 from me as well.
>>
>> On Sun, Jun 19, 2022 at 1:33 PM Tim Jacomb  wrote:
>>
>>> +1 although I'd also be +1 on core maintainer status as well for Alex.
>>>
>>> He's helped out a lot recently
>>>
>>> Cheers
>>> Tim
>>>
>>> On Sun, 19 Jun 2022 at 17:36, Alexander Brandes  
>>> wrote:
>>>
 Hey everyone,

 late reply but I would be interested in joining as well.

 Since I joined the release team a few months ago to take care of the 
 last point release and the upcoming 2.346 LTS release, I moderate a bunch 
 of core PRs by applying labels, fixing up changelog entries, PR titles or 
 spinning up ATH and bom runs, if needed; granted by the permissions as 
 release team member, besides the typical reviews for PRs.
 Aside the LTS PRs, I merged a few minor ones in the past fulfilling the 
 requirements to be eligible for a merge too, to facilitate a backport into 
 LTS or to unblock and prevent a delay of a weekly release e.g.

 Kind regards
 Alex

 On Friday, 16 April 2021 at 22:51:04 UTC+2 Oleg Nenashev wrote:

> Welcome aboard Basil! I have updated the permissions and added you to 
> the Jenkins Core PR reviewers team.
>
> Just for the record, the Pull request review guidelines and other 
> maintainer docs are available here 
> .
>  
> We are always interested in onboarding more core maintainers, and 
> everyone 
> is welcome to participate.
>
> Best regards,
> Oleg Nenashev
>
>
> On Thu, Apr 15, 2021 at 10:35 PM Oleg Nenashev  
> wrote:
>
>> +1. I will grant Basil permissions tomorrow if no negative feedback. 
>> And again, thanks to Basil for all the contributions to Jenkins!
>>
>> On Thu, Apr 15, 2021, 22:33 Tim Jacomb  wrote:
>>
>>> +1
>>>
>>> On Thu, 15 Apr 2021 at 19:07, Mark Waite  
>>> wrote:
>>>
 +1 from me that Basil becomes part of the core PR reviewers team.

 On Thu, Apr 15, 2021 at 11:54 AM Basil Crow  
 wrote:

> I'm interested in joining the Core PR reviewers team as well.
>
> -- 
> 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/CAFwNDjrnHZmDg-JmtP%2B3fO%3Df1w_uNRFevrOy9dHfsq29n0xDnA%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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFoN%3DsiPzRHcLHJyJbs1xBqnFVAkfQONGcwcE4a90hGhw%40mail.gmail.com
  
 
 .

>>> -- 
>>> You received this message because you are subscribed to a topic in 
>>> the Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/0sdrcSOQW64/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifbZ_nDppzESg7VQSzM3-HKzk96V%2B7WYDP5-LFwoHZhRg%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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/b3c16811-4f63-4550-99ed-02179c2e1b5en%40googlegroups.com
  

Re: Infra Outage: Update Center not updating

[Damien Duportal]

Hello y'all.

The outage is now finished and all plugin releases are now visible as usual.

More details on https://github.com/jenkins-infra/helpdesk/issues/2950 if 
you are interested (and if you want to give feedbacks).

Sorry for the inconvenience.

The Jenkins Infra team

Le mardi 31 mai 2022 à 19:16:07 UTC+2, Damien Duportal a écrit :

> Hello dear contributors,
>
> We are experiencing a minor outage on the infra: the update center is not 
> updated since earlier today (around noon UTC approximatively).
>
> It means that any plugin released since the last update are not visible 
> for end users.
> It's classified as minor because end user can still install plugins.
>
> More details on https://github.com/jenkins-infra/helpdesk/issues/2950.
>
> Summary: we need to renew the update-center certificate and we need help 
> from one of the owner of the associated Certificate Authority key (to allow 
> us signing the new one).
>
> We'll keep you updated in the next 24 hours.
>
> 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/31c1b26b-303b-4259-bdd1-762b9c1a755fn%40googlegroups.com.

Infra Outage: Update Center not updating

[Damien Duportal]

Hello dear contributors,

We are experiencing a minor outage on the infra: the update center is not 
updated since earlier today (around noon UTC approximatively).

It means that any plugin released since the last update are not visible for 
end users.
It's classified as minor because end user can still install plugins.

More details on https://github.com/jenkins-infra/helpdesk/issues/2950.

Summary: we need to renew the update-center certificate and we need help 
from one of the owner of the associated Certificate Authority key (to allow 
us signing the new one).

We'll keep you updated in the next 24 hours.

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/1d1b4e0b-495a-4a9e-bc6b-4356785f192an%40googlegroups.com.

[Jenkins Docker Images] Request for maintainer access

[Damien Duportal]

Hello dear contributors, maintainers, readers.


I'm writing this email to request a maintainer access (GitHub handle 
"dduportal") to the following repositories:

- https://github.com/jenkinsci/docker
- https://github.com/jenkinsci/docker-agent
- https://github.com/jenkinsci/docker-ssh-agent
- https://github.com/jenkinsci/docker-inbound-agent


The reason for this request are the following:

- With the persona  of Jenkins Infrastructure officer and team member, the 
ability to operate these repositories to ensure fast CI/CD process on the 
infra are key (reality check: we always had maintainers whom did the review 
work so we never were slowed down, but it would be a "plus")
- With the persona of contribuor who want to increase his area of 
contribution:
  * I've already contributed to these repositories in the past years on 
many topics (from build process to bugfix or features) and I plan to 
propose more contribution in the upcomings weeks/months
  * I'm spending more personal time on helping users on their issues on 
this area  and I also plan and commit to help more (triaging, writing JEP, 
and helping more)

Of course, this is a question that can be answered by YES or NO: it is for 
the actual maintainers and Jenkins board and the community to decide (and I 
would accept whatever answer is given of course without complaining).


Cheers,

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/43b0ec6d-4255-44d2-a9a0-c117ed97ba60n%40googlegroups.com.

Re: Request for access to Zoom +YT account

[Damien Duportal]

Many Thanks Olivier!

I confirm that I now have access and I’m autonomous to upload Infra meeting 
videos.

Damien

> Le 23 mai 2022 à 14:02, 'Olblak' via Jenkins Developers 
>  a écrit :
> 
> Hi Damien,
> I sent you an invite.
> At the moment, they are 4 owners, KK, Tyler, Oleg, and me
> 
> And 10 "managers", so it's probably a good time to review those permission
> 
> 
> On Sun, May 22, 2022, at 1:08 PM, Damien Duportal wrote:
>> Hi @Olivier @Oleg @Kohsuke (at least?),
>> 
>> It appears that Mark lacks the permissions to add me to the YouTube account 
>> (so I might post Infra meeting recordings).
>> 
>> Could you add me as member of the "Jenkins" account so I’m autonomous to do 
>> so? (my gmail id is damien.duportal  gmail.com <http://gmail.com/>).
>> 
>> Many thanks!
>> 
>> Damien
>> 
>>> Le 9 juin 2021 à 18:45, Damien Duportal >> <mailto:damien.dupor...@gmail.com>> a écrit :
>>> 
>>> Thanks, credentials for Zoom received, and working as expected.
>>> 
>>> I now need help from someone with access to the YT channel to help me to 
>>> upload the recording (I've NEVER uploaded a video on YT of my life so 
>>> help/guidelines are more than welcome)
>>> 
>>> Damien
>>> 
>>> Le mercredi 9 juin 2021 à 11:42:01 UTC+2, timja...@gmail.com 
>>> <http://gmail.com/> a écrit :
>>> I've sent Damien the zoom account details
>>> 
>>> Someone else will need to set him up on YouTube I think? (not sure if I 
>>> have access)
>>> 
>>> 
>>> On Tue, 8 Jun 2021 at 15:14, Mark Waite > wrote:
>>> +1 from me
>>> 
>>> On Tue, Jun 8, 2021 at 7:59 AM Tim Jacomb > wrote:
>>> +1 from me
>>> 
>>> On Tue, 8 Jun 2021 at 14:53, Oleg Nenashev > wrote:
>>> +1 from me
>>> 
>>> On Tuesday, June 8, 2021 at 3:41:39 PM UTC+2 damien@gmail.com <> wrote:
>>> 
>>> As per https://groups.google.com/g/jenkinsci-dev/c/K0wqZpL5a88 
>>> <https://groups.google.com/g/jenkinsci-dev/c/K0wqZpL5a88> , Mark is having 
>>> limited bandwidth and I've volunteered to drive the next UX SIG meeting 
>>> until everything goes back to normal.
>>> 
>>> Therefore I'm asking the authorization to be granted access to the Zoom 
>>> account (to allow me to start the meeting and record it), and to the 
>>> Youtube account/channel (to upload the recording in the channel)?
>>> 
>>> Cheers,
>>> 
>>> Damien DUPORTAL
>>> damien@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-de...@googlegroups.com <>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/078ff174-45e2-4980-aabd-6635784b52a2n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/078ff174-45e2-4980-aabd-6635784b52a2n%40googlegroups.com?utm_medium=email_source=footer>.
>>> 
>>> -- 
>>> 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/CAH-3BidL0khnq3NeMnwcwbe6kz2cGFqOaR5heMXOqv7_X%2BjTyQ%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidL0khnq3NeMnwcwbe6kz2cGFqOaR5heMXOqv7_X%2BjTyQ%40mail.gmail.com?utm_medium=email_source=footer>.
>>> 
>>> -- 
>>> 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/CAO49JtELR0fdpA3NdSwey%3DU3-%2BMvCm8oCJmVLSWpzr8WYKfGzg%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtELR0fdpA3NdSwey%3DU3-%2BMvCm8oCJmVLSWpzr8WYKfGzg%40mail.gmail.com?utm_medium=email_source=footer>.
>>> 
>>> -- 
>>> You r

Re: Request for access to Zoom +YT account

[Damien Duportal]

Hi @Olivier @Oleg @Kohsuke (at least?),

It appears that Mark lacks the permissions to add me to the YouTube account (so 
I might post Infra meeting recordings).

Could you add me as member of the "Jenkins" account so I’m autonomous to do so? 
(my gmail id is damien.duportal  gmail.com <http://gmail.com/>).

Many thanks!

Damien

> Le 9 juin 2021 à 18:45, Damien Duportal  a écrit :
> 
> Thanks, credentials for Zoom received, and working as expected.
> 
> I now need help from someone with access to the YT channel to help me to 
> upload the recording (I've NEVER uploaded a video on YT of my life so 
> help/guidelines are more than welcome)
> 
> Damien
> 
> Le mercredi 9 juin 2021 à 11:42:01 UTC+2, timja...@gmail.com a écrit :
> I've sent Damien the zoom account details
> 
> Someone else will need to set him up on YouTube I think? (not sure if I have 
> access)
> 
> On Tue, 8 Jun 2021 at 15:14, Mark Waite  > wrote:
> +1 from me
> 
> On Tue, Jun 8, 2021 at 7:59 AM Tim Jacomb  > wrote:
> +1 from me
> 
> On Tue, 8 Jun 2021 at 14:53, Oleg Nenashev  > wrote:
> +1 from me
> 
> On Tuesday, June 8, 2021 at 3:41:39 PM UTC+2 damien@gmail.com 
>  wrote:
> 
> As per https://groups.google.com/g/jenkinsci-dev/c/K0wqZpL5a88 
> <https://groups.google.com/g/jenkinsci-dev/c/K0wqZpL5a88> , Mark is having 
> limited bandwidth and I've volunteered to drive the next UX SIG meeting until 
> everything goes back to normal.
> 
> Therefore I'm asking the authorization to be granted access to the Zoom 
> account (to allow me to start the meeting and record it), and to the Youtube 
> account/channel (to upload the recording in the channel)?
> 
> Cheers,
> 
> Damien DUPORTAL
> damien@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-de...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/078ff174-45e2-4980-aabd-6635784b52a2n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/078ff174-45e2-4980-aabd-6635784b52a2n%40googlegroups.com?utm_medium=email_source=footer>.
> 
> -- 
> 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/CAH-3BidL0khnq3NeMnwcwbe6kz2cGFqOaR5heMXOqv7_X%2BjTyQ%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidL0khnq3NeMnwcwbe6kz2cGFqOaR5heMXOqv7_X%2BjTyQ%40mail.gmail.com?utm_medium=email_source=footer>.
> 
> -- 
> 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/CAO49JtELR0fdpA3NdSwey%3DU3-%2BMvCm8oCJmVLSWpzr8WYKfGzg%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtELR0fdpA3NdSwey%3DU3-%2BMvCm8oCJmVLSWpzr8WYKfGzg%40mail.gmail.com?utm_medium=email_source=footer>.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/NxbSC6uL0x0/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/NxbSC6uL0x0/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/3df8ce86-1d45-4b0a-ab1b-6a730c5faf8dn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/3df8ce86-1d45-4b0a-ab1b-6a730c5faf8dn%40googlegroups.com?utm_medium=email_source=footer>.

-- 
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/DE069EC5-C5CB-42A4-8450-C0678A35BCEB%40gmail.com.

Re: Enforcing HTTPS on mirrors.jenkins.io + consolidating to get.jenkins.io

[Damien Duportal]

Hello FredG,

our messages crossed, but yes, the errors on updates.jenkins.io are an un 
planned side effect of this change.

We try our best to keep status.jenkins.io up to date (sometime we fail ;) ) 
but it has the informations.

updates.jenkins.io should be back for you now: can you confirm?
Le jeudi 19 mai 2022 à 11:59:59 UTC+2, FredG a écrit :

> Hi,
>
> Do I assume correctly that this also affects the availability of 
> ùpdates.jenkins.io`?
> I'm having issues connecting to it (e.g. while trying to access the update 
> center).
>
>
> Regards,
>
> Fred
>
>
> On Thursday, May 19, 2022 at 9:57:33 AM UTC+2 damien@gmail.com wrote:
>
>> Hello there!
>>
>> Reminder that we’re going to change the DNS record of `mirrors.jenkins.io` 
>> to `get.jenkins.io` in the upcoming hour, enforcing HTTPS.
>>
>>
>> Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/
>>
>>
>> Cheers, 
>>
>> 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/df3ca44c-e046-4c83-b6f8-0653c8e86eban%40googlegroups.com.

Re: Enforcing HTTPS on mirrors.jenkins.io + consolidating to get.jenkins.io

[Damien Duportal]

Hello !

As per 
https://github.com/jenkins-infra/helpdesk/issues/2888#issuecomment-1131453254 
and https://status.jenkins.io/issues/2022-05-19-outage-updates/,
we suffered from a side effect of this change: the DNS record 
"updates.jenkins.io" was a CNAME to mirrors.jenkins.io.

As a consequence, requests to updates.jenkins.io were sent to the 
Kubernetes cluster (instead of the VM serving the service 
updates.jenkins.io), leading to either HTTPS issues or HTTP/404 errors.
We fixed the DNS updates.jenkins.io (back to the VM) around 09:00am UTC but 
since the TTL was 1 hour, then you might see issues until 10:00am UTC (or 
until your DNS uncache the record).

Sorry for the inconvenience

Le jeudi 19 mai 2022 à 11:59:59 UTC+2, FredG a écrit :

> Hi,
>
> Do I assume correctly that this also affects the availability of 
> ùpdates.jenkins.io`?
> I'm having issues connecting to it (e.g. while trying to access the update 
> center).
>
>
> Regards,
>
> Fred
>
>
> On Thursday, May 19, 2022 at 9:57:33 AM UTC+2 damien@gmail.com wrote:
>
>> Hello there!
>>
>> Reminder that we’re going to change the DNS record of `mirrors.jenkins.io` 
>> to `get.jenkins.io` in the upcoming hour, enforcing HTTPS.
>>
>>
>> Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/
>>
>>
>> Cheers, 
>>
>> 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/c71953c7-3817-4b1a-9016-15269f18305bn%40googlegroups.com.

Enforcing HTTPS on mirrors.jenkins.io + consolidating to get.jenkins.io

[Damien Duportal]

Hello there!

Reminder that we’re going to change the DNS record of `mirrors.jenkins.io` 
to `get.jenkins.io` in the upcoming hour, enforcing HTTPS.


Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/


Cheers, 

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/b72fd797-c704-44b9-aeb3-829a4b0e5e57n%40googlegroups.com.

Re: JFrog Artifactory service at repo.jenkins-ci.org is down

[Damien Duportal]

Many thanks Tim for taking care of taking care of checking and closing the 
incident!

Le vendredi 6 mai 2022 à 23:09:38 UTC+2, timja...@gmail.com a écrit :

> It's back now
>
> On Fri, 6 May 2022 at 07:27, Damien Duportal  wrote:
>
>> Hello dear contributors,
>>
>> The service repo.jenkins-ci.org (JFrog Artifactory) is currently down.
>>
>> The UI reports that all its component are either down or unhealty.
>>
>> We are working with JFrog to fix this.
>>
>> More details in https://github.com/jenkins-infra/helpdesk/issues/2920.
>>
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/d3ff1a8b-d20a-4a55-8a27-f8b7551958f7n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/d3ff1a8b-d20a-4a55-8a27-f8b7551958f7n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/b5bf6dae-285c-4397-9427-c7de9db69fbfn%40googlegroups.com.

Re: Sunsetting mirror.jenkins.io in favor of get.jenkins.io

[Damien Duportal]

Thanks Olivier for the feedback!

Le vendredi 6 mai 2022 à 08:48:19 UTC+2, Olblak a écrit :

Is there any motivation to not just redirect traffic from mirror.jenkins.io 
> to get.jenkins.io
> that would only be one CNAME change.
>

That is the idea as a "fallback", even though it requires an ingress rule 
to be added to mirrorbits (current service has an ingress for 
get.jenkins.io) in the Kubernetes cluster.

But changing the domain name helps to track the "HTTP" usages: better to 
use the actual domain to make it clear in our code. The effort is low and 
it is a good opportunity to cleanup stuff.
 

>
> And if you want to take extra care, we could just announce on the blogpost 
> that HTTP support will be remove in one month.
>

We are aligned: that is the TL;DR; of the blog post  \o/
 

> Anyway the updatecenter only use HTTPS if I recall correctly.
>


 

>
> On Thu, May 5, 2022, at 12:01 PM, Damien Duportal wrote:
>
> Hello dear contributors!
>
> The infrastructure team is going, in the upcoming weeks, to sunset the 
> service "mirror.jenkins.io" in favor of get.jenkins.io.
>
> More details can be found in this issue: 
> https://github.com/jenkins-infra/helpdesk/issues/2888.
>
> One of the first steps is to change the code on the Jenkins project that 
> uses the old "mirror.jenkins.io" and change it to https://get.jenkins.io.
>
> However this might have some impact and the infra team need help to 
> review, challenge and approve this change.
>
> A first step is on the shared pipeline library: 
> https://github.com/jenkins-infra/pipeline-library/pull/374 .
> This change request might have an impact on the Jenkins Core build and the 
> test harnesses so better notifying contributors.
>
> ETA of this 1st change is 9th of May unless there is strong reason to not 
> to.
>
> Many thanks in advance!
>
> 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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/4de12a3f-160d-4b17-baeb-358e718fe884n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/4de12a3f-160d-4b17-baeb-358e718fe884n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
>

-- 
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/2260bc60-bea5-42d6-a024-3b60c9146a97n%40googlegroups.com.

JFrog Artifactory service at repo.jenkins-ci.org is down

[Damien Duportal]

Hello dear contributors,

The service repo.jenkins-ci.org (JFrog Artifactory) is currently down.

The UI reports that all its component are either down or unhealty.

We are working with JFrog to fix this.

More details in https://github.com/jenkins-infra/helpdesk/issues/2920.

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/d3ff1a8b-d20a-4a55-8a27-f8b7551958f7n%40googlegroups.com.

Sunsetting mirror.jenkins.io in favor of get.jenkins.io

[Damien Duportal]

Hello dear contributors!

The infrastructure team is going, in the upcoming weeks, to sunset the 
service "mirror.jenkins.io" in favor of get.jenkins.io.

More details can be found in this issue: 
https://github.com/jenkins-infra/helpdesk/issues/2888.

One of the first steps is to change the code on the Jenkins project that 
uses the old "mirror.jenkins.io" and change it to https://get.jenkins.io.

However this might have some impact and the infra team need help to review, 
challenge and approve this change.

A first step is on the shared pipeline library: 
https://github.com/jenkins-infra/pipeline-library/pull/374 .
This change request might have an impact on the Jenkins Core build and the 
test harnesses so better notifying contributors.

ETA of this 1st change is 9th of May unless there is strong reason to not 
to.

Many thanks in advance!

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/4de12a3f-160d-4b17-baeb-358e718fe884n%40googlegroups.com.

[ci.jenkins.io] Replace Blue Ocean in default display URL

[Damien Duportal]

Hello dear contributors!

The Jenkins infra team recently received a request 
(https://github.com/jenkins-infra/helpdesk/issues/2833) to change the 
default display URL for ci.jenkins.io.

The goal of the request is to ensure that when you click on a GitHub check 
link related to ci.jenkins.io, then you are redirect to the classic Jenkins 
UI (instead of Blue Ocean).

Blue Ocean is still kept in ci.jenkins.io as it is still used by many (and 
provides features that does not exist on the classic UI as for today).

But since Blue Ocean is not really well maintained, chanigng the default 
display link would centralize the actual contribution UI effort on the 
classic UI by... using it !

Are there any voices (and if yes: why?) against this change for 
ci.jenkins.io?

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/41c17c2f-0d23-4979-b223-ce41c930081bn%40googlegroups.com.