Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • heptapod-tests heptapod-tests
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapodheptapod
  • heptapod-testsheptapod-tests
  • Merge requests
  • !68

WIP prebootstrapped CI images

  • Review changes

  • Download
  • Patches
  • Plain diff
Open Georges Racinet requested to merge topic/default/prebuilt-images into branch/default Nov 30, 2020
  • Overview 0
  • Commits 5
  • Pipelines 27
  • Changes 7

Currently, all our jobs running the functional tests in the Heptapod images go through the data initialization sequence of an Heptapod instance: creation of service configurations, database schema etc. This takes about 5 minutes

Our docker-inside jobs add the installation of chromium-driver on top of that, so that heptapod-tests can run inside the image. This is necessary for the backups tests, for instance.

In this MR, we create two new images, built with Kaniko, in which all of this is already done: bootstrapped and bootstrapped-chromium. On freshly produced images (by the omnibus-heptapod pipeline), this won't change the latency. But it will save at least 25 minutes of CI time for other jobs to run, especially when our container image caching plan is in service.

Of course, if the base image has not changed, it is expected to save 30 minutes of total CI time and 5 minutes of latency.

We can perhaps in a follow up also reduce the extra startup waiting time (currently 3 minutes).

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: topic/default/prebuilt-images