GitLab Extended

Overview

This node integrates with GitLab to manage pipelines among other resources. Specifically, the "Pipeline - Create" operation triggers a new pipeline run on a specified branch or tag within a GitLab project. This is useful for automating CI/CD workflows, such as starting builds or tests whenever code changes are pushed to a particular branch.

Practical examples:

• Automatically trigger a pipeline on the main branch after pushing new commits.
• Start a pipeline on a feature branch to validate changes before merging.
• Use in automation workflows to programmatically start pipelines based on external events.

Properties

Output

The node outputs JSON data representing the created pipeline object returned by the GitLab API. This typically includes details such as pipeline ID, status, ref, SHA, user who triggered it, and timestamps.

No binary data output is involved.

Dependencies

• Requires an API key credential for authenticating with GitLab.
• The node expects configuration of the GitLab project either by project ID or by owner and project name.
• Uses internal helper functions to make authenticated REST API calls to GitLab.

Troubleshooting

• Common issues:
  • Invalid or missing API credentials will cause authentication failures.
  • Incorrect project identification (wrong project ID or owner/name) will result in "not found" errors.
  • Specifying a non-existent branch/tag in the "Ref" property will cause pipeline creation to fail.
• Error messages:
  • Errors from GitLab API are propagated; for example, 404 if the project or ref does not exist.
  • Validation errors if required parameters like "Ref" are missing or invalid.
• Resolutions:
  • Verify API credentials and permissions.
  • Confirm project details and existence of the specified branch/tag.
  • Ensure all required input properties are correctly set.

Links and References

• GitLab Pipelines API Documentation
• GitLab CI/CD Concepts