Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for specifying container registry #95

Closed

Conversation

philip-mannes-cardano
Copy link

@philip-mannes-cardano philip-mannes-cardano commented Nov 4, 2024

Please help, we're facing rate throttling by Dockerhub due to this action. Please allow us to specify the registry.

Dockerfile Outdated
@@ -1,4 +1,5 @@
FROM sonarsource/sonar-scanner-cli:11.1
ARG CONTAINER_REGISTRY
FROM ${CONTAINER_REGISTRY}/sonarsource/sonar-scanner-cli:11.1

Choose a reason for hiding this comment

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

Maybe letting the leading / in the CONTAINER_REGISTRY arg and adding a default value as ""

Choose a reason for hiding this comment

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

Hi @marciorgb, thanks for reaching out. I've been running some tests.. the above won't work.

The problem is that using: docker changes the flow of github actions in a way that images are pulled during the setup step. There's no way to login before the setup step. This will always result in throttling by Dockerhub for users at scale.

The way to address this is by using: composite and by building the container at runtime. Am I missing something? See my update.

Copy link
Author

@philip-mannes-cardano philip-mannes-cardano Nov 5, 2024

Choose a reason for hiding this comment

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

New scans do not pass using this rewrite, the scanned branch is master, though the action is being called from a non-default branch. Please help, Dockerhub throttling caused by this action is blocking all our CICD processes.

image

@henryju
Copy link
Member

henryju commented Nov 6, 2024

Hi,

Thanks for your contribution. We are aware of the rate limit issue and are willing to replace this action with a composite action without relying on Docker.
See for example https://github.com/SonarSource/sonarqube-scan-action/tree/jh/experiment_composite_action

This is likely to come before the end of the year.

@antonioaversa
Copy link
Contributor

antonioaversa commented Dec 2, 2024

Hi @philip-mannes-cardano,
We have just released [email protected]. v4.0.0 removes Docker, moving to a composite action, while v4.1.0 brings several improvements to the action, which is now the single entry-point for SonarQube Server and Cloud (formerly SonarCloud).

You can read about these new releases

[email protected] should be a drop-in replacement. Please, give it a try and let us know.

@pierre-guillot-gh
Copy link
Contributor

Closing the PR as we won't merge this contribution, as we migrated to composite action. Feel free to continue the conversation here.

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.

5 participants