-
Georges Racinet authored
Release branches are the current `heptapod-0-16`, `heptapod-0-17` etc. They are essentially the result of merging of development branches (`heptapod` or `heptapod-stable`) with the latest upstream patch release. The rationale is that the extended RSpec scope is too heavy for regular development work, and even moreso in the near future, because we are precisely in the process of re-enabling more RSpec tests. For now, failures are allowed, so that it's non-blocking, but we should come up with a policy to prepare the release branches in advance. It's also possible to trigger the extended job by passing the `CI_HEPTAPOD_RSPEC_SCOPE` variable directly from the Web UI. Name differs from the environment variable that `heptapod_knapsack.sh` interprets because check occurs after the variable has been set with the `variable` directive (hence if it were the same, the job would always be triggered) We're also taking care that the regular job doesn't start when using the variable to trigger the extended job.
a8a3f5d7e397
Validating GitLab CI configuration…
Learn more