https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-10-01T07:58:03ZopenSUSE Project Management ToolopenQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=1530892018-10-01T07:58:03Zszarate
<ul><li><strong>Subject</strong> changed from <i>Link version to a possible delta</i> to <i>Link version to a possible deployed delta</i></li></ul> openQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=1531852018-10-01T11:59:35Zokurzokurz@suse.com
<ul></ul><p>szarate wrote:</p>
<blockquote>
<p>[…] pointing to a .md file would work, that could keep the same structure as our current deployment schedule.</p>
</blockquote>
<p>That wiki page was not updated for a year. How is it supposed to work differently now? And also: As long as we are talking about an osd-only solution I doubt the real need of QA engineers would be sufficiently adressed. How about an automatic email to the mailing list triggered by salt/deployment-script?</p>
openQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=1532122018-10-01T12:37:05Zszarate
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a> Email comes naturally after everything is done. </p>
<p>The idea of the link to a delta fits into an automated deploy, which chould generate the information and publish it, no human needed :).</p>
<p>In any case, the solution should be kind of agnostic or as agnostic as possible, so that it can be used with other deployments. Pretty much like the changelog feature that we have... (That nobody uses)</p>
openQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=1532962018-10-02T05:46:16Zokurzokurz@suse.com
<ul></ul><p>szarate wrote:</p>
<blockquote>
<p>The idea of the link to a delta fits into an automated deploy, which chould generate the information and publish it, no human needed :).</p>
</blockquote>
<p>Certainly. Take for example the automatic submit requests to openSUSE Factory that are created based on the openQA-in-openQA tests, e.g. <a href="https://build.opensuse.org/request/show/639153" class="external">https://build.opensuse.org/request/show/639153</a> which already provides a changelog. When we would ensure to update automatically to each new tested version then the changelog in the submit request would be equivalent to the changelog of what got deployed, problem solved :)</p>
openQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=1575622018-10-16T09:20:41Zcoolocoolo@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Project</i> to <i>openQA Infrastructure</i></li><li><strong>Category</strong> deleted (<del><i>168</i></del>)</li></ul> openQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=2368102019-08-20T14:08:43Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/55301">action #55301</a>: semi-automatic deployments on osd</i> added</li></ul> openQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=2458672019-09-24T19:48:25Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>As described on <a href="https://confluence.suse.com/pages/viewpage.action?pageId=194052156" class="external">https://confluence.suse.com/pages/viewpage.action?pageId=194052156</a> as well we decided to do weekly deployments, if not more, and for now use a semi-automatic approach, potentially moving to fully automatic later on as we already have on o3. With this the need for a changelog delta is easier to get from e.g. <a href="https://gitlab.suse.de/openqa/osd-deployment/pipelines" class="external">https://gitlab.suse.de/openqa/osd-deployment/pipelines</a> showing the changelog if the deployment was conducted successfully.</p>
openQA Infrastructure - action #41846: Link version to a possible deployed deltahttps://progress.opensuse.org/issues/41846?journal_id=2484382019-10-09T05:59:34Zcoolocoolo@suse.com
<ul><li><strong>Target version</strong> changed from <i>Ready</i> to <i>Done</i></li></ul>