-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
buildDockerImageTask runs in every invocation of :distribution:docker:integTest #49359
Comments
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
Also very irritating when iterating on Docker packaging tests and running them locally. |
Indeed, we should make these tasks support incremental build. |
This commits sets an output marker file for the docker build tasks so that it can be tracked as up to date. It also fixes the docker build context task to omit the build date as in input property which always left the task as out of date. relates elastic#49359
This commits sets an output marker file for the docker build tasks so that it can be tracked as up to date. It also fixes the docker build context task to omit the build date as in input property which always left the task as out of date. relates #49359
This commits sets an output marker file for the docker build tasks so that it can be tracked as up to date. It also fixes the docker build context task to omit the build date as in input property which always left the task as out of date. relates #49359
@jkakavas this should be fixed in master. Would you mind verifying? |
This was fixed with #49613. Here's an example build with all the build tasks UP-TO-DATE: https://gradle-enterprise.elastic.co/s/fb36ht6rfwtty |
@mark-vieira there seems to be a regression here - https://gradle-enterprise.elastic.co/s/y447z33bdzgrg What happened was:
|
Looks like the ML jar changed: |
@pugnascotia Do you have the build scan from the build just before the one you linked? |
@mark-vieira I did two test runs back-to-back in my IDE: First: https://gradle-enterprise.elastic.co/s/4ddr4hi2dlpa2 You can see in the second that it rebuilt the linux tar and docker image, when I had changed nothing. |
Another run from the command line, instead of IntelliJ, and just building the Docker image. Again, back-to-back runs, on |
@pugnascotia Can you please add |
@pugnascotia I am unable to reproduce this locally for the life of me. Is this continuing to happen for you? @rjernst were you able to reproduce this locally? If this is still happening do you mind sharing the contents of |
Something's changed on master, because I just did two back-to-back builds and the second run was fine. I even ran the tests and saw that the first time it exported the Docker image as expected, and the second time it didn't. So we're all good here as far as I can tell. |
Thanks, Rory. |
This happens even though nothing has changed in between, which I would assume make gradle reuse existing images.
Reproduces for instance, by running:
consecutively
The text was updated successfully, but these errors were encountered: