[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [jwt-dev] Build tomorrow
|
Hi Mickael,
I just discussed with Antoine on IRC, there will be no big discussion today
concerning build for #eclipse-stp, since Oisin did publish a document
describing what needs to be done with SVN yesterday. So Antoine is currently
working on that from his side and we'll need to check the documents made
available by releng that you already cited on one of your (thousands of ;-)
bug messages.
The link (bugzilla by Oisin) sent by Marc will be quite helpful, I guess,
too.
So, I'll contact you via Skype in the next minutes.
Best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Marc Dutoo
Gesendet: 05 December 2008 10:55
An: Java Workflow Toolbox
Betreff: Re: [jwt-dev] Build tomorrow
Here is Oisin's generic build system taking BPMN as an example at STP :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=257655
(using buckminster though)
a+
Marc
Florian Lautenbacher a écrit :
> Hi there,
>
> just a short notice that STP is going to discuss everything about
> their build process on IRC tomorrow already (see discussion below).
> There seems to be a basic description about how to build which we
> might talk about tomorrow as well. If Chris got time, then I'll try to
> start the specific steps with him tomorrow, maybe Mickael might join
> us at some point via Skype or IRC?
>
> http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.build/build/trunk/h
> ow-to-
> build.txt
>
> Best regards,
>
> Florian
>
> ---
>
>
> Today's Topics:
>
> 1. Re: Requirements for the build. (Antoine Toulme)
> 2. Re: Requirements for the build. (Oisin Hurley)
> 3. Re: Requirements for the build. (Antoine Toulme)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 4 Dec 2008 10:03:01 +0100
> From: "Antoine Toulme" <antoine@xxxxxxxxxxxxxxx>
> Subject: Re: [stp-dev] Requirements for the build.
> To: "STP Dev list" <stp-dev@xxxxxxxxxxx>
> Message-ID:
> <f97124910812040103w1daf05ffsdca5c2b68cf73f28@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I just discussed a bit about this with Stephane on IRC.
> Several facts are piling up:
> -we need a M4 build for the 5th of January.
> -Stephane is on vacations from the 12th of December to the 10th of
January.
>
> Stephane is ok with all propositions so far.
>
> I think we need to work on the build ASAP.
> We should have the IRC hacking session tomorrow.
> We should make sure we have a build for the next telco.
>
> Oisin, please pick a time tomorrow, and we will all need to arrange with
it.
>
> I'll try to get familiar with the build today. If no IRC sessions can
> happen tomorrow, expect many questions from me on this list.
>
> Thanks,
>
> Antoine
>
> On Wed, Dec 3, 2008 at 4:00 PM, Antoine Toulme
> <antoine@xxxxxxxxxxxxxxx>wrote:
>
>
>> On Wed, Dec 3, 2008 at 3:22 PM, Oisin Hurley
>>
> <oisin.hurley@xxxxxxxxx>wrote:
>
>>> I'd like to open up some discussion on the way we build things right
>>> now and ask for opinions, advice, and eventually, help.
>>>
>>> Our build will be changing to accomodate the various SVN changes and
>>> now is the team to think about greater change and flexibility.
>>>
>>> The question is, what do you want from it? Cruisecontrol, hudson
>>> build-on-change is very useful, as is a regular full build and test
>>> schedule. Documentation is a must, as is the capability for
>>> developers to build from the command line locally on their own
>>> machine. An automatically generated home page is the norm for other
>>> projects too, so something like that is necessary.
>>>
>> I'd be happy to help set up a cruise control system for BPMN and
>> document that for other components/sub-projects.
>>
>>
>>> What else? For example, right now the build is just one big blob,
>>> wherein everything gets constructed. I'd suggest that build-per-
>>> component and build-per-project seems to be a better idea. A full
>>> roll-up build can be useful, but follows a different schedule, i.e.
>>> it will consume from the individual builds.
>>>
>> I would focus on this first. Have one person per
>> component/sub-project responsible for the build, and have them have
>> access to the build machine, and get a quick intro to Buckminster
>> from you. I would suggest to pick a date and a time, have everybody
>> interested logged into IRC, and start hacking for an hour. Rinse and
>> repeat until
>>
> everybody's build works.
>
>>> Also, there's platforms - 3.3.2 anyone? Certainly 3.5, that's
>>> mandatory, but maybe people want 3.4.x stream builds too?|
>>>
>> The BPMN modeler needs a respin for 3.4.2.
>>
>>
>>> For EID, I would like to have regular 3.4.x, 3.5.x stream builds,
>>> with test and coverage reports, and be able to build on my local
>>> machine, outside of the UI. Consumption then by update site is good.
>>> I'd like a separate download page for EID, linked from a top level
>>> STP page, kind of like the way Modeling does theirs. Also, a list of
>>> the dependencies would be very useful.
>>>
>>> Comments? Can we create a plan?
>>>
>>
>>> --oh
>>> _______________________________________________
>>> stp-dev mailing list
>>> stp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/stp-dev
>>>
>>>
>>
>> --
>> http://www.lunar-ocean.com/blog
>>
>>
>>
>
>
> --
> http://www.lunar-ocean.com/blog
> -------------- next part -------------- An HTML attachment was
> scrubbed...
> URL:
> https://dev.eclipse.org/mailman/private/stp-dev/attachments/20081204/a
> f70920
> 7/attachment.html
>
> ------------------------------
>
> Message: 2
> Date: Thu, 4 Dec 2008 09:24:26 +0000
> From: "Oisin Hurley" <oisin.hurley@xxxxxxxxx>
> Subject: Re: [stp-dev] Requirements for the build.
> To: antoine@xxxxxxxxxxxxxxx, "STP Dev list" <stp-dev@xxxxxxxxxxx>
> Message-ID:
> <e77cb25c0812040124t930dbd7ifd6fd686eee971a3@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
>
>> I just discussed a bit about this with Stephane on IRC.
>>
>
> Can you post the discussion on this list please, so we can all see it.
>
> Antoine, start with the document at
>
> http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.build/build/trunk/h
> ow-to-
> build.txt
>
> if you find bugs in the doc, fix em or give me a ping. I should be on
> IRC for at least some of the day today and tomorrow, exact times I'm
> not sure about yet.
>
> I suggest that to narrow down the potential issues that you copy the
> build trunk into a working copy of your project and basically hack on
> it to exclude the stuff that you don't need. You will probably want to
> run a full build from that document first to get familiar with the feel of
it.
>
> Building up the platform we use is manual - you'll find the instance
> for M3 in /shared/stp/platforms/3.5M3
>
> The build should run fine, the only annoying pieces are the moving
> around of files and the waiting for signing. But some of this can be
> solved by extending the existing ant script or adding some more.
>
> I think maybe once we get to the point that you can run a BPMN-only
> build, then we can get cracking on the automation and you can set up
> your instructions for cruisecontrol.
>
> I'll get on IRC later, I've a few things to get finished up this
morning...
>
> --oh
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 4 Dec 2008 11:26:10 +0100
> From: "Antoine Toulme" <antoine@xxxxxxxxxxxxxxx>
> Subject: Re: [stp-dev] Requirements for the build.
> To: "Oisin Hurley" <oisin.hurley@xxxxxxxxx>
> Cc: STP Dev list <stp-dev@xxxxxxxxxxx>
> Message-ID:
> <f97124910812040226g6489859xd1b389dbf0e7c8f1@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thu, Dec 4, 2008 at 10:24 AM, Oisin Hurley
<oisin.hurley@xxxxxxxxx>wrote:
>
>
>>> I just discussed a bit about this with Stephane on IRC.
>>>
>> Can you post the discussion on this list please, so we can all see it.
>>
>
> Sure:
> [09:36:46] <toulmean> hello sdrapeau
> [09:37:01] <toulmean> what do you think of the recommendations for the
> build ?
> [09:42:34] <sdrapeau> hi Antoine
> [09:42:49] <sdrapeau> I agree with the idea that each project has its
> own build [09:42:49] <sdrapeau> + automatically generated websites
> [09:42:53] <sdrapeau> etc.
> [09:46:21] <sdrapeau> I'm interested also for a common working session
> on IRc to set up the build process and an introduction to Buckminster
> [09:46:37] <toulmean> so I have your +1 [09:46:38] <toulmean> ok
> [09:46:42] <sdrapeau> I would like to do this before the 12 of
> december [09:46:56] <toulmean> got a build coming up ?
> [09:46:57] <toulmean> ok
> [09:47:05] <sdrapeau> I will be on vacation from the 12 of december to
> the 10 of january [09:47:20] <toulmean> you're lucky [09:47:21]
> <toulmean> ok [09:47:26] <sdrapeau> :) [09:47:42] <toulmean> either
> you post this info to the mailing list or I do it [09:47:47]
> <toulmean> let's target Thursday [09:47:57] <toulmean> ok ?
> [09:48:42] <sdrapeau> If I'm right, we must set-up the build process
> for M4 ?
> [09:48:45] <sdrapeau> ok
> [09:49:00] <toulmean> yep
> [09:49:05] <toulmean> and M4 is ...
> [09:49:17] <sdrapeau> 5 of January ?
> [09:50:06] <sdrapeau> yep M4+3 is 5 of January [09:50:59] <toulmean>
> f*** [09:51:09] <toulmean> we'd better start even earlier [09:51:37]
> <toulmean> we should do this tomorrow [09:51:56] <toulmean> and make
> sure we have a build in the telco of the 12th [09:52:09] <toulmean>
> ok, so who's writing to the list [09:52:10] <sdrapeau> yep [09:52:18]
> <toulmean> feel like writing to the list ?
> [09:53:21] <sdrapeau> I have a meeting at 10 (in 6 minutes). So, if
> you want you can do it, or I will do it in the afternoon [09:54:46]
> <toulmean> I'll do it
>
>
>
>> Antoine, start with the document at
>>
>>
>> http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.build/build/trunk/
>> h
>> ow-to-build.txt
>>
>> if you find bugs in the doc, fix em or give me a ping. I should be on
>> IRC for at least some of the day today and tomorrow, exact times I'm
>> not sure about yet.
>>
>> I suggest that to narrow down the potential issues that you copy the
>> build trunk into a working copy of your project and basically hack on
>> it to exclude the stuff that you don't need. You will probably want
>> to run a full build from that document first to get familiar with the
>> feel of it.
>>
>> Building up the platform we use is manual - you'll find the instance
>> for M3 in /shared/stp/platforms/3.5M3
>>
>> The build should run fine, the only annoying pieces are the moving
>> around of files and the waiting for signing. But some of this can be
>> solved by extending the existing ant script or adding some more.
>>
>> I think maybe once we get to the point that you can run a BPMN-only
>> build, then we can get cracking on the automation and you can set up
>> your instructions for cruisecontrol.
>>
>> I'll get on IRC later, I've a few things to get finished up this
>> morning...
>>
>
> Sounds like a plan.
>
>
>> --oh
>>
>>
>
>
>
> --
> http://www.lunar-ocean.com/blog
> -------------- next part -------------- An HTML attachment was
> scrubbed...
> URL:
> https://dev.eclipse.org/mailman/private/stp-dev/attachments/20081204/7
> 24d5c4
> 9/attachment.html
>
> ------------------------------
>
> _______________________________________________
> stp-dev mailing list
> stp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/stp-dev
>
>
> End of stp-dev Digest, Vol 36, Issue 4
> **************************************
>
> _______________________________________________
> jwt-dev mailing list
> jwt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jwt-dev
>
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
