ursus
02/25/2024, 3:26 PMephemient
02/25/2024, 3:29 PMursus
02/25/2024, 3:29 PMursus
02/25/2024, 3:42 PMDaniel B Duval
02/28/2024, 1:59 PMonVariants
part of the DSL to define a copy task and relocate it.
At the same time, does your build actually know/care about the SHA?
If your set up is anything like the one I deal with, the actual SHA of the check out isn’t going to be known to the pipeline, just the branch (e.g., release
) and not the actual SHA.
If that’s the case, then to get the SHA would require a command line statement to get it (such as git rev-parse --short HEAD
or --long
).
In that case, would a post build phase in the CI make more sense to have a script that collects and renames the APK for this need?
It’s been my experience with larger teams that when you start baking items like this into your build scripts itself rather than clearly defined phases in your CI, the larger group easily looses sight of these sorts of items.ursus
02/28/2024, 2:29 PMursus
02/28/2024, 2:30 PMursus
02/28/2024, 2:35 PMandroid {
defaultConfig {
buildConfigField "String", "GIT_HASH", "..."
}
}
that however would be the same thing right? here it needs to be eagerly ready, or can I mutate the buildConfigFields postprocess-y?
so we're back to square one again - same issue