Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Mini-Tutorial: Fetching, archiving and re-using a target platform with Buckminster/Hudson
Mini-Tutorial: Fetching, archiving and re-using a target platform with Buckminster/Hudson [message #517256] Fri, 26 February 2010 17:13 Go to previous message
Ralf Ebert is currently offline Ralf EbertFriend
Messages: 72
Registered: July 2009
Member
This is a multi-part message in MIME format.

----------------1152948806826114542
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Following up on

http://www.ralfebert.de/blog/eclipsercp/rcp_builds/
http://www.eclipse.org/forums/index.php?t=msg&th=160977& amp;start=0&

here's how you can archive and re-use a target platform in
Buckminster+Hudson builds. Thanks to Johannes Utzig for providing the
missing piece of the puzzle!

The idea is to use two jobs, one to fetch and archive the target
platform and a 2nd one that uses this pre-fetched target platform. This
has the advantage that you control when the target platform is fetched,
the online software sites are only used when you run the target job.
This is a bit faster and decouples your actual build jobs from the
software sites:

- Add a .target file to your project, referring only software sites
(see Preferences > Plug-in Development > Target Platform, esp. "Move"
button to save a existing target definition to a file)
- Create a new freestyle job for fetching the target platform.
Configure it to import your project from the VCS.
- Add a "Run Buckminster" step to configure the target platform:

importtargetdefinition -A '${WORKSPACE}/com.example.mail.build/rcp.target'

- Check "Archive and publish an Eclipse Target Platform". Specify
".metadata/.plugins/org.eclipse.pde.core/.bundle_pool" as path.
- Run the job.
- Create a 2nd freestyle build job and configure your project build.
Choose the target platform in your "Run Buckminster" steps.

Actually it would be cool if you could tell the importtargetdefinition
command to save the provisioned target platform for late re-use to some
dedicated folder, I created a bug for such a feature:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=304062

Greetings,

Ralf

--
http://www.ralfebert.de/blog/
----------------1152948806826114542
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<title></title>
<meta name="Generator" content="Cocoa HTML Writer">
<meta name="CocoaVersion" content="949.54">
<style type="text/css">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px TheSansMono}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px TheSansMono; min-height: 17.0px}
p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Courier}
p.p4 {margin: 0.0px 0.0px 0.0px 0.0px; font: 16.0px TheSansMono; color: #808080}
span.s1 {font: 12.0px Courier}
</style>
</head>
<body>
<p class="p1">Following up on</p>
<p class="p2"><br></p>
<p class="p1">http://www.ralfebert.de/blog/eclipsercp/rcp_builds/</p>
<p class="p1">http://www.eclipse.org/forums/index.php?t=msg&amp;th=160977&amp;start=0&amp;</p>
<p class="p2"><br></p>
<p class="p1">here's how you can archive and re-use a target platform in Buckminster+Hudson builds. Thanks to Johannes Utzig for providing the missing piece of the puzzle!</p>
<p class="p2"><br></p>
<p class="p1">The idea is to use two jobs, one to fetch and archive the target platform and a 2nd one that uses this pre-fetched target platform. This has the advantage that you control when the target platform is fetched, the online software sites are only used when you run the target job. This is a bit faster and decouples your actual build jobs from the software sites:</p>
<p class="p2"><br></p>
<p class="p1">- Add a .target file to your project, referring only software sites (see Preferences &gt; Plug-in Development &gt; Target Platform, esp. "Move" button to save a existing target definition to a file)</p>
<p class="p1">- Create a new freestyle job for fetching the target platform. Configure it to import your project from the VCS.</p>
<p class="p1">- Add a "Run Buckminster" step to configure the target platform:</p>
<p class="p2"><br></p>
<p class="p3">importtargetdefinition -A '${WORKSPACE}/com.example.mail.build/rcp.target'</p>
<p class="p2"><br></p>
<p class="p1">- Check "Archive and publish an Eclipse Target Platform". Specify ".metadata/.plugins/org.eclipse.pde.core/.bundle_pool" as path.</p>
<p class="p1">- Run the job.</p>
<p class="p1">- Create a 2nd freestyle build job and configure your project build. Choose the target platform in your "Run Buckminster" steps.</p>
<p class="p2"><br></p>
<p class="p1">Actually it would be cool if you could tell the <span class="s1">importtargetdefinition</span> command to save the provisioned target platform for late re-use to some dedicated folder, I created a bug for such a feature: https://bugs.eclipse.org/bugs/show_bug.cgi?id=304062</p>
<p class="p2"><br></p>
<p class="p1">Greetings,</p>
<p class="p2"><br></p>
<p class="p1">Ralf</p>
<p class="p2"><br></p>
<p class="p4">--<span class="Apple-converted-space">
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon14.gif
Previous Topic:Problems with source feature generation/resolution
Next Topic:Git checkout appears to get wrong branch
Goto Forum:
  


Current Time: Wed Dec 08 04:39:47 GMT 2021

Powered by FUDForum. Page generated in 0.01941 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top