https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/RELENG-101 releng <p>This issue is to organize the work around the <a href="https://lists.opendaylight.org/pipermail/integration-dev/2018-April/011768.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/integration-dev/2018-April/011768.html</a> idea to have a new "Weather Item" process with full preparation on topic and verification instead of breaking the world.</p> <p>The currently planned weather items that we should try this against are listed on <a href="https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10303" class="external-link" rel="nofollow">https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10303</a>.</p> RELENG-101

New "Weather Item" process with full preparation on topic and verification instead of breaking the world

New Feature Medium Open Unresolved Unassigned Michael Vorburger Thu, 26 Apr 2018 17:15:49 +0000 Wed, 9 May 2018 13:22:21 +0000 Fluorine 0 3 <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> how about we track what you posted above in <a href="https://jira.opendaylight.org/browse/TSC-99" title="MDSAL Fluorine API breakage window 2" class="issue-link" data-issue-key="TSC-99"><del>TSC-99</del></a> instead of here? </p> <p>That way we can use this JIRA for the new process in general.</p> <p>Sure I moved the content to <a href="https://jira.opendaylight.org/browse/TSC-99" title="MDSAL Fluorine API breakage window 2" class="issue-link" data-issue-key="TSC-99"><del>TSC-99</del></a></p> <p><a href="https://lists.opendaylight.org/pipermail/daexim-dev/2018-May/000156.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/daexim-dev/2018-May/000156.html</a> has an example of how I envision this working...</p> <p>Cool, is the mail to project sent automatically or for now someone has to extract build error and send to project?</p> <p>currently semi-manual - the <a href="https://github.com/vorburger/opendaylight-bot" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/vorburger/opendaylight-bot</a> code that is currently running on <a href="http://opendaylight-bot-opendaylight-bot.6923.rh-us-east-1.openshiftapps.com/" class="external-link" target="_blank" rel="nofollow noopener">http://opendaylight-bot-opendaylight-bot.6923.rh-us-east-1.openshiftapps.com</a> will produce the email from a template, but not actaully automatically send it out, yet. I'm open to contributions to The Bot to make it more integrated and automated.</p> <p>I wonder whether we could enhance the existing multipatch job to:</p> <ul class="alternate" type="square"> <li>Get a topic and figure out the patch-list (same you do in your bot).</li> <li>Send an automatic mail when a project build fails (same we do for AR failure).</li> </ul> <p>I also wonder whether the above could be done by just running a bash/python script from jenkins.</p> <p>I can probably take a look at these questions before the end of this week.</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> let's discuss this further in <a href="https://jira.opendaylight.org/browse/RELENG-119" title="Run (something like?) the bot directly on existing multipatch job?" class="issue-link" data-issue-key="RELENG-119"><del>RELENG-119</del></a> ?</p> Blocks TSC-99 RELENG-100 Relates RELENG-120 RELENG-103 RELENG-102 RELENG-104 RELENG-106 RELENG-107 RELENG-108 RELENG-109 RELENG-110 RELENG-111 RELENG-112 RELENG-116 RELENG-117 RELENG-118 RELENG-119 Development Rank 0|i03dyn: