Skip to content
This repository was archived by the owner on Jan 22, 2025. It is now read-only.

Trigger all CI jobs for Dockerfile changes #10651

Merged
merged 5 commits into from
Jun 17, 2020

Conversation

ryoqun
Copy link
Contributor

@ryoqun ryoqun commented Jun 17, 2020

problem

I was completely blind of incompatibility of #10585 and the CI docs job... Causing some noises: #10633, #10634, #10640.

solution

Run the docs job when we're updating nightly docker image! I broadened yet more to re-test all the jobs.

@ryoqun
Copy link
Contributor Author

ryoqun commented Jun 17, 2020

I guess this is working as intended:

image

@@ -41,7 +42,8 @@ affects() {
# the worse (affected)
return 0
fi
for pattern in "$@"; do
# Assume everyting needs to be tested when any Dockerfile changes
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mvines FYI, I think this is safe bet. :)

@ryoqun ryoqun changed the title No tearful rust update Trigger docs job for possible mdbook updates, too Jun 17, 2020
@ryoqun ryoqun changed the title Trigger docs job for possible mdbook updates, too Trigger all CI jobs for updated Dockerfile changes Jun 17, 2020
@ryoqun ryoqun changed the title Trigger all CI jobs for updated Dockerfile changes Trigger all CI jobs for Dockerfile changes Jun 17, 2020
@ryoqun
Copy link
Contributor Author

ryoqun commented Jun 17, 2020

@mvines I'm going to merge this because this is minor and I checked this doesn't affect normal CI jobs at all. Feel free to do any post-merge comments! I'll gladly address them!

@ryoqun ryoqun merged commit 540ac9e into solana-labs:master Jun 17, 2020
@ryoqun ryoqun mentioned this pull request Jun 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant