[FOLIO-780] Find a better way to rebuild folio-testing Created: 16/Aug/17 Updated: 12/Nov/18 Resolved: 14/Feb/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Mike Taylor | Assignee: | Wayne Schneider |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | ci, for-next-sprint | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
In the olden tames, we had a super-convenient auto-rebuild regimen for folio-testing where every commit of a Stripes library or UI module caused a rebuild. Then we could quickly see our changes reflected on a live demo site. But we ran into issues with multiple changes to multiple repos causing folio-testing builds to overlap and eventually take down the Jenkins slave nodes. So now we just blindly do a rebuild every hour. How about this: when a commit is made, wait 120 seconds; if another commit happens in that time, restart the timer; when the timer runs down, build. (Either that, or give me back the old ability to manually start the build!) |
| Comments |
| Comment by Wayne Schneider [ 14/Feb/18 ] |
|
Mike Taylor – is this still a requirement (or nice to have) for your work? |
| Comment by Mike Taylor [ 14/Feb/18 ] |
|
I think folio-snapshot does what we need now, doesn't it? Or does it? |
| Comment by Wayne Schneider [ 14/Feb/18 ] |
|
TBH, I think we learned to live with it, and have since developed better tools (I'm thinking of ui-testing and stripescli) for devs to be able to preview their work on their own system, rather than relying on folio-testing to see the effects of integration. If folio-testing still serves an important purpose for developers, however, and if that purpose would be better served by a more flexible schedule for building, we can certainly keep this issue open. |
| Comment by Mike Taylor [ 14/Feb/18 ] |
|
I can tell you that I have not used folio-testing at all for some time. I don't know if anyone else is using it: it's probably worth asking on Slack. But my sense is that it can be retired. |
| Comment by Wayne Schneider [ 14/Feb/18 ] |
|
Thanks for the feedback, Mike Taylor. I agree, folio-testing may have outlived its purpose, but that's probably a separate issue. I'll close this one. |