Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set build string to GIT_BUILD_STR in meta.yaml #33

Closed
jrsmith3 opened this issue Apr 15, 2015 · 2 comments
Closed

Set build string to GIT_BUILD_STR in meta.yaml #33

jrsmith3 opened this issue Apr 15, 2015 · 2 comments
Assignees
Labels
development infrastructure Issues having to do with development workflow itself, not feature development.

Comments

@jrsmith3
Copy link
Owner

Add the following to meta.yaml:

build:
    string: {{ environ.get('GIT_BUILD_STR', '') }}

In this way the commit hash (more or less) will be set as the conda build string and therefore I will be able to identify from which commit a particular conda build was produced.

@jrsmith3 jrsmith3 added the development infrastructure Issues having to do with development workflow itself, not feature development. label Apr 15, 2015
@jrsmith3 jrsmith3 self-assigned this Apr 15, 2015
@jrsmith3
Copy link
Owner Author

I'm reopening this issue in order to reorganize the commits. Also I want to use the noarch directive in meta.yaml (see #38) and I can't figure out how to simultaneously get the functionality described in this issue to work with the funcitonality described in #38.

@jrsmith3 jrsmith3 reopened this Dec 23, 2015
@jrsmith3
Copy link
Owner Author

This issue is old so I’m closing it. If I need something like it again, I will reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development infrastructure Issues having to do with development workflow itself, not feature development.
Projects
None yet
Development

No branches or pull requests

1 participant