-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Linux OS id [arch-null] is not present in the Docker exclude list? #50393
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
Comments
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
@pugnascotia I'm inclined to short-circuit this stuff when not in a CI environment. Our exclusion list is based on our own custom images. There's nothing to say that a developer using Debian 8 can't run Docker-based tests. Thoughts? |
@mark-vieira Yeah, I think that's fair. Do you happen to know what is the best way of detecting CI for us? |
You can use |
Closes #50393. When generating the packaging test tasks, skip the Linux OS checks unless we're running in CI.
Closes elastic#50393. When generating the packaging test tasks, skip the Linux OS checks unless we're running in CI.
Elasticsearch version (
bin/elasticsearch --version
):master
Plugins installed: none
JVM version (
java -version
): jdk-13OS version (
uname -a
if on a Unix-like system): Linux/archDescription of the problem including expected versus actual behavior:
./gradlew :run
logsThis seems like a message that we log for CI, but it was an odd greeting while compiling the project for the first time in a year.
The text was updated successfully, but these errors were encountered: