ICT ALMA Common Software

Space shortcuts

Page tree

Versions Compared

Old Version 2

changes.mady.by.user Tomas Staig

Saved on

compared with

New Version 3

changes.mady.by.user Tomas Staig

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The dates for each of these phases is coordinated by the Release Manager and the information is persisted in Release Planning confluence page.

Build

ACS gets build using a dedicated Jenkins build service and an on-demand docker infrastructure. Each release has 4 tasks configured:

  • ExtProd-<OS>-<RELEASE>: Builds the external products and prepares an artifact with the results. Triggers ACS-<OS>-<RELEASE>.
  • ACS-<OS>-<RELEASE>: Retrieves ExtProd-<OS>-<RELEASE> artifact and builds ACS, preparing an artifact as a result. Triggers ACS-test-<OS>-<RELEASE>.
  • ACS-test-<OS>-<RELEASE>: Retrieves ExtProd-<OS>-<RELEASE> and ACS-<OS>-<RELEASE> artifacts and executes the test modules on ACS.
  • Publish-COMMON-<RELEASE>: A parameter for either PreRelease or Release is chosen, which defines the destination directory in WebDav. Retrieves ExtProd-<OS>-<RELEASE> and ACS-<OS>-<RELEASE> artifacts and copies them to WebDav according to the given parameter.

Pre-Release

ACS Pre-releases are intermediate roll-outs of the COMMON software, which are used by other developers to anticipate changes and to prepare their environments for development of their upcoming releases. In principle, it would be possible to have 1 ACS pre-release at the end of the development phase, along with preparing all the "Pull Requests for Verification". Usually, at least one additional ACS pre-release is prepared before, so developers can anticipate their work and have configured their building and testing environments beforehand. There are situations that also trigger additional ACS pre-releases, like finding important bugs during verification or development time.

...