Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[CI][Build] Use BUILD_NUMBER for building bundles
When running a release build for example: ``` yarn build-platform --linux --skip-os-packages --release ``` The build task runs through get_build_number and checks how many commits you have locally and determines the build number. From there, and this is the value that is used to as a cache busting mechanism. However, in the release build repo https://github.com/opensearch-project/opensearch-build When this gets packaged and verified it actually pulls from the specified branch and only retrieves the HEAD commit. Thus making the count of commits locally equal to `1` and get_build_number always return `1` for releases essentially breaking the cache buster. The build repo however, sets an env variable of `BUILD_NUMBER` so if this value is available it will use it instead of commit count. The CI runs the unit tests and only gets the latest commit as well so instead of setting a env build number and basically creating the same unit test only check this locally. Issues resolved: * opensearch-project/opensearch-build#1769 * opensearch-project#1363 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
- Loading branch information