Project

General

Profile

Functionality #15589

document release engineering better

Added by Antoine Beaupré over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Target version:
Media players - 2015-June
Start date:
2014-10-07
Due date:
% Done:

100%

Estimated time:
1.00 h
RT ticket:
Points:
1

Description

#14652 clearly showed some problems with release engineering:

  1. some tags and commits are often done without being pushed into the central git repo
  2. some releases are built by jenkins instead of manually, which gives horrible release numbers
  3. it is unclear how to make an official (non-jenkins) release

we need to review those procedures and document them better.

in particular, it seems we are heading away from debian package to manage configurations. we are deploying less and less actual code, as packages already exist for git-annex and puppet. so this should rather document the dev/stage/prod workflows that we use in puppet.

History

#1 Updated by Antoine Beaupré over 5 years ago

  • Project changed from Media players to Isuma Documentation

#2 Updated by Antoine Beaupré over 5 years ago

  • Target version changed from 2014-October to 2014-November

#3 Updated by Antoine Beaupré over 5 years ago

  • Target version changed from 2014-November to 2015-January

#4 Updated by Antoine Beaupré about 5 years ago

  • Target version changed from 2015-January to 2015-March

#5 Updated by Antoine Beaupré about 5 years ago

  • Estimated time set to 1.00 h

#6 Updated by Antoine Beaupré almost 5 years ago

  • Target version changed from 2015-March to 2015-April

#7 Updated by Antoine Beaupré almost 5 years ago

  • Status changed from New to Postponed
  • Assignee changed from Antoine Beaupré to Gabriel Filion
  • Target version changed from 2015-April to 2015-May

it seems more and more that this will become irrelevant as we are ending up switching all code currently distributed through Debian packages as Puppet manifests instead.

we should, however, document the dev/staging/prod environments. i will throw that gabriel's way to see if there's anything to be done there.

#8 Updated by Antoine Beaupré almost 5 years ago

  • Description updated (diff)

#9 Updated by Antoine Beaupré almost 5 years ago

  • Target version changed from 2015-May to 2015-June

#10 Updated by Gabriel Filion almost 5 years ago

Antoine Beaupré a écrit :

we should, however, document the dev/staging/prod environments. i will throw that gabriel's way to see if there's anything to be done there.

with regards to puppet environments, there is currently nothing set up for such a workflow (e.g. everything is pushed to prod directly).

however, since puppet 3.x insisted on our using "directory environments", it should be easy to have more of them. the most complex part would be to make the hooks push different branches of the git repos to different environments and maybe find a way to make some machines stick to an alternate environment (if that's relevant..)

#11 Updated by Antoine Beaupré almost 5 years ago

  • Status changed from Postponed to Resolved

okay thanks. then this becomes only #17670, which will simply have to be documented properly.

#12 Updated by Antoine Beaupré almost 5 years ago

  • % Done changed from 0 to 100

#13 Updated by Cleve Higgins over 4 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF