BRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.orgStarted by upstream project "linux-shallow-clone" build number 7070linux-shallow-clonejob/linux-shallow-clone/000013107131071.000070087e365bff834c5ffe9322620f863e3dc27e3c68087e365bff834c5ffe9322620f863e3dc27e3c68origin/master087e365bff834c5ffe9322620f863e3dc27e3c68087e365bff834c5ffe9322620f863e3dc27e3c68origin/master5608a09dee86914bd87d58cc10ca29de95762aa37608a09dee86914bd87d58cc10ca29de95762aa37refs/remotes/origin/osmith/wip608a09dee86914bd87d58cc10ca29de95762aa37608a09dee86914bd87d58cc10ca29de95762aa37refs/remotes/origin/osmith/wip087e365bff834c5ffe9322620f863e3dc27e3c68087e365bff834c5ffe9322620f863e3dc27e3c68origin/masterhttps://gerrit.osmocom.org/osmo-cifalse#701310712911linux-shallow-clone » build4-deb12build-ansible #7070falsefalse7088621SUCCESS1776198000237https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/linux-shallow-clone/label=build4-deb12build-ansible/70/build4-deb12build-ansiblejobs/octsim_osmo-ccid-firmware.yml42d5005d705167f38cb5387549211ad99340f5031776150671000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejobs/octsim_osmo-ccid-firmware: add email param Allow configuring the email notifications before starting a job, so no notifications can be set while testing changes to the jenkins job. Add jenkins-notifications@lists.osmocom.org while at it, as we have it with almost all other jobs. Change-Id: Ifcd580873479fc259119139d47447ba0e21b21f4 2026-04-14 09:11:11 +020042d5005d705167f38cb5387549211ad99340f503jobs/octsim_osmo-ccid-firmware: add email parameditjobs/octsim_osmo-ccid-firmware.ymljobs/octsim_osmo-ccid-firmware.ymlef69061f36bb989a5c3e5b3c126f8e161568cd841776151205000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejobs/octsim_osmo-ccid-firmware: don't use axis There is only one node, so we can specify it directly instead of using a build axis. Change-Id: I552c8f1b244c8e8b0f902720698fbb6ba660fb72 2026-04-14 09:20:05 +0200ef69061f36bb989a5c3e5b3c126f8e161568cd84jobs/octsim_osmo-ccid-firmware: don't use axiseditjobs/octsim_osmo-ccid-firmware.ymljobs/octsim_osmo-ccid-firmware.yml9571b31f4cb8d5b18a4090e8105b6633b88184581776152052000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejobs/octsim_osmo-ccid-firmware: various tweaks * move name and desc up (in preparation to adding another job in the same file) * remove "concurrent: false": the octsimtest node is already configured to only accept one job. if we had multiple octsimtest nodes, we wouldn't need this limitation of not running concurrently, so this isn't useful. * remove options without effect (block-downstream, block-upstream, disabled, build-blocker, etc.) * add "scm checkout" comment to retry-count as we have it in other files Change-Id: If64787efbe4a1305cd60941b69e9416960d056a2 2026-04-14 09:34:12 +02009571b31f4cb8d5b18a4090e8105b6633b8818458jobs/octsim_osmo-ccid-firmware: various tweakseditjobs/octsim_osmo-ccid-firmware.ymljobs/README.mdjobs/octsim_osmo-ccid-firmware.yml9407586f49d43f0470556a1bcb9ed23559cb05ef1776152429000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejobs/octsim_osmo-ccid-firmware: remove timer This job already gets triggered once a day from master-osmo-ccid-firmware. Running it once a day like all other master jobs should be enough, remove the timed trigger that caused it to run twice a day. Change-Id: Ia4fdb6d504c7a08cf258e82436627894602f7301 2026-04-14 09:40:29 +02009407586f49d43f0470556a1bcb9ed23559cb05efjobs/octsim_osmo-ccid-firmware: remove timereditjobs/octsim_osmo-ccid-firmware.ymleditjobs/README.mdjobs/octsim_osmo-ccid-firmware.yml139235c113d09efb052d1b891e9a6dfb98da5c8b1776156914000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejobs/octsim_osmo-ccid-firmware: add branch param Change-Id: I05321cd2c174060381e099aa49d5932f9cafdd28 2026-04-14 10:55:14 +0200139235c113d09efb052d1b891e9a6dfb98da5c8bjobs/octsim_osmo-ccid-firmware: add branch parameditjobs/octsim_osmo-ccid-firmware.ymljobs/octsim_osmo-ccid-firmware.yml087e365bff834c5ffe9322620f863e3dc27e3c681776159289000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dejobs/octsim_osmo-ccid-firmware: PYTHONUNBUFFERED=1 Ensure that the python output is getting displayed directly when running in jenkins. Change-Id: Iffe74b270f33286f394db1be03e6ce1953aff4bf 2026-04-14 11:34:49 +0200087e365bff834c5ffe9322620f863e3dc27e3c68jobs/octsim_osmo-ccid-firmware: PYTHONUNBUFFERED=1editjobs/octsim_osmo-ccid-firmware.ymlgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith