19 Jun
2017
19 Jun
'17
1:09 p.m.
Hi.
I've problem figuring out how to use osmo-ci in jenkins: the build steps for
osmo-bts-gerrit and osmo-pcu-gerrit look pretty-much the same but osmo-pcu fails with:
osmo-layer1-headers.sh: command not found
while osmo-bts (which uses other scripts from osmo-ci) works fine.
Any ideas where this difference might come from?
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
19 Jun
19 Jun
3:52 p.m.
Hi,
Any ideas where this difference might come from?
Scripts must be in PATH (e.g. /home/osmocom-build/bin on
OsmocomBuild1). Your recently added script might not have been added
to PATH yet?
Not sure how it's done atm, but no "update-osmo-ci" job or similar on
Jenkins' side.
20 Jun
20 Jun
1:54 p.m.
On Mon, Jun 19, 2017 at 03:52:02PM +0200, André Boddenberg wrote:
But of course there is: http://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/
It last ran three months ago. Run that and your new script will be available.
~N
Any ideas
where this difference might come from?
Not sure how it's done atm, but no "update-osmo-ci" job or similar on
Jenkins' side.
2:19 p.m.
Now, when osmo-ci is on gerrit as well, can we run this job automatically on every
commit to master branch?
On 20.06.2017 13:54, Neels Hofmeyr wrote:
But of course there is: http://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/
It last ran three months ago. Run that and your new script will be available.
~N
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
21 Jun
21 Jun
12:37 a.m.
On Tue, Jun 20, 2017 at 02:19:17PM +0200, Max wrote:
Now, when osmo-ci is on gerrit as well, can we run
this job automatically on every
commit to master branch?
(The question whether we do this is not related to being on gerrit or not.)
So far the times I had to run this were extremely rare and I saw no need /
preferred to trigger manually to know when it ran. You can configure a "Poll
SCM" on that job if you like.
~N
10:25 a.m.
Actually I'd prefer this job to be converted into JobDSL so instead of being
configured via web UI it could be declaratively described under git (in osmo-ci?) and
automatically generated from that description using seed job.
It seem like a perfect candidate to begin with: it's rather rarely used, pretty
simple (no complex config matrix) etc.
André, what do you think?
On 21.06.2017 00:37, Neels Hofmeyr wrote:
You can configure a "Poll SCM" on that job
if you like.
~N
--
Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
2524
days inactive
2526
days old
5 comments
3 participants
participants (3)
-
André Boddenberg -
Max -
Neels Hofmeyr