Mirroring https://packages.atlassian.com/mvn/maven-external/ in repo.jenkins-ci.org?
Hello, To fix the issue https://github.com/jenkins-infra/helpdesk/issues/3434 I've added an exception for atlassian-public Maven repository in the artifact caching proxy settings, as we only have version org.codehaus.jackson:jackson-xc:jar:1.9.13-atlassian-2 and below in repo.jenkins-ci.org while the version 1.9.13-atlassian-6 is required by the confluence-publisher plugin. Discussing it with Damien, we were wondering if we should instead mirror this repository in our artifactory instance too. WDYT? Hervé -- 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/CAL-Lwjxa6232TO-Lt%3DCL_0imAq8OVc2LB-Eac7-2J7%2Bx9qg-wQ%40mail.gmail.com.
Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle
For those using buildPluginWithGradle() from the shared pipeline library, we could add a note about it in the logs. On Wed, Mar 22, 2023 at 6:38 PM Basil Crow wrote: > Here are the most popular plugins still using Gradle for their build: > > gradle 232,746 > multiple-scms 22,241 > allure-jenkins-plugin 17,121 > terraform 5,046 > checkmarx 4,502 > jira-trigger 3,996 > blackduck-detect 2,838 > npm-yarn-wrapper-steps 2,152 > ez-templates 2,145 > templating-engine 1,742 > synopsys-coverity 1,480 > > Multiple SCMs is already deprecated. Gradle, Allure, Checkmarx, and > the Synopsys plugins appear to be maintained by corporate teams that > may have their own build system policies. Terraform, Jira Trigger, NPM > and Yarn Wrapper and Steps, EZ Templates, and Templating Engine appear > to be community-maintained. > > I wonder if there is a way we could more clearly communicate to the > above parties that we offer only partial support for Gradle and full > support only for Maven. > > -- > 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/CAFwNDjoXcdRte%3DXuUwp9XbTcFte_kiT4-CBqXqvgJzzRU98LcQ%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/CAL-LwjwAPHyt62E5YxZBt-7ySEVZSpiPb0BeUB1fXF2BxbmX4A%40mail.gmail.com.
Re: release.ci.jenkins.io migration
Hello, In order to access https://release.ci.jenkins.io, you now need to use the new private VPN private.vpn.jenkins.io To do so, if you already have access to the existing VPN, fill an help desk issue explaining why you need access to release.ci.jenkins.io If you don't already have access to the existing VPN, follow the instructions given at https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access, and mention why you'll also need access to release.ci.jenkins.io Regards, Hervé for the Jenkins Infrastructure Team On Thu, Mar 23, 2023 at 12:20 PM Herve Le Meur wrote: > Hello, > > We'll migrate release.ci.jenkins.io to a new private cluster for a better > segregation of release jobs, and easier maintenance as this new cluster and > related resources are managed as code. > > This migration will start today Thursday 23th of May at 15h00 UTC. Most of > the work has been done in a preliminary phase, it should take two to three > hours to finish the migration, with a total unavailability of > release.ci.jenkins.io until it's done. > > Important notice: every person needing to work on the next releases will > need access to the new private VPN before next Tuesday, as the existing VPN > doesn't allow access to this new cluster and thus the next location of > release.ci.jenkins.io. > We'll send further instructions for this by email. > > More information and detailed migration plan: > https://github.com/jenkins-infra/helpdesk/issues/2844#issuecomment-1463863691 > > Regards, > > Hervé for the Jenkins 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/CAL-Lwjykb5DPVSCPs_9MU18eK%2BQGejpMuA3N1_QpJH6XQg6UeQ%40mail.gmail.com.
