May be something around the passphrase with my key. No time tomorrow neither on saturday. But I will try something explain here : https://help.github.com/articles/working-with-ssh-key-passphrases
But if someone wants to give me some input, he is welcome. Le vendredi 26 septembre 2014 00:38:29 UTC+2, Etienne Jouvin a écrit : > > Thanks for the response. > > There is some good news ;) > First of all, I look at one actual plugin to reproduce the pom. I saw many > errors in mine. > Then I had some difficulties with my Maven settings. I already had a > mirror, but this is out of the scope for now. > > But now, when I run the mvn > org.apache.maven.plugins:maven-release-plugin:2.5:prepare command I got an > error during the push. > > [INFO] Executing: cmd.exe /X /C "git push > [email protected]:jenkinsci/dependency-an > alyzer.git refs/tags/dependencyanalyzer-0.7" > [INFO] Working directory: C:\Datas\git\dependency-analyzer-plugin > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Unable to tag SCM > Provider message: > The git-push command failed. > Command output: > ERROR: Repository not found. > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > > Configuration in the pom for the scm is the following: > <scm> > <connection>scm:git:git://github.com/jenkinsci/dependency-analyzer.git > </connection> > > <developerConnection>scm:git:[email protected]:jenkinsci/dependency-analyzer.git</developerConnection> > <url>https://github.com/jenkinsci/dependency-analyzer-plugin.git</url> > <tag>HEAD</tag> > </scm> > > May be I can not create a tag, I do not know. > For tonight I give up, it is too late but if someone can help me, he will > be welcome. > > For sure, I will write somewhere an article when everything will be OK ;) > > > > Le jeudi 25 septembre 2014 17:11:09 UTC+2, Jesse Glick a écrit : >> >> On Wed, Sep 24, 2014 at 6:24 PM, Etienne Jouvin <[email protected]> >> wrote: >> > I update my .m2/settings.xml with >> > >> > <server> >> > <id>java.net-m2-repository</id> >> > <username>ejouvin</username> >> > <password>...</password> >> > </server> >> >> I do not think this repository even exists any more. >> >> > >> https://jenkins.ci.cloudbees.com/job/plugins/job/dependency-analyzer-plugin/ >> > >> > I do not understand why this job failed. >> >> You are using an ancient parent POM predating the Hudson/Jenkins >> split, and it does not support Java 7 (or newer); the earliest version >> that the CI builder will run is org.jenkins-ci.plugins:plugin:1.420, >> which does not offer Hudson compatibility. (1.424 is usually used as >> that is an LTS baseline.) >> >> If you do update your POM, you can delete pluginRepositories and >> distributionManagement as these are picked up from the parent. >> (<repositories> is still needed to bootstrap the parent POM itself.) >> To do releases your local settings should have a server with >> <id>maven.jenkins-ci.org</id>. >> >> If you want to continue using the older parent, just ignore the CI >> failures, and I cannot help you with the server information but maybe >> someone else knows. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
