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

Poll Interval Parameter #32

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

peterbevan-dg
Copy link

@peterbevan-dg peterbevan-dg commented Feb 27, 2023

Description

Added poll-interval-mins to the interface and pass that through to ScanTools if supplied

Note: I've trried to emulate the existing patterns where possible - made the poll-inverval to be in mins to be consistent with the rest of the public interface and then multiplied up in place (same as the timeout is). By no means saying this is the right thing to do, but it it at least consistent now.

Testing

Untested as of now - I presume you'll want to check this to your own satisfaction before merging.

@peterbevan-dg peterbevan-dg changed the title Poll Timeout option Poll Interval option Feb 27, 2023
@peterbevan-dg peterbevan-dg changed the title Poll Interval option Poll Interval Parameter Feb 27, 2023
@jgamble-r7 jgamble-r7 requested a review from a team March 13, 2023 11:50

# Optional:
# The maximum amount of time (in minutes) the scan is allowed to run before canceling and failing the job.
scan-timeout-mins: "15"

Choose a reason for hiding this comment

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

Is this a reasonable default for the use case? I'm not sure if the use case targets mainly cloud or on premise engines, but during busy periods, scans may queue for a time before execution

Copy link
Author

Choose a reason for hiding this comment

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

Probably not actually tbh - now I've used this in practice these scans are LONG.

So long in fact I'm starting to question if this tool is really appropriate to be used as a pipeline tool in this way.

Setting of scans on production etc seems sensible, but if one has to wait often an hour or more for a scan to complete - how useful is it as a bit of developer feedback really?

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