Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "LTS/HowTos"

< LTS
(Setting up Git)
(Setting up a Hudson Maven project)
Line 9: Line 9:
  
 
== Setting up a Hudson Maven project ==
 
== Setting up a Hudson Maven project ==
 +
 +
For the steps below. Navigate to your Job you wish to configure and choose '''Configure'''
  
 
=== Setting up Git ===
 
=== Setting up Git ===

Revision as of 11:43, 23 November 2012

Howtos

Using TortoiseGit to "git submodule update"

  1. Navigate to your git repository which you cloned (eg. eclipse.platform.releng.aggregator)
  2. Right click > TortoiseGit > Submodule Update
  3. Select to Initialize Submodules
  4. Click OK

Setting up a Hudson Maven project

For the steps below. Navigate to your Job you wish to configure and choose Configure

Setting up Git

  1. Enter URL of git repo (eg. /gitroot/lts-central/platform/eclipse.platform.releng.aggregator.git)
  2. Set the build branch (eg. R4_2_maintenance)
  3. Set the Config user.name and user.email values
  4. Save

Setting up Platform Build

Build step 1, invoke maven for eclipse-parent

  1. click Advanced
  2. Set goals: clean install
  3. Set pom-file: eclipse-parent/pom.xml
  4. Set private repository enabled
  5. Save

Build step 2, invoke maven for maven-cbi-plugin

  1. click Advanced
  2. Set goals: clean install
  3. Set pom-file: maven-cbi-plugin/pom.xml
  4. Set private repository enabled
  5. Save

Build step 3, invoke maven for Platform build

  1. click Advanced
  2. Set goals: clean install
  3. Set properties: maven.test.skip=true
  4. Set pom-file: pom.xml
  5. Set private repository enabled
  6. Set profiles: no-bree-libs
  7. Save

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.

Back to the top