Hi
thx for the feedback and creating the directories.
I have requested the new hudson job and the changes to the old
one:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=396704
Just to make sure I understand, you are basically suggesting the
following path:
* nightly build: publishes unsigned artifacts to a temp directory
from where a cron job will copy them to the downloads directory
* release build: will be used for release builds only which will
be signed and manually (?) published to a seperate downloads
directory (to be created)
Any reason why we should not sign the nightly builds? To
expensive?
regards,
Stefan
On 13.12.2012 22:14, Denis Roy wrote:
Hi Stefan,
Good to see you're making rapid progress.
Some input, below:
On 12/10/2012 03:50 AM, Stefan Strobl wrote:
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?
I suggest changing the current job name to *nightly and creating a
new *release job (which would (eventually) perform signing).
* create directories as described
below
I've created
/home/data/httpd/download-staging.priv/technology/babel and it is
directly writable by Hudson.
I've also created
/home/data/httpd/download.eclipse.org/technology/babel/tools-updates-nightly
.. it is not writable by Hudson.
Denis
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
