Hi
short update: I just pushed my changes and the CI build is still
green [0] ;) so we're good for now:
Next Steps:
* If anyone with experience in using the
eclipse-signing-maven-plugin could review the changes [1] I
would be really greatful (thx to Martin for the initial review)
* Decision on Hudson Jobs: currently we have one job [2] which
is configured for continuous integration (e.g. building more or
less after every build). I do not think that signing and
publishing the results is good/necessary to do so often. The
question therefore is: do we change the current build to a
"nightly" build or should I request a new one?
* create directories as described below
* Setup/configure the build to use maven profile -Pbuild-server
(if we use the current build I need someone with the necessary
permissions to do the change - or grant them to me)
* run test build and see if everything publishes correctly -
again, for existing build I would need someone to push the
button (as I do not have permissions to manually trigger build
:/)
* update babel downloads page
cheers
Stefan
[0]
https://hudson.eclipse.org/hudson/job/babel-tools-indigo/5/
[1]
http://git.eclipse.org/c/babel/plugins.git/commit/?id=ee33571a2f91f3f32a456b25b5f1eea344edd480
[2]
https://hudson.eclipse.org/hudson/job/babel-tools-indigo/
On 07.12.2012 14:41, Stefan Strobl wrote:
Hi
Matthias, first of, thanks a lot for the pointers. Having a
project to "steal" most of the setup from really makes this
job quite a bit easier. Btw: I spent most of my time figuring
out how to produce a suitable category.xml file. From what I
understand, and I learnt today that I still understand very
little ;), this basically does all the steps that Denis
described in his previous post (creating a p2 repo, etc..)
I got around to playing with the eclipse-signing-maven-plugin
today and I think, I have a working version locally. I'm going
to let Martin review my changes and wait for the answers to my
question below before pushing to the babel repo though.
@Denis, Matthias: it seems that egit copies the repository
directly to the downloads section
(/home/data/httpd/download.eclipse.org/...), correct?
@Denis: you mentioned that the webmasters are not so happy
about this approach. If it is ok with you I would still like
to take the direct route first to test the setup etc and then
subsequently introduce the cron job, once everything is
working.
currently, I would use the following two directories:
* temp location for signing:
/home/data/httpd/download-staging.priv/technology/babel
* destination for singed p2 repository:
/home/data/httpd/download.eclipse.org/technology/babel/tools-updates-nightly
If these directories are ok, I will create them on
build.eclipse.org (I just tested, unblocked and used my shell
access ;) ) and then push my changes and test them on the
server with hudson.
Cheers
Stefan
On 28.11.2012 23:21, Matthias Sohn wrote:
2012/11/28 Stefan Strobl <stefan.strobl@xxxxxxxxxxxxxxxxx>
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
