[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: Didn't Build for Me [Re: [orbit-dev] Orbit Build process ready for review and contributions]

David, a few build notes/questions:

1). Do you think that we should be using the branch name as part of the tag
when we version? I was releasing changes to org.junit (both streams) and I
ran into problems because I used the v200701261100 version tag for both
streams. So then I created one with a v200701261101 tag but it became hard
to remember which branch this one was for, etc. Would it be ok to use
something like v3_8_2_20070126, etc?

2). If we can update the builder to be running on the latest version of
PDE-Build, that would be cool. There was a bug that Pascal fixed which
allows for qualifier replacement in the middle of strings that we will need
when we have a bundle that already has a 4 part version. (e.g. org.junit
4.1.0.1_qualifier -> 4.1.0.1_20070126)

3). What is the process for adding additional versions to the build? (e.g.
a 3rd version of a plug-in) I would assume the following steps but wanted
to confirm with you before doing it: create a new branch of the releng
project and use an empty map file with just your new bundle's entry, create
a new feature project following the naming convention (.set3) and add your
bundle to the feature.xml.

Thanks.

                  dj


orbit-dev-bounces@xxxxxxxxxxx wrote on 01/25/2007 06:06:02 PM:

>
> Perfect. even the directions of "... so if you do not see an updated
> build on the committers area within an hour and a half, please
> contact one of the Orbit release engineers " must
> have been pretty clear :)
>
> From what I can see, you did everything just right, and discovered a
> silly error in the cruise control scripts ... I'm so used to "head",
> I forgot to tell it to detect change on branches too.
> I've fixed the script and "manually" started a new build, so you
> don't have to wait any longer than needed.
> But, I almost hope you notice something small you want to change,
> re-release to 'set1', and _then_ we'll see if my fix for auto-build
> actually works!
> If not ... I'm sure there will be more opportunities soon.
>
> Keep'm comin'
>
>
>
>

>
> Christian Damus <cdamus@xxxxxxxxxx>
> Sent by: orbit-dev-bounces@xxxxxxxxxxx
> 01/25/2007 03:01 PM
>
> Please respond to
> Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
>
> To
>
> Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
>
> cc
>
> Subject
>
> Didn't Build for Me [Re: [orbit-dev] Orbit Build process ready for
> review and contributions]
>
>
>
>
>
> Hi, David,
>
> I followed the (very clear and easy) steps that you set out in the
> Wiki for releasing new bundles into the build.  I added the Apache
> Batik bundles to the 'set1' feature and released with the
> v200701251713 label (using UTC time as you indicated).  It's now a
> few hours since then and the Orbit build daemon hasn't built it, yet.
>
> What have I done wrong?  The CruiseControl seems to be healthy; it
> produced a build early this morning and updates its "waiting since"
> status every hour.
>
> TIA,
>
> Christian
>
>
> Christian W. Damus
> Component Lead, Eclipse OCL and EMFT-QTV
> IBM Rational Software_______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev