New "Weather Item" process with full preparation on topic and verification instead of breaking the world
(RELENG-101)
|
|
| Status: | Open |
| Project: | releng |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
For now, The Bot just produces that Magic String for the multipatch job - and I I manually put it into https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-fluorine/build. Perhaps there is a way to make a link to that "Build with Parameters" page and have the {{ PATCHES_TO_BUILD}} automatically filled in? zxiiro or rovarga or skitt or jluhrsen or dfarrell07, have you ever seen anything like that? Even cooler, if The Bot had a Jenkins login (or I gave it mine), there may be some REST API in Jenkins that it could even just directly kick off a parametrized multipatch a job itself? This would also open the door to it actually knowing the resulting Build Number (currently it does not yet; I do this manually) - which would be useful in RELENG-116. |
| Comments |
| Comment by Michael Vorburger [ 07/May/18 ] |
|
More ideas for further Jenkins integration from the (now closed)
|
| Comment by Jamo Luhrsen [ 09/May/18 ] |
|
so can we get this bot running as an actual jenkins job as a first step? I didn't really keep track of how the |
| Comment by Michael Vorburger [ 22/May/18 ] |
|
Things move fast, and this point/idea is already moot with This issue really is about actually kicking off such jobs now. I think The Bot can do that: |