Skip to content

Conversation

@tomasz-tylenda-sonarsource
Copy link
Contributor

@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource commented Nov 20, 2025

@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod bot changed the title Delete Cirrus CI config SONARJAVA-5875 Delete Cirrus CI config Nov 20, 2025
@hashicorp-vault-sonar-prod
Copy link

hashicorp-vault-sonar-prod bot commented Nov 20, 2025

SONARJAVA-5875

Copy link
Contributor

@dorian-burihabwa-sonarsource dorian-burihabwa-sonarsource left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are still a couple of mentions of cirrus-ci that can be removed from the code base:

  1. The <cIManagement> section in the root pom still mentions cirrus
  2. The badge at the top of the README still points to cirrus
  3. The ReleasabilityCheck workflow still has some conditions that depend on cirrus

@tomasz-tylenda-sonarsource
Copy link
Contributor Author

There are still a couple of mentions of cirrus-ci that can be removed from the code base:

  1. The <cIManagement> section in the root pom still mentions cirrus
  2. The badge at the top of the README still points to cirrus
  3. The ReleasabilityCheck workflow still has some conditions that depend on cirrus
  1. Fixed pom.xml
  2. Fixed the badge.
  3. Updated the actin according to https://github.com/SonarSource/gh-action_releasability?tab=readme-ov-file#usage-with-github-actions-pipelines

@sonarqube-next
Copy link

@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource merged commit 618dca2 into master Nov 27, 2025
15 checks passed
@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource deleted the tt/delete-cirrus branch November 27, 2025 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants