|
I think I was mistaken with an email
which was basically stating "don't rely on staging/" which is fine
and different from "we don't use staging anymore".
Thanks to both of you, I'll wait for the simrel process to finish
and will re-trigger my patchset on EPP.
Le 02/05/2016 14:32, David M Williams a écrit :
I have re-enabled the
job. I am surprised
it was disabled (for so long) and surprised no one has mentioned
it before
now.
From:
Markus Knauer
<mknauer@xxxxxxxxxxxxxxxxx>
To:
Eclipse Packaging
Project
<epp-dev@xxxxxxxxxxx>,
Date:
05/02/2016 05:31 AM
Subject:
Re: [epp-dev]
epp-tycho-build.gerrit builds and consuming "staging" update
site
Sent by:
epp-dev-bounces@xxxxxxxxxxx
Okay, I see there's a problem...
Solution 1 could be to update /releases/staging
more often.
AFAIK the only reason for disabling the promote to Staging job
is to give
the main EPP build a chance to rebuild during release week
(especially
on Thursday/Friday). From my point of view we could simply
re-enable this
job.
And your second proposal could be done, too. The
main
reason for using /releases/staging (and /releases/maintenance
for the second
release stream) is that we currently have only one Gerrit job
for multiple
release streams. We'd need to duplicate the Gerrit jobs, one for
every
release stream, and then we could switch to the Hudson URLs. My
only concern
is that we've experienced problems with Hudson serving large
amounts of
data via its web frontend in the past. But if webmasters are
fine with
it now, we could certainly change the URL in our Gerrit job.
Regards,
Markus
On 2 May 2016 at 11:17, Cédric Brun <cedric.brun@xxxxxxx>
wrote:
Hi,
I have patchsets in mid-air to adapt the content of the Modeling
package.
One of those includes a new feature which got introduced in the
simrel
repository post M6 [1].
Problem is the "promote to Staging" job has been disabled since
then (see: https://hudson.eclipse.org/simrel/job/simrel.neon.promoteToStaging/)
and I tend to recall (but I can't find the mail) that it was "by
design
for a specific purpose" but I'm not sure which.
Anyway this prevents me from getting "fresh content" into the
package and I can't get my patchset in without staging being
promoted in
some way or I would break all the other packages builds.
That makes me wonder, should I do things differently ? And why
not using
https://hudson.eclipse.org/simrel/job/simrel.neon.runaggregator.BUILD__CLEAN/lastSuccessfulBuild/artifact/aggregation/final/as the input to the epp-tycho-build.gerrit job ?
[1]: https://git.eclipse.org/r/#/c/69892/
--
Cédric Brun
CTO
+33 2 51 13 51 42
@bruncedric
7 Boulevard
Ampère - Carquefou
- France
obeo.fr| twitter| linkedin
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
Cédric
Brun
CTO
+33
2 51 13 51 42
@bruncedric
7 Boulevard Ampère - Carquefou -
France
obeo.fr | twitter | linkedin
|
