Skip to main content
Jump to: navigation, search

Difference between revisions of "SWT/Native Builds on Foundation"

< SWT
(Force Build Natives)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
SWT Native Builds are run on the Eclipse Foundation Infrastructure. (Associated bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=476642)
 
SWT Native Builds are run on the Eclipse Foundation Infrastructure. (Associated bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=476642)
  
The Jobs are on the Releng HIPP and can be seen in the SWT Natives view (https://hudson.eclipse.org/releng/view/SWT%20Natives/)
+
The Jobs are on the Releng HIPP and can be seen in the SWT Natives view (https://ci-staging.eclipse.org/releng/view/SWT%20Natives/)
  
 
The SWT Native build has been broken down into multiple steps. There are separate jobs for each of these steps and they run in a sequence automatically.
 
The SWT Native build has been broken down into multiple steps. There are separate jobs for each of these steps and they run in a sequence automatically.
Line 10: Line 10:
 
If there are no changes in the repo, then the Build exits at this step.
 
If there are no changes in the repo, then the Build exits at this step.
 
If natives_changed = true, then jobs to build the SWT libraries are triggerred.
 
If natives_changed = true, then jobs to build the SWT libraries are triggerred.
1. SWT-native-build
+
1. win32_x86_64, gtk_linux_x86_64, cocoa_x86_64, gtk_linux_ppc64le
2. win32_x86, win32_x86_64, gtk_linux_x86, gtk_linux_x86_64, cocoa_x86_64, gtk_linux_ppc64, gtk_linux_ppc64le
+
2. Generates and Writes the qualifier to pom file source and binaries repo
3. swt-collect-libs
+
3. Commits the changes in source and binaries repo
 
+
4. Tags the commits
== Step2: 2-SWT-Commit_Binaries_and_Tag ==
+
5. Pushes the commits in source and binaries repo to remote
Generates and Writes the qualifier to pom file source and binaries repo\
+
Commits the changes in source and binaries repo
+
Tags the commits
+
 
+
== Step3: 3-SWT-git_push ==
+
Pushes the commits in source and binaries repo to remote
+
  
 
== Build Schedule ==
 
== Build Schedule ==
Line 27: Line 21:
  
 
== Manual Build Input ==
 
== Manual Build Input ==
To do a SWT build input, go to Job 1-SWT-Increment_if_needed - https://hudson.eclipse.org/releng/view/SWT%20Natives/job/1-SWT-Increment_if_needed/ and build now. This will automatically run all the other jobs and push the changes/tags to the repos.
+
To do a SWT build input, go to Job 1-SWT-Increment_if_needed - https://ci-staging.eclipse.org/releng/view/SWT%20Natives/job/1-SWT-Increment_if_needed/ and build now. This will automatically run all the other jobs and push the changes/tags to the repos.
  
 
== Force Build Natives ==
 
== Force Build Natives ==
Line 35: Line 29:
 
#touch "${WORKSPACE}/tmp/build_changed.txt"
 
#touch "${WORKSPACE}/tmp/build_changed.txt"
 
#touch "${WORKSPACE}/tmp/natives_changed.txt"
 
#touch "${WORKSPACE}/tmp/natives_changed.txt"
 
== Test Native Builds ==
 
You can test if the native builds will run successfully on any of the platforms by running the respective test build jobs (without running through all the steps). Below are the test build jobs:
 
* Test-build-swt-win32-x86_64
 
* Test-build-swt-win32-x86
 
* Test-build-swt-cocoa-x86_64
 
* Test-build-swt-gtk-x86
 
* Test-build-swt-gtk-x86_64
 

Latest revision as of 06:05, 23 March 2020

SWT Native Builds are run on the Eclipse Foundation Infrastructure. (Associated bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=476642)

The Jobs are on the Releng HIPP and can be seen in the SWT Natives view (https://ci-staging.eclipse.org/releng/view/SWT%20Natives/)

The SWT Native build has been broken down into multiple steps. There are separate jobs for each of these steps and they run in a sequence automatically.

Sequence of the jobs:

Step1: 1-SWT-Increment_if_needed

Clones the SWT source and binaries repo and checks the java compilation. Checks for source and native changes in the repo. If there are no changes in the repo, then the Build exits at this step. If natives_changed = true, then jobs to build the SWT libraries are triggerred. 1. win32_x86_64, gtk_linux_x86_64, cocoa_x86_64, gtk_linux_ppc64le 2. Generates and Writes the qualifier to pom file source and binaries repo 3. Commits the changes in source and binaries repo 4. Tags the commits 5. Pushes the commits in source and binaries repo to remote

Build Schedule

1-SWT-Increment_if_needed job is triggered automatically by the I-build job as the first step.

Manual Build Input

To do a SWT build input, go to Job 1-SWT-Increment_if_needed - https://ci-staging.eclipse.org/releng/view/SWT%20Natives/job/1-SWT-Increment_if_needed/ and build now. This will automatically run all the other jobs and push the changes/tags to the repos.

Force Build Natives

1-SWT-Increment_if_needed job will exit if there are no changes in the repos for a new build. And if there are no changes in the source repo that require native build, then natives will not be built.

To force native build in this case, uncomment these lines in the job.

  1. touch "${WORKSPACE}/tmp/build_changed.txt"
  2. touch "${WORKSPACE}/tmp/natives_changed.txt"

Back to the top