Skip to content

Conversation

@marc-jasper-sonarsource
Copy link

No description provided.

@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod bot changed the title Migrate the mac os qa and its tasks SCANPY-231 Migrate the mac os qa and its tasks Jan 8, 2026
@hashicorp-vault-sonar-prod
Copy link

hashicorp-vault-sonar-prod bot commented Jan 8, 2026

SCANPY-220

Copy link
Contributor

@Seppli11 Seppli11 left a comment

Choose a reason for hiding this comment

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

Overall, the job looks good.

There are a few things missing for the macos runners to work without a problem (see the documentation here).

Also, it would be really nice if on failure a slack notification is sent.

Last but not least, I didn't find any runs of this workflow. Macos can be a fickle thing, so it would make sense to test.

But, the workflow as it is, looks promising and should work (I think...)

jobs:
qa-macos:
name: "Test macOS Python ${{ matrix.python-version }}"
runs-on: github-macos-large
Copy link
Contributor

Choose a reason for hiding this comment

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

according to the documentation, the label used for the macos runenrs is macos-latest-xlarge

matrix:
python-version: ["3.9.18", "3.10.13", "3.11.7", "3.12.1", "3.13.2"]
steps:
- name: Checkout repository
Copy link
Contributor

Choose a reason for hiding this comment

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

The SonarSource/gh-action_setup-cloudflare-warp@v1 action is missing

env:
SONARQUBE_VERSION: 25.3.0.104237
steps:
- name: Checkout repository
Copy link
Contributor

Choose a reason for hiding this comment

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

same here, the SonarSource/gh-action_setup-cloudflare-warp@v1 action is missing

steps:
- name: Notify team about nightly failure
run: |
echo "macOS nightly build failed. Check the workflow run for details."
Copy link
Contributor

Choose a reason for hiding this comment

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

This should probably be outputted to a step summary.

Also, it would make sense if a slack message is sent in the #squad-python-notifs channel so we don't miss it

@Seppli11
Copy link
Contributor

Seppli11 commented Jan 9, 2026

SCANPY-231

Also, it seems the jira automation created a new ticket, instead of latching on to SONARPY-220

@marc-jasper-sonarsource marc-jasper-sonarsource changed the title SCANPY-231 Migrate the mac os qa and its tasks SCANPY-220 Migrate the mac os qa and its tasks Jan 9, 2026
@sonarqube-next
Copy link

sonarqube-next bot commented Jan 9, 2026

Quality Gate passed Quality Gate passed for 'Python Scanner'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

Copy link
Contributor

@Seppli11 Seppli11 left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for the fixes. I've left one comment about the slack notification.

echo "**Workflow Run:** ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}" >> $GITHUB_STEP_SUMMARY
- name: Send Slack notification
uses: SonarSource/[email protected]
Copy link
Contributor

Choose a reason for hiding this comment

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

Going to the action's repository, it says that this is only suppose to be used for "legacy Cirrus CI notifications based on GitHub check suite events". They recommend using rtCamp/action-slack-notify

(It might also make sense to fail one run, to test this code path as well)

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