Spoon snapshot repository at maven.irisa.fr unreachable

[slarse]

Hello!

Since yesterday, my builds can't reach the Spoon snapshot repository at maven.irisa.fr. This causes some builds that depend on snapshots to slow to a crawl as Maven tries to resolve dependencies from that server. For example, sorald now builds in >20 minutes, as opposed to <1 minute.

Does anyone have any idea of what's going on?

[monperrus]

There is a problem at maven.irisa.fr. It's not the first time. If we want to move to avoid this in the future, one alternative option is to move the snapshots to the Nexus at https://repository.ow2.org/ If you or somebody want to make the conf, I can share the authorization tokens.

[slarse]

I've never configured for publishing snapshots. How are snapshots currently published? I can't find it in the CI configuration, is it manual?

How about using GitHub Packages for snapshots? It seems very straightforward, and it can be configured in a GitHub Action workflow to update the snapshot on each push to master, or as a cron-job (e.g. once a day). No need to share any tokens either as the workflow has the necessary token by default. I could try that out on one of my projects first and see how it goes. Thoughts?

[monperrus]

Today, snapshots are deployed by a Jenkins job: https://ci.inria.fr/sos/job/Spoon-Snapshot-Deployer/

[monperrus]

How about using GitHub Packages for snapshots?

I would be fine with this too.

[slarse]

How about using GitHub Packages for snapshots?

I would be fine with this too.

Great, I'll give this a shot then as it's what I'm familiar with. I'll have a go at it today as the unresponsive snapshot server is really slowing down my workflow.

[slarse]

@monperrus I've been playing around with GitHub packages for the past hour, and I think it's insufficient. The biggest hurdle is that it requires authentication even to fetch public packages. I've tried it with Spork just to verify, and it's indeed not possible to fetch the package without supplying a username and auth token.

I'm guessing we want snapshots to be publicly available, and then we should probably use the OW2 Nexus. In my mind, it should be about as simple as doing the following in spoon-pom/pom.xml

-        <repository>
-            <id>maven.inria.fr-snapshot</id>
-            <name>Maven Repository for Spoon Snapshots</name>
-            <url>https://maven.irisa.fr/artifactory/spoon-public-snapshot</url>
-        </repository>
+        <repository>
+            <!-- Not sure what the ID should be? -->
+            <id>ow2-nexus</id>
+            <name>Maven Repository for Spoon Snapshots</name>
+            <url>https://repository.ow2.org/nexus/content/repositories/snapshots/</url>
+        </repository>

-        <snapshotRepository>
-            <id>maven.inria.fr-snapshot</id>
-            <name>Maven Repository for Spoon Snapshots</name>
-            <url>http://maven.inria.fr/artifactory/spoon-public-snapshot</url>
-        </snapshotRepository>
+        <snapshotRepository>
+            <!-- Not sure what the ID should be? -->
+            <id>ow2-nexus</id>
+            <name>Maven Repository for Spoon Snapshots</name>
+            <url>https://repository.ow2.org/nexus/content/repositories/snapshots/</url>
+        </snapshotRepository>

And then updating the credentials in the Jenkins job. We could set it up as a GitHub Action if you configure the secrets for https://repository.ow2.org/ in this repository (see the secrets docs), but if the Jenkins job works why change it?

[slarse]

FYI maven.irisa.fr appears to be back up again, so the matter is less pressing now. But since it's happened before we should probably still make the switch. Do you want me to create a PR with the above changes to the pom?

I don't know why I'm asking, PR is up, let's take it from there :)