-
Notifications
You must be signed in to change notification settings - Fork 140
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
Front End Deployment Changes #1895
Front End Deployment Changes #1895
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
/gcbrun |
WARNING: DO NOT MERGE WITHOUT TALKING TO NAG |
@cboneti tested this in my dev environment, everything worked as expected. Can you merge this if it's still possible without rebasing and if the OFE test still fails I will look into that in the separate PR. |
/gcbrun |
…ployment-changes Front End Deployment Changes
Allows the Front End source code to be deployed on the service machine through a git clone rather than building a tarball. The deploy.sh script will ask for a forked repository owner and branch (or they can be added to a config file) so that development changes can be tested. It would be best to verify in future work if the branch exists once provided, instead of the possibility of failing once the service machine infrastructure has been created