Project

General

Profile

Bug #11808

Upgrade Redmine on labs.r.n

Added by intrigeri almost 2 years ago. Updated 10 months ago.

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Infrastructure
Target version:
Start date:
09/19/2016
Due date:
% Done:

100%

QA Check:
Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:

Description

  • Let's upgrade the system to Stretch first, and immediately try to go back to the redmine Debian package (instead of maintaining an installation from the upstream tarball with tons of vendorized Gems). Figuring out who's responsible to run SQL migration code might be tricky: dpkg will believe we're upgrading from 3.0~20140825-8~deb8u4, while we're actually upgrading from a newer version. But db/schema.rb contains the version of our DB and is likely used for ActiveRecord migrations, so let's inject it in the relevant place before upgrading the system. Worst case, let's hope that the ActiveRecord migrations are idempotent.
  • Locally patched files (let's Puppet'ize any remaining change as part of the upgrade):
    • app/models/attachment.rb: let's try without patching and see if it's still needed
    • bin/rails: can be dropped
    • config/application.rb and lib/: the patch configures paths depending on $X_DEBIAN_SITEID; should come for free with the Debian package, presumably (actually IIRC that's where the patch comes from originally)
    • config/configuration.yml has potentially relevant custom settings
    • config/initializers/secret_token.rb will probably be re-generated by the Debian packaging
    • public/dispatch.fcgi: do we need that file at all?
    • public/maintenance.html, public/maintenance.jpg: vaguely useful
    • public/themes/Modula Mojito/: our custom theme
  • We need to upgrade the redmine_git_hosting plugin.
  • While we're at it, let's also upgrade the redmine_bootstrap_kit plugin.
  • ensure email notifications still work
  • ensure Git → Redmine integration still works
  • ensure incoming email gateway still works
  • ensure Git hooks (push to mirrors? anything else?) still work

Related issues

Blocks Tails - Feature #13284: Core work 2017Q2→2019Q1: Sysadmin (Adapt our infrastructure) Confirmed 06/30/2017

History

#2 Updated by intrigeri almost 2 years ago

  • Target version set to 284

(Just so that it pops up on my radar "soonish".)

#3 Updated by anonym over 1 year ago

  • Target version changed from 284 to Tails 2.10

#4 Updated by intrigeri over 1 year ago

  • Target version changed from Tails 2.10 to Tails_2.12

(I had to take over a bunch of more urgent sysadmin tasks so I'll postpone this one.)

#5 Updated by intrigeri over 1 year ago

  • Target version changed from Tails_2.12 to Tails_3.1

#6 Updated by intrigeri about 1 year ago

  • Target version changed from Tails_3.1 to Tails_3.2

Maybe to be done before starting the Puppet 4 work.

#7 Updated by intrigeri about 1 year ago

  • Blocks Feature #13284: Core work 2017Q2→2019Q1: Sysadmin (Adapt our infrastructure) added

#8 Updated by intrigeri 12 months ago

#9 Updated by intrigeri 12 months ago

Tentatively scheduled a sprint to do that: September 4-5.

#10 Updated by intrigeri 11 months ago

  • Description updated (diff)

#11 Updated by intrigeri 11 months ago

  • Description updated (diff)

#12 Updated by intrigeri 11 months ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

#13 Updated by intrigeri 11 months ago

  • Description updated (diff)

#14 Updated by intrigeri 11 months ago

Test!

#15 Updated by intrigeri 11 months ago

  • Description updated (diff)

#16 Updated by intrigeri 11 months ago

  • Description updated (diff)
  • % Done changed from 10 to 20

#17 Updated by intrigeri 11 months ago

  • Description updated (diff)
  • % Done changed from 20 to 50
  • QA Check set to Ready for QA

Everything seems to work. Will ask our community to report any regression.

#18 Updated by intrigeri 11 months ago

intrigeri wrote:

Will ask our community to report any regression.

Done. I'll close this ticket as resolved if no serious regression is identified by the end of the week.

#19 Updated by intrigeri 11 months ago

#20 Updated by intrigeri 11 months ago

  • QA Check changed from Ready for QA to Dev Needed

Modifying ticket metadata over email doesn't work anymore, e.g. #11831#note-126. Commenting does work though.

#21 Updated by intrigeri 11 months ago

  • Priority changed from Normal to Elevated
  • % Done changed from 50 to 60

Let's try this.

#22 Updated by intrigeri 11 months ago

intrigeri wrote:

Modifying ticket metadata over email doesn't work anymore,

Fixed!

#23 Updated by intrigeri 11 months ago

  • QA Check changed from Dev Needed to Ready for QA

#24 Updated by intrigeri 10 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 60 to 100
  • QA Check deleted (Ready for QA)

Nobody complained about regressions while I've seen a few people use Redmine intensively.

Also available in: Atom PDF