Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

christian åkerström
Hi, I have read https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues and tried several different things but when I try to release a new plugin version it always fail with:

INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project claim: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:claim:hpi:2.9 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/content/repositories/releases): Connect to maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24] failed: Operation timed out -> [Help 1]


I have a ~/.m2/settings.xml that looks like this:

<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">


  <servers>

    <server>

      <id>maven.jenkins-ci.org</id> <!-- For parent 1.397 or newer; before this use id java.net-m2-repository -->

      <username>ki82</username>

      <password>***************</password>

    </server>

  </servers>


</settings>


I have verified that my password works at https://repo.jenkins-ci.org/webapp/#/login and I use the encrypted password in the ~/m2/settings.xml

I have executed the effective pom and verified that the id is correct.


Does anyone have any idea why this is failing for me?

Is there any way to test the connection to maven.jenkins-ci.org without doing an actual release?




--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/94b6e22b-fc94-4697-9d5d-acd2110a1336%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

Daniel Beck

> On 08.11.2016, at 09:17, Christian <[hidden email]> wrote:
>
> Does anyone have any idea why this is failing for me?
>

Second issue in the common issues list (granted, it's Operation timed out rather than Connection refused, but close enough).

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0537313F-2914-4E62-A544-05CF364E27E5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

Fritz Elfert
On 08.11.2016 12:32, Daniel Beck wrote:
>
>> On 08.11.2016, at 09:17, Christian <[hidden email]> wrote:
>>
>> Does anyone have any idea why this is failing for me?
>>
>
> Second issue in the common issues list (granted, it's Operation timed out rather than Connection refused, but close enough).
>
Having exactly the same now. So:

Which "common" issues list?

I have searched this group, and the various Links on
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
but did not yet stuble over that timeout thingie.

URL please!

Thanks
 -Fritz

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/edd539f4-9292-08e4-8fed-65ba64bd1013%40fritz-elfert.de.
For more options, visit https://groups.google.com/d/optout.

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

Daniel Beck

> On 08.11.2016, at 16:30, Fritz Elfert <[hidden email]> wrote:
>
> Which "common" issues list?
>
> I have searched this group, and the various Links on
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
> but did not yet stuble over that timeout thingie.
>
> URL please!

The one you linked to:

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

Second item:

> The upload to maven.jenkins-ci.org fails with "Connection refused" or "401 Unauthorized"
> The Maven repository is now located at repo.jenkins-ci.org.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/25268E51-6A2E-4FFD-8D3E-87653C9A2FF1%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

Baptiste MATHUS

2016-11-08 18:37 GMT+01:00 Daniel Beck <[hidden email]>:

> On 08.11.2016, at 16:30, Fritz Elfert <[hidden email]> wrote:
>
> Which "common" issues list?
>
> I have searched this group, and the various Links on
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
> but did not yet stuble over that timeout thingie.
>
> URL please!

The one you linked to:

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

Second item:

> The upload to maven.jenkins-ci.org fails with "Connection refused" or "401 Unauthorized"
> The Maven repository is now located at repo.jenkins-ci.org.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/25268E51-6A2E-4FFD-8D3E-87653C9A2FF1%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4RtVMt1cjBN7u18-vZATEwkfY6c%3D0Tt1hdix%2BNb5Pq4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

christian åkerström
In reply to this post by Daniel Beck
Thanks Daniel,

I tried locally with several different jenkins-test-harness.version but it always fails with compilation errors, what am I doing wrong?

I am currently not developing this plugin actively but thought I would release a new version with some pull request from the community but the release process is not as easy as one would like..

On Tue, Nov 8, 2016 at 6:37 PM, Daniel Beck <[hidden email]> wrote:

> On 08.11.2016, at 16:30, Fritz Elfert <[hidden email]> wrote:
>
> Which "common" issues list?
>
> I have searched this group, and the various Links on
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
> but did not yet stuble over that timeout thingie.
>
> URL please!

The one you linked to:

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

Second item:

> The upload to maven.jenkins-ci.org fails with "Connection refused" or "401 Unauthorized"
> The Maven repository is now located at repo.jenkins-ci.org.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/25268E51-6A2E-4FFD-8D3E-87653C9A2FF1%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAHcVhVkzbCgm1fvVTKDS8kJoMymf0ULv5teSxfuJ_RjjPYALFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

Daniel Beck

> On 10.11.2016, at 08:12, Christian <[hidden email]> wrote:
>
> I tried setting a new parent, but then the build fails see https://github.com/jenkinsci/claim-plugin/commit/56098d240dfedffd6f1fbc2426ac4724de0880f3#diff-0
> I tried locally with several different jenkins-test-harness.version but it always fails with compilation errors, what am I doing wrong?
>
> I am currently not developing this plugin actively but thought I would release a new version with some pull request from the community but the release process is not as easy as one would like..

It seems like the dependency on mock_javamail needs to be explicit now. Not sure where that's coming from.

And since we moved from our forked and patched HtmlUnit to the upstream one more than a year ago[1] to be able to support testing with modern JavaScript frameworks, some methods and types have changed. The alternative is stagnation and obsolescence.

Additionally, the plugin used unsafe Jelly files, which could (with a combination of other factors) result in XSS vulnerabilities. The HPI plugin requires it to have an XML PI to escape by default for almost two years now.

This might look like a lot, but if the plugin has been stale for years, even a single change per year can pile up.

Note that the parent POM now by default runs FindBugs to improve code quality, which results in a number of failures. You need to disable FindBugs, or address these findings (fixing or ignoring).

I've opened a pull request with all my changes.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4818CB7C-5371-4531-A49D-E8739FD38758%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

georg.henzler
Just ran into the same issue... updating the <distributionManagement> section works. The Plugin Tutorial is outdated though:

  https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial  
links to 
  https://github.com/jenkinsci/hello-world-plugin/blob/master/pom.xml#L34 (uses v2.2 of plugin parent)
v2.2 of plugin parent still uses the old <distributionManagement>:
  https://github.com/jenkinsci/plugin-pom/blob/plugin-2.2/pom.xml#L761 

It's probably best if the parent of hello-world-plugin would be updated to the latest plugin parent?

Regards
Georg

On Thursday, 10 November 2016 16:39:34 UTC+1, Daniel Beck wrote:

> On 10.11.2016, at 08:12, Christian <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="bbyeZU1hBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">chra...@...> wrote:
>
> I tried setting a new parent, but then the build fails see <a href="https://github.com/jenkinsci/claim-plugin/commit/56098d240dfedffd6f1fbc2426ac4724de0880f3#diff-0" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fclaim-plugin%2Fcommit%2F56098d240dfedffd6f1fbc2426ac4724de0880f3%23diff-0\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFHAiekNVLM2Chvny7OeGS-d6NrQg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fclaim-plugin%2Fcommit%2F56098d240dfedffd6f1fbc2426ac4724de0880f3%23diff-0\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFHAiekNVLM2Chvny7OeGS-d6NrQg&#39;;return true;">https://github.com/jenkinsci/claim-plugin/commit/56098d240dfedffd6f1fbc2426ac4724de0880f3#diff-0
> I tried locally with several different jenkins-test-harness.version but it always fails with compilation errors, what am I doing wrong?
>
> I am currently not developing this plugin actively but thought I would release a new version with some pull request from the community but the release process is not as easy as one would like..

It seems like the dependency on mock_javamail needs to be explicit now. Not sure where that's coming from.

And since we moved from our forked and patched HtmlUnit to the upstream one more than a year ago[1] to be able to support testing with modern JavaScript frameworks, some methods and types have changed. The alternative is stagnation and obsolescence.

Additionally, the plugin used unsafe Jelly files, which could (with a combination of other factors) result in XSS vulnerabilities. The HPI plugin requires it to have an XML PI to escape by default for almost two years now.

This might look like a lot, but if the plugin has been stale for years, even a single change per year can pile up.

Note that the parent POM now by default runs FindBugs to improve code quality, which results in a number of failures. You need to disable FindBugs, or address these findings (fixing or ignoring).

I've opened a pull request with all my changes.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5814114f-1463-4d9e-b743-5050716699cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

Yuanbo Han
In reply to this post by christian åkerström

Please refer here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues.  You should update the parent org.jenkins-ci.plugins version.

在 2016年11月8日星期二 UTC+8下午4:17:08,Christian写道:
Hi, I have read <a href="https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FHosting%2BPlugins%23HostingPlugins-Workingaroundcommonissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHGFTtEb8eJvizlxsheTBF8VT2Y1A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FHosting%2BPlugins%23HostingPlugins-Workingaroundcommonissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHGFTtEb8eJvizlxsheTBF8VT2Y1A&#39;;return true;">https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues and tried several different things but when I try to release a new plugin version it always fail with:

INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project claim: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:claim:hpi:2.9 from/to <a href="http://maven.jenkins-ci.org" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEbH4wNAUcuIryNrQEo-DSIWx86VQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEbH4wNAUcuIryNrQEo-DSIWx86VQ&#39;;return true;">maven.jenkins-ci.org (<a href="http://maven.jenkins-ci.org:8081/content/repositories/releases" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org%3A8081%2Fcontent%2Frepositories%2Freleases\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFEkTk7omzDmd49OKH4j32WrgZ5zg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org%3A8081%2Fcontent%2Frepositories%2Freleases\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFEkTk7omzDmd49OKH4j32WrgZ5zg&#39;;return true;">http://maven.jenkins-ci.org:8081/content/repositories/releases): Connect to <a href="http://maven.jenkins-ci.org:8081" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org%3A8081\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEWjbVSIoO9AAoNi_TzsoYKUvfwnQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org%3A8081\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEWjbVSIoO9AAoNi_TzsoYKUvfwnQ&#39;;return true;">maven.jenkins-ci.org:8081 [<a href="http://maven.jenkins-ci.org/199.193.196.24" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org%2F199.193.196.24\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHB85zHerrgs5CKZwnmFv11rZP-Bw&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org%2F199.193.196.24\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHB85zHerrgs5CKZwnmFv11rZP-Bw&#39;;return true;">maven.jenkins-ci.org/199.193.196.24] failed: Operation timed out -> [Help 1]


I have a ~/.m2/settings.xml that looks like this:

<settings xmlns="<a href="http://maven.apache.org/SETTINGS/1.0.0" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.0.0\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFFDm89L65OUelL3uKc7t_GFGPnjQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.0.0\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFFDm89L65OUelL3uKc7t_GFGPnjQ&#39;;return true;">http://maven.apache.org/SETTINGS/1.0.0"

  xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instance\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFERp6A_kcvqihMCKJ7EHX8O14vIA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instance\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFERp6A_kcvqihMCKJ7EHX8O14vIA&#39;;return true;">http://www.w3.org/2001/XMLSchema-instance"

  xsi:schemaLocation="<a href="http://maven.apache.org/SETTINGS/1.0.0" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.0.0\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFFDm89L65OUelL3uKc7t_GFGPnjQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.0.0\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFFDm89L65OUelL3uKc7t_GFGPnjQ&#39;;return true;">http://maven.apache.org/SETTINGS/1.0.0

                      <a href="http://maven.apache.org/xsd/settings-1.0.0.xsd" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.apache.org%2Fxsd%2Fsettings-1.0.0.xsd\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG00w_6Y8uo9FDh4fUjGBaDBTidog&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.apache.org%2Fxsd%2Fsettings-1.0.0.xsd\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG00w_6Y8uo9FDh4fUjGBaDBTidog&#39;;return true;">http://maven.apache.org/xsd/settings-1.0.0.xsd">


  <servers>

    <server>

      <id><a href="http://maven.jenkins-ci.org" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEbH4wNAUcuIryNrQEo-DSIWx86VQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEbH4wNAUcuIryNrQEo-DSIWx86VQ&#39;;return true;">maven.jenkins-ci.org</id> <!-- For parent 1.397 or newer; before this use id java.net-m2-repository -->

      <username>ki82</username>

      <password>***************</password>

    </server>

  </servers>


</settings>


I have verified that my password works at <a href="https://repo.jenkins-ci.org/webapp/#/login" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Fwebapp%2F%23%2Flogin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNER_6hTZEwRiTxFfMNFL2KREOoLFQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Fwebapp%2F%23%2Flogin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNER_6hTZEwRiTxFfMNFL2KREOoLFQ&#39;;return true;">https://repo.jenkins-ci.org/webapp/#/login and I use the encrypted password in the ~/m2/settings.xml

I have executed the effective pom and verified that the id is correct.


Does anyone have any idea why this is failing for me?

Is there any way to test the connection to <a href="http://maven.jenkins-ci.org" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEbH4wNAUcuIryNrQEo-DSIWx86VQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmaven.jenkins-ci.org\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEbH4wNAUcuIryNrQEo-DSIWx86VQ&#39;;return true;">maven.jenkins-ci.org without doing an actual release?




--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d3c3d903-44cf-40c4-9ad8-5c5f8596bbde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.