-
Notifications
You must be signed in to change notification settings - Fork 73
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
feat: add a polling timeout #50
feat: add a polling timeout #50
Conversation
The property timeout-minutes in a GitHub step is not supported in composed actions. So the workaround to stop the waiting for finishing the sonar scan is not working in such cases. To fix this issue, a polling timeout variable was introduced, which stops the waiting, if the timout is reached.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR; I have a small nitpick regarding the variable description. The rest looks good
Hey @MueChr. Thank you for your contribution. Did you have a chance to look at @jacek-poreda-sonarsource's request? :) |
Hi @davividal, thank you for the reminder. I applied the change. So from my side it is ready for the merge :) |
@MueChr It seems like unit tests have failed; could you update it? Apart from that PR looks good 👍 |
…eached The code never sets a quality-gate-status, if the polling timeout is reached. Interestingly, it did not display an error when the tests were run locally.
@MueChr Thanks a lot for your contribution! |
### Proposed Changes * Fix the action to the current commit https://github.com/sonarsource/sonarqube-quality-gate-action/tree/dc2f7b0dd95544cd550de3028f89193576e958b9 for reproducability instead of auto updting any change to master branch. Includes the timeout change in this PR SonarSource/sonarqube-quality-gate-action#50 * * set the new pollingTimeoutSec to 600 (e.g. 10 minutes) To test, check the logs of the build run in the sonarqube step and it should show the timeout passed in as "600" instead of "300" ### Checklist - [ ] Tests - [ ] Translations - [ ] Security Implications Contemplated (add notes if applicable) ### Additional Info This PR resolves #29886 (Fix SonarQube timeout property). ### Screenshots Original | Updated :-------------------------:|:-------------------------: ** original screenshot ** | ** updated screenshot **
### Proposed Changes * Fix the action to the current commit https://github.com/sonarsource/sonarqube-quality-gate-action/tree/dc2f7b0dd95544cd550de3028f89193576e958b9 for reproducability instead of auto updting any change to master branch. Includes the timeout change in this PR SonarSource/sonarqube-quality-gate-action#50 * * set the new pollingTimeoutSec to 600 (e.g. 10 minutes) To test, check the logs of the build run in the sonarqube step and it should show the timeout passed in as "600" instead of "300" ### Checklist - [ ] Tests - [ ] Translations - [ ] Security Implications Contemplated (add notes if applicable) ### Additional Info This PR resolves #29886 (Fix SonarQube timeout property). ### Screenshots Original | Updated :-------------------------:|:-------------------------: ** original screenshot ** | ** updated screenshot **
The property timeout-minutes in a GitHub step is not supported in composed actions. So the workaround to stop the waiting for finishing the sonar scan is not working in such cases. To fix this issue, a polling timeout variable was introduced, which stops the waiting, if the timeout is reached.