Project

General

Profile

Feature #3079

Feature #3076: migrate to new (2018-03) server "host2.osmocom.org"

migrate jenkins to new server

Added by laforge over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/19/2018
Due date:
% Done:

100%

Spec Reference:

Description

jenkins can also be rather CPU/IO intensive, so it makes sense to migrate it with high priority to a new server.

The question is what kind of external servers/services might depend on it being on a given IP address / hostname?

AFAIK, all slaves are only accessed via SSH, so that shouldn't be an issue.

But what about the gerrit / build verifcation integration?


Checklist

  • try docker container with jenkins on new machine
  • docker-compose.yml integration
  • migrate configuration
  • can it reach all build slaves?
  • what about gerrit integration?
  • change reverse proxy to point to new machine

History

#1 Updated by laforge over 1 year ago

  • Checklist item try docker container with jenkins on new machine set to Done
  • Checklist item docker-compose.yml integration set to Done

#2 Updated by laforge over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

currently rsync'ing existing data+config (from a script, so it can be repeated).

#3 Updated by laforge about 1 year ago

  • Checklist item migrate configuration set to Done
  • Checklist item can it reach all build slaves? set to Done
  • Checklist item change reverse proxy to point to new machine set to Done

#4 Updated by laforge about 1 year ago

  • % Done changed from 20 to 90

#5 Updated by laforge about 1 year ago

  • Checklist item what about gerrit integration? set to Done

#6 Updated by laforge about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)