Move from exotic pre-built image

Created on 25 April 2023, almost 2 years ago
Updated 18 March 2024, about 1 year ago

Problem/Motivation

Currently the image the bot runs on is a quite custom image that was used on the old infrastructure. Although this is good for speed, this does make the runs less flexible. We need to be able to run on multiple versions of Drupal at some point, and be able to optimize the base.

Steps to reproduce

Proposed resolution

We can go 2 ways here.

1. Fully run on a default image and prepare the enviroment in a init job. Archive that enviroment and usa those artifacts as the starting point for all the other jobs.

Pro's:
Fully transparant flow and steps.
Full control on how the basic enviroment is setup.
Easy to start branched for new version if we like.

Cons:
Probably slower
Will require rewriting of the analysis code so it uses new paths.

2. Keep the docker file, support multiple versions and push it somewhere so we can use it.

Pro's:

  1. Faster builds since we don't install Drupal.
  2. Less chance to get regressions based on changes in packages or core changes.
  3. Less work.

Cons:

  1. Extra complexity to make sure we have a proper image built.
  2. Harder to contribute to I recon
  3. Dependency on external image host

Personally I feel like moving the setup code to a seperate job and passing those artifacts it the way to go.

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Fixed

Component

Code

Created by

🇳🇱Netherlands bbrala Netherlands

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024