AWS Pipeline Tools

A collection of AWS CDK constructs and custom actions that extend AWS CodePipeline capabilities, primarily focused on GitLab integration.

The library is still in early development and will change quite frequently. So be aware of bugs.

• GitLab Source Action for AWS CodePipeline
• Multiple trigger strategies:
  • Webhook-based triggering for automatic pipeline execution
  • Manual triggering for controlled deployments
• Secure OAuth token handling via AWS Secrets Manager
• Configurable branch selection
• Support for both GitLab Cloud and self-hosted instances

npm install aws-pipeline-tools
# or
pnpm add aws-pipeline-tools
# or
yarn add aws-pipeline-tools

import { GitLabSourceAction, GitlabTrigger } from 'cdk-gitlab-codepipeline';

// Create a GitLab source action with webhook trigger
new GitLabSourceAction(this, GitlabTrigger.WEBHOOK, {
	actionName: 'Source',
	output: sourceOutput,
	host: 'gitlab.com',
	projectPath: '/my-group/my-project',
	projectId: '12345', // Required for webhook trigger
	branch: 'main',
	oauthToken: secretsManager.Secret.fromSecretNameV2(this, 'GitLabToken', 'gitlab-token'),
});

// Create a GitLab source action without webhook (manual trigger)
new GitLabSourceAction(this, GitlabTrigger.NONE, {
	actionName: 'Source',
	output: sourceOutput,
	host: 'gitlab.com',
	projectPath: '/my-group/my-project',
	branch: 'main',
	oauthToken: secretsManager.Secret.fromSecretNameV2(this, 'GitLabToken', 'gitlab-token'),
});

The GitLab OAuth token needs the following permissions:

• Repository read access for cloning the code
• Webhook management (if using webhook trigger)

The integration works by:

1. Creating a custom source action in AWS CodePipeline
2. Using AWS CodeBuild to clone the GitLab repository
3. Implementing Lambda functions to handle webhook events and job processing
4. Managing pipeline artifacts in S3
5. Using EventBridge for orchestration

Main class for creating a GitLab source action in AWS CodePipeline.

# Install dependencies
pnpm install

# Run tests
pnpm test

# Build
pnpm build

# Format code
pnpm format

This project uses release-please for version management and publishing. The release process is automated through GitHub Actions.

1. Make changes and commit them using Conventional Commits format:

   • feat: add new feature (bumps minor version)
   • fix: resolve bug (bumps patch version)
   • feat!: or fix!: or refactor!: etc. (bumps major version)
   • chore: update dependencies (no version bump)

2. Push changes to the main branch. Release-please will:

   • Create/update a release PR
   • Update CHANGELOG.md
   • Bump version in package.json
   • Create GitHub releases

3. When the release PR is merged:

   • A new GitHub Release is created
   • The package is automatically published to npm

MIT License

hassma