Update to bionic in travis

Author: Yevgeny Pats

.travis.yml

@@ -1,3 +1,4 @@
+dist: bionic
 language: go
 go:
   - "1.12.x"
@@ -7,12 +8,12 @@ services:
 
 env:
   global:
-    # This is FUZZIT_API_KEY created with https://docs.travis-ci.com/user/environment-variables/#encrypting-environment-variables
+    # This is FUZZIT_API_KEY. see https://docs.travis-ci.com/user/environment-variables/#encrypting-environment-variables for how to create secrets in Travis.
     secure: "mUwEzKZKeF6nLswJOCsYxBIQct7v79Wz0ZfiRvPtpKdPD0hNsWHZHXd25E1gTDyAxwUZ1jXoOhMBBUejEAMEe8P64Ali4GZqADxK5JrBGfLNmfvwQJNiJQEyazwhD5m5X+N4ypaxgAfU2jjKn+14u9eKqOYjnKjMbZB2eyEH+F+xtpqA9UsdLbVaI/Pok2CooOk/9sWMxtbqIbwIlqb4l3Sld4/SH3ag7jDWdmcM7sVDALAlDNESGgigjJ47J8uVkV/+kL1CPJY9VfpcXPTgrZmep7QR7/qb2gKGqJgz7dYNLa/iv8vENMyycLsh5GtJzeZU3dLHdDIZH8iUf9+OEr3XKZq0JAh2najxPDrc4A/3VjTPNSgZGEuqTbt1EKGRsVNSIUoBemDobcIEKsyUInQobF2ievtaJqACFG6iVTX2bykS2Y75P0XzHKAiso+Yer0JeAD+xhkzC+m78Gr//Bpb2t2ty2bwgKyukUIbm/Xzmg7yGsl0HFQ6B3AsL0LklHgwHLIPrOcvBZG7F9w4l8U11s3D9e4Ic1P3V5TGABzZ3QvKHmj6iMvAFuuF749tR9iH14ryHyPg50QshoOPYLWLhsCQWOkJ4haa49NsfJMB9ZwJWceq0gc6wA51J7tnqEivohWiwZrZo6uDlHdn/oO1IbwqlWc16FnbSjB5DxY="
 
 jobs:
   include:
-    - stage: Build & test
+    - stage: Build, Unit-Tests & Fuzz-Tests
       go: 1.12.x
       script:
         - go build ./...

README.md

@@ -1,5 +1,5 @@
 [![Build Status](https://travis-ci.org/fuzzitdev/example-go.svg?branch=master)](https://travis-ci.org/fuzzitdev/example-go)
-![fuzzit](https://app.fuzzit.dev/badge?org_id=hP8u8bNAda91Cnj0mKPX&branch=master)
+[![fuzzit](https://app.fuzzit.dev/badge?org_id=hP8u8bNAda91Cnj0mKPX&branch=master)](https://fuzzit.dev)
 
 # Continuous Fuzzing for Golang Example
 
@@ -140,13 +140,23 @@ Base64: RlVaWkk=
 
 ## Integrating with Fuzzit from CI
 
-The best way to integrate with Fuzzit is by adding a stage in your Contintous Build system
-(like Travis CI or Circle CI). In that stage:
+The best way to integrate with Fuzzit is by adding a two stages in your Contintous Build system
+(like Travis CI or Circle CI).
+
+Fuzzing stage:
+
 * build a fuzz target
 * download `fuzzit` cli
 * authenticate with `fuzzit auth`
 * create a fuzzing job by uploading fuzz target
 
+Sanity stage
+* build a fuzz target
+* download `fuzzit` cli
+* authenticate with `fuzzit auth`
+* create a local sanity fuzzing job - This will pull all the generated corpus and run them through
+the fuzzing binary. If new bugs are introduced this will fail the CI and alert
+
 here is the relevant snippet from the [./ci/fuzzit.sh](https://github.com/fuzzitdev/example-go/blob/master/ci/fuzzit.sh)
 which is being run by [.travis.yml](https://github.com/fuzzitdev/example-go/blob/master/.travis.yml)
 

ci/fuzzit.sh

@@ -18,12 +18,12 @@ go build ./...
 go-fuzz-build -libfuzzer -o fuzzer.a .
 clang -fsanitize=fuzzer fuzzer.a -o fuzzer
 
-wget -q -O fuzzit https://github.com/fuzzitdev/fuzzit/releases/download/v2.4.1/fuzzit_Linux_x86_64
+wget -q -O fuzzit https://github.com/fuzzitdev/fuzzit/releases/download/v2.4.2/fuzzit_Linux_x86_64
 chmod a+x fuzzit
 ./fuzzit auth ${FUZZIT_API_KEY}
 
 if [ $1 == "fuzzing" ]; then
     ./fuzzit create job --branch $TRAVIS_BRANCH --revision $TRAVIS_COMMIT parse-complex ./fuzzer
 else
     ./fuzzit create job --local parse-complex ./fuzzer
-end
+fi