You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we create releases for pontem, we should update (as part of the commits in the release) a change to a global string in pontem that tracks the version.
Then src/main/java/com/google/cloud/pontem/Util.java#L81 should reference that global version string so things between it and util.java stay in sync.
The text was updated successfully, but these errors were encountered:
Is there a pipeline, etc. that we can use to run tests for this against a release candidate? (I'm looking for a way to automate this instead of just human dependent and I don't see one looking around in GitHub).
EricBeach
changed the title
Codify pontem's version
[Spanner Backup & Restore] Codify pontem's version
Nov 3, 2018
I'll close it in that case. Well probably need a new cross platform way to track releases and doing it just for one tool probably isn't the right default option anymore. Michael feel free to reopen if you disagree.
As we create releases for pontem, we should update (as part of the commits in the release) a change to a global string in pontem that tracks the version.
Then
src/main/java/com/google/cloud/pontem/Util.java#L81
should reference that global version string so things between it and util.java stay in sync.The text was updated successfully, but these errors were encountered: