Problem during plugin release

[Thomas Fürer]

Hi,

I'm the maintainer of thinBackup-plugin and I want to release several
commits.
I tried it several time now with

mvn release:prepare release:perform -Dusername=tofuatjava -Dpassword=...

but I finally I get the error message

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy)
on project thinBackup: Failed to deploy artifacts: Could not transfer
artifact org.jvnet.hudson.plugins:thinBackup:hpi:1.8 from/to
maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Failed to
transfer file:
https://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/thinBackup/1.8/thinBackup-1.8.hpi.
Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

I tried to update my credentials at accounts.jenkins-ci.io, but nothing
changes.
So, please could anyone check my credentials on the plugin hosting
repository or verify my settings in the pom?

thomas

PS: I found several posts in the wiki, most of them are in my opinion
outdate and it is not easy to find the relevant things.

[Fritz Elfert]

Hi,

You do not have permissions to release thinBackup (actually NOBODY has).
You can fix this yourself. Read the README here:
https://github.com/jenkins-infra/repository-permissions-updater/

Cheers
-Fritz

[Daniel Beck]

> On 06.11.2016, at 11:05, Fritz Elfert <fr...@fritz-elfert.de> wrote:
>
> You do not have permissions to release thinBackup (actually NOBODY has).

True, but that should result in 403 Forbidden, not 401 Unauthorized.

It appears credentials are also not sent (although the pom appears to use the repo.j.o host name).

[Thomas Fürer]

I have tried to execute these script but get an NullPointerException.

I also have filed an Pull Request for my change.

Maybe anyone from the infrastructure crew can add this.


Thanks

Thomas

[Bruno P. Kinoshita]

Hi Thomas,

I had a similar problem trying to release active-choices-plugin last Friday.

What worked for me was reading


https://issues.jenkins-ci.org/browse/INFRA-588

and updating the project pom.xml. Here's the summary for the fix, extracted from INFRA-588:

"""
UPDATE: the recommended and simplest solution is to just upgrade to the 2.x parent plugin pom. See https://github.com/jenkinsci/plugin-pom
This issue has been fixed in that pom starting with its 2.5 version.
So, just use that pom, and remove the references/overrides from your pom to make sure you inherit the right values.
"""

So here's what I did:

https://github.com/jenkinsci/active-choices-plugin/commit/ccb6ed06784cc5499ef268e7d6bb81dfec46c350

Furthermore, after fixing it, the mvn release:prepare failed, due to FindBugs warnings (I assume this new parent is checking plug-ins for FindBugs issues). So I'd suggest

1) try changing your pom.xml as per INFRA-588
2) run mvn clean test findbugs:findbugs findbugs:gui and confirm all tests are passing, and that FindBugs is happy too
3) release it :)

Hope that helps,
Bruno

> --
> 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 jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/d37fb7fc-a767-592b-f83f-523625b9450e%40gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.
>

[Thomas Fürer]

it seams that I'm still not authorized to release thinBackup plugin.

I hadded the missing information to the yaml file some days ago, but
still get the same error.

Thomas


Am 06.11.2016 um 11:05 schrieb Fritz Elfert:

[Peter Tierno]

On Wednesday, November 9, 2016 at 12:41:38 PM UTC-5, Thomas Fuerer wrote:

it seams that I'm still not authorized to release thinBackup plugin.

I hadded the missing information to the yaml file some days ago, but
still get the same error.

have you resolved this? if so, how? im experiencing the same issue.

[Thomas Fürer]

No, sorry.

I still get the error

[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project thinBackup: Failed to deploy artifacts: Could not transfer artifact org.jvnet.hudson.plugins:thinBackup:hpi:1.8 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Failed to transfer file: https://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/thinBackup/1.8/thinBackup-1.8.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

Any idea?

Thomas

--

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 jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8e0449bf-221a-48be-9099-b9c8efd4f39c%40googlegroups.com.

[Martin Reinhardt]

having the same error

[Baptiste Mathus]

401 or 403? Read Daniel's answer about it above if 401. You're probably missing something in your settings.xml or so.

If possible, come over to IRC right now to get a bit more interactive. Ping batmat

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4e33e958-3db9-4935-aa6b-8c9669cd0ea0%40googlegroups.com.

[Thomas Fürer]

finally i did it. v1.8.0 of thinBackup is out now.

Well, thot took some doing.

What I've done:
* upgrade to parent pom 2.11 (-> look at thinBackup @ github)
* update the settings.xml temporary for this release and it looks like this one

<pluginGroups>
    <pluginGroup>org.jenkins-ci.tools</pluginGroup>
  </pluginGroups>

  <profiles>
    <!-- Give access to Jenkins plugins -->
    <profile>
      <id>jenkins</id>
      <activation>
        <activeByDefault>true</activeByDefault> <!-- change this to false, if you don't like to have it on per default -->
      </activation>
      <repositories>
        <repository>
          <id>repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/public/</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/public/</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
  <mirrors>
    <mirror>
      <id>repo.jenkins-ci.org</id>
      <url>https://repo.jenkins-ci.org/public/</url>
      <mirrorOf>m.g.o-public</mirrorOf>
    </mirror>
  </mirrors>

hope this will help

Tom

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6Sz7Lz29%2BrhRB0-vpuuyDDzaAFmhK46vf2S%2BayA49Vzg%40mail.gmail.com.

[Daniel Beck]

So basically, what you did is what's described in https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-SettingUpEnvironment as merely 'helpful', with parts 'probably unnecessary'? Without this file, it didn't work?

>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4e33e958-3db9-4935-aa6b-8c9669cd0ea0%40googlegroups.com.
>>
>> 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 jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6Sz7Lz29%2BrhRB0-vpuuyDDzaAFmhK46vf2S%2BayA49Vzg%40mail.gmail.com.
>> 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 jenkinsci-de...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a1b7e634-2308-e7f0-762a-2b0c045f5418%40gmail.com.

[Thomas Fürer]

jep, but it is very hard to read the wiki, because lot of information is
outdated and I could not find this post you linked; and I was able to
release this plugin in the past and dont want to do the whole
configuration again. Nevertheless I did it again and found the pices I
need between alot of data at this page
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins. Hope the
configuration will be stable for now.

tom

[Baptiste Mathus]

This is a wiki. Please feel free to fix outdated things. Or please, please, tell us what is outdated. I'm curious which one is. 

I think many pages should just be wiped out, or heavily shortened to keep the really important things, but doing that takes time. If things are outdated then it's just to be deleted, and we save time if you show us obviously outdated things...

>>> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.

>>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4e33e958-3db9-4935-aa6b-8c9669cd0ea0%40googlegroups.com.
>>>
>>> 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 jenkinsci-dev+unsubscribe@googlegroups.com.

>>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6Sz7Lz29%2BrhRB0-vpuuyDDzaAFmhK46vf2S%2BayA49Vzg%40mail.gmail.com.
>>> 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 jenkinsci-dev+unsubscribe@googlegroups.com.

>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a1b7e634-2308-e7f0-762a-2b0c045f5418%40gmail.com.
>> 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 jenkinsci-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d256091c-87b8-8346-8eb5-af8fcac670c1%40gmail.com.

[Daniel Beck]

> On 26.11.2016, at 20:54, Baptiste Mathus <m...@batmat.net> wrote:
>
> This is a wiki. Please feel free to fix outdated things. Or please, please, tell us what is outdated. I'm curious which one is.
> I think many pages should just be wiped out, or heavily shortened to keep the really important things, but doing that takes time. If things are outdated then it's just to be deleted, and we save time if you show us obviously outdated things...

This.

We also have a new mailing list for collaborating on documentation now:

https://groups.google.com/forum/#!forum/jenkinsci-docs

[Thomas Fürer]

Sorry, my bad. This is not what I want to say.
I just want to note that it was very hard to find the solution for my
problem(s).
When I do a recap, it was probably better to read all the documentation
top down.

Don't get me wrong, I joined the community some years ago, because I
think jenkins was/is great and I want to do what I could do to make it a
little bit greater. But as always in software projects the documentation
sometimes not covers the things in a structure that all kinds of
problems are in place for all types of persons.

To make long story short, in my case I have troubles with releasing
plugins. IMHO What about using our own infrastructure at
https://jenkins.ci.cloudbees.com or https://ci.jenkins-ci.org to release
the plugins?

Thomas

[Jesse Glick]

On Sun, Nov 27, 2016 at 2:43 AM, Thomas Fürer <tfuerer...@gmail.com> wrote:
> What about using our own infrastructure at
> https://jenkins.ci.cloudbees.com or https://ci.jenkins-ci.org to release
> the plugins?

Long been on our wishlist; no proposal yet for how to do an
authentication check.