Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-releng] Do you use releng.builder? Proposed restructuring

Updates below:

John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861


John Lanuti/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

04/18/2007 10:31 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
To
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
cc
Subject
Re: [wtp-releng] Do you use releng.builder?  Proposed restructuring






Isn't the only way to truly understand something complicated to completely take it apart and try and put it back together again?  :-)  Or is that just me....?

Thanks for the additional information David and Naci.  Let me break this up into specific tasks:


DONE  1. Empty out releng.builder and leave with a readme. Delete all old unused files and move everything to releng.wtpBuilder.  Ensure builds and tests are still running and no oversights.

DONE  2. Start new releng.wtptools top level node, and add all non build related wtp releng tools underneath.  Fix up references and again ensure builds and tests are running.

-org.eclipse.wtp.releng.tools = access rule warnings, file counting, other build statistic gathering

-org.eclipse.wtp.releng.wtpbuilder = used to automate and upload performance, api and junit test execution

-org.eclipse.wtp.releng.tools.component.core +
org.eclipse.wtp.releng.tools.component.ui = these two plugins are currently packaged by hand as wtp-apiscanner.zip on downloads site.  They are the code for the usage scans and breakage scans.

183064 3. Remove whatisfixed.  I think this is large and overengineered.  I've not heard of anyone using it, and I think mylar can provide similar support and for now bugzilla queries should be sufficient.


183066 4. For the other tools, mimic how org.eclipse.wtp.releng.tools is included in builds by a feature and is also being built using a CC target.  The build doesn't really require these other tools, but we could build them with each build?  Or just build them manually when necessary invoking the CC target?

183067 5. Ensure all tools are OSGI bundles and run as eclipse applications or ant tasks.   So, anything can be run using an ant task, however the tricky part is these ant tasks are in the releng.wtpbuilder node.  Should the api, performance, and adopter breakage related ant tasks be moved to the wtptools node?  We also have about half of our api scans which are just java executables.  I don't think it is a top priority to convert them to applications, but we can open bugs to.

183069 6. Document build infrastructure in wiki pages and keep community informed of all changes.


Does that about sum it up?  Oh, and I'm not sure _brave_ is the right choice of words Naci.  :-)

Thanks,

John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861
Naci Dai <naci.dai@xxxxxxxxxxxxx>
Sent by: wtp-releng-bounces@xxxxxxxxxxx

04/18/2007 09:53 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
To
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
cc
Subject
Re: [wtp-releng] Do you use releng.builder?  Proposed restructuring







John,  you are a brave soul and many thanks for improving our build infrastructure in this last few months.


Naci, can you comment on "what is fixed"? Should it just be removed? Or, would
you like to move your tool to it's own OSGi bundle and project under the new
releng.wtptools
What is fixed queries CVS changes and CVS comments and correlates them with bugzilla history for a given period of times (typically between two builds) and creates a report.  This is useful for generating a bug fix list for build since another as close to reality as possible.

When we wrote it we did a very simple minded implementation that took a very long time to run.  It uses xml-beans for parsing the xml files (hence the large libraries).

However, it has been patched to run under ten minutes for a build now, but it can be improved to use XML queries from bugzilla.

If people think that this report is still useful, we can patch it otherwise it is end-of-life :-)

Also, all, what's to become of the old releng.builder? Just nothing in head and left in place?
Or, should we have it deleted? I guess for appropriate version control, we should leave
all the old stuff in place, just not in head, with a small readme explaining why its empty.

Thanks,


David Williams:
Thanks for cleaning stuff up, John.

If I understand you right, releng.wtptools would be a new "top level" directory, and individual releng releted tool projects would then go under this directory?

I think worth documenting our tools off one of our build releated wiki pages.

org.eclipse.wtp.releng.tools
is the main tools I'm familar with

It is actually in a a map file, and built each build via
org.eclipse.wtp.releng.tests.feature
even though that version that is built is not necessarily immediately used -- just good hygiene :)

And, we have a CC target so it can be built seperatly.

When it's built seperately, it's actually uploaded to a special
download directory (a peer to 'committers' and 'downloads'), namely
~/downloads/webtools/wtpBuildTools/

The actual build, then, "pulls" the desired version of org.eclipse.wtp.releng.tools
from that download site, via our normal "dependancy" files, as setup in the
build.cfg file in releng.

Phew, good thing I wrote that down .... never realized how complicated it was :)

I suspect, though, this should be the pattern we use for all our releng tools.
If you agree, let's wite this up in the wiki and convert other releng tools to work similarly.

One implication, if not obvious, is that all our tools, IMHO, should be developed as
OSGi bundles and ran as Eclipse Apps, or, in some cases, as Ant Tasks.

Another request I have is to move "what is fixed" out of releng.wtpbuilder.
It has a pretty hefty set of jars in it, but is not really needed each build.
In fact, I'm not sure we ever run this any more.

Naci, can you comment on "what is fixed"? Should it just be removed? Or, would
you like to move your tool to it's own OSGi bundle and project under the new
releng.wtptools

Also, all, what's to become of the old releng.builder? Just nothing in head and left in place?
Or, should we have it deleted? I guess for appropriate version control, we should leave
all the old stuff in place, just not in head, with a small readme explaining why its empty.

Thanks,


John Lanuti/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

04/17/2007 04:46 PM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
To
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
cc
Subject
Re: [wtp-releng] Do you use releng.builder?  Proposed restructuring







Hey team,

Ok, so I almost have things working again...  One more respin hopefully which is running now.

Once we have a successful build, I can confirm what was unecessary and out of date in releng.builder.  For convenience, I have temporarily lumped all of the build, test and api scan related *stuff* into releng.wtpbuilder.  However, this is not a great design and we really should try and trim down our releng.wtpbuilder to really only be build related artifacts.  To this end, I am proposing the creation of a new project called releng.wtptools where we can house any of our testing, performance, and api scanning tools we currently use.  This will be a much more straightforward and managable design then having like 4 or 5 projects all called builder.  This will also help keep our releng.wtpbuilder to be pure and just as the name would suggest, an actual wtp builder.

Any comments, thoughts, suggestions, before I make progress (and hopefully not too much regression)  on this?

Thanks,

John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861
John Lanuti/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

04/17/2007 12:28 PM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
To
wtp-releng@xxxxxxxxxxx
cc
Subject
[wtp-releng] Do you use releng.builder?








Hopefully not.  :-)

The releng.builder was our old builder project which has been replaced by releng.wtpbuilder and releng.control.  There were a few items we still used the old releng builder for and I have now ported those items to also be in the new releng.wtpbuilder project.  I updated both the 1.5 and head stream of releng.wtpbuilder because releng.builder was not branched.  A 2.0 build is underway with these changes applied.  So far, so good.  :-)

Let me know if you have any questions on where to find something, or if you were using releng.builder for whatever reason.

Thanks,

John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng

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


--
Naci Dai,

eteration a.s.
itu teknokent ari-1 25
Maslak, Istanbul 34469

+90 (533) 580 2393 (cell)
+90 (212) 328 0825 (phone)
+90 (212) 328 0521 (fax)
http://www.eteration.com/
mailto:naci.dai@xxxxxxxxxxxxx_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng

Back to the top