| Re: [cf-dev] Release new milestone |
Hi Mikael,
you are right, that doesn't work out of the box. However, [1] describes how this can be achieved. [2] describes how to configure ssh on the client and make it work from Hudson.
I think it would be very convenient to reuse the PGP key for this purpose, but in the end this is up to you of course....
[1] http://budts.be/weblog/2012/08/ssh-authentication-with-your-pgp-key
[2] http://invariantproperties.com/2014/02/02/accessing-private-github-repositories-from-hudson/
I don't think gpg keys can be used to authenticate against Github. I will need to generate a ssh keypair. But maybe I misunderstand what you are saying. If you can send me the blog entry that would be great.Thanks.Mikael_______________________________________________Le 15 oct. 2015 à 14:13, Kai <sophokles.kh@xxxxxxxxx> a écrit :Mikael,
I will take a look at the Promoted Build plugin. A note regarding push access to GitHub from Hudson: you can upload a "Deploy Key" to GitHub which can be used to authenticate a client based on the private key. I think you should then be able to simply use the Californium key pair you created for code signing to authenticate to GitHub as well. If you need help with that, I recently stumbled across a blog entry about that which I could try to find again...
Kai
Kai
_______________________________________________Mikael Barbero <mikael@xxxxxxxxxxx> schrieb am Do., 15. Okt. 2015, 10:49:Hi,
See my responses below.
> Kai and I looked at the release build through Hudson. The following issues popped up:
>
> - Our HIPP needs to be able to write to GitHub to push the release version and tag and next version
I can do that. But I will need to create a new user on github for the HIPP user (genie.californium). Let me check that with Denis later today. I will keep you posted about that.
> - The deploy goal needs both settings, for the Eclipse repo and for Maven Central (maybe that is possible by setting both "Settings" and "Global settings"; otherwise, we might need to put both settings in our project-specific settings.xml)
I just created a "super settings" named "Deploy to repo.eclipse.org + OSSRH".
> - We want to deploy only when also the version update to next version and the push to GitHub was successful (otherwise there might be a half-baked deployment that needs manual resolution, for instance when someone pushes to GitHub while the release build is running on Hudson)
You should have a look at the Hudson promote plugin (http://wiki.hudson-ci.org/display/HUDSON/Promoted+Builds+Plugin). I can install it on your HIPP if you want.
Cheers,
Mikael
> - "mvn versions:set -DnewVersion=..." does not work anymore, since the components inherit from parent, but are in different repos :(
>
> Mikael, can you comment if you could enable a push from Hudson to GitHub?
>
> Ciao
> Matthias
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev