-
Notifications
You must be signed in to change notification settings - Fork 168
Added a crontab configuration option to scheduledScans #1722
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
Conversation
🦙 MegaLinter status:
|
Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
---|---|---|---|---|---|
golangci-lint | 9 | 1 | 2.47s | ||
✅ JSON | eslint-plugin-jsonc | 2 | 0 | 1.19s | |
prettier | 1 | 1 | 1.64s |
See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true
in mega-linter.yml to validate all sources, not only the diff
062d04d
to
241c10b
Compare
Current status: Cronjob configuration works |
241c10b
to
5ebb84a
Compare
038ebaa
to
e750f61
Compare
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
fakeClock can fake the passing of time Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
…ion is found and included the changes to FakeClock. It will be however later changed depending on the solution Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
… Cron Schedule tests This minimizes how much the test is slowed down (slower by between 0 and 50 seconds) Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
This is done to make sure that any edge cases do not fail the tests we still expect to be a maximum 60s Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
fast tests can be called by "make test-fast" and all tests will run when command "make test" is used. This is done to keep the CI workflow as usual Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
…of scheduledScan Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
dc44598
to
21fc70b
Compare
Description
closes #150
Current status: Cronjob configuration works
(tested manually), However no unit test have been implemented.Unit tests are implemented that use polling to test if the cronjob has started. This is slower by a maximum of 60 seconds and a minimum of 0 seconds. the slow test has the golang build tag "slow" and other/fast tests have the tag "fast".Calling
make test
runs all tests i.e "slow and fast"Calling
make test-fast
runs only the tests with "fast" tag.Checklist