Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

71%

+3 −0

Q&A How to disable jobs in GitLab CI after they are successfully executed

I'm working with GitLab CI. The pipelines I'm designing contain several jobs that, once executed successfully, there shouldn't be any reason to retry/rerun them. This is an example: default: # ...

1 answer · posted 6d ago by ɯıpɐʌ‭ · edited 5h ago by ɯıpɐʌ‭

Question gitlab-ci

#2: Post edited by

ɯıpɐʌ‭ · 2025-02-18T21:02:18Z (about 5 hours ago)
Clarify guidance for preventing the re-run of successful jobs in a given pipeline

Copy Link

Raw

Markdown

I'm working with GitLab CI. The pipelines I'm designing contain several jobs that, once executed successfully, there shouldn't be any reason to retry/rerun them. This is an example:
```yaml
default:
# Cache set up
image: docker.io/library/eclipse-temurin:21-jdk-alpine
stages:
- verification
- testing
- assembly
- deployment
# Global environment variables
assess-code-quality:
...
stage: verification
build-release:
...
stage: assembly
deploy-dev:
... # manual job
stage: deployment
deploy-test:
needs: deploy-dev
... # manual job
stage: deployment
deploy-prod:
needs: deploy-test
... # manual job
stage: deployment
test-release:
...
stage: testing
verify-source-code-formatting:
...
stage: verification
```
I've been searching through the [CI/CD YAML syntax reference](https://docs.gitlab.com/ee/ci/yaml/), but I haven't found anything to accomplish this across the board.
Any help or examples would be greatly appreciated!

I'm working with GitLab CI. The pipelines I'm designing contain several jobs that, once executed successfully, there shouldn't be any reason to retry/rerun them. This is an example:
```yaml
default:
# Cache set up
image: docker.io/library/eclipse-temurin:21-jdk-alpine
stages:
- verification
- testing
- assembly
- deployment
# Global environment variables
assess-code-quality:
...
stage: verification
build-release:
...
stage: assembly
deploy-dev:
... # manual job
stage: deployment
deploy-test:
needs: deploy-dev
... # manual job
stage: deployment
deploy-prod:
needs: deploy-test
... # manual job
stage: deployment
test-release:
...
stage: testing
verify-source-code-formatting:
...
stage: verification
```
I've been searching through the [CI/CD YAML syntax reference](https://docs.gitlab.com/ee/ci/yaml/), but I haven't found anything to accomplish this across the board.
To clarify, I want to make sure that jobs like `assess-code-quality`, `build-release`, and others do not allow for reruns if they complete successfully **within** a given pipeline, **not across** the pipelines.
Any help or examples would be greatly appreciated!

#1: Initial revision by

ɯıpɐʌ‭ · 2025-02-12T20:40:18Z (6 days ago)

Copy Link

Raw

Markdown

How to disable jobs in GitLab CI after they are successfully executed

I'm working with GitLab CI. The pipelines I'm designing contain several jobs that, once executed successfully, there shouldn't be any reason to retry/rerun them. This is an example:

```yaml
default:
  # Cache set up
  image: docker.io/library/eclipse-temurin:21-jdk-alpine

stages:
  - verification
  - testing
  - assembly
  - deployment

# Global environment variables

assess-code-quality:
  ...
  stage: verification

build-release:
  ...
  stage: assembly

deploy-dev:
  ... # manual job
  stage: deployment

deploy-test:
  needs: deploy-dev
  ... # manual job
  stage: deployment

deploy-prod:
  needs: deploy-test
  ... # manual job
  stage: deployment

test-release:
  ...
  stage: testing

verify-source-code-formatting:
  ...
  stage: verification
```

I've been searching through the [CI/CD YAML syntax reference](https://docs.gitlab.com/ee/ci/yaml/), but I haven't found anything to accomplish this across the board.

Any help or examples would be greatly appreciated!

gitlab-ci

Communities

Post History