Attention is currently required from: laforge, lynxis lazus.
osmith has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/simtrace2/+/43281?usp=email )
Change subject: contrib/jenkins.sh: pin libosmocore to the last release
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> I would use the same version in gerrit verifications as in master builds, as otherwise we may get un […]
s/osmocom master/libosmocore master/
--
To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43281?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: simtrace2
Gerrit-Branch: master
Gerrit-Change-Id: I753d634674f76c50e1a9cf67e5adc43201d54f0c
Gerrit-Change-Number: 43281
Gerrit-PatchSet: 1
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Tue, 18 Aug 2026 12:59:26 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: osmith <osmith(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Attention is currently required from: laforge, lynxis lazus.
osmith has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/simtrace2/+/43281?usp=email )
Change subject: contrib/jenkins.sh: pin libosmocore to the last release
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> But then you are also pinning it for host ones... […]
I would use the same version in gerrit verifications as in master builds, as otherwise we may get unexpected build failures in master with patches that passed in gerrit. IMHO it makes sense to do it like this.
Note that the debian builds still use libosmocore master, so we still additionally verify that it builds against osmocom master in gerrit.
--
To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43281?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: simtrace2
Gerrit-Branch: master
Gerrit-Change-Id: I753d634674f76c50e1a9cf67e5adc43201d54f0c
Gerrit-Change-Number: 43281
Gerrit-PatchSet: 1
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Tue, 18 Aug 2026 12:58:50 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Attention is currently required from: laforge, pespin.
Hello Jenkins Builder, laforge, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ci/+/43283?usp=email
to look at the new patch set (#2).
Change subject: ansible: build-host: configure email sending
......................................................................
ansible: build-host: configure email sending
Configure the hosts to forward e-mails addressed to "root", so we get
mdmonitor reports about failing raid devices.
Related: OS#7068
Change-Id: I22ea83de3417cbbb578345d34f18095c47441610
---
A ansible/roles/configure-email-sending/handlers/main.yml
A ansible/roles/configure-email-sending/tasks/main.yml
M ansible/setup-build-host.yml
3 files changed, 37 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/83/43283/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/43283?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I22ea83de3417cbbb578345d34f18095c47441610
Gerrit-Change-Number: 43283
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Attention is currently required from: laforge, lynxis lazus.
pespin has posted comments on this change by lynxis lazus. ( https://gerrit.osmocom.org/c/simtrace2/+/43281?usp=email )
Change subject: contrib/jenkins.sh: pin libosmocore to the last release
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
But then you are also pinning it for host ones...
In any case, if there's a specific jenkins job uploading the build to some published http server, then imho it probably makes sense to have an ENVVAR defaulting to master which that specific job pins to whatever libosmocore version we want to upload.
--
To view, visit https://gerrit.osmocom.org/c/simtrace2/+/43281?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: simtrace2
Gerrit-Branch: master
Gerrit-Change-Id: I753d634674f76c50e1a9cf67e5adc43201d54f0c
Gerrit-Change-Number: 43281
Gerrit-PatchSet: 1
Gerrit-Owner: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Tue, 18 Aug 2026 12:29:44 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No