https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092018-11-14T16:46:01ZOpen Source Mobile CommunicationsCellular Network Infrastructure - Feature #3695: generate VTY reference manuals from 'make' directlyhttps://projects.osmocom.org/issues/3695?journal_id=125842018-11-14T16:46:01Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Due date</strong> set to <i>07/09/2018</i></li><li><strong>Start date</strong> changed from <i>11/14/2018</i> to <i>07/09/2018</i></li><li><strong>Follows</strong> <i><a class="issue tracker-2 status-3 priority-2 priority-default closed" href="/issues/3385">Feature #3385</a>: Move project specific manuals from osmo-gsm-manuals to each respective git repository</i> added</li></ul> Cellular Network Infrastructure - Feature #3695: generate VTY reference manuals from 'make' directlyhttps://projects.osmocom.org/issues/3695?journal_id=125862018-11-14T16:48:28Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Assignee</strong> set to <i>osmith</i></li></ul><p><a class="user active" href="https://projects.osmocom.org/users/7">laforge</a> : assigning this to osmith, please change that if it makes no sense.</p> Cellular Network Infrastructure - Feature #3695: generate VTY reference manuals from 'make' directlyhttps://projects.osmocom.org/issues/3695?journal_id=125902018-11-15T09:40:02Zosmith
<ul><li><strong>Due date</strong> deleted (<del><i>07/09/2018</i></del>)</li><li><strong>Start date</strong> deleted (<del><i>07/09/2018</i></del>)</li></ul><p>(removed due date and start date that was set in the past)</p> Cellular Network Infrastructure - Feature #3695: generate VTY reference manuals from 'make' directlyhttps://projects.osmocom.org/issues/3695?journal_id=128102018-12-03T13:20:01Zosmith
<ul></ul><p>We have a Jenkins job, that builds each project whenever commits land in master (master-builds.yml, <a href="https://osmocom.org/projects/osmocom-servers/wiki/Jenkins_build_verification_jobs" class="external">see also</a>). Some of these are built for multiple axes, which means multiple versions will be built with different configure flags enabled. Right now, we have configured the scripts to build the manuals with the fastest job (where the additional features are turned off), so it goes through the fastest way. See the discussion here:</p>
<p><a class="external" href="https://gerrit.osmocom.org/#/c/osmo-ci/+/12045/">https://gerrit.osmocom.org/#/c/osmo-ci/+/12045/</a></p>
<p>However, <a class="user active" href="https://projects.osmocom.org/users/91">neels</a> noted that when we will implement automatic VTY reference manual generation, we would want to do this with a complete build, so we get a full VTY reference manual for all commands. So this would need to be changed as part of this issue.</p> Cellular Network Infrastructure - Feature #3695: generate VTY reference manuals from 'make' directlyhttps://projects.osmocom.org/issues/3695?journal_id=147172019-06-05T07:36:54Zosmith
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-6 priority-2 priority-default closed" href="/issues/4044">Feature #4044</a>: regenerate vty reference during release process</i> added</li></ul> Cellular Network Infrastructure - Feature #3695: generate VTY reference manuals from 'make' directlyhttps://projects.osmocom.org/issues/3695?journal_id=149972019-06-27T08:14:16Zosmith
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>This would break manual generation during cross compiling, see <a class="issue tracker-2 status-6 priority-2 priority-default closed" title="Feature: regenerate vty reference during release process (Rejected)" href="https://projects.osmocom.org/issues/4044">#4044</a>.</p>