You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For instance when rebuilding a failed build, I would like to rebuild the "reference OK" build : means the last one that was green.
We won't be able to do this completely, because inputs are maybe not available (commit or deps) but we could at least try to emulate some parts : the sparrowfile and sparky.yaml and therefore, as it is inside these files, the docker image and/or host target (but not its state of course).
It requires to store this "last OK config" somehow (versioning ? db ?).
It's not 100% clear in my mind and it's a nice to have, but I really think it has great added value for end user.
On end user side, I would like to have an option to start 2 builds at the same time, one behing the reference and the other the current.
I would say yes, but since it will just start 2 individual builds, it's not perfect. I would like to have somewhat like a link between them (for the launch and the analysis), but don't know exactly on which form (yet).
On end user side, I would like to have an option to start 2 builds at the same time, one behing the reference and the other the current.
I do understand the idea, I am not sure if we can make a really clear UX on that ... Right now like I said we at least can find the last successful build and rebuild it. Maybe we can think of last successful build / last build / rebuild last successful build / links on project page as a simple start ?
For instance when rebuilding a failed build, I would like to rebuild the "reference OK" build : means the last one that was green.
We won't be able to do this completely, because inputs are maybe not available (commit or deps) but we could at least try to emulate some parts : the sparrowfile and sparky.yaml and therefore, as it is inside these files, the docker image and/or host target (but not its state of course).
It requires to store this "last OK config" somehow (versioning ? db ?).
It's not 100% clear in my mind and it's a nice to have, but I really think it has great added value for end user.
On end user side, I would like to have an option to start 2 builds at the same time, one behing the reference and the other the current.
Should play well with #32 😀
The text was updated successfully, but these errors were encountered: