https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692018-06-22T15:14:29ZOpen-Source ProjectsKlever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=334532018-06-22T15:14:29ZVladimir Gratinskiygratinskiy@ispras.ru
<ul></ul><p>Population is not a developer feature. It's needed for deployment only.</p> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=334572018-06-23T05:21:12ZEvgeny Novikovnovikov@ispras.ru
<ul></ul><p>Vladimir Gratinskiy wrote:</p>
<blockquote>
<p>Population is not a developer feature. It's needed for deployment only.</p>
</blockquote>
<p>First of all developers also make deployment (not only initial installation, but also updates). Besides, even for production deployment it can be very valuable to restrict population. Otherwise there can be many similar (the same) jobs, although one doesn't need them.</p>
<p>BTW, for marks and tags updates are purely incremental, so, nobody complains. Thus, perhaps instead of implementing a switch for enabling/disabling population of verification jobs, we can support incremental population for them as well. I.e. Bridge will compare all files for verification jobs with the same names and populate just new ones or ones where files differ.</p> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=335962018-06-29T11:38:01ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Target version</strong> deleted (<del><i>1.0</i></del>)</li></ul><p>This was marked for <a class="version" href="https://forge.ispras.ru/versions/248">1.0</a> by mistake.</p> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=365092019-07-11T14:34:58ZVladimir Gratinskiygratinskiy@ispras.ru
<ul><li><strong>Due date</strong> set to <i>07/11/2019</i></li><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>Implemented in bridge-3.0 (population is on manager page now).</p> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=365202019-07-12T11:58:20ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Target version</strong> set to <i>3.0</i></li></ul> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=368682019-09-18T07:55:40ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Open</i></li></ul><p>I suggest a small extension. Let's allow to select either all jobs or just some ones (Bridge should get a list of existing ones in advance). For web UI this will be very nice. For CLI Bridge can allow to populate a single job according to specified name.</p> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=368832019-09-24T07:41:03ZEvgeny Novikovnovikov@ispras.ru
<ul></ul><p>Evgeny Novikov wrote:</p>
<blockquote>
<p>Vladimir Gratinskiy wrote:</p>
<blockquote>
<p>Population is not a developer feature. It's needed for deployment only.</p>
</blockquote>
<p>First of all developers also make deployment (not only initial installation, but also updates). Besides, even for production deployment it can be very valuable to restrict population. Otherwise there can be many similar (the same) jobs, although one doesn't need them.</p>
<p>BTW, for marks and tags updates are purely incremental, so, nobody complains. Thus, perhaps instead of implementing a switch for enabling/disabling population of verification jobs, we can support incremental population for them as well. I.e. Bridge will compare all files for verification jobs with the same names and populate just new ones or ones where files differ.</p>
</blockquote>
<p>Rather than to implement the small extension I suggested earlier, it will be much better to implement incremental job population that I suggested a long ago but that was not implemented.</p>
<p>Evgeny Novikov wrote:</p>
<blockquote>
<p>I suggest a small extension. Let's allow to select either all jobs or just some ones (Bridge should get a list of existing ones in advance). For web UI this will be very nice. For CLI Bridge can allow to populate a single job according to specified name.</p>
</blockquote> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=371362019-11-05T10:19:22ZVladimir Gratinskiygratinskiy@ispras.ru
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-4 status-5 priority-6 priority-high2 closed" href="/issues/9858">Feature #9858</a>: Support new verification jobs base</i> added</li></ul> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=372042019-11-15T08:09:52ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Resolved</i></li></ul><p>There is a great solution of this issue in <em>klever-3.0</em>. There is no more preset jobs population at all. Instead, users need to either create verification jobs on the base of actual preset ones or copy previously created verification jobs.</p> Klever - Feature #8989: Allow to populate just jobs/marks/tagshttps://forge.ispras.ru/issues/8989?journal_id=377262020-01-16T14:14:46ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>In master.</p>