Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "LTS/HowTos"
(→Setting up a Hudson Maven project to build Eclipse Platform) |
(→Updating LTS Repository) |
||
Line 56: | Line 56: | ||
== Updating LTS Repository == | == Updating LTS Repository == | ||
+ | |||
+ | === Adding LTS Central remotes === | ||
+ | |||
+ | Before you can update your repos with the latest changes from the LTS Central repo you will need to add the LTS Central repos as a remote. | ||
+ | |||
+ | <pre> | ||
+ | git remote add central https://<username> | ||
+ | @lts.eclipse.org/gitroot/lts-central/platform/eclipse.platform.releng.aggregator.git | ||
+ | </pre> | ||
= Known Issues = | = Known Issues = |
Revision as of 15:53, 28 February 2013
Contents
Howtos
Using TortoiseGit to "git submodule update"
- Navigate to your git repository which you cloned (eg. eclipse.platform.releng.aggregator)
- Right click > TortoiseGit > Submodule Update
- Select to Initialize Submodules
- Click OK
Setting up a Hudson Maven project to build Eclipse Platform
For the steps below. Navigate to your Job you wish to configure and choose Configure
Setting up Git
- Enter URL of git repo (example: /gitroot/lts-central/platform/eclipse.platform.releng.aggregator.git)
- Note: This is the path component of the https:// provider.
- Example: https://lts.eclipse.org/gitroot/lts-central/platform/eclipse.platform.releng.aggregator.git
- Becomes: /gitroot/lts-central/platform/eclipse.platform.releng.aggregator.git
- Note: This is the path component of the https:// provider.
- Set the build branch (eg. R4_2_maintenance)
- Click Advanced... under Branches to Build
- Check Skip internal tag
- Save
Setting up Platform Build
Build step 1, invoke maven for eclipse-parent
- click Add Build Step -> Invoke Maven 3
- click Advanced
- Set goals: clean install
- Set pom-file: eclipse-parent/pom.xml
- Set private repository enabled
- Save
Build step 2, invoke maven for maven-cbi-plugin
- click Add Build Step -> Invoke Maven 3
- click Advanced
- Set goals: clean install
- Set pom-file: maven-cbi-plugin/pom.xml
- Set private repository enabled
- Save
Build step 3, invoke maven for Platform build
- click Add Build Step -> Invoke Maven 3
- click Advanced
- Set goals: clean install
- Set properties: maven.test.skip=true
- Set pom-file: pom.xml
- Set private repository enabled
- Set profiles: no-bree-libs
- Save
Updating LTS Repository
Adding LTS Central remotes
Before you can update your repos with the latest changes from the LTS Central repo you will need to add the LTS Central repos as a remote.
git remote add central https://<username> @lts.eclipse.org/gitroot/lts-central/platform/eclipse.platform.releng.aggregator.git
Known Issues
Fail to clone submodules using msysgit
Per Bug 376400 we discovered that msysgit has a max character limit somewhere around 256 which causes cloning files with a path longer than that to fail.
See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=376400#c4
Workaround: Put your repo in the root of a drive and give it a short name. For example: C:\z
Error assembling JAR: Could not find a common basedir (Resolved)
In git version 1.7.8 and newer, git changed it's behaviour with respect to submodules https://raw.github.com/gitster/git/master/Documentation/RelNotes/1.7.8.txt
The new behaviour causes Tycho Eclipse-SourceReference provider for git to be unable to calculate the basedir correctly. There is a open Tycho bug that includes a patch for getting this resolved https://bugs.eclipse.org/bugs/show_bug.cgi?id=393752
Workaround: Use a git version 1.7.7 or earlier.
Cannot git clone via ssh:// protocol (Resolved)
The issue with this is that most user accounts on the Forge will not have shell access to the forge and the ssh:// protocol requires shell to operate. The solution we decided to go with was we provisioned a https:// protocal instead which we will recommend users to use instead.