https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-09-07T15:18:33ZOpen Source Mobile CommunicationsOsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=53442017-09-07T15:18:33Zlaforge
<ul><li><strong>Category</strong> set to <i>osmo-bts-litecell15</i></li></ul> OsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=64872017-12-03T10:22:54Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>This is like a 15-30 minute task, which has been pending for 3 months. Please get it done, we don't want to continue to have code in our tree that's not build tested. Thanks!</p> OsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=65412017-12-04T13:06:01Zpespin
<ul><li><strong>Assignee</strong> changed from <i>pespin</i> to <i>laforge</i></li></ul><p>The gerrit job seems to be building for lc15 already, and it can be seen the job was generated by jenkins-job-builder: <a class="external" href="https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/">https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/</a></p>
<p>The "osmo-bts" job, according to osmo-ci jobs/master-builds.yml should also be building for lc15 (has same config for that project as jobs/gerrit-verifications.yml), however the jenkins jobs doesn't seem to be yet populated by jenkins-job-builder from the yaml config: <a class="external" href="https://jenkins.osmocom.org/jenkins/job/osmo-bts">https://jenkins.osmocom.org/jenkins/job/osmo-bts</a></p>
<p>Making jenkins to use jenkins-job-builder for that job should resolve this task afaiu, but I'm not sure how to do it. I re-assign for feedback as I think someone with privileges has to push the config somehow.</p> OsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=70332018-01-04T11:04:40Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>pespin</i></li></ul><p>Let's make sure you have the required privileges to do it yourself.</p> OsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=70392018-01-04T11:09:01Zlaforge
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul> OsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=70512018-01-04T21:43:18Zpespin
<ul></ul><p>Reminder: Let's sync with Neels, afair he was actually in the process of changing the yml files but still didn't push the changes at that time. I'll check current status and make sure I can push those myself.</p> OsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=70632018-01-07T17:43:19Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>pespin wrote:</p>
<blockquote>
<p>Reminder: Let's sync with Neels, afair he was actually in the process of changing the yml files but still didn't push the changes at that time. I'll check current status and make sure I can push those myself.</p>
</blockquote>
<p>All pushed and nothing in the pipeline. I usually edit around and update jenkins without pushing, but try to push the yml changes the moment I'm done figuring out the proper yml...</p> OsmoBTS - Feature #2503: extend jenkins job for osmo-bts to build osmo-bts-lc15https://osmocom.org/issues/2503?journal_id=70772018-01-08T16:05:37Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>The osmo-bts-lc15 is already being built. I also checked I can successfuly push stuff to jenkins using jenkins-job-builder -> task resolved.</p>