Skip to main content
Jump to: navigation, search

Difference between revisions of "Building Equinox Launcher"

(Execution of build jobs)
 
Line 24: Line 24:
 
   
 
   
 
====Execution of build jobs====
 
====Execution of build jobs====
Run the [https://hudson.eclipse.org/releng/view/Launcher/job/Step-1-Increment-build-id/ Step-1-Increment-build-id] in the next page it asks for 4 options.
+
Run the [https://ci-staging.eclipse.org/releng/view/Launcher/job/Build-eclipse-launcher/ Build-eclipse-launcher] in the next page it asks for 4 options.
 
   * increment build id (check this if you have determined the build_id needs to be incremented)
 
   * increment build id (check this if you have determined the build_id needs to be incremented)
 
   * buildGtk (check this if linux platforms needs to be built)
 
   * buildGtk (check this if linux platforms needs to be built)
Line 30: Line 30:
 
   * buildWin32 (check this for windows platforms)
 
   * buildWin32 (check this for windows platforms)
  
After this click on build button. then build will start and you'll see [https://hudson.eclipse.org/releng/view/Launcher/job/collect-launcher-libs/ collect libraries job] scheduled multiple times(4 times for gtk, 2 for win32 and 1 for Mac).
+
After this click on build button, then build will start, this triggers build on native configurations and once the builds succeed newly built libraries are pushed to git repos as well
 
+
Wait for the collect-launcher-libs jobs to complete and also check for any failures. If there are no failures run [https://hudson.eclipse.org/releng/view/Launcher/job/Step-2-Commit-libraries-and-push/ Step-2-Commit-libraries-and-push]. This will push newly built libraries to git repos.
+

Latest revision as of 05:38, 23 March 2020

Equinox Launchers can be built from Releng CI Instance. This needs to be used on demand only.

https://hudson.eclipse.org/releng/view/Launcher/job/Step-1-Increment-build-id/


Process

Identify affected platforms

The library source structure is (can be seen here Launcher Source)

library - contains common code
cocoa - contains Mac specific code
gtk - contains Linux specific code
win32 - contains Windows specific code

If common code is changed you need to build all platforms. Otherwise only the specific platforms needs to built

Identify whether build id needs to increment

You need to compare last build id

  • used in the last successful build of launcher across all platforms and
Can be identified by the variable LIB_VERSION in make_version.mak
  • used for that specific platform
Verify platform specific eclipse_<version>.<so/dll> at binaries repo eclipse_<version>.<so/dll> would be present in org.eclipse.equinox.launcher.<ws>.<os>.<arch>

If both are same you'll need to increment, otherwise build id should not be incremented

Execution of build jobs

Run the Build-eclipse-launcher in the next page it asks for 4 options.

 * increment build id (check this if you have determined the build_id needs to be incremented)
 * buildGtk (check this if linux platforms needs to be built)
 * buildCocoa (check this for Macos platforms)
 * buildWin32 (check this for windows platforms)

After this click on build button, then build will start, this triggers build on native configurations and once the builds succeed newly built libraries are pushed to git repos as well

Back to the top