-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Make sure generated quarkus-artifact.properties is stable #41587
Conversation
At the moment, it contains a timestamp, which is going to be in the way of the cache. Also make sure the properties are sorted.
When running ITs for native, we need quarkus-artifact.properties to be around so it needs to be part of the cache. Also make it an input of Failsafe. This file contains a relative path to the binary to run and a few additional metadata such as the full GraalVM version. Whenever this version has changed, we need to run the tests again so it makes sense to make it an input. Note that we will need quarkusio/quarkus#41587 to be in so that quarkus-artifact.properties doesn't contain a timestamp.
When running ITs for native, we need quarkus-artifact.properties to be around so it needs to be part of the cache. Also make it an input of Failsafe. This file contains a relative path to the binary to run and a few additional metadata such as the full GraalVM version. Whenever this version has changed, we need to run the tests again so it makes sense to make it an input. Note that we will need quarkusio/quarkus#41587 to be in so that quarkus-artifact.properties doesn't contain a timestamp. Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com>
The timestamp is actually not a problem as the file is not a direct input, its entries are parsed and used to create a list of inputs The sorting is important though as the order matters on compile classpath normalization. |
@jprinet I actually made it an input of the Failsafe goal in gradle/develocity-build-config-samples#1280. But I can drop it from the extension PR if you think it's better not to have it as an input. That being said, even if we don't make it an input, I would prefer this PR to go in. |
* Add quarkus-artifact.properties as an output of quarkus:build When running ITs for native, we need quarkus-artifact.properties to be around so it needs to be part of the cache. Also make it an input of Failsafe. This file contains a relative path to the binary to run and a few additional metadata such as the full GraalVM version. Whenever this version has changed, we need to run the tests again so it makes sense to make it an input. Note that we will need quarkusio/quarkus#41587 to be in so that quarkus-artifact.properties doesn't contain a timestamp. Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com> * Do not register quarkus-artifact.properties as input of Failsafe Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com> --------- Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com>
Status for workflow
|
At the moment, it contains a timestamp, which is going to be in the way of the cache.
Also make sure the properties are sorted.
/cc @jprinet