[RELENG-101] New "Weather Item" process with full preparation on topic and verification instead of breaking the world Created: 26/Apr/18 Updated: 09/May/18 |
|
| Status: | Open |
| Project: | releng |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Fluorine |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Description |
|
This issue is to organize the work around the https://lists.opendaylight.org/pipermail/integration-dev/2018-April/011768.html idea to have a new "Weather Item" process with full preparation on topic and verification instead of breaking the world. The currently planned weather items that we should try this against are listed on https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10303. |
| Comments |
| Comment by Michael Vorburger [ 30/Apr/18 ] |
|
ecelgp how about we track what you posted above in That way we can use this JIRA for the new process in general. |
| Comment by Luis Gomez [ 30/Apr/18 ] |
|
Sure I moved the content to |
| Comment by Michael Vorburger [ 02/May/18 ] |
|
https://lists.opendaylight.org/pipermail/daexim-dev/2018-May/000156.html has an example of how I envision this working... |
| Comment by Luis Gomez [ 02/May/18 ] |
|
Cool, is the mail to project sent automatically or for now someone has to extract build error and send to project? |
| Comment by Michael Vorburger [ 07/May/18 ] |
|
currently semi-manual - the https://github.com/vorburger/opendaylight-bot code that is currently running on http://opendaylight-bot-opendaylight-bot.6923.rh-us-east-1.openshiftapps.com 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. |
| Comment by Luis Gomez [ 07/May/18 ] |
|
I wonder whether we could enhance the existing multipatch job to:
I also wonder whether the above could be done by just running a bash/python script from jenkins. I can probably take a look at these questions before the end of this week. |
| Comment by Michael Vorburger [ 08/May/18 ] |
|
ecelgp let's discuss this further in |