Gitlab Runner Failure -
This job depends on upstream jobs that need to succeed in order for this job to be triggered.
Pipeline do not start and get stuck
You have an issue in your Pipeline logic. Unless you share your Pipeline definitions it’s hard to help.
1 Like
Hi
I am using the default gitlab-ci.yml file
stages: # List of stages for jobs, and their order of execution
- build
- test
- deploy
build-job: # This job runs in the build stage, which runs first.
stage: build
script:
- echo “Compiling the code…”
- echo “Compile complete.”
unit-test-job: # This job runs in the test stage.
stage: test # It only starts when the job in the build stage completes successfully.
script:
- echo “Running unit tests… This will take about 60 seconds.”
- sleep 60
- echo “Code coverage is 90%”
lint-test-job: # This job also runs in the test stage.
stage: test # It can run at the same time as unit-test-job (in parallel).
script:
- echo “Linting code… This will take about 10 seconds.”
- sleep 10
- echo “No lint issues found.”
deploy-job: # This job runs in the deploy stage.
stage: deploy # It only runs when both jobs in the test stage complete successfully.
environment: production
script:
- echo “Deploying application…”
- echo “Application successfully deployed.”
I am using on premise Gitlab EE version - [16.1.2-ee] , which was upgraded recently . All the pipelines were running successfully . All of a sudden everything stopped working .
I have tried registering new Gitlab runners . All the runners shows online but the jobs are stuck when runs .