Remove `jcenter`, and `oss.sonatype.org-releases` repositories from `public` virtual repository; reconfigure Atlassian remote repositories #3842

MarkEWaite · 2023-12-03T12:48:42Z

Service(s)

Artifactory

Summary

The data transfer volume from https://repo.jenkins-ci.org is still unexpectedly high. Log file analysis for a recent 5 day period shows that the top repositories based on the sum of the sizes of the requested files are:

Repository	Sum of GB requested
releases	2380
jcenter-cache	1787
incrementals	298
jcenter	98
nodejs-dist-cache	78
public	26
jgit-cache	14
oss.sonatype.org-releases-cache	8
snapshots	8
npm-dist-cache	5

JFrog has explained that even though we removed Apache Maven Central from the public repository, the contents of Apache Maven Central still exist as copies in the jcenter repository. We need to also remove the jcenter repository and the jcenter-cache repository from the definition of the public repository so that binaries from Apache Maven Central will be resolved from Apache Maven Central instead of being resolved from our repository.

When I had tried some initial experiments removing jcenter, several months ago, there were some cases where it appeared that we depend on artifacts that are only in jcenter and possibly only in our cache of jcenter. Unfortunately, my memory is weak and I cannot find any notes that reference that experiment.

I think that we should take the following steps:

Reproduction steps

Steps that I took to analyze the requests:

Request Artifactory log files from JFrog
Update my artfiactory-sql fork to handle the new format of Artifactory log files
Upload the log files to a sqlite3 database
Identity top repositories with the SQL query
select repo,sum(size_bytes)/1024/1024/1024 as SUM_GB from logs group by repo order by SUM_GB desc limit 10;

The text was updated successfully, but these errors were encountered:

MarkEWaite · 2023-12-04T04:26:07Z

I built over 240 of the top 250 plugins with the settings.xml file listed later (using repo.jenkins-ci.org for the releases repository, the jgit repository, and the netbeans repository).

I had to download the jbcrypt library separately but other than that, I was able to build without running tests.

The repositories that did not build with those settings are:

artifactory-plugin - cannot resolve com.jayway.jsonpath:json-path:jar:2.4.0 from token-macros dependency, works with my default settings (refer to analysis of failure)
blueocean-plugin - cannot resolve com.atlassian.jira:jira-rest-java-client-api:jar:5.2.1, works with my default settings
configuration-as-code-plugin - cannot resolve com.atlassian.crowd:crowd-integration-api:jar:5.1.5, works with my default settings (analysis of failure)
jira-plugin - cannot resolve com.atlassian.jira:jira-rest-java-client-core:jar:5.2.7, works with my default settings (analysis of failure)
promoted-builds-plugin - http downloads blocked for hudson.plugins:project-inheritance:jar:21.04.03, works with my default settings (analysis of failure)
robot-plugin - cannot resolve com.jayway.jsonpath:json-path:jar:2.4.0, works with my default settings (analysis of failure)
scp-plugin (fails to build even with my default settings and fails to build with Java 8 as well)

One plugin (gradle-plugin) does not build with Maven, so I can't check it.

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                              http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <pluginGroups>
    <pluginGroup>org.jenkins-ci.tools</pluginGroup>
  </pluginGroups>
  <profiles>
    <profile>
      <id>jenkins</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <repositories>
        <repository>
          <id>repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/releases/</url>
        </repository>
        <repository>
          <id>jgit.repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/jgit/</url>
        </repository>
        <repository>
          <id>netbeans.repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/netbeans/</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/releases/</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
</settings>

MarkEWaite · 2023-12-04T04:34:10Z

@daniel-beck do you have a recommendation or a preference for the location where the org.connectbot.jbcrypt:jbcrypt:1.0.0 artifact from jcenter-cache should be placed? My first thought was to place it in the Jenkins releases repository because it is required for a Jenkins release and not available in our other repositories.

According to mvnrepository.com, that library is available from the Spring plugins repository and the Spring Lib M repository. The 1.0.1 and 1.0.2 versions of that library are available from repo.maven.apache.org, but the 1.0.0 version is not.

timja · 2023-12-04T09:37:13Z

or update whatever is using 1.0.0 to a newer version?

daniel-beck · 2023-12-04T10:22:54Z

My first thought was to place it in the Jenkins releases repository because it is required for a Jenkins release and not available in our other repositories.

That's an approach we've used in the past but would consider it mostly legacy from when just everything went into releases (there are issues complaining about differences in artifacts in releases vs. elsewhere, for example). Consider a new repo also added to the public virtual repo (populate exclusively by copying from cache to that new repo as admin).

MarkEWaite · 2023-12-04T12:20:00Z

or update whatever is using 1.0.0 to a newer version?

That would break builds of previous versions of Jenkins core, since it requires jbcrypt 1.0.0. I failed the last time that I tried to update the jbcrypt 1.0.0 dependency to a newer version. I don't have notes on the failure, but I remember that the attempt did not succeed.

I think it is a good idea to update the version of jbcrypt to a newer release if possible, but I think that should be handled separately from this effort.

MarkEWaite · 2023-12-04T12:34:57Z

Consider a new repo also added to the public virtual repo (populate exclusively by copying from cache to that new repo as admin).

Thanks. I've updated the text of the issue to propose the creation of a new repository, addition of that new repository to the public virtual repository, and the move of the jbcrypt 1.0.0 artifact into the new repository.

dduportal · 2023-12-04T13:41:55Z

This plan looks good to me, I'm gonna proceed with the first step. proposal for the new repository name: orphans to convey the "status" of the hosted artifacts within this repo.

jenkins-infra/helpdesk#3842 is the issue that outlines the plan for this brownout.

dduportal · 2023-12-04T15:22:02Z

Create a new repository on repo.jenkins-ci.org and copy the org.connectbot.jbcrypt:jbcrypt:1.0.0 artifact from jcenter-cache to the new repository (required for Jenkins core, appears to only be available from jcenter-cache). Add the new repository to the public virtual repository

A new "local" repository orphans has been created and added to the permission set "Anything" which grant read access to anyone (e.g. public access)
The artifact org.connectbot.jbcrypt:jbcrypt:1.0.0 has been deployed to this new repository, along with its POM, sources and javadoc. A Maven metadat file has been autogenerated and looks the same as jcenter's
Please note this repository is not included in the public virtual repository (yet?).

See: https://repo.jenkins-ci.org/artifactory/orphans/org/connectbot/jbcrypt/jbcrypt/

cc @MarkEWaite so you can continue your tests.

* Announce Artifactory brownout Wed Dec 6, 2023 jenkins-infra/helpdesk#3842 is the issue that outlines the plan for this brownout. * Link to developer list announcement * Fix spelling errors

MarkEWaite · 2023-12-04T19:19:57Z

Analyzing artifactory plugin build failure

The artifactory plugin has a dependency on the token macro plugin 2.12. The token macro plugin 2.12 has a dependency on com.jayway.jsonpath:json-path:2.4.0. Our cached copy of the JGit repository includes an outdated copy of the json-path 2.4.0 pom file for the 2.4.0 release of json-path.

Based on comments in openhab/openhab-addons#10102 (comment) , we need to replace our outdated copy of 2.4.0 with an updated pom file and jar file.

If we don't want to replace the file in our cached copy of the JGit repository (because the outdated file still exists in the Eclipse JGit repository), we could place a fresh copy into the orphans repository and move the orphans repository before the JGit repository in our virtual repository search order.

Is there a way to safely remove or exclude the outdated / incorrect json-path 2.4.0 that we are getting from the Eclipse repository?

MarkEWaite · 2023-12-04T20:02:01Z

Analyzing configuration as code plugin build failure

The configuration as code plugin depends on the crowd2 plugin. The crowd2 plugin depends on the crowd-integration-client-common 5.1.5 library that appears to only be available from our jcenter-cache. Since crowd2 is an Atlassian product, I expected it to be in the atlassian-cache repository, but it does not seem to be there.

We could add the Atlassian repository to the configuration as code plugin like this:

diff --git a/pom.xml b/pom.xml
index f8c7d60e..9a1d5c37 100644
--- a/pom.xml
+++ b/pom.xml
@@ -51,6 +51,10 @@
       <id>repo.jenkins-ci.org</id>
       <url>https://repo.jenkins-ci.org/public/</url>
     </repository>
+    <repository>
+      <id>Atlassian</id>
+      <url>https://packages.atlassian.com/mvn/maven-atlassian-external/</url>
+    </repository>
   </repositories>
 
   <pluginRepositories>

That won't solve the case for other projects that depend on the Atlassian libraries. It also does not explain why the Atlassian libraries are not in our atlassian-cache repository but are in our jcenter-cache repository.

MarkEWaite · 2023-12-04T20:29:36Z

Analyzing Jira plugin build failure

The Jira plugin depends on Atlassian libraries that are available from our jcenter-cache but are not found unless jcenter-cache is included.

The build passed after I added the Atlassian repository to the jira-plugin pom file:

diff --git a/pom.xml b/pom.xml
index e3ca697..d56a0ff 100644
--- a/pom.xml
+++ b/pom.xml
@@ -330,6 +330,10 @@
       <id>repo.jenkins-ci.org</id>
       <url>https://repo.jenkins-ci.org/public/</url>
     </repository>
+    <repository>
+      <id>Atlassian</id>
+      <url>https://packages.atlassian.com/mvn/maven-atlassian-external</url>
+    </repository>
   </repositories>
 
   <pluginRepositories>

MarkEWaite · 2023-12-04T20:58:07Z

Analyzing robot plugin build failure

The robot plugin requires Java 11. It won't build with Java 21.

The robot plugin has a dependency on com.jayway.jsonpath:json-path:2.4.0. Our cached copy of the JGit repository includes an outdated copy of the json-path 2.4.0 pom file for the 2.4.0 release of json-path.

Based on comments in openhab/openhab-addons#10102 (comment) , we need to replace our outdated copy of 2.4.0 with an updated pom file and jar file.

If we don't want to replace the file in our cached copy of the JGit repository (because the outdated file still exists in the Eclipse JGit repository), we could place a fresh copy into the orphans repository and move the orphans repository before the JGit repository in our virtual repository search order.

Is there a way to safely remove or exclude the outdated / incorrect json-path 2.4.0 that we are getting from the Eclipse repository?

MarkEWaite · 2023-12-04T21:20:58Z

Analyzing promoted builds plugin build failure

The promoted builds plugin has an optional dependency on the project inheritance plugin 21.04.03. The project inheritance plugin 21.04.03 pom file uses http instead of https in its repository URL references. Maven rejects attempts to from an http repository.

There are hints like this on several pages that http blocking can be bypassed with a mirrorOf definition, but I've not been able to make it work.

daniel-beck · 2023-12-04T21:22:03Z

The artifact org.connectbot.jbcrypt:jbcrypt:1.0.0 has been deployed to this new repository, along with its POM, sources and javadoc. A Maven metadat file has been autogenerated and looks the same as jcenter's

Any particular reason why?

MarkEWaite · 2023-12-04T21:25:01Z

The artifact org.connectbot.jbcrypt:jbcrypt:1.0.0 has been deployed to this new repository, along with its POM, sources and javadoc. A Maven metadat file has been autogenerated and looks the same as jcenter's

Any particular reason why?

I could not find the artifact org.connectbot.jbcrypt:jbcrypt:1.0.0 on repo.jenkins-ci.org in any repository other than jcenter-cache. Since the goal is to remove jcenter-cache from the definition of the public virtual repository, it seemed like we need to copy that artifact to a new repository that can be included in the public virtual repository without including all of jcenter-cache.

Did that address your question or is there something more that I'm not understanding in the question?

daniel-beck · 2023-12-04T21:26:45Z

Did that address your question or is there something more that I'm not understanding in the question?

From my proposal of the new repo holding these dependencies:

populate exclusively by copying from cache to that new repo as admin

That trivially ensures identical artifacts. Per Damien,

has been deployed to this new repository, along with its POM, sources and javadoc. A Maven metadat file has been autogenerated and looks the same as jcenter's

That looks very manual and results in differences. For example, we don't have *.asc files now. No idea whether they're needed, but any difference seems unnecessary.

If my proposed approach is not possible, or has drawbacks I'm unaware of, and that's the reason for the different approach, I'd like to know.

basil · 2023-12-04T21:38:22Z

Is there a way to safely remove or exclude the outdated / incorrect json-path 2.4.0 that we are getting from the Eclipse repository?

Googling brings up https://jfrog.com/help/r/jfrog-artifactory-documentation/basic-settings-for-remote-repositories which shows that you can configure exclude patterns on a remote repository (i.e., a cache). Based on this documentation I think we should delete the json-path dependency from our Eclipse remote repository (i.e., our cache) and add an exclude pattern so that it won't be downloaded again. Then requests for it from the JGit remote repository should 404 and the lookup should proceed to the (valid) version on Central.

basil · 2023-12-10T18:55:21Z

Confluence Publisher is also impacted: #3856

* Suspend Crowd2 plugin distribution - uses closed source dependency jenkins-infra/helpdesk#3854 explains that the Crowd2 integration plugin uses a dependency that is not open source licensed. The Crowd2 integration library is Atlassian licensed as described in jenkins-infra/helpdesk#3842 (comment) The Atlassian license is not an open source license. Refer to https://www.atlassian.com/legal/software-license-agreement for the details of the license. https://www.jenkins.io/project/governance/#license says that the Jenkins project requires plugins that it distributes to be open source, including their dependencies. When a closed source dependency is detected in a plugin, we suspend distribution of that plugin. If maintainers update the plugin to remove the closed source dependency, distribution can begin for the new release that removes the closed source dependency. Fixes jenkins-infra/helpdesk#3854 * Better comment phrase * Reduce diffs

dduportal · 2023-12-14T15:04:03Z

The artifacts are there in the remote repositories:
* https://packages.atlassian.com/maven-public/com/atlassian/jira/jira-rest-java-client-core/5.2.7/

* https://packages.atlassian.com/mvn/maven-atlassian-external/com/atlassian/jira/jira-rest-java-client-core/5.2.7/
https://repo.jenkins-ci.org/atlassian-maven-public/ is returning 401, not 404. Seems like it was not set up for anonymous access (i.e., an unrealistic test environment).

Pairing operation with @MarkEWaite today: the repository https://repo.jenkins-ci.org/artifactory/atlassian-maven-public is now available publicly (added to the permissions scheme "Any Remote" which adds Read and Cache to the anonymous user.

dduportal · 2023-12-15T13:32:37Z

Start of the 2nd brownout on repo.jenkins-ci.org with @MarkEWaite:

We've updated the public virtual repository to the following setup:

curl --silent https://repo.jenkins-ci.org/api/repositories/public | jq -r '.'
{
  "key": "public",
  "packageType": "maven",
  "description": "All public repositories aggregated for the purpose of building Jenkins and its plugins",
  "repositories": [
    "releases",
    "orphans",
    "atlassian-maven-public",
    "shibboleth",
    "maven.jenkins-ci.org",
    "maven.twttr.com",
    "javanet2",
    "tmate",
    "cloudbees.public.release",
    "jgit",
    "netbeans",
    "fusesource",
    "snapshots"
  ],
  "rclass": "virtual"
}

Removed jcenter and atlassian
Added orphans and atlassian-maven-public

MarkEWaite · 2023-12-15T14:01:11Z

After implementing the production change, we found that the artifactory plugin depends on a 3.1.7 release of a platform pom that is only available from the Spring plugins repository at https://repo.spring.io/plugins-release/ . Other versions of that artifact are available from Atlassian public, but not that version.

@dduportal created a jcenter-orphans remote repository that includes a specific item

com.atlassian.pom:public-pom:pom:4.0.7 was then missing. That was fixed by adding another entry to jcenter-orphans

com.atlassian.sal:sal-api:jar:3.0.7 was missing.

Items that were missing have been added to the jcenter-orphans remote repository with a narrow inclusion definition to avoid including any more of jcenter than those few items that are not available elsewhere. The jcenter-orphans repository is intentionally placed near the end of the search list so that the official Atlassian repository cache is used first.,

MarkEWaite · 2023-12-15T17:30:14Z

The crawler job that detects updated tools is failing on ci.jenkins.io with a Grape error

https://ci.jenkins.io/job/Infra/job/crawler/job/master

Resolved by adding Maven central to the Grape repository list in:

Add Maven Central to Grape configuration crawler#134

dduportal · 2023-12-17T08:59:53Z

The crawler job that detects updated tools is failing on ci.jenkins.io with a Grape error
* https://ci.jenkins.io/job/Infra/job/crawler/job/master
Resolved by adding Maven central to the Grape repository list in:
* [Add Maven Central to Grape configuration crawler#134](https://github.com/jenkins-infra/crawler/pull/134)

Thanks @basil for the batch of PRs to fix and improve the crawler (and @MarkEWaite @timja @NotMyFault for the revies/deploys).

dduportal · 2023-12-19T08:57:02Z

Update:

Update the allow list pattern of jcenter to solve declarative-pipeline-migration-assistant-plugin no longer compiles #3872 (see issue for details)
Removed jcenter-cache and atlassian-cache from both Any Remote and Anything permissions scheme to ensure they cannot be reached anonymously (as such the outbound bandwidth should drastically decrease)

MarkEWaite · 2023-12-19T17:00:24Z

Removed jcenter-cache and atlassian-cache from both Any Remote and Anything permissions scheme to ensure they cannot be reached anonymously (as such the outbound bandwidth should drastically decrease)

Thanks very much. Should the same change be applied to oss.sonatype.org-releases since it also contains a copy of Apache Maven Central?

The Artifactory bandwidth reduction project described at jenkins-infra/helpdesk#3842 has shown that some outdated JIRA API jar files are only available from the jcenter cache. Let's test with a newer version of the Jira plugin to avoid that older JIRA API jar file dependency. JIRA plugin 3.12 fixes a security vulnerability. It was released 4 weeks ago.

* Require Jenkins 2.401.3 or newer https://stats.jenkins.io/pluginversions/declarative-pipeline-migration-assistant.html shows: * 88% of the installations of the most recent release are already running Jenkins 2.401.3 or newer. The most recent release was 4 months ago. The most recent release is installed on 460 / 1388 total installations. * 48% of the installations of the next most recent release are already running Jenkins 2.401.3 or newer. That release was 6 months ago. That release is installed on 104 / 1388 total installations. Updating to require Jenkins 2.401.3 or newer allows us to rely on the plugin bill of materials for two more version declarations: * GitHub plugin * Ansicolor plugin Updating to require Jenkins 2.401.3 replaces the following two pull requests: * #233 #233 * #234 #234 * Test with JIRA plugin 3.12 to avoid outdated API jar dependency The Artifactory bandwidth reduction project described at jenkins-infra/helpdesk#3842 has shown that some outdated JIRA API jar files are only available from the jcenter cache. Let's test with a newer version of the Jira plugin to avoid that older JIRA API jar file dependency. JIRA plugin 3.12 fixes a security vulnerability. It was released 4 weeks ago. * Depend on build timeout plugin 1.31 Build timeout plugin 1.31 includes the removal of Prototype.js that is required for Jenkins 2.426.1 and newer. It was released 7 months ago and is already installed on 40% of all build timeout plugin installations. * Use parent pom 4.76 * Test with Java 21 and Java 17 Java 21 was released Sep 19, 2023. Full support for Java 21 was announced in November 2023. The acceptance test harness and plugin bill of materials tests are already passing with Java 21. This is a further step to improve plugin readiness for use with Java 21 and for development with Java 21. The change intentionally tests only two Java configurations, Java 17 and Java 21 because we believe that the risk of a regression that only affects Java 11 is low. We generate Java 11 byte code with the Java 17 and the Java 21 builds, so we're already testing Java 11 byte code. Java 11 is also tested for this plugin in the plugin bill of materials each week.

MarkEWaite · 2024-01-02T15:07:58Z

Jenkins core 2.439 and later now depend on a version of the jbcrypt library that is available from Apache Maven Central. Thanks to @andham for that improvement. Refer to the merged pull request:

[JENKINS-72466] Upgrade jbcrypt dependency jenkinsci/jenkins#8811

dduportal · 2024-01-02T16:27:26Z

Removed jcenter-cache and atlassian-cache from both Any Remote and Anything permissions scheme to ensure they cannot be reached anonymously (as such the outbound bandwidth should drastically decrease)

Thanks very much. Should the same change be applied to oss.sonatype.org-releases since it also contains a copy of Apache Maven Central?

The repository oss.sonatype.org-releases is no longer available anonymously: it requires authentication.

dduportal · 2024-01-08T13:04:21Z

Update:

The repository orphans has been removed (in favor of adding filters in the jcenter-orphans mirror repository - Remove orphans local repository #3884
We forgot to clean the ACP cache: Artifact caching proxy repo.do.jenkins.io is not answering requests from bom build #3889

MarkEWaite added the triage Incoming issues that need review label Dec 3, 2023

jenkins-infra-helpdesk-app bot added the artifactory label Dec 3, 2023

MarkEWaite changed the title ~~Remove jcenter-cache and jcenter repositories from public on repo.jenkins-ci.org~~ Remove jcenter-cache and jcenter repositories from public repo Dec 3, 2023

dduportal added this to the infra-team-sync-2023-12-05 milestone Dec 4, 2023

dduportal assigned MarkEWaite, lemeurherve and smerle33 Dec 4, 2023

dduportal removed the triage Incoming issues that need review label Dec 4, 2023

MarkEWaite mentioned this issue Dec 4, 2023

Announce Artifactory brownout Wed Dec 6, 2023 jenkins-infra/status#432

Merged

MarkEWaite added a commit to MarkEWaite/status that referenced this issue Dec 4, 2023

Announce Artifactory brownout Wed Dec 6, 2023

8b40f47

jenkins-infra/helpdesk#3842 is the issue that outlines the plan for this brownout.

This was referenced Dec 4, 2023

Explicitly use Atlassian repository jenkinsci/jira-plugin#578

Closed

Explicitly use Atlassian repository jenkinsci/blueocean-plugin#2531

Closed

This was referenced Dec 9, 2023

Remove Crowd2 demo and integration test - suspended plugin jenkinsci/configuration-as-code-plugin#2433

Merged

Document that Crowd2 plugin distribution will be suspended jenkinsci/crowd2-plugin#240

Merged

dduportal modified the milestones: infra-team-sync-2023-12-12, infra-team-sync-2023-12-19 Dec 12, 2023

dduportal mentioned this issue Dec 15, 2023

feat: introduce a fake change to trigger a release jenkinsci/jenkins-infra-test-plugin#109

Merged

basil mentioned this issue Dec 19, 2023

declarative-pipeline-migration-assistant-plugin no longer compiles #3872

Closed

dduportal modified the milestones: infra-team-sync-2023-12-19, infra-team-sync-2024-01-02 Dec 19, 2023

Divyaasm mentioned this issue Dec 19, 2023

[Bug]: Missing plugin dependencies from the Jenkins maven repository opensearch-project/opensearch-build#4297

Closed

dduportal closed this as completed Jan 2, 2024

This was referenced Jan 8, 2024

Artifact caching proxy repo.do.jenkins.io is not answering requests from bom build #3889

Closed

Remove orphans local repository #3884

Closed

MarkEWaite mentioned this issue Feb 15, 2024

Mirroring of https://packages.atlassian.com/mvn/maven-public/ #3950

Closed

dduportal mentioned this issue Feb 15, 2024

Deflake PipelineApiTest.testPipelineQueue jenkinsci/blueocean-plugin#2542

Merged

dduportal mentioned this issue Apr 9, 2024

[Artifactory (repo.jenkins-ci.org)] perform a systematic audit of all non-plugin artifacts in our releases repository to identify and quarantine unused artifacts #4034

Open

MarkEWaite mentioned this issue Jan 7, 2025

Artifactory outdated maven-metadata.xml for public/com/github/jnr/jnr-posix/ #4472

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remove `jcenter`, and `oss.sonatype.org-releases` repositories from `public` virtual repository; reconfigure Atlassian remote repositories #3842

Remove `jcenter`, and `oss.sonatype.org-releases` repositories from `public` virtual repository; reconfigure Atlassian remote repositories #3842

MarkEWaite commented Dec 3, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

timja commented Dec 4, 2023

daniel-beck commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023

dduportal commented Dec 4, 2023

dduportal commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023 •

edited

Loading

daniel-beck commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023

daniel-beck commented Dec 4, 2023 •

edited

Loading

basil commented Dec 4, 2023

basil commented Dec 10, 2023

dduportal commented Dec 14, 2023

dduportal commented Dec 15, 2023

MarkEWaite commented Dec 15, 2023 •

edited

Loading

MarkEWaite commented Dec 15, 2023 •

edited

Loading

dduportal commented Dec 17, 2023

dduportal commented Dec 19, 2023

MarkEWaite commented Dec 19, 2023

MarkEWaite commented Jan 2, 2024 •

edited

Loading

dduportal commented Jan 2, 2024

dduportal commented Jan 8, 2024

Remove jcenter, and oss.sonatype.org-releases repositories from public virtual repository; reconfigure Atlassian remote repositories #3842

Remove jcenter, and oss.sonatype.org-releases repositories from public virtual repository; reconfigure Atlassian remote repositories #3842

Comments

MarkEWaite commented Dec 3, 2023 • edited Loading

Service(s)

Summary

Reproduction steps

MarkEWaite commented Dec 4, 2023 • edited Loading

MarkEWaite commented Dec 4, 2023 • edited Loading

timja commented Dec 4, 2023

daniel-beck commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023

dduportal commented Dec 4, 2023

dduportal commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023 • edited Loading

Analyzing artifactory plugin build failure

MarkEWaite commented Dec 4, 2023 • edited Loading

Analyzing configuration as code plugin build failure

MarkEWaite commented Dec 4, 2023

Analyzing Jira plugin build failure

MarkEWaite commented Dec 4, 2023

Analyzing robot plugin build failure

MarkEWaite commented Dec 4, 2023 • edited Loading

Analyzing promoted builds plugin build failure

daniel-beck commented Dec 4, 2023

MarkEWaite commented Dec 4, 2023

daniel-beck commented Dec 4, 2023 • edited Loading

basil commented Dec 4, 2023

basil commented Dec 10, 2023

dduportal commented Dec 14, 2023

dduportal commented Dec 15, 2023

MarkEWaite commented Dec 15, 2023 • edited Loading

MarkEWaite commented Dec 15, 2023 • edited Loading

dduportal commented Dec 17, 2023

dduportal commented Dec 19, 2023

MarkEWaite commented Dec 19, 2023

MarkEWaite commented Jan 2, 2024 • edited Loading

dduportal commented Jan 2, 2024

dduportal commented Jan 8, 2024

Remove `jcenter`, and `oss.sonatype.org-releases` repositories from `public` virtual repository; reconfigure Atlassian remote repositories #3842

Remove `jcenter`, and `oss.sonatype.org-releases` repositories from `public` virtual repository; reconfigure Atlassian remote repositories #3842

MarkEWaite commented Dec 3, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 4, 2023 •

edited

Loading

daniel-beck commented Dec 4, 2023 •

edited

Loading

MarkEWaite commented Dec 15, 2023 •

edited

Loading

MarkEWaite commented Dec 15, 2023 •

edited

Loading

MarkEWaite commented Jan 2, 2024 •

edited

Loading