[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI

Tuesday, 30 January 2018

This is a multi-part message in MIME format...

------------=_1517312708-12381-241
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

     [
https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jir...
]

Daniel Belenky updated OVIRT-1867:
----------------------------------
    Component/s: STDCI DSL
                 Standard CI (Pipelines)

...
 Allow embedded secrets inside the source repo for CI
 ----------------------------------------------------

                 Key: OVIRT-1867
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867
             Project: oVirt - virtualization made easy
          Issue Type: By-EMAIL
          Components: Standard CI (Pipelines), STDCI DSL
            Reporter: Roman Mohr
            Assignee: infra

 In order to improve the self-service capabilities of standard-ci it is
 important for projects, that they can add their own secrets to projects (to
 reach external services, e.g. docker hub, ...).
 Travis has a very nice system which helps engineers there:
 https://docs.travis-ci.com/user/encryption-keys/
 Basically the CI system needs to generate a public/private key pair for
 every enabled git repo. The engineer simply fetches the public key via a
 well know URL and encrypts the secrets. Then the encrypted secret can be
 made part of the source repo. Before the tests are run the CI system
 decrypts the secrets. Than can play together pretty well with Jenkinsfiles
 too.
 Benefit:
  * Less manual intervention from CI team to add secrets to jobs
  * Strengthen the config-in-code thinking 

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100077)

------------=_1517312708-12381-241
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jir...
]</pre>
<h3>Daniel Belenky updated OVIRT-1867:</h3>
<pre>    Component/s: STDCI DSL
Standard CI (Pipelines)</pre>
<blockquote><h3>Allow embedded secrets inside the source repo for
CI</h3>
<pre>     Key: OVIRT-1867
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
         Components: Standard CI (Pipelines), STDCI DSL
Reporter: Roman Mohr
Assignee: infra</pre>
<p>In order to improve the self-service capabilities of standard-ci it is important
for projects, that they can add their own secrets to projects (to reach external services,
e.g. docker hub, &hellip;). Travis has a very nice system which helps engineers there:
<a
href="https://docs.travis-ci.com/user/encryption-keys/">http...
Basically the CI system needs to generate a public/private key pair for every enabled git
repo. The engineer simply fetches the public key via a well know URL and encrypts the
secrets. Then the encrypted secret can be made part of the source repo. Before the tests
are run the CI system decrypts the secrets. Than can play together pretty well with
Jenkinsfiles too. Benefit:</p>
<pre>* Less manual intervention from CI team to add secrets to jobs
* Strengthen the config-in-code thinking</pre></blockquote>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100077)</p>

------------=_1517312708-12381-241--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011