2 pipelines for 1 merge request
Without workflow
, Heptapod triggers 2 pipelines, 1 that does not seem to detect the changed files and another with the merge request content as modified files.
Here is an example: tryton/tryton!152 (merged)
I cancelled the first one because it runs all the jobs which is resource consuming.
I tried to remove the workflow as it does not trigger a pipeline when:
- push directly to the protected branches
- when publish changeset from command line
The problem is that it is not clear how to use the CI variables in the Heptapod context because the documentation is based on Git design with fork.
But basically we could expect from a usage without workflow
, Heptapod will trigger only 1 pipeline for a merge request and only another pipeline when the merge request is published.
It seems that workflow
like this:
workflow:
- if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
when: never
- if: $CI_COMMIT_BRANCH =~ /^branch\/.*/
does not work when pushing directly or make changeset public from command line.