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

Logic revisions needed in build_release.sh script #49

Closed
martinholmer opened this issue Jul 6, 2017 · 2 comments
Closed

Logic revisions needed in build_release.sh script #49

martinholmer opened this issue Jul 6, 2017 · 2 comments
Assignees

Comments

@martinholmer
Copy link
Collaborator

The Release Process described in webapp-public issue 560 implies, it seems to me, the need for some fundamental changes in the logic of the build_release.sh script. My thoughts on this are part of the 560 discussion. I'm linking here to that comment here because it is here in the policybrain-builder repository that these logic changes need to be made.

@martinholmer
Copy link
Collaborator Author

martinholmer commented Jul 11, 2017

@jbcrail, Thanks for fixing issue #43.

As I first said almost a week ago in issue #49, the Release Process described in webapp-public issue 560 implies the need for some fundamental changes in the logic of the build_release.sh script.

There are two main design changes:

(1) make the script operate on one, and only one, OSPC repository at a time, and

(2) remove from the script any logic that changes the taxcalc version in the requirements section of a repository's conda.recipe/meta.yaml file.

Here are some implications of those two design changes:

(a) Because the script is building conda packages with a specified name (taxcalc, ogusa, or btax) and a specified repo release tag (e.g., 0.1.6 for btax), the name of the script should be changed to build_packages.sh. It is conda packages that are being built and optionally uploaded to anaconda.org.

(b) The SKIP_TAXCALC, SKIP_OGUSA, and SKIP_BTAX variables should be replaced by one variable that specifies the kind of packages being built: PKG_NAME. This new variable would have (at the moment) just three valid values: taxcalc, ogusa, btax. The script would know how to translate the specified package name into the repository's name, etc.

(c) The TAXCALC_TAG variable should be replaced by a variable that specifies the release tag being used to build the packages: PKG_TAG.

It seems to me, that these changes are essential if the build_packages.sh script is to support the new Release Process. But maybe I've missed something or I am confused. If so, please let me know how you think the script should be revised to support the new Release Process.

@MattHJensen @PeterDSteinberg

@jbcrail jbcrail mentioned this issue Jul 21, 2017
@martinholmer
Copy link
Collaborator Author

Pull request #52 by @jbcrail resolved issue #49. Thanks, @jbcrail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants