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


Am 26.11.2016 um 16:24 schrieb 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?
>
>> On 26.11.2016, at 09:17, Thomas Fürer <[email protected]> wrote:
>>
>> 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
>> Am 24.11.2016 um 22:48 schrieb 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
>>>
>>> 2016-11-24 22:41 GMT+01:00 Martin Reinhardt <[email protected]>:
>>> having the same error
>>>
>>> Am Mittwoch, 23. November 2016 19:26:26 UTC+1 schrieb Thomas Fuerer:
>>> 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
>>>
>>> Am 21.11.2016 um 20:15 schrieb 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.
>>>> -- 
>>>> 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].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/8e0449bf-221a-48be-9099-b9c8efd4f39c%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 [email protected].
>>> 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 [email protected].
>>> 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 [email protected].
>> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d256091c-87b8-8346-8eb5-af8fcac670c1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to