Started by timerEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.orgBRANCH_CImaster00111963121963121.0330196315006265207691242d23b927f2ecf22990b90162ddadee35207691242d23b927f2ecf22990b90162ddadee3origin/master5207691242d23b927f2ecf22990b90162ddadee35207691242d23b927f2ecf22990b90162ddadee3origin/master506254b2d2d6f5bd650a595db321c7083f747055127254b2d2d6f5bd650a595db321c7083f747055127refs/remotes/origin/osmith/wip254b2d2d6f5bd650a595db321c7083f747055127254b2d2d6f5bd650a595db321c7083f747055127refs/remotes/origin/osmith/wip5207691242d23b927f2ecf22990b90162ddadee35207691242d23b927f2ecf22990b90162ddadee3origin/masterhttps://gerrit.osmocom.org/osmo-cihttps://jenkins.osmocom.org/jenkins/job/build-kernel-net-next/626/artifacthttps://jenkins.osmocom.org/jenkins/job/build-kernel-net-next/changeshttps://jenkins.osmocom.org/jenkins/job/build-kernel-net-next/626/https://jenkins.osmocom.org/jenkins/job/build-kernel-net-next/626/testReportbuild.logbuild.logoutput/build.loglinuxlinuxoutput/linuxfalse#626196312198420build-kernel-net-next #626626falsefalse626139017SUCCESS1781048700865https://jenkins.osmocom.org/jenkins/job/build-kernel-net-next/626/build4-deb12build-ansible- coverity/jenkins.sh5207691242d23b927f2ecf22990b90162ddadee31780996008000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.decoverity/jenkins: check if upload was successful
When the server returns an error, the curl command does not fail -
probably because the server sends a wrong http status code:
curl \
--form token="$token" \
--form email=holger@freyther.de --form file=@Osmocom.tgz \
--form version=Version --form description=AutoUpload \
https://scan.coverity.com/builds?project=Osmocom
+ set +x
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
…
<html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx/1.19.10</center>
</body>
</html>
Finished: SUCCESS
Fail if the output doesn't contain the "Build successfully submitted"
string, so the job fails if there was an error.
(The request entity too large error is probably an error on their end,
scan.coverity.com still says they are performing upgrades on their
servers.)
Change-Id: Ie63a33dfa7648b38f1f01cb8c87db76949f69e10
2026-06-09 11:06:48 +02005207691242d23b927f2ecf22990b90162ddadee3coverity/jenkins: check if upload was successfuleditcoverity/jenkins.sh
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith