Hi Curtis, The Jenkins Release-Version job doesn’t currently work for me because /tmp/hudson4570292381982454361.sh: 43: .: Can't open /var/lib/jenkins/.mvn.gnupg/tobias.pietz...@jenkins.imagej.net.settings Build step 'Execute shell' marked build as failure Finished: FAILURE Mark is helping me with this (thanks a lot Mark!), so hopefully it will work soon.
For the release-version.sh I doubt that it is a network issue because the error occured at exactly the same point for two different projects. I noticed that the mvn outpu for the uploads of the jars follows this pattern: [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ spim_data --- Uploading: dav:http:// maven.imagej.net/ content/ repositories/ releases/ sc/ fiji/ spim_data/ 1.0.0-beta-4/ spim_data-1.0.0-beta-4.jar … Uploaded: dav:http:// maven.imagej.net/ content/ repositories/ releases/ sc/ fiji/ spim_data/ 1.0.0-beta-4/ spim_data-1.0.0-beta-4.jar (171 KB at 60.0 KB/sec) Uploading: http:// maven.imagej.net/ content/ repositories/ releases/ sc/ fiji/ spim_data/ 1.0.0-beta-4/ spim_data-1.0.0-beta-4.pom … Uploaded: http:// maven.imagej.net/ content/ repositories/ releases/ sc/ fiji/ spim_data/ 1.0.0-beta-4/ spim_data-1.0.0-beta-4.pom (5 KB at 2.4 KB/sec) So always Uploading:<something> followed by Uploaded:<something> For the failing projects, I get Uploaded:<something> for X.jar, X.pom, maven-metadata.xml, X-sources.jar After that, I think it should try to upload the X-javadoc.jar However, apparently, it tries to upload X-sources.jar again Uploaded: dav:http://maven.imagej.net/content/repositories/releases/sc/fiji/spim_data/1.0.0-beta-4/spim_data-1.0.0-beta-4-sources.jar (114 KB at 44.1 KB/sec) Uploading: dav:http://maven.imagej.net/content/repositories/releases/sc/fiji/spim_data/1.0.0-beta-4/spim_data-1.0.0-beta-4-sources.jar Dec 16, 2014 2:36:43 PM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected Dec 16, 2014 2:36:44 PM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ That seems odd. Could this be related to the Maven wagon plugin that you mentioned? best regards, Tobias On 16 Dec 2014, at 16:55, Curtis Rueden <ctrue...@wisc.edu> wrote: > Hi Tobias, > > > Failed on releasing the javadoc and is now stuck… > > It is probably a network error. This has happened to me several times when I > try to release from a remote machine, even one on the same subnet as the > ImageJ Maven server. So to avoid that, I always run release-version.sh from > the dev server itself. Or use the Release-Version Jenkins job to release when > possible. > > > I don’t really understand what goes on in the release-version.sh > > script. > > The script mostly just leans on the maven-release-plugin. The actual deploy > happens with a Maven wagon plugin: the wagon-webdav-jackrabbit [1]. The > version we used was chosen for cross-compatibility with both Maven 2 and > Maven 3 -- newer webdav wagon plugins I looked at stopped working with Maven > 2. But now that we have migrated fully to requiring Maven 3 anyway, we should > probably upgrade the wagon plugin to the latest, to see whether it helps with > these connectivity issues. > > In the meantime, let's add the BDV projects to the Jenkins Release-Version > job. See you on IRC. > > Regards, > Curtis > > [1] > https://github.com/scijava/pom-scijava/blob/pom-scijava-5.2.3/pom.xml#L919-L927 > > On Tue, Dec 16, 2014 at 8:18 AM, Tobias Pietzsch <pietz...@mpi-cbg.de> wrote: > Ok, and the same thing happened with bigdataviewer-core. Failed on releasing > the javadoc and is now stuck… > > I don’t really understand what goes on in the release-version.sh script. From > the git history of that script it does not look like there have been recent > changes that could explain why it fails now and didn’t a few weeks back. Is > there something changed in the maven.imagej.net that could cause it? > > best regards, > Tobias > > On 16 Dec 2014, at 14:54, Tobias Pietzsch <pietz...@mpi-cbg.de> wrote: > >> Hi, >> >> I just tried to releaseVersion.sh for >> https://github.com/bigdataviewer/spimdata project. >> It failed in the middle of the release: >> In the imagej maven repository >> http://maven.imagej.net/index.html#nexus-search;quick~spim_data the >> spim_data-1.0.0-beta-4.jar and >> spim_data-1.0.0-beta-4-sources.jar are there. >> The upload of the spim_data-1.0.0-beta-4-javadoc.jar is missing. >> That’s where the script failed: >> … >> Dec 16, 2014 2:36:40 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Dec 16, 2014 2:36:40 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Uploaded: >> http://maven.imagej.net/content/repositories/releases/sc/fiji/spim_data/maven-metadata.xml >> (772 B at 0.4 KB/sec) >> Uploading: >> dav:http://maven.imagej.net/content/repositories/releases/sc/fiji/spim_data/1.0.0-beta-4/spim_data-1.0.0-beta-4-sources.jar >> Dec 16, 2014 2:36:41 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Dec 16, 2014 2:36:41 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Dec 16, 2014 2:36:42 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Dec 16, 2014 2:36:42 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Dec 16, 2014 2:36:42 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Dec 16, 2014 2:36:43 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Uploaded: >> dav:http://maven.imagej.net/content/repositories/releases/sc/fiji/spim_data/1.0.0-beta-4/spim_data-1.0.0-beta-4-sources.jar >> (114 KB at 44.1 KB/sec) >> Uploading: >> dav:http://maven.imagej.net/content/repositories/releases/sc/fiji/spim_data/1.0.0-beta-4/spim_data-1.0.0-beta-4-sources.jar >> Dec 16, 2014 2:36:43 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> Dec 16, 2014 2:36:44 PM >> org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme >> INFO: basic authentication scheme selected >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 22.047 s >> [INFO] Finished at: 2014-12-16T14:36:44+01:00 >> [INFO] Final Memory: 33M/447M >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy) >> on project spim_data: Failed to deploy artifacts: Could not transfer >> artifact sc.fiji:spim_data:jar:sources:1.0.0-beta-4 from/to imagej.releases >> (dav:http://maven.imagej.net/content/repositories/releases): Failed to >> transfer file: >> http://maven.imagej.net/content/repositories/releases/sc/fiji/spim_data/1.0.0-beta-4/spim_data-1.0.0-beta-4-sources.jar. >> Return code is: 400 -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e >> switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, please >> read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> pietzsch@tomancak-mac-17:~/workspace/BigDataViewer/SpimData >> ((spim_data-1.0.0-beta-4))$ >> >> >> Now, I don’t know how to proceed... >> In git I’m in a detached HEAD state at spim_data-1.0.0-beta-4. >> Can I somehow manually try to upload the spim_data-1.0.0-beta-4-javadoc.jar? >> And then just checkout master branch again? >> Or, can I git reset HEAD^ and re-run the releaseVersion.sh (Is it even >> possible to re-deploy the already deployed jars…)? >> >> thanks for any help, >> Tobias >> _______________________________________________ >> ImageJ-devel mailing list >> ImageJ-devel@imagej.net >> http://imagej.net/mailman/listinfo/imagej-devel > > > _______________________________________________ > ImageJ-devel mailing list > ImageJ-devel@imagej.net > http://imagej.net/mailman/listinfo/imagej-devel > > _______________________________________________ > ImageJ-devel mailing list > ImageJ-devel@imagej.net > http://imagej.net/mailman/listinfo/imagej-devel
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ ImageJ-devel mailing list ImageJ-devel@imagej.net http://imagej.net/mailman/listinfo/imagej-devel
