Hi Miles,
Our site feature does not contain p2 mirrorring configurations
because the build can not know in advance where it will be promoted
to. Instead our current promotion script does the following to
insert the needed property into the already promoted repository:
for F in artifacts content
do
$JAR xf $F.jar
sed -i "/<property name='p2\.compressed'/a \ \ \ \
<property name='p2.mirrorsURL'
value='http://www.eclipse.org/downloads/download.php?file=/modeling/emf/cdo/updates/$stream/$stream-$milestone-$label&protocol=http&format=xml'/>'>"
$F.xml
$JAR cf $F.jar $F.xml
done
I'm currently working on a new cron based "promotion service" infra
structure to automate almost all aspects of the promotion process.
When it's ready I'll probably blog about it to see if others find it
interesting.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 17.06.2011 21:24, schrieb Miles Parker:
That's a big help, thanks. It does seem like another repos,
namely AMP's full release repos which I'm using because it has
some extra bits I need that are *not* in the repos that was used
for the b3aggr build. I'd given up on trying to get the
mirrorURL automated, so it simply points to the same repos which
I guess is what gets spit out by default. I had thought that
setting a mirror was desirable but not necessary and this works
fine from a regular desktop p2 install. Anyway, not your
problem, and thanks again for the tip. :)
On Jun 16, 2011, at 10:14 PM, David M Williams wrote:
My
first guess would be the value of a
mirrorsURL attribute would be wrong ... where '&' is
omitted, or
'&' is used instead of the required '&'
(required, that is,
in the xml file).
Are you using other
repositories in
addition to .../releases/staging? I ask because I visually
checked the
mirrorsURL values at staging, and it appears correct to me:
<property
name='p2.mirrorsURL'
value='http://www.eclipse.org/downloads/download.php?format=xml&file=/releases/staging/aggregate/&protocol=http'/>
I'm asking if others repos
are also
used, since there's been several issues with that in the
past ... such
as see bug 230924 [1] so am wondering if one of those repos
as an incorrect
value?
Or ... could be something
else Just
trying to help, little as I could.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=230924
From:
Miles Parker <milesparker@xxxxxxxxx>
To:
Cross project
issues
<cross-project-issues-dev@xxxxxxxxxxx>
Date:
06/16/2011 09:24 PM
Subject:
[cross-project-issues-dev]
Staging
repos issue?
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
I've just started building an SDK based on
my project
and when I go up against the releases/staging repository,
Buckminster is
giving me a slew of these:
[Fatal Error]
indigo?countryCode=us&timeZone=-8&format=xml:6:450:
The reference to entity "lang" must end with the ';'
delimiter.
After complaining like this for a while, the
resolution
seems to succeed anyway.
I just mention this here because I wonder if it
implicates
anything going wrong with some artifacts somewhere._______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
