GitLab Manual Jobs Tutorial: Optional Actions and Blocking Gates
A manual job waits for an authorized person to initiate its execution. That choice is separate from whether the pipeline can finish without the job. This tutorial explains optional and blocking manual jobs, including the effect of allow_failure and rule placement. You will examine how a human gate fits deployment work and how supplied inputs affect the action. The aim is to distinguish deliberate waiting from a missing runner or a failed command.
Here's a popular GitLab Manual Jobs video — watch it, then summarize it with one click. Or paste any other YouTube link below.
— or paste your own YouTube link —
Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.
Why Use GitLab Manual Jobs Tutorial: Optional Actions and Blocking Gates
- Identify a manual action in pipeline state
- Distinguish optional execution from a blocking gate
- Interpret allow_failure alongside manual configuration
- Review inputs before initiating a sensitive task
- Relate execution permission to deployment context
Frequently Asked Questions
Does every manual job block a pipeline?
Manual jobs can be optional or blocking depending on their configuration. The interaction between when: manual, rules and allow_failure matters. Inspect those settings rather than inferring pipeline behavior from the manual label alone.
Why use a manual deployment job?
A manual job allows a person to choose when a prepared action runs. It can provide a deliberate release gate, but its effectiveness also depends on permissions, deployment configuration and the evidence available before initiation.
Is a waiting manual job the same as a pending job?
A manual job awaits human initiation, whereas a pending job awaits suitable execution capacity after scheduling. Those states require different responses. Starting a manual action does not resolve an unrelated runner-availability problem.
What should be checked before running the action?
Review the source revision, intended environment and supplied parameters. Confirm that prerequisite validation belongs to the same change. These checks connect the requested manual action to the particular deployment or operation it will perform.
Can manually supplied values expose sensitive information?
Values entered for manual execution have visibility and handling rules that differ from protected secret storage. Understand that scope before providing sensitive inputs. Use the project's appropriate secret-management mechanism for credentials required by the job.