Skip to content

Commit f04478b

Browse files
CongFelicianoTech
Cong
authored andcommitted
Note that gcloud may deploy extra artifacts (circleci#1042)
During the testing phase, extra artifacts (not git commited) may be generated on CircleCI, and will be deployed by `gcloud app deploy` to App Engine. This behavior is normally not expected, so it should be noted.
1 parent cb3320f commit f04478b

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

jekyll/_cci1/deploy-google-app-engine.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,15 @@ Once you're finished following the above instructions on authentication linked t
1414

1515
gcloud -q app deploy app.yaml --promote --version=staging
1616

17+
This will deploy everything in the current folder, including artifacts created during the testing phase.
18+
If that behavior is not expected, consider clean up the folder after testing, by specifying in `circle.yml` as follows:
19+
20+
```
21+
test:
22+
post:
23+
- git reset --hard; git clean -d -x -f
24+
```
25+
1726
Note that while the gcloud command can be used to interact with your App Engine project, it does not include the App Engine SDK, which you may want if you are running local unit tests. It can be downloaded separately by doing the following:
1827

1928
```

0 commit comments

Comments
 (0)