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

[gmon...@redhat.com]

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

[gmon...@redhat.com]

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]


[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)

[Daniel Beck]

> On 5. Feb 2019, at 21:41, gmon...@redhat.com 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, gmon...@redhat.com 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

[gmon...@redhat.com]

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, gmon...@redhat.com 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.

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, gmon...@redhat.com 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

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


 

[gmon...@redhat.com]

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

[Daniel Beck]

> On 12. Feb 2019, at 22:17, gmon...@redhat.com 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.

[gmon...@redhat.com]

Will do - thanks Daniel