Kubernetes 1.27 upgrade for public cluster

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 jen

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

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

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

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

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

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

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

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 tod

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

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

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

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

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

://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...@google

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

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

[Jenkins Infra] Upgrade of Kubernetes 1.26 in Azure

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

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

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 a

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

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 (

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

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

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

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

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

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 Devel

Re: Backporting for LTS 2.414.3 has started

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

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

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-de

Re: Proposal: Kris Stern to join the release team

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 pro

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

023. 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, Damie

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

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 > c

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

l" 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 becaus

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

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 je

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

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

CD release of Plugins fixed

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

[ci.jenkins.io] JDK21 availability

desk/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...@googlegr

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

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

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

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(repo.jenkins-ci.org) Brownout of "repo1" mirrors at 14h30 UTC today, 2nd August 2023

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

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

s-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 > ET

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

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

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

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 d

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

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

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

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

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

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

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

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,

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

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

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

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/helpd

Re: Maven 3.9.2: ready to roll?

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

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

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-de

Maven 3.9.2: ready to roll?

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 unsubs

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

esk/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, Damie

Re: Alex Brandes as a copy editor

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

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

ported 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 emai

ci.jenkins.io: rollout of Maven 3.9.1

/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...@google

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

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 Kubern

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

://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

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

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 : > He

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

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

Re: [Event]: FOSDEM'23

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

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

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

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

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 o

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

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-de

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

+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

Re: JDK19 is now available 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? 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.

Re: Next baseline shift

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

Re: Next baseline shift

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

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

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!

Re: Next baseline shift

+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

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

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.

Re: JDK 11.0.17+8

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

Re: JDK 11.0.17+8

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

Re: Request for access to YouTube account

+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

JDK 11.0.17+8

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

Re: Marking plugins for adoption

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

[ci.jenkins.io] Agent template update

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

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

+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! >>

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

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

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

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 sh

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

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

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

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

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

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

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

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

Re: Failing Windows build on ci.jenkins.io

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.

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

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:

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

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 unsubs

ci.jenkins.io: performing maintenance operations

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

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

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

Re: New member of jenkins.io triage team

+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: >> > >>

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

, 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

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

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

Re: Proposal: Jenkins Core PR reviewers team

+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

Re: Infra Outage: Update Center not updating

à 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 upda

Infra Outage: Update Center not updating

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

[Jenkins Docker Images] Request for maintainer access

n 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 "

Re: Request for access to Zoom +YT account

yler, 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

Re: Request for access to Zoom +YT account

.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

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

>> >> 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 unsubs

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

cord 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 receiv

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

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

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

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, >> >> T

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

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 det

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

, 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 vi

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

ub.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 t

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

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

Re: Need Jenkins Jira access to create a Support ticket

Hi, Infrastructure team member here  Could you open an issue on https://github.com/jenkins-infra/helpdesk/issues stating the email + userid that you used for the account? I can't find any log on accounts.jenkins.io with your names on it so it seems like that you had an issue on webbrowser

Re: Request to transfer my maintainer role for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

Additional note: the failures in reports and RPU are my fault, apologies for that. Please check https://github.com/jenkins-infra/plugin-site/pull/1150#issuecomment-1093986510 for more informations. Apologies for this: it should be fixed in 3-4 hours. Le samedi 9 avril 2022 à 05:37:50 UTC+2,

Builds are often failing with timeout due to JFrog's Artifactory service (repo.jenkins-ci.org) being slow

Hello dear contributors and maintainers, The service repo.jenkins-ci.org (JFrog Artifactory Service) is (once again) currently really slow, which leads to slow builds or worse: failed builds due to timeouts. We are tracking it in https://github.com/jenkins-infra/helpdesk/issues/2864 for more

Builds are often failing with timeout due to JFrog's Artifactory service (repo.jenkins-ci.org) being slow

Hello dear contributors and maintainers, The service repo.jenkins-ci.org (JFrog Artifactory Service) is currently really slow, which leads to slow builds or worse: failed builds due to timeouts. We are tracking it in https://github.com/jenkins-infra/helpdesk/issues/2849 for more informations

Re: FYI: Problems publishing artifacts in Artifactory

Many thanks Daniel for handling this task! As discussed in IRC, the issue is fixed and the releases can be done again without any issue. For context, the support exchange with Jfrog (not fisnished yet) is available here: https://groups.google.com/g/jenkins-infra/c/ZdyYIhlNJQY/m/_8LnZBfaAwAJ.

Re: Zoom access for Alyssa Tong and Jean-Marc Meessen

That is also a +1 for me as well. Le mardi 15 février 2022 à 18:59:47 UTC+1, Mark Waite a écrit : > Alyssa Tong and Jean-Marc Meessen are heading the Google Summer of Code > effort. They need access to the Zoom account so that they can use it to > schedule the upcoming Google Summer of Code

  1   2   >