Re: [wtp-incubator-dev] Vex: Empty Integration Build

[David M Williams <david_williams@xxxxxxxxxx>]

This may take a few notes, before I
understand what's being asked ... but, I'll give some answers and we'll
go from there. 

> 1. The Incubator WTP Build based Integration
builds should eventually go 
> away or be enhanced reworked due to the upcoming switch from CVS to
Git 
> as the repository.

I agree they should go away. It'd be great if someone
wanted to integrate 
Git with them and their underlying PDE build, but
I won't be looking at 
all this new stuff any time soon so don't want my
schedule to hold you up. 

> So I can setup a Vex Integration build, but will
probably need help from 
> David in regards to what needs to be done to promote that build to
the 
> appropriate folders and downloads area for WTP projects.

First, to clarify, the "build.eclipse.org/webtools/committers"
build is the 
URL to our "continuous" builds produced
by cruisecontrol. I've configured cruisecontrol to "copy artifacts"

there after each build. You are welcome to do the
same with hudson if you'd like. 
The only restriction is you'd need a three part "project
name" to fit in. Such as
we currently have "wtp-R3.2.0-S" as three
parts. Under that a datetimestamp directory, 
and under that the usually visible director such as
S-3.2.0RC4-20100608222047 and under 
that some "standard" files, and index.php
file, testsumnary.xml, etc., which are expected
(and, no, not spec'd except "in the code").
:) 

So, you're welcome to try and fit in there, if you'd
like, with the understanding that 
as continuous builds, they can be deleted just about
any time. (And need to be "cleaned up" 
if nothing else, on a regular basis, and the current
cleaner might automatically work, 
I think it's rule is to remove anything over 5 days
old, but always leave at least one). 

Next, I, S, and R builds all get "promoted"
to the same place on download.eclipse.org. 
These are normally mirrored (so should be limited
in number and size), but the eclipse.org 
infrastructure knows not to mirror directories starting
with "I-". (and some other rules
I don't recall right now). 

Those directories have a structure like 
~/downloads/webtools/downloads/drops/Rx.y.z/<standard
named directory> 
where "standard named directory" is the
normally visible directory, such as S-3.2.0RC4-20100608222047. 

The key is they all have to start with I-, S-, or
R- ... and similar index.php, testsummary.xml, etc. 
same as in 'committers' area. I've pained to created
some "common files" that work on both 
download.eclipse.org, and build.eclipse.org.  There's
many directories there, if you want to see examples. 

The "common files" I mentioned scan directories
and see what builds are available and "summarize" them, 
allowing uses to "click down" to the specific
build they want. 

If we want/need to do many improvements here, we should
probably move to more of "xml file" based system, 
so the php script doesn't have to "scan the directories"
so much, but instead the xml file contains 
the summary info of where to find a build, and when
that xml file is update is when the end user would 
see new builds to click down to. 

Hope this long note makes some sense ... and answers
some questions at least. If this rambling brief
description doesn't turn you off completely and you
want to pursue "integrating" multiple types of build 
result directories perhaps we should continue in a
bugzilla, so it'd be "self documenting". 

But, there could be other, easier approaches ... and
I might be completely misunderstanding what you were 
asking :) 

thanks,

From:	David Carver <d_a_carver@xxxxxxxxx>
To:	WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Date:	06/09/2010 09:41 AM
Subject:	Re: [wtp-incubator-dev] Vex: Empty Integration Build
Sent by:	wtp-incubator-dev-bounces@xxxxxxxxxxx

---

My feelings on this are as follows:

1. The Incubator WTP Build based Integration builds should eventually go
away or be enhanced reworked due to the upcoming switch from CVS to Git
as the repository.

2. The current Maven/Tycho based builds are currently for CI 
builds...however, we can enhance these to provide 
Integration/Milestone/Release builds as well.

So I can setup a Vex Integration build, but will probably need help from
David in regards to what needs to be done to promote that build to the
appropriate folders and downloads area for WTP projects.   If it is
just 
a matter of Aggregating the Update Site into the existing site, I can 
provide a URL to the Vex Update site from the appropriate build.

David is there some documentation on what is done to promote an 
Integration build to something more public?

Dave

On 06/09/2010 01:01 AM, Holger Voormann wrote:
> @Dave (Carver): Should Vex webtools/committer files removed?
>
> Best regards, Holger
>
>
> 09.06.2010 09:48, David M Williams:
>>
>> yes, I think so. I did (finally) "pause" the old cruisecontrol
job,
>> since its always failed.
>> and will remove the job altogether before long.
>>
>> I'll wait for you request, "please remove webtools/committer
files"
>> before I do ... just to make sure that's what you want,
>> (Hard to tell if you are asking a question, or making a statement).
>>
>> I'm glad your hudson/git/maven/tycho builds are going well. ...
and,
>> more important, that vex is active and going well!
>>
>> Much thanks!
>>
>>
>>
>>
>> From:     Holger Voormann <eclipse@xxxxxxxxxxx>
>> To:     wtp-incubator-dev@xxxxxxxxxxx
>> Date:     06/09/2010 03:39 AM
>> Subject:     Re: [wtp-incubator-dev] Vex: Empty Integration
Build
>> Sent by:     wtp-incubator-dev-bounces@xxxxxxxxxxx
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>>
>> Hi David, hi Dave,
>>
>> is Hudson a replacement of the old Integration Builds? The other
builds
>> listed at http://build.eclipse.org/webtools/committers/
are up-to-date.
>> If Vex should be build only with Hudson+Maven+Tycho (which makes
sense)
>> then we should remove Vex from 
>> http://build.eclipse.org/webtools/committers/
>>
>> Best regards, Holger
>>
>>
>> 09.06.2010 09:26, David M Williams:
>> >
>> > That URL is for our cruisecontrol produced builds. You'd
have another
>> > one now for your huson/git/tycho/maven builds.
>> > (or am I missing something?)
>> > But, sorry, I do not know what that URL is.
>> >
>> >
>> >
>> > From: Holger Voormann <eclipse@xxxxxxxxxxx>
>> > To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
>> > Date: 06/09/2010 02:55 AM
>> > Subject: [wtp-incubator-dev] Vex: Empty Integration Build
>> > Sent by: wtp-incubator-dev-bounces@xxxxxxxxxxx
>> >
>> >
>> > 
>> ------------------------------------------------------------------------
>> >
>> >
>> >
>> > Hi Dave,
>> >
>> > I released an Integration Build but no ZIP files have been
produced:
>> >
>> <http://build.eclipse.org/webtools/committers/vex-R0.5-I/20100609062838/I-I20100609062838-20100609062838/>
>>
>> >
>> > Unfortunately, now there are no Vex Integration Builds to
>> download/use.
>> >
>> > Any ideas?
>> >
>> > Best regards, Holger
>> > _______________________________________________
>> > wtp-incubator-dev mailing list
>> > wtp-incubator-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > wtp-incubator-dev mailing list
>> > wtp-incubator-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>> _______________________________________________
>> wtp-incubator-dev mailing list
>> wtp-incubator-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>>
>>
>>
>>
>> _______________________________________________
>> wtp-incubator-dev mailing list
>> wtp-incubator-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
> _______________________________________________
> wtp-incubator-dev mailing list
> wtp-incubator-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>

_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev