Re: [dsdp-tm-dev] Re: Building on build.eclipse.org

[David Dykstal <dykstal@xxxxxxx>]

So a proper way to do an I-Build is to declare a particular time to  
do the build, have you and Javier (and myself of course) version our  
maps, then run the build scripts.

Since you and Javier are in Europe, it makes sense to do the  
declaration in the morning (US) and the build around noon (US).

I'll attempt an I-Build tomorrow immediately after the TM Conference  
call. Please tag your projects and update your maps prior to that.

Thanks.
---------------------------
Dave Dykstal
dykstal@xxxxxxx


---------------------------
Dave Dykstal
dykstal@xxxxxxx


On Oct 3, 2006, at 6:07 PM, Martin Oberhuber wrote:

> Hi Dave, Javier,
>
> I split up rse.map:
>
> - Dave can now release into rse.map
> - Javier can release into discovery.map
> - I'm going to release into tmcore.map.
>
> I tagged the HEAD version of discovery.map, so you'll be ready
> to do an I-Build at any time. In the future, Javier can tag
> discovery.map himself.
>
> Cheers,
> Martin
>
> Martin Oberhuber schrieb:
>
> > Hi Dave,
> >
> > I recommend you ask Javier to tag his files himself.
> >
> > Javier - please tag the HEAD version of Discovery (or whatever  
> > version you'd
> > like to go into the release) using the releng tools from the  
> > Eclipse Platform download
> > page.  If you have no permission to update the mapfile in  
> > org.eclipse.rse.build,
> > I recommend you create a new project  
> > (org.eclipse.tm.discovery.build) to hold
> > the mapfile for discovery only.
> >
> > That way, Javier - as component lead for discovery - can decide  
> > himself what
> > to tag for a release.
> >
> > Cheers,
> > Martin
> >
> > David Dykstal schrieb:
> >
> > > Martin -
> > >
> > > Very nice scheme of updating the map files using the releng  
> > > tools. I am
> > > running into one problem however, It appears I am not authorized  
> > > to tag the
> > > files in the tm.core project that holds the discovery plugins. I  
> > > believe
> > > this something that will break the build since the .project  
> > > and .classpath
> > > files are the ones being tagged. Is there someway around this?
> > >
> > > Hope things are going OK.
> > > _______________________
> > > David Dykstal
> > > david_dykstal@xxxxxxxxxx
> > >
> > >
> > >                                                                      
> > >                   Martin  
> > > Oberhuber                                                          < 
> > > martin.oberhuber                                                     
> > >      @windriver.com>                                             
> > > To                                       David Dykstal/Rochester/ 
> > > IBM@IBMUS,              09/29/2006 05:51          "Williams,  
> > > Ted"                                 PM                         
> > > <ted.williams@xxxxxxxxxxxxx>                                         
> > >                                         
> > > cc                                                                   
> > >                                                                      
> > >        Subject                                       Building on  
> > > build.eclipse.org
> > >
> > >
> > >
> > > Hi Dave,
> > >
> > > building RSE on build.eclipse.org should be real simple now:
> > >
> > > 1.) In you local workspace, apply the tags: Rightclick > Team >  
> > > Release
> > >   - select all plugins from the workspace; tag changed plugins  
> > > only etc.
> > >
> > > 2.) Prepare the build environment on build.eclipse.org
> > >
> > > ssh build.eclipse.org -l ddykstal
> > > mkdir $HOME/ws
> > > cd $HOME/ws
> > > wget -O setup.sh
> > > "
> > > http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/ 
> > > releng/org.eclipse.rse.build/setup.sh? 
> > > rev=HEAD&cvsroot=DSDP_Project&content-type=text/plain
> > > "
> > > sh setup.sh
> > >
> > > 3.) Do the build:
> > > ./doit_ibuild.sh
> > > <enter>
> > > I
> > > <enter>
> > >
> > > 4.) Publish on testUpdates
> > > cd testUpdates/bin
> > > ./mkTestUpdateSite.sh
> > >
> > > 5.) Test the testUpdates, then stage to updates
> > > cd ../updates
> > > rm -rf plugins features
> > > cp -R ../testUpdates/plugins .
> > > cp -R ../testUpdates/features .
> > > cd bin
> > > ./mkTestUpdates.sh
> > >
> > >
> > > That's it... release completed!
> > > Enjoy,
> > >
> > > --
> > > Martin Oberhuber
> > > Wind River Systems, Inc.
> > > Target Management Project Lead, DSDP PMC Member
> > > http://www.eclipse.org/dsdp/tm
>
>
> --
> Martin Oberhuber
> Wind River Systems, Inc.
> Target Management Project Lead, DSDP PMC Member
> http://www.eclipse.org/dsdp/tm
>
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev