Make CI information available to scripts in standard CI

Description

Right now scripts running in standard-CI have no information about the environment they are running in. This is by design, because the scripts are supposed to behave the same if they are running locally or on a Jenkins slave.

But there are cases where letting the script know it is running in CI is useful. For example - to make it use the package mirrors in the CI system instead of getting packages over the internet.

It seems that essentially all the information that is passed to 'mock_runner.sh' on the command line should be made available to the automation script as environment variables. Additionally, information from Gerrit would probably also be useful.

Activity

Show:
Barak Korren
May 21, 2017, 1:39 PM

The feature described in required the functionality described in this ticket.

More specifically it defines a requirement for the following information provided as environment variables:

  1. STD_CI_STAGE: Will contain the name of the Standard-CI stage, e.g. “{{build-artifacts}}”.

  2. STD_CI_DISTRO: Will contain the distribution version identifier (e.g “el7” or “fc25”) of the Standard-CI runtime.

  3. STD_CI_YUMREPOS: Will point to an existing “{{*.yumrepos}}” file that most closely matches the current running stage and distribution

Fixed

Assignee

Daniel Belenky

Reporter

Barak Korren

Blocked By

Code

Components

Priority

Medium
Configure