I haven't really read the thread in too much detail so I apologize if
what I'll say below is silly or covered elsewhere, but since there seems
to be a proposal around replacing the try syntax with machines figuring
out what jobs are needed for a push (presumably based on what changed in
the push), here is a use case that may not be satisfied if we do down
that route:
Developer pushes to try, runs N jobs, M << N jobs fail, developer
realizes her mistakes, fixes, wants to push to try but because of the
nature of the fix only a run on those M jobs is now needed, but if the
machines want to figure things out, they may pick a number K where N > K
>= M jobs to run, so developer needs to politely ask the machines to
get out of her way and let her do her job. :-)
Has this been taken into account?
Thanks,
Ehsan
On 06/02/2017 04:30 PM, Dustin Mitchell wrote:
I wrote up
https://docs.google.com/document/d/1kEEUC3ETCIerOxYDoRRZSEFspunJgU331CX2wwkFZ_8/edit
It's not a particularly ambitious text, aiming to capture a consensus
rather than propose something new. It's also worth repeating that this
is not a proposal for a big new project, but a design strategy to
guide work that is occurring anyway!
I omitted discussion of AFFECTS, since it's more detailed than a
"design strategy". I did include some of the important factors that
we've discussed here, and focused the goals a little more.
Please have a look and add comments!
Dustin
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
