[Don't Merge] Force suppression of timestamps in OpenAPI generated code #1838
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This sample shows how a Develocity convention extension could enforce the
hideGenerationTimestamp
config option of thejava
OpenAPI code generator always betrue
. This config option is problematic because it defaults tofalse
. When disabled, OpenAPI generated code will including timestamps inGenerated
annotations, causing cache misses and non-reproducible builds.This sample makes it possible to opt-out of this behavior via
-Dopenapi.suppressTimestampGeneration
.I am mainly interested in getting feedback on the changes to the extension. The example is just there to support testing.
I won't merge this into the extension example as it should not belong here, but this best shows the changes I made.