osmith has uploaded this change for review. ( 
https://gerrit.osmocom.org/c/osmo-ci/+/35267?usp=email )


Change subject: coverity: add job to check for failed uploads
......................................................................

coverity: add job to check for failed uploads

Related: SYS#6685
Change-Id: Ideabcb30f9f8f365acff2de7751eb74a2762a7a6
---
A coverity/badge_status.sh
M jobs/README.adoc
A jobs/coverity-status.yml
3 files changed, 79 insertions(+), 0 deletions(-)



  git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/67/35267/1

diff --git a/coverity/badge_status.sh b/coverity/badge_status.sh
new file mode 100755
index 0000000..6143f75
--- /dev/null
+++ b/coverity/badge_status.sh
@@ -0,0 +1,23 @@
+#!/bin/sh -e
+# Check if the coverity badge says "failed". This can happen for example if we
+# use a coverity version that is no longer supported, and it doesn't fail in
+# any other obvious way. (SYS#6685)
+
+BADGE="_temp/badge.svg"
+
+mkdir -p _temp
+rm -f "$BADGE"
+
+wget --no-verbose -O "$BADGE" 
"https://scan.coverity.com/projects/7523/badge.svg";
+
+if grep -q failed "$BADGE"; then
+       echo
+       echo "ERROR: coverity status is 'failed'!"
+       echo
+       echo "Find the error details here:"
+       echo "https://scan.coverity.com/projects/osmocom?tab=overview";
+       echo
+       exit 1
+fi
+
+echo "Success, the coverity status badge does not say 'failed'."
diff --git a/jobs/README.adoc b/jobs/README.adoc
index c37b3bb..eb14152 100644
--- a/jobs/README.adoc
+++ b/jobs/README.adoc
@@ -144,5 +144,6 @@
    04:XX osmocom-release-manuals
    05:XX osmocom-release-tarballs
    06:XX repo-install-test
+   06:XX coverity-status (runs intentionally much later than the coverity job)

 master-builds: to avoid complexity, these run throughout the day (H H * * *).
diff --git a/jobs/coverity-status.yml b/jobs/coverity-status.yml
new file mode 100644
index 0000000..7a2e9fd
--- /dev/null
+++ b/jobs/coverity-status.yml
@@ -0,0 +1,45 @@
+# Check if the coverity badge says "failed". This can happen for example if we
+# use a coverity version that is no longer supported, and it doesn't fail in
+# any other obvious way. (SYS#6685)
+- project:
+    name: osmocom-coverity-status
+    jobs:
+      - osmocom-coverity-status
+
+- job:
+    name: 'osmocom-coverity-status'
+    project-type: freestyle
+    defaults: global
+    description: |
+        Verify that the coverity badge doesn't say "failed" (SYS#6685).
+    builders:
+      - shell: |
+          coverity/badge_status.sh
+    publishers:
+      - email:
+          recipients: 'jenkins-notificati...@lists.osmocom.org'
+          notify-every-unstable-build: true
+    properties:
+      - build-discarder:
+          days-to-keep: 30
+          num-to-keep: 30
+    parameters:
+      - string:
+          name: BRANCH
+          description: osmo-ci.git branch
+          default: 'origin/master'
+    scm:
+      - git:
+          url: https://gerrit.osmocom.org/osmo-ci
+          git-config-name: 'Jenkins Builder'
+          git-config-email: 'jenk...@osmocom.org'
+          branches:
+            - '$BRANCH'
+    triggers:
+      - timed: "H 06 * * *"
+    publishers:
+      - email:
+          notify-every-unstable-build: true
+          recipients: 'jenkins-notificati...@lists.osmocom.org'
+
+# vim: expandtab tabstop=2 shiftwidth=2

--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/35267?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: Ideabcb30f9f8f365acff2de7751eb74a2762a7a6
Gerrit-Change-Number: 35267
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osm...@sysmocom.de>
Gerrit-MessageType: newchange

Reply via email to