-
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
ci: exclude builds with changes on the k8s templates files #25864
ci: exclude builds with changes on the k8s templates files #25864
Conversation
This pull request doesn't have a |
@elastic/integrations are these files used for something else? |
These files are used in docs as reference, and as reference in general. We don't test sth on top of these explicitly. I think that we only check if they are able to be deployed at beats/deploy/kubernetes/Makefile Line 9 in 8398f8b
|
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
@ChrsMark do we know where we call |
The deploys/k8s folder has got a pipeline:
Linting is mandatory for every PR, including docs only. I think we should be good with this, if my assumption is correct |
Yes, Lines 82 to 102 in 9e5aafd
make check that IIUC, it's the meta make goal to run all the linting for all the beats.
|
(cherry picked from commit 7ba5980) # Conflicts: # Jenkinsfile
(cherry picked from commit 7ba5980) # Conflicts: # Jenkinsfile
(cherry picked from commit 7ba5980) # Conflicts: # Jenkinsfile
… k8s templates files (elastic#25943)
What does this PR do?
deploy/kubernetes/.*-kubernetes.yaml
files are templates for the docsWhy is it important?
Filter what to run for those builds with docs changes.
Issue
Tested with elastic/apm-pipeline-library#1131