fix git pathing in jenkins
Closed, ResolvedPublic

Description

Right now we manually tell jenkins to use ~/tooling/git instead of git from path. This has two side effects:

  1. Git in of itself cannot be run on slaves as they don't have a working tooling git
  2. The slaves not having a working tooling git prevents us from fully decentralizing source jobs

To improve this two things could be done. Either we don't hardcode git path anymore but change PATH accordingly, or we fully roll out the git semaphore on slaves. Could also do one after the other which probably is the best as the former change at least frees us up to selectively run git jobs on slaves (e.g. mergers don't need to run on master as we have no connection limit on packaging.neon's git)

Related Objects

sitter created this task.Jul 28 2016, 8:53 AM

This is about pangea-tooling/git-monitor/git which limits git connections to 16 connections as required by KDE git

jriddell moved this task from Discussing to Ready To Do on the Neon board.Sep 6 2016, 11:41 AM
sitter moved this task from Ready To Do to Review on the Neon board.Nov 9 2016, 12:47 PM
sitter triaged this task as Low priority.

I changed our jenkins slave settings to use the default git binary. Except for when the semaphore client is hardcoded (which should be nowhere) this fixes git usage on slaves. The overall connection limit problem remains though.

T4495 replaces the overall problem

sitter closed this task as Resolved.Nov 11 2016, 12:43 PM
sitter claimed this task.

No issues observed and we are partially running git on slaves now