Skip to main content
Streamline your GitLab CI/CD pipelines by extracting complex commands into standalone shell scripts. This approach improves readability, maintainability, and version control for your build logic.

​
1. Example Inline Job

Below is a simple .gitlab-ci.yml that installs the cowsay gem and runs commands directly:
While this works, embedding multiple commands can quickly clutter your CI file.
Extract repetitive or lengthy command sequences into versioned scripts to keep your pipeline definitions clean and reusable.

​
2. Create a Dedicated Shell Script

  1. Open the GitLab Web IDE.
  2. Add a file named ascii-script.sh at your repository root:
The image shows the GitLab Web IDE interface with a welcome screen and options for connecting to a remote development environment. The left sidebar displays a file explorer with a project structure.
Save and commit ascii-script.sh so it’s tracked by Git.

​
3. Update Your CI Configuration

Modify .gitlab-ci.yml to invoke the script instead of inline commands:
Commit and push your changes. The pipeline will now call the external script.

​
4. Monitor Pipeline Status

Navigate to CI/CD > Pipelines in the GitLab UI to view your job status in real time.
The image shows a GitLab interface displaying a list of CI/CD pipelines with their statuses, such as "Running," "Passed," "Failed," and "Canceled." The sidebar includes navigation options like "Issues," "Merge requests," and "Pipelines."
You should see the ascii_job running under the “Generate ASCII Artwork” pipeline.

​
5. Handling Permission Errors

If your script isn’t executable, GitLab will report a permission denied error:
The image shows a GitLab pipeline interface with a failed job named "ascii_job" under the "Generate ASCII Artwork" project. The pipeline was created for a specific commit and has options to retry or delete.
Always ensure your shell scripts have execute permissions. Without chmod +x, GitLab runners cannot run them.

​
6. Grant Execute Permissions

Add a chmod step in before_script to make the script executable:
Commit and push. The next pipeline run will apply the new permissions automatically.

​
7. Confirm Successful Execution

Once fixed, your job logs should show:
With this pattern, your .gitlab-ci.yml stays concise, and complex logic lives in maintainable, version-controlled scripts.

Watch Video