I’m working on some CI templates. Those templates live in one project (on a branch that hasn’t been merged yet) and the project I’m testing them with (call it
app) is separate. So
app has a
.gitlab-ci.yml file that looks a bit like
include: - project: .../gitlab-ci-templates file: template1.yml - project: .../gitlab-ci-templates file: template2.yml ref: duvall/test job: - extends: .template2
.template2 template, living in
gitlab-ci-templates (on the branch
.template2: image: ... ...
My template doesn’t work yet, so my
app jobs are failing. I want to just hit the retry button after I’ve updated the template and pushed to
gitlab-ci-templates, but the log of the new job suggests that the changes haven’t been picked up yet. If I make an arbitrary change to
app and push it, the corresponding pipeline run definitely does pick up the change. So does the job retry use a cached copy of the included files? Is there something else I should be doing instead?
This is on gitlab.com.