[
https://issues.apache.org/jira/browse/BEAM-11512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Weaver updated BEAM-11512:
-------------------------------
Fix Version/s: 2.28.0
Assignee: Nelson Osacky (was: Kyle Weaver)
Resolution: Fixed
Status: Resolved (was: Open)
> sdk.properties is often (always?) stale.
> ----------------------------------------
>
> Key: BEAM-11512
> URL: https://issues.apache.org/jira/browse/BEAM-11512
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Kyle Weaver
> Assignee: Nelson Osacky
> Priority: P2
> Fix For: 2.28.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> I'm not sure when sdk.properties is rebuilt, but it is not often (perhaps it
> is only regenerated on a clean build). `./gradlew
> :sdks:java:core:processResources` never does anything, it always reports
> being up to date.
> One consequence of this is that when the SDK version property in Gradle
> changes, sdk.properties does not change. We rely on sdk.properties to get the
> default Java SDK container version tag, among other things, so this causes
> the default container environment to become incorrect.
>
> For example, this caused cross language tests to fail on the release branch
> because they looked for the wrong Java SDK container.
> https://ci-beam.apache.org/job/beam_PostCommit_Python38_PR/179/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
