https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-04-27T01:42:43ZOpen Source Mobile CommunicationsOsmoGSMTester - Feature #2205: osmo-gsm-tester should tell jenkins where to find test result fileshttps://projects.osmocom.org/issues/2205?journal_id=37072017-04-27T01:42:43Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-high2 closed" href="/issues/2201">Feature #2201</a>: osmo-gsm-tester: compose jenkins result XML</i> added</li></ul> OsmoGSMTester - Feature #2205: osmo-gsm-tester should tell jenkins where to find test result fileshttps://projects.osmocom.org/issues/2205?journal_id=37122017-04-27T01:45:46Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-high2 closed" href="/issues/2206">Feature #2206</a>: osmo-gsm-tester should write to a log file, not only stdout</i> added</li></ul> OsmoGSMTester - Feature #2205: osmo-gsm-tester should tell jenkins where to find test result fileshttps://projects.osmocom.org/issues/2205?journal_id=37712017-05-04T21:08:08Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li></ul> OsmoGSMTester - Feature #2205: osmo-gsm-tester should tell jenkins where to find test result fileshttps://projects.osmocom.org/issues/2205?journal_id=38732017-05-14T11:18:10Zlaforge
<ul><li><strong>Assignee</strong> deleted (<del><i>118</i></del>)</li></ul> OsmoGSMTester - Feature #2205: osmo-gsm-tester should tell jenkins where to find test result fileshttps://projects.osmocom.org/issues/2205?journal_id=39192017-05-15T12:58:55Zlaforge
<ul><li><strong>Assignee</strong> set to <i>55360</i></li></ul> OsmoGSMTester - Feature #2205: osmo-gsm-tester should tell jenkins where to find test result fileshttps://projects.osmocom.org/issues/2205?journal_id=39752017-05-15T14:38:00Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>In the new setup on the public jenkins, where a build slave actually runs on the main unit, this is solved by keeping the trial entirely within the jenkins workspace.</p>
<p>If we're going to implement a daemon to schedule test runs concurrently, this is still an open question, which we will come back to once we need to.</p> OsmoGSMTester - Feature #2205: osmo-gsm-tester should tell jenkins where to find test result fileshttps://projects.osmocom.org/issues/2205?journal_id=48362017-08-08T19:04:04Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>