Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Allow overriding docker build environment variables #1227

Merged

Conversation

ajorgensen
Copy link
Contributor

It is possible to build heron in an environment that does not include
the git repository (this can be the case in ci for instance). We should
allow people building override the derived variables to manually set the
version.

It is possible to build heron in an environment that does not include
the git repository (this can be the case in ci for instance). We should
allow people building override the derived variables to manually set the
version.
@objmagic objmagic added the build label Aug 8, 2016
@ajorgensen
Copy link
Contributor Author

ajorgensen commented Aug 8, 2016

There is actually a heron version string that is passed in whose purpose was to be the version that the release was tagged with. What are peoples thoughts about

either

  • removing that and allowing the override as I have implemented here

or

  • removing the git parsing for the version string

(See: https://github.com/twitter/heron/pull/1227/files#diff-489b3a1dc33fb4234394f371a8e67fe1R104)

It appears that HERON_VERSION is only used in naming the file which feels a bit misleading.

@kramasamy
Copy link
Contributor

Ship it!

@ajorgensen ajorgensen merged commit 8114425 into apache:master Aug 9, 2016
nicknezis pushed a commit that referenced this pull request Sep 14, 2020
It is possible to build heron in an environment that does not include
the git repository (this can be the case in ci for instance). We should
allow people building override the derived variables to manually set the
version.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants