fix: run linux integration on CI#1186
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
|
Shouldn't we do something so that every new scenario added is executed on CI without more ceremony? ie, have the option maybe to opt out in case it is useful, instead of having to opt in. |
Agree. There is an open issue to standardise the tags used in feature files, which could simplify how they are spread across the different parallel executions. I can picture this:
If this makes sense to you, we can convert this comment into a new issue to start working on it, as I totally agree with you about the ceremonies :) |
|
Another idea, related to the used tags, could be to group all integrations under the |
(cherry picked from commit dc479f5)
(cherry picked from commit dc479f5)
(cherry picked from commit dc479f5)
* master: fix: run linux integration on CI (elastic#1186) docs: document integrations in the proper README file (elastic#1181) fix: resolve issues in k8s-autodiscover test suite (elastic#1171) feat: make a stronger verification of fleet-server being bootstrapped (elastic#1164)
could we be even a folder? |
Yes, or a glob expression: *.feature. but on CI we want to create a separation of concerns per feature, to speed up the build |
What does this PR do?
It includes the linux integration scenarios in the CI job, as a new parallel branch
Why is it important?
This suite was missing from CI execution
Checklist
make noticein the proper directory)