Skip to content

feat: custom job definition for arbitrary jobs

Marco Wettstein requested to merge f/custom-jobs into main

not tested yet

@leu this might help us with !16 (merged), at least as some last resort to add arbitrary jobs.

The job definitions are slightly abstracted (they have the type CatladderJob). There are multiple reasons for that:

  • stage is a specific union type with only the stages we have
  • they contain some additional properties like name (obvious, as its not a hash), envMode (which controls whether to run the job once per env or once for all envs), needsStages (which is useful to declare dependency on a whole stage, thats a feature not yet available in gitlab) and similar.
  • we can hide props that we don't need or not recommend (looking at you, dependencies)
  • we may abstract it further to enable other ci-tools (github? azure devops?)
Edited by Marco Wettstein

Merge request reports