-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Migrate job to build test docker images to beats repo #18785
Migrate job to build test docker images to beats repo #18785
Conversation
73a0821
to
9f6ba83
Compare
What do you think about moving the job as-is, and then once working apply the filebeat changes? |
Changes for filebeat reverted, now the pipeline and the script are [mostly] as the original ones. |
quietPeriod(10) | ||
} | ||
triggers { | ||
cron '@daily' |
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.
We usually schedule jobs on a range of time (to avoid overload the CI) an from Monday to Friday, on weekend the CI rest :D
cron '@daily' | |
cron 'H H(0-5) * * 1-5' |
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.
@daily means '0 0 * * *'
What does this PR do?
Migrate job to pre-build docker images used in integration tests to beats repository.
Why is it important?
To have the definition of this job in the beats repository, as is related to the beats project.