One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

gmontero
The plugin in question is openshift-sync.

The other openshift related plugins I actively maintain are still listed there.

I'm not seeing any notifications in the spots I know where to look where as to
why it might have been removed.

Any pointers folks could provide?

thanks,
gabe

--
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/a00a7c6f-b941-45a2-8733-4793668a0738%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

gmontero
Perhaps related, when I tried to cut a new version today, I got:

Failed to deploy artifacts: Could not transfer artifact io.fabric8.jenkins.plugins:openshift-sync:hpi:1.0.32 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Failed to transfer file: https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/openshift-sync-1.0.32.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

On Tuesday, February 5, 2019 at 3:41:32 PM UTC-5, [hidden email] wrote:
The plugin in question is openshift-sync.

The other openshift related plugins I actively maintain are still listed there.

I'm not seeing any notifications in the spots I know where to look where as to
why it might have been removed.

Any pointers folks could provide?

thanks,
gabe

--
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/f2ba7319-9885-47b4-9696-9c30f4449185%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

Victor Martinez
When I faced a 401 error when pushing to the central repo in the past it was regarding some settings.xml misconfiguration, maybe https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins might help 
(see section HTTP 401 when transferring a file to the Jenkins Maven repository)


--
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/a8d22872-7770-457a-bd8c-9a2f2875e17d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

Daniel Beck
In reply to this post by gmontero


> On 5. Feb 2019, at 21:41, [hidden email] wrote:
>
> Any pointers folks could provide?
>

Perhaps a side effect of the failed release of 1.0.32:
https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/

Depends on when it went missing and when you tried to release.

> On 5. Feb 2019, at 21:49, [hidden email] wrote:
>
> Failed to deploy artifacts: Could not transfer artifact io.fabric8.jenkins.plugins:openshift-sync:hpi:1.0.32 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Failed to transfer file: https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/openshift-sync-1.0.32.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
>

401 Unauthorized is usually a problem with authentication, such as a password change on accounts.jenkins.io. See https://jenkins.io/doc/developer/publishing/releasing/#artifactory-credentials-for-maven

--
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/D822C7A0-2173-4280-8B28-1768710A74A6%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

gmontero
Thanks for the response Daniel.

Some additional details embedded below.

On Wednesday, February 6, 2019 at 3:10:55 PM UTC-5, Daniel Beck wrote:


> On 5. Feb 2019, at 21:41, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="56IRlya-FAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">gmon...@... wrote:
>
> Any pointers folks could provide?
>

Perhaps a side effect of the failed release of 1.0.32:
<a href="https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEL_YhKr22tkKEnHmMjk0Y6gQXpBw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEL_YhKr22tkKEnHmMjk0Y6gQXpBw&#39;;return true;">https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/

Depends on when it went missing and when you tried to release.

It has been since Dec 11 2018 since I tried to craft a new release, and I did not look at that location beforehand when attempting to cut
a new release earlier this week.

BTW, I just tried it again now and it failed the same way.

> On 5. Feb 2019, at 21:49, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="56IRlya-FAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">gmon...@... wrote:
>
> Failed to deploy artifacts: Could not transfer artifact io.fabric8.jenkins.plugins:openshift-sync:hpi:1.0.32 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="https://repo.jenkins-ci.org/releases/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHeKZNR7f1vjTS3LIvQ2j7wEaDXpQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHeKZNR7f1vjTS3LIvQ2j7wEaDXpQ&#39;;return true;">https://repo.jenkins-ci.org/releases/): Failed to transfer file: <a href="https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/openshift-sync-1.0.32.hpi" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2Fopenshift-sync-1.0.32.hpi\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxyPVlRRtZZibQSK1ckJ0O0-Cd6g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2Fopenshift-sync-1.0.32.hpi\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxyPVlRRtZZibQSK1ckJ0O0-Cd6g&#39;;return true;">https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/openshift-sync-1.0.32.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
>

401 Unauthorized is usually a problem with authentication, such as a password change on <a href="http://accounts.jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Faccounts.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4icI2DQ_cnLN3jCLO8fBquwUIXA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Faccounts.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4icI2DQ_cnLN3jCLO8fBquwUIXA&#39;;return true;">accounts.jenkins.io. See <a href="https://jenkins.io/doc/developer/publishing/releasing/#artifactory-credentials-for-maven" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Freleasing%2F%23artifactory-credentials-for-maven\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHECQwZ_7qa6lp6AlXg37PBN9MlNQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Freleasing%2F%23artifactory-credentials-for-maven\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHECQwZ_7qa6lp6AlXg37PBN9MlNQ&#39;;return true;">https://jenkins.io/doc/developer/publishing/releasing/#artifactory-credentials-for-maven

My only sticking point there  is using the same workstation with the same ~/.m2/settings.xml
I've been able to cut new release for the openshift-login-plugin since reporting
this failure.

The authentication required should be the same for both plugins, no?

And I just checked jenkins-infra/repository-permissions-updater/permissions and I'm listed
for both plugins.

Would it make sense to open and issue on https://issues.jenkins-ci.org/projects/HOSTING/issues/HOSTING-702?filter=allopenissues
Or some other jira category to track what is up?

thanks
 

--
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/ceb5d4a9-e83a-4587-bb66-305d54709cbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

gmontero
So I hit refresh on the browser tabs I had for https://updates.jenkins-ci.org/download/plugins/openshift-sync/ and https://updates.jenkins-ci.org/download/plugins/
today and the sync plugin reappeared !!!!!

Including the version I attempted to create last week where I got the 401's during mvn release:prepare release:perform

I'm curious if there was some known recovery operation that might have recovered things for me here.

But otherwise I'm happy I don't have to open issues and track down further.

Thanks again to those who responded

On Friday, February 8, 2019 at 2:43:42 PM UTC-5, [hidden email] wrote:
Thanks for the response Daniel.

Some additional details embedded below.

On Wednesday, February 6, 2019 at 3:10:55 PM UTC-5, Daniel Beck wrote:


> On 5. Feb 2019, at 21:41, [hidden email] wrote:
>
> Any pointers folks could provide?
>

Perhaps a side effect of the failed release of 1.0.32:
<a href="https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEL_YhKr22tkKEnHmMjk0Y6gQXpBw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEL_YhKr22tkKEnHmMjk0Y6gQXpBw&#39;;return true;">https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/

Depends on when it went missing and when you tried to release.

It has been since Dec 11 2018 since I tried to craft a new release, and I did not look at that location beforehand when attempting to cut
a new release earlier this week.

BTW, I just tried it again now and it failed the same way.

> On 5. Feb 2019, at 21:49, [hidden email] wrote:
>
> Failed to deploy artifacts: Could not transfer artifact io.fabric8.jenkins.plugins:openshift-sync:hpi:1.0.32 from/to <a href="http://maven.jenkins-ci.org" rel="nofollow" target="_blank" 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="https://repo.jenkins-ci.org/releases/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHeKZNR7f1vjTS3LIvQ2j7wEaDXpQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHeKZNR7f1vjTS3LIvQ2j7wEaDXpQ&#39;;return true;">https://repo.jenkins-ci.org/releases/): Failed to transfer file: <a href="https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/openshift-sync-1.0.32.hpi" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2Fopenshift-sync-1.0.32.hpi\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxyPVlRRtZZibQSK1ckJ0O0-Cd6g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2Fopenshift-sync-1.0.32.hpi\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxyPVlRRtZZibQSK1ckJ0O0-Cd6g&#39;;return true;">https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/openshift-sync-1.0.32.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
>

401 Unauthorized is usually a problem with authentication, such as a password change on <a href="http://accounts.jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Faccounts.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4icI2DQ_cnLN3jCLO8fBquwUIXA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Faccounts.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4icI2DQ_cnLN3jCLO8fBquwUIXA&#39;;return true;">accounts.jenkins.io. See <a href="https://jenkins.io/doc/developer/publishing/releasing/#artifactory-credentials-for-maven" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Freleasing%2F%23artifactory-credentials-for-maven\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHECQwZ_7qa6lp6AlXg37PBN9MlNQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Freleasing%2F%23artifactory-credentials-for-maven\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHECQwZ_7qa6lp6AlXg37PBN9MlNQ&#39;;return true;">https://jenkins.io/doc/developer/publishing/releasing/#artifactory-credentials-for-maven

My only sticking point there  is using the same workstation with the same ~/.m2/settings.xml
I've been able to cut new release for the openshift-login-plugin since reporting
this failure.

The authentication required should be the same for both plugins, no?

And I just checked jenkins-infra/repository-permissions-updater/permissions and I'm listed
for both plugins.

Would it make sense to open and issue on <a href="https://issues.jenkins-ci.org/projects/HOSTING/issues/HOSTING-702?filter=allopenissues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fprojects%2FHOSTING%2Fissues%2FHOSTING-702%3Ffilter%3Dallopenissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFksYT8DmNl5NPeCX1r69gtZJef4Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fprojects%2FHOSTING%2Fissues%2FHOSTING-702%3Ffilter%3Dallopenissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFksYT8DmNl5NPeCX1r69gtZJef4Q&#39;;return true;">https://issues.jenkins-ci.org/projects/HOSTING/issues/HOSTING-702?filter=allopenissues
Or some other jira category to track what is up?

thanks
 

--
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/d86dd0c7-575d-4168-9b42-a793b75244f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

Daniel Beck


> On 12. Feb 2019, at 22:17, [hidden email] wrote:
>
> Including the version I attempted to create last week where I got the 401's during mvn release:prepare release:perform
>
> I'm curious if there was some known recovery operation that might have recovered things for me here.
>

The release at https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/ is now sort of fixed (no sources, Javadoc, etc.). I expect that this is the cause for the recovery you're seeing. Note that when I wrote my earlier response, I saw errors related to that release in the update center generator logs.

Don't know what the cause for HTTP 401 could be if it works with a different plugin at the same time on the same machine.(Password change might still be it.) Ping me on IRC when it happens the next time, we only have 20 minutes or so worth of logs from Artifactory.


--
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/765E3179-29B2-4556-ABBF-636FC268D9F2%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: One of the plugins I maintain is now missing from https://updates.jenkins-ci.org/download/plugins/

gmontero


On Wednesday, February 13, 2019 at 7:31:08 AM UTC-5, Daniel Beck wrote:


> On 12. Feb 2019, at 22:17, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="jvBol6FOAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">gmon...@... wrote:
>
> Including the version I attempted to create last week where I got the 401's during mvn release:prepare release:perform
>
> I'm curious if there was some known recovery operation that might have recovered things for me here.
>

The release at <a href="https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEL_YhKr22tkKEnHmMjk0Y6gQXpBw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Freleases%2Fio%2Ffabric8%2Fjenkins%2Fplugins%2Fopenshift-sync%2F1.0.32%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEL_YhKr22tkKEnHmMjk0Y6gQXpBw&#39;;return true;">https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/1.0.32/ is now sort of fixed (no sources, Javadoc, etc.). I expect that this is the cause for the recovery you're seeing. Note that when I wrote my earlier response, I saw errors related to that release in the update center generator logs.

Don't know what the cause for HTTP 401 could be if it works with a different plugin at the same time on the same machine.(Password change might still be it.) Ping me on IRC when it happens the next time, we only have 20 minutes or so worth of logs from Artifactory.

Will do - thanks Daniel

--
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/649365ac-a6b6-44f5-816a-6ffffd153c45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.