Skip to content

Add release pipeline to CodeArtifact - #16

Closed
ebrard wants to merge 2 commits into
masterfrom
release-pipeline-setup
Closed

Add release pipeline to CodeArtifact#16
ebrard wants to merge 2 commits into
masterfrom
release-pipeline-setup

Conversation

@ebrard

@ebrard ebrard commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Publishes a SNAPSHOT version (<version>-SNAPSHOT) to CodeArtifact on every master merge
  • Publishes a proper release to CodeArtifact when a GitHub Release is created (version from tag)
  • Adds distributionManagement to pom.xml targeting private-store
  • Adds service-provisioning.yml for CI IAM role provisioning
  • Runs on self-hosted java-small runners

Prerequisites

Test plan

  • Verify CI passes on this PR (build job)
  • After merge, confirm snapshot is published to CodeArtifact
  • Create a test GitHub Release and confirm the artifact appears in CodeArtifact

🤖 Generated with Claude Code

…ease

Publishes to CodeArtifact private-store using the ci-datastores-config
IAM role. Snapshots are published automatically on every master merge,
proper releases are triggered by GitHub Release events using the tag as
the version.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ebrard
ebrard requested a review from a team as a code owner June 11, 2026 10:23
@service-provisioning

service-provisioning Bot commented Jun 11, 2026

Copy link
Copy Markdown

This pull request modifies one or more service config files. Below is a summary of changes for each resource. They will be applied once this pull request is merged.

📖 For additional details, see the documentation.

Service: parquet-json 🟢

Service Catalog 🟢

You are about to create a new service.

Please follow the naming conventions so that we know quickly what the service does and can avoid name clashes. Your service name fulfills the automated naming validation because it consists of between 3 - 32 alphanumeric or hyphen characters. Make sure to also these follow manually-checked the naming conventions:

  • Use words in the singular form (e.g. "question" instead of "questions")
  • Pick a name that describes what the service does (e.g., "authentication", "translation")

Examples:

Good names Bad names
question questions, question-service, question_service, ...
question-stats statistics, question_statistics
question-responder
review reviews, review-service, ...
review-stats
supplier-authentication authentication, auth_service, auth-service, gygauthentication, authenticate-supplier...
email-confirmation confirmation, email, email-sender, confirmation-service
availability-update update-availability, availabilityUpdate
my-name-is-way-too-big-i-wont-fit-in-thirtytwo-characters

Ci: IAM role 🟢

Role ci-parquet-json will be created

@gygrobot

Copy link
Copy Markdown

Closing stale PR. If this is a mistake, please re-open.

@gygrobot gygrobot closed this Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants