starred/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-08-03 19:52:34 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2940 from certbot/whatsa-letsencrypt

Browse Source 
s/--letsencrypt/--certbot
This commit is contained in:
bmw
2016-05-06 17:55:08 -07:00
parent 47c874cd1d 5c0eabcd76
commit 38d7503f0f
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/travis-integration.sh
+3 -3
View File
@@ -6,14 +6,14 @@ set -o errexit
source .tox/$TOXENV/bin/activate source .tox/$TOXENV/bin/activate
export LETSENCRYPT_PATH=`pwd` export CERTBOT_PATH=`pwd`
cd $GOPATH/src/github.com/letsencrypt/boulder/ cd $GOPATH/src/github.com/letsencrypt/boulder/
# boulder's integration-test.py has code that knows to start and wait for the # boulder's integration-test.py has code that knows to start and wait for the
# boulder processes to start reliably and then will run the certbot # boulder processes to start reliably and then will run the certbot
# boulder-interation.sh on its own. The --letsencrypt flag says to run only the # boulder-interation.sh on its own. The --certbot flag says to run only the
# certbot tests (instead of any other client tests it might run). We're # certbot tests (instead of any other client tests it might run). We're
# going to want to define a more robust interaction point between the boulder # going to want to define a more robust interaction point between the boulder
# and certbot tests, but that will be better built off of this. # and certbot tests, but that will be better built off of this.
python test/integration-test.py --letsencrypt python test/integration-test.py --certbot