Permalink
Browse files

Add sha256 hashgen for watchdog to ci config

Issue #955 suggested that the watchdog binaries should have associated sha256 files to help assure the veracity of the built artefacts.  This change mirrors the method employed on
faas-cli to generate and deploy the sha256 hash for each flavour of the current watchdog.

Signed-off-by: Richard Gee <richard@technologee.co.uk>
  • Loading branch information...
rgee0 authored and alexellis committed Nov 14, 2018
1 parent 98a76c6 commit 78a4584019a2a5d86b606a00b4fba979930cc2a7
Showing with 12 additions and 0 deletions.
  1. +1 −0 .gitignore
  2. +7 −0 .travis.yml
  3. +4 −0 ci/hashgen.sh
@@ -7,3 +7,4 @@ fwatchdog-armhf
certifier
.editorconfig
/contrib/staging/
**/*.sha256
@@ -34,6 +34,9 @@ after_success:
fi
before_deploy:
- ./ci/hashgen.sh
deploy:
provider: releases
api_key:
@@ -43,6 +46,10 @@ deploy:
- ./watchdog/fwatchdog-armhf
- ./watchdog/fwatchdog-arm64
- ./watchdog/fwatchdog.exe
- ./watchdog/fwatchdog.sha256
- ./watchdog/fwatchdog-armhf.sha256
- ./watchdog/fwatchdog-arm64.sha256
- ./watchdog/fwatchdog.exe.sha256
skip_cleanup: true
on:
tags: true
@@ -0,0 +1,4 @@
#!/bin/sh
cd ./watchdog
for f in fwatchdog*; do shasum -a 256 $f > $f.sha256; done
cd ..

0 comments on commit 78a4584

Please sign in to comment.