Gitlab CI 脚本：排除分支

Question

I'm trying to improve the project building script, described in YML-file, the improvement itself seems quite trivial, but the idea of accidentally ruining the auto-builds scares me a bit.

Right now there are several branches, version tags and other stuff in the project.

A development branch, not built by the runners would be of use, because copying a huge project somehow between virtual machines to test the build on different platforms is not convenient at all. So, I want to exclude from builds some "prj-dev" branch.

And there we have:

stages:
 - build
 - linuxbuild
job:
 tags:
 - win2008build
 stage: build
 script:
  # something complex

job1:
 tags:
 - linux
 stage: linuxbuild
 script:
  # something else complex

I googled and found a solution like:

stages:
 - build
 - linuxbuild
job:
 tags:
 - win2008build 
 branches:
  except:
    - *dev-only

But it seems that our pipelines are quite different, the tags are not git tags, they are pipeline tags. So, I'm considering rather to use a config like:

stages:
 - build
 - linuxbuild
job:
 tags:
 - win2008build 
 except:
   branches:
    - *dev-only

...which would mean "build as usual, but not my branch". There are complications in trying it both ways, I'm pretty sure someone should know the recipe for sure.

So, if you please, -- how do I exclude my dev branch without changing the pipelines, config only? Is it possible at all?

Answer 1

All you need to do is use except in the gitlab-ci.yml file and add your branches directly below like this:

mybuild:
    stage: test
    image: somedockerimage
    script:
        - some script running
    except:
        - branch-name

This is working on my project without problems.

Answer 2

@blurryroots Kind of... In the case of commercial deployment, what you tend to do is branch off for specific features and merge back into master. The branch created from master can be called anything eg "Dev1-Metrics-Feature-Logger", this in turn means if you were to use "Only" tag to have the pipeline run only on the development branches you would need to change the script everytime a new branch is created, thus "except" would work better > Run testing on everything "EXCEPT" master, and then when you merge into master the other jobs designed for master will kick in.