archive/blender-cloud
0
1
Fork 1
Code Issues 24 Pull Requests Projects Releases Wiki Activity

Remove mention of DEPLOY_BRANCH which is not actually used anywhere

Browse Source
This commit is contained in:
Anna Sirota
2021-03-18 12:21:13 +01:00
parent 78c2dfb6ab
commit a04bb4c8ce
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
deploy/2docker.sh
View File

@@ -102,7 +102,7 @@ git_clone pillar $STAGING_BRANCH $PILLAR_DIR
git_clone attract $STAGING_BRANCH $ATTRACT_DIR git_clone attract $STAGING_BRANCH $ATTRACT_DIR
git_clone flamenco $STAGING_BRANCH $FLAMENCO_DIR git_clone flamenco $STAGING_BRANCH $FLAMENCO_DIR
git_clone pillar-svnman $STAGING_BRANCH $SVNMAN_DIR git_clone pillar-svnman $STAGING_BRANCH $SVNMAN_DIR
git_clone blender-cloud $DEPLOY_BRANCH $ROOT git_clone blender-cloud $STAGING_BRANCH $ROOT
# Gulp everywhere # Gulp everywhere
GULP=$ROOT/node_modules/.bin/gulp GULP=$ROOT/node_modules/.bin/gulp

2
deploy/README.md
View File

@@ -35,5 +35,5 @@ For `xxx` there are:
## Hacking Stuff ## Hacking Stuff
To deploy another branch than `production`, do `export DEPLOY_BRANCH=otherbranch` before starting To deploy another branch than `production`, do `export STAGING_BRANCH=otherbranch` before starting
the above commands. the above commands.