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

Improve the SCB CI pipeline to prevent flaky timeouts #224

Closed
rseedorff opened this issue Nov 25, 2020 · 0 comments · Fixed by #389
Closed

Improve the SCB CI pipeline to prevent flaky timeouts #224

rseedorff opened this issue Nov 25, 2020 · 0 comments · Fixed by #389
Labels
bug Bugs ci Changes to the continuous integration setup

Comments

@rseedorff
Copy link
Member

Is your feature request related to a problem? Please describe.

The secureCodeBox github pipeline fails from time to time due to some flaky timeouts during the end-to-end testphase. Due to the fact that the pipeline steps depend on external ressource there might be situations ending up in timeouts. This can be frustrating while developing new stuff.

It would be great to improve the pipeline to be more robust against flaky timeouts.

Describe the solution you'd like

Implement a retry function with exponential timeout growth to retry failed steps (especially the end-to-end tests) within the CI pipeline. This could be implemented as a wrapper / closure for this function:

async function getScan(name) {

The following JS Package maybe can help to implement this: https://www.npmjs.com/package/promise-retry

@rseedorff rseedorff added the bug Bugs label Nov 25, 2020
@rseedorff rseedorff added this to To do in secureCodeBox v2 via automation Nov 25, 2020
@rseedorff rseedorff added the ci Changes to the continuous integration setup label Mar 20, 2021
@fuhrmeistery fuhrmeistery moved this from To do to Done in secureCodeBox v2 Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bugs ci Changes to the continuous integration setup
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants