Problems publishing repo

[Terry Moreland]

I've made some recent updates to the appspider-builder-plugin and have committed these to github (tagged 1.0.9) and am in the process of trying to perform the release.

I ran maven release:prepare without issue and most of release:perform is working but it's failing at the point of upload with 'Resource temporarily unavailable' error.

Settings.xml has been updated to match up https://jenkins.io/doc/developer/publishing/releasing/

my jenkins account has been added as a developer to https://github.com/jenkins-infra/repository-permissions-updater (appspider-builder-plugin), is there something more I need to do?

The error doesn't really imply a permissions issue but more of a redirect one, are there more settings required?

[Gavin Mogan]

do you have the actual error message? including the urls/ids its using trying to upload

Temporarily unavailable says to me to try again.

Gavin

--
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/CAM5UBjdjM8jM8i%2BnrPwnLgDkoAoP2jBcQdOXunrQot72YKKXPA%40mail.gmail.com.

[Terry Moreland]

other than a callstack no, that's the error coming off a call to 'mvn release:perform', followed by the callstack.  Retry were my thoughts as well but it'd occurred every time after 4-5 attempts spread out over a few hours

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dus-WkRsBdppLgp4S1DuXn0PuH8gXy4L5D6h53e45eMR2Q%40mail.gmail.com.

[Terry Moreland]

This is the error I'm seeing;  

[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on projec
t jenkinsci-appspider-plugin: Failed to deploy artifacts: Could not transfer artifact com.rapid7:jenkinsci-appspider-plu
gin:hpi:1.0.9 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/content/repositories/releases): Resource te
mporarily unavailable (connect failed) -> [Help 1]  

Should I be expecting maven.jenkins-ci.org there?  I've read the address has changed (to repo.jenkins-ci.org if I recall but the page I linked in the first of this chain said maven.jenkins-ci.org was still needed as an identifier and near as I can that's the only location I have it specified

[Gavin Mogan]

Sadly this is outside my immediate knowledge

I will say you should take advantage of doing a release to move your docs from wiki to github

https://github.com/jenkinsci/appspider-build-scanner-plugin/blob/master/pom.xml#L21 (you can use https://jenkins-wiki-exporter.jenkins.io/ to migrate the wiki to markdown or asciidoc)

Also the base plugin https://github.com/jenkinsci/appspider-build-scanner-plugin/blob/master/pom.xml#L9 is incredibly old, which may somehow default to the wrong publishing url.

I would goto at least 3.50 or newer, and add some properties to make a modern lts and java 8

For example:

<jenkins.version>2.164.3</jenkins.version>
<java.level>8</java.level>

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAM5UBjdnmwLFB3LB-xoM_vMb%3Dqcdo32R4u0uCK5LTfie%3D6ANzA%40mail.gmail.com.

[Terry Moreland]

I got the java version updated already, I'll look into upping the base plugin as well, this plugin was last updated in 2015 and outside of adding the extra feature requested I was aiming to keep the first push fairly small.  Thanks for your help, I'll post again if/when I hit any more roadblocks

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dusq-M5Z8AfNM6sx-7aB6pKGWKWHTnuT8%2Bfdy3Mya-EHzA%40mail.gmail.com.

[Gavin Mogan]

Well at the very least i'd do the <url>, you can only change the docs url on release, and you can't edit wiki pages at all anymore.

.

https://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html.

$ mvn help:effective-pom 2>&1 | grep -B 5 -A 5 8081
    <url>http://ci.jenkins-ci.org</url>
  </ciManagement>
  <distributionManagement>
    <repository>
      <id>maven.jenkins-ci.org</id>
      <url>http://maven.jenkins-ci.org:8081/content/repositories/releases</url>
    </repository>
    <snapshotRepository>
      <id>maven.jenkins-ci.org</id>
      <url>http://maven.jenkins-ci.org:8081/content/repositories/snapshots</url>
    </snapshotRepository>
    <site>
      <id>github-pages</id>
      <url>gitsite:g...@github.com/jenkinsci/maven-site.git:plugin-parent/jenkinsci-appspider-plugin</url>
    </site>

The url is absolutely coming from the old base plugin

The newer one also enables a lot of good security features like findbugs and stuff, so good idea to upgrade

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAM5UBjeV_FGPDJ%2Beq7zoq4TheR4EjPVPw6aTu8BYNVjLDukq4w%40mail.gmail.com.

[Daniel Beck]

The host name you specify in your pom.xml hasn't existed in ~5 years. Your plugin might need a general pom.xml update.

The repo is now at https://repo.jenkins-ci.org/releases/

Also, releasing as documented will automatically tag as well.

[Terry Moreland]

ah the joys of legacy code, or configurations, either way it can eat up a fair bit of time.  I should've expected something like this as the code update was too easy

--

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/CAMo7PtJb9TzLRzCcnVsXAsD%3DbUx2W2chwTo9TeorPzBR-HbTFw%40mail.gmail.com.

[Tony Noble]

If you need a quick fix to get the upload working without having to re-engineer for a more modern POM, you can just override the distributionmanagement section to point to the correct host:

<distributionManagement>
<repository>
<id>maven.jenkins-ci.org</id>

<url>https://repo.jenkins-ci.org/releases/</url>

</repository>
<snapshotRepository>
<id>maven.jenkins-ci.org</id>

<url>https://repo.jenkins-ci.org/snapshots/</url>
</snapshotRepository>
</distributionManagement>

Bear in mind, you'll need to revert the release first, commit that change and then run the release from the start.  You'll also need to add your credentials for that host to the maven settings file as well.

Tony

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAM5UBjeHJTv9KCiQbX6CjexZ%2BVNejxFOo0ukL_OU-MAMdwdtkw%40mail.gmail.com.