Project

General

Profile

Bug #8509

Bug #11869: CI: use locally hosted Git repositories on Lizard

Use puppet-git's tails Git repo in reprepro config generation script

Added by bertagaz almost 5 years ago. Updated 4 months ago.

Status:
Confirmed
Priority:
Low
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
01/01/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
No
Affected tool:

Description

Reprepro scripts that need to fetch the main Tails git repo must use the one on puppet-git so that network troubles are handled at the git level and we don't get annoyed by tons of emails when cronjobs fail.

This means passing another $git_remote parameter to the tails::reprepro::custom class, managing a SSH key pair with Puppet, and configuring Gitolite to give read-only access to that key.

History

#1 Updated by bertagaz almost 5 years ago

  • Starter changed from No to Yes

Setting `easy` to `yes` because it doesn't require any access to be able to patch the code.

#2 Updated by intrigeri almost 5 years ago

This means changing $git_remote in the tails::reprepro class.

No, this means passing a different value for the $git_remote parameter in our manifests. That's what class parameters are for :)

#3 Updated by intrigeri almost 5 years ago

  • Starter changed from Yes to No

bertagaz wrote:

Setting `easy` to `yes` because it doesn't require any access to be able to patch the code.

Well, no: the code is already generic enough, what needs to be done will be in our manifests (and gitolite config).

#4 Updated by bertagaz about 3 years ago

  • Parent task set to #11869

#5 Updated by intrigeri about 3 years ago

  • Subject changed from Use puppet-git tails repo in reprepro config generation script to Use puppet-git's tails Git repo in reprepro config generation script

#6 Updated by intrigeri 4 months ago

  • Description updated (diff)

Also available in: Atom PDF