Wanted to NOT trigger CI pipeline when a README.md is committed, so added to .gitlab-ci.yml for each job:
except: changes: - README.md
which worked as expected. But if try to trigger the pipeline manually with the “Run Pipeline” button, I get the following error:
The form contains the following error: No stages / jobs for this pipeline.
Remove the except setting and pipeline can be manually triggered as expected.
Newbie here, is this expected behavior? Definitely no show-stopper but would be nice to have both features.
cache: paths: - node_modules/ stages: - local_build - image_build build: image: node:latest stage: local_build script: - npm config set https-proxy $NPM_HTTPS_PROXY - npm install - npm run build:prod artifacts: paths: - build except: changes: - README.md docker: image: docker:latest stage: image_build script: - docker info - docker login -u $DOCKER_REG_USER -p $DOCKER_REG_PASSWD $DOCKER_REG_HOST - docker build --no-cache -t $DOCKER_REG_HOST/image . - docker push $DOCKER_REG_HOST/image except: changes: - README.md