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

Trigger travis builds on more cases #16985

Merged
merged 2 commits into from
Mar 16, 2020

Conversation

jsoriano
Copy link
Member

What does this PR do?

Trigger travis builds also for x-pack beats.

Also trigger all builds if dev-tools or .travis.yml file change. Changes
there can also affect all Travis builds.

Why is it important?

Changes in x-pack beats are not triggering builds, see #16971 for example.

Add a common place to add files that can affect all builds.

Trigger travis builds also for x-pack beats.

Also trigger all builds if dev-tools or .travis.yml file change. Changes
there can also affect all Travis builds.
@jsoriano jsoriano added :Testing Team:Integrations Label for the Integrations team labels Mar 12, 2020
@jsoriano jsoriano requested a review from urso March 12, 2020 19:10
@jsoriano jsoriano self-assigned this Mar 12, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@jsoriano jsoriano changed the title Trigger travis builds on more cases. Trigger travis builds on more cases Mar 12, 2020
@jsoriano jsoriano merged commit ab2d591 into elastic:master Mar 16, 2020
@jsoriano jsoriano deleted the travis-test-more-common-files branch March 16, 2020 19:12
@@ -1,11 +1,14 @@
#!/usr/bin/env bash
set -exuo pipefail

# commit range to check for. For example master...<PR branch>
# Changes on these files will trigger all builds.
COMMON_DIRLIST="vendor dev-tools .travis.yml"
Copy link

Choose a reason for hiding this comment

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

should we add .ci as well?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, it would make sense, opened PR for that #17387, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
review Team:Integrations Label for the Integrations team :Testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants