From e776390c7c6fb5241fc041ef720fbe88e6724e61 Mon Sep 17 00:00:00 2001 From: Toby Lorne Date: Tue, 12 Nov 2019 11:47:47 +0000 Subject: [PATCH] Add skeleton continuous integration (CI) proposal Signed-off-by: Toby Lorne Co-authored-by: Stephen Co-authored-by: Toby --- source/continuous-integration.html.md.erb | 7 +++ .../continuous-integration/index.md | 1 + .../continuous-integration/proposal.md | 44 +++++++++++++++++++ 3 files changed, 52 insertions(+) create mode 100755 source/continuous-integration.html.md.erb create mode 100755 source/documentation/continuous-integration/index.md create mode 100755 source/documentation/continuous-integration/proposal.md diff --git a/source/continuous-integration.html.md.erb b/source/continuous-integration.html.md.erb new file mode 100755 index 0000000..4e6edd2 --- /dev/null +++ b/source/continuous-integration.html.md.erb @@ -0,0 +1,7 @@ +--- +title: Continuous integration +weight: 3 +--- + +<%= partial 'documentation/continuous-integration/index' %> +<%= partial 'documentation/continuous-integration/proposal' %> diff --git a/source/documentation/continuous-integration/index.md b/source/documentation/continuous-integration/index.md new file mode 100755 index 0000000..257fa0f --- /dev/null +++ b/source/documentation/continuous-integration/index.md @@ -0,0 +1 @@ +# Continuous Integration diff --git a/source/documentation/continuous-integration/proposal.md b/source/documentation/continuous-integration/proposal.md new file mode 100755 index 0000000..17ac445 --- /dev/null +++ b/source/documentation/continuous-integration/proposal.md @@ -0,0 +1,44 @@ +## Summary + +We have a number of different tools in use across GDS for CI/CD purposes: +- Jenkins +- Concourse +- Travis +- Github Actions +- CircleCI + +and possibly others. + +We would ideally be moving towards a smaller set of approved tools which we +document in the GDS Way, where the current advice (2019/11/12) is: + +> ...set up any tests to run in a public continuous integration environment +> using tools such as Travis CI, CircleCI or Jenkins + +The benefits of reduced number of tools is: + +- reduced toil managing user accounts and authorisation for each tool +- more consistent tooling and configuration +- consolidated billing + +## Proposal + +@tlwr @stephenharker to write comments from GitHub thread into proposal / outcome. +## Problem + +Given the recent move towards using Concourse and the adoption in some places +of the new Github Actions, we are seeing a proliferation of tools rather than a +consolidation. + +In Techops we want to be able to assess and procure a small set +of tools that have been approved by IA and have a commercial agreement in place +for the use across the whole of GDS. + +Github Actions, in particular, we will lose access to shortly without an +Enterprise agreement in place with Github which will incur a significant +increase in costs. This is currently being assessed but it is by no means +definite that we will be able to use Github Actions going forward. + +## Proposal + +@tlwr @stephenharker to write comments from GitHub thread into proposal / outcome.