summaryrefslogtreecommitdiffstats
path: root/.github
diff options
context:
space:
mode:
authorPaul Katsoulakis <34388743+paulkatsoulakis@users.noreply.github.com>2019-03-29 14:53:35 +0000
committerGitHub <noreply@github.com>2019-03-29 14:53:35 +0000
commit1856a50b8355e94fd33ecabc9ae50f2c3650df2b (patch)
treee211c2638796d55d3b1705aed1f83e2b41a3c827 /.github
parentc8d2e6c7d3b955b6d5781e2710b02bccc29a3c79 (diff)
netdata/packaging/ci: Make Travis CI more strict on nightlies run (#5708)
* netdata/packaging/ci: Make nightlies fail hard on all errors except changelog (#5580) 1) Add the necessary comments for documentation 2) Reinstate set -e to fail hard on errors 3) When changelog generation fails, just report a log entry and continue so that we dont break the release These changes are temporary, we are following up with more aggressive changes that re-distribute processing * netdata/packaging/nightlies: Clean up nightlies, round one of many 1) Move ALL changelog generation related code, to generate changelog script 2) Remove that || logic from everywherem, except the part we execute changelog generation. We have said its optional, so do not fail nightlies if this script fails, just report the problem 3) change the gitignore change and use the more stable logic that monitors folder path utilizing git 4) Add a bit more verbosity everywhere so we can tell what is going on 5) Adjust generate changelog script, based on the newly migrated code. a) Variable declarations to the top, so that if something wrong with the generated ones we break early and avoid the mess b) put all that github handling, right after markmandel's changelog generation c) Gently handle github commands, add enough verbosity to identify where we broke and also check in the end what happened and clean-up github before you bail out 6) A couple of renames for variables here and there, for clarity and readability * netdata/packaging/ci: nits and fixes 1) Make sure nightlies still dont run when no changes are seen since last nightly 2) Artifacts creation should happen even if docker breaks. Ensure that and on the next iteration we will restructure the pipeline to a more productive layout 3) settle a couple of shellcheck warnings * netdata/packaging/docker: build and publish are using a BASH v4 capability. Make sure you break early with a message if we ever run on a different bash by accident
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions