New build system in placehttps://www.eclipse.org/forums/index.php/mv/msg/7561/23106/#msg_23106
First off, a big word of thanks for your kind words and votes in the
recent committer election. Looking forward now to getting access sorted
and working closer with you.

I just wanted to send this brief note to say that an automated build
system is now in place for Buckminster at [1]. The first successful
build was a short while ago, and this build will now execute on every
commit to the svn repository.

So this is just a build for now, I have some test execution stuff that
I'll put in there next week when I get a chance.

As a little experiment, I configured it to use twitter, so for those you
hanging out in that space, you can follow "buckminster_dev" on twitter
to see latest build results.

I've tried configuring Hudson to link directly into the eclipse bugzilla
instance, but there seems to be a problem with it and I don't have time
to investigate it.

Cheers,
Adrian.

[1] http://dev.cloudsmith.com:8088/]]>Adrian Skehill2008-07-30T13:58:23-00:00Access controlhttps://www.eclipse.org/forums/index.php/mv/msg/7561/23146/#msg_23146
You may want to set up some access control to the build machine. It
looks like anyone can reconfigure it. I can certainly access the
reconfigure page; I didn't try to save but I can certainly change things.

Regards
Doug]]>Douglas Palmer2008-07-31T20:22:54-00:00Re: Access controlhttps://www.eclipse.org/forums/index.php/mv/msg/7561/23185/#msg_23185
> Hi Adrian
>
> You may want to set up some access control to the build machine. It
> looks like anyone can reconfigure it. I can certainly access the
> reconfigure page; I didn't try to save but I can certainly change things.
>
> Regards
> Doug

Thanks Doug,

Secured with just me to configure it. Will chat with the team next week
to see who gets access to what.

After encouraging you to lock down the Hudson configuration I have
started looking into Hudson for my own builds. It would be useful to see
how you configure hudson with buckminster. Is you configuration in the
buckminster svn somewhere? Similarly is your ant script in there too?
If not would you mind sending them to me?

Douglas Palmer wrote:
> Hi Adrian
>
> After encouraging you to lock down the Hudson configuration I have
> started looking into Hudson for my own builds. It would be useful to see
> how you configure hudson with buckminster. Is you configuration in the
> buckminster svn somewhere? Similarly is your ant script in there too?
> If not would you mind sending them to me?
>
> Regards
> Doug

Hi Doug,

I'm attaching the files that are used in the current build (they've
changed alot from those attached to my bug), so you can take a look at
them. Regarding the configuration of Hudson, it's trivial, basically,
you will need a machine that has the following:

* ant, javac and svn available
* allows a port to be opened and accessed, default 8080

Install Hudson and create a new job, chose free style(I think) project
and point it to build.xml in the attached zip file. You will need to
give it a location where it can check out your repository to. In the
end, the main smarts are in the ant build system which in turn delegates
heavily to Buckminster.

Once Thomas (ping!) gets my commit rights sorted, these files will be in
the Buckminster svn repo for all to look at and make suggestions for
improvement.

Adrian Skehill wrote:
> Douglas Palmer wrote:
>> Hi Adrian
>>
>> After encouraging you to lock down the Hudson configuration I have
>> started looking into Hudson for my own builds. It would be useful to
>> see how you configure hudson with buckminster. Is you configuration in
>> the buckminster svn somewhere? Similarly is your ant script in there
>> too? If not would you mind sending them to me?
>>
>> Regards
>> Doug
>
>
> Hi Doug,
>
> I'm attaching the files that are used in the current build (they've
> changed alot from those attached to my bug), so you can take a look at
> them. Regarding the configuration of Hudson, it's trivial, basically,
> you will need a machine that has the following:
>
> * ant, javac and svn available
> * allows a port to be opened and accessed, default 8080
>
> Install Hudson and create a new job, chose free style(I think) project
> and point it to build.xml in the attached zip file. You will need to
> give it a location where it can check out your repository to. In the
> end, the main smarts are in the ant build system which in turn delegates
> heavily to Buckminster.
>
> Once Thomas (ping!) gets my commit rights sorted, these files will be in
> the Buckminster svn repo for all to look at and make suggestions for
> improvement.
>
> Feel free to drop me a line if you need any further assistance.
>
> A.

Thanks Adrian.

Doug]]>2008-08-06T10:08:04-00:00Re: New build system in placehttps://www.eclipse.org/forums/index.php/mv/msg/7561/23808/#msg_23808
The new build-system looks very promising. Right now I'm only lacking
one thing and that's the installation of the delta-pack on top of the
target platform.

Normally when I build, I use a target platform consisting of the SDK
(just like the new build system) and the platform delta-pack that
contains all the launchers. This delta-pack is supposed to be unzipped
right on top of an existing Eclipse installation (this is in contrast to
the recommendations to use dropins folder etc. The dropins folder will
not work).

With the delta pack in place, the build should normally execute with the
following parameters set:

We'll need to figure out how to cope with the privileges needed in order
to do signing and later automatic publishing. Both involves sending
things to Eclipse.org.

Regards,
Thomas Hallgren

Adrian Skehill wrote:
> Hi guys,
>
> First off, a big word of thanks for your kind words and votes in the
> recent committer election. Looking forward now to getting access sorted
> and working closer with you.
>
> I just wanted to send this brief note to say that an automated build
> system is now in place for Buckminster at [1]. The first successful
> build was a short while ago, and this build will now execute on every
> commit to the svn repository.
>
> So this is just a build for now, I have some test execution stuff that
> I'll put in there next week when I get a chance.
>
> As a little experiment, I configured it to use twitter, so for those you
> hanging out in that space, you can follow "buckminster_dev" on twitter
> to see latest build results.
>
> I've tried configuring Hudson to link directly into the eclipse bugzilla
> instance, but there seems to be a problem with it and I don't have time
> to investigate it.
>
> Cheers,
> Adrian.
>
> [1] http://dev.cloudsmith.com:8088/]]>Thomas Hallgren2008-08-06T11:36:16-00:00Re: New build system in placehttps://www.eclipse.org/forums/index.php/mv/msg/7561/24320/#msg_24320
> Hi Adrian,
> The new build-system looks very promising. Right now I'm only lacking
> one thing and that's the installation of the delta-pack on top of the
> target platform.
>
> Normally when I build, I use a target platform consisting of the SDK
> (just like the new build system) and the platform delta-pack that
> contains all the launchers. This delta-pack is supposed to be unzipped
> right on top of an existing Eclipse installation (this is in contrast to
> the recommendations to use dropins folder etc. The dropins folder will
> not work).
>
> With the delta pack in place, the build should normally execute with the
> following parameters set:
>
> qualifier.replacement.*=generator:lastRevision
> generator.lastRevision.format=r{0,number,00000}
> target.os=*
> target.ws=*
> target.arch=*
>
> The product of the build will then have correct qualifiers and also
> become platform independent.
>
> It would be interesting to see what happens if you use the following
> target:
>
> <target name="buckminster.build.site">
> <echo message="Building Buckminster Update Site"/>
> <buckminster command="perform">
> <arg value="org.eclipse.buckminster#normalize.site"/>
> </buckminster>
> </target>
>
> This will build the complete update site except signing and pack200.
>
> We'll need to figure out how to cope with the privileges needed in order
> to do signing and later automatic publishing. Both involves sending
> things to Eclipse.org.
>

Thanks Thomas,

I am already bringing down the dela pack and extracting it as part of
the build. I'll take a look at setting the arch etc. to "*" but I had
some difficulties, so I left those unset in the current build. Will revisit.

I'll pop in the update site target and commit the file into svn so it's
more accessible. It should work though, I have this already up and
running on my own product builds.

Let's have a chat after I get these updates in to see what the best
solution will be on doing the signing and packing.