Update verification instructions

parent e9b900de
Pipeline #1907 passed with stages
in 30 minutes and 10 seconds
......@@ -21,7 +21,7 @@ build:
- docker build -t ${TEST_IMAGE} .
- docker push $TEST_IMAGE
# TODO unify with test_verify once latest release was uploaded to jcenter
# TODO unify with test_verify once latest stable release was uploaded to jcenter
test_build:
stage: test
script:
......@@ -44,4 +44,3 @@ release:
- docker push $RELEASE_IMAGE
only:
- master
- tags
......@@ -45,7 +45,7 @@ Build our Docker image:
To verify a specific version of Briar, run
docker run briar/tor-reproducer:latest ./build-tor.py [version]
docker run briar/tor-reproducer:latest ./verify-tor.py [version]
Where `[version]` is the version of Tor you want to test, for example `0.3.3.6`.
......@@ -55,3 +55,19 @@ Just remove the `tor-` from `tor-0.3.3.6`.
If you leave out `[version]` it will build the latest version
that was registered in `tor-versions.json`.
In case there is an issue with the verification of an old build,
this *might* be caused by an update of the container.
You can try to use the original container by running:
docker run briar/tor-reproducer:[version] ./build-tor.py [version]
There should be a tag with the name `[version]` in this repository
that you could be used to reproduce the old container.
Note that this will not work if the issue is caused by an updated Debian package.
### Only build Tor
To build a specific version of Briar, run
docker run briar/tor-reproducer:latest ./build-tor.py [version]
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment