Hi,
I'm glad to see this thread!
Am 12.03.19 um 10:52 schrieb Andrey Loskutov:
[...]
It would be great if the people contributing patches would also verify that the
patches do not cause new regressions.
Please after you have merged something (even if Gerrit is OK), consider to
verify that your changes do not cause regressions on the next day SDK build.
[...]
(Unfortunately, my insights into the Eclipse build process is limited.)
For me an ideal build infrastructure would have two properties:
(1) It makes test failures visible (that works already :-) ).
(2) All test failures are "immediately" visible to a
contributor/committer/... while contributing a change so he can improve
the change before others see the failed tests. That seems to involve
"waiting" for the SDK build right now and it is not only the contributor
who sees the failures.
Do others feel that (2) should/could be improved here? Does Bugzilla
have issues for proposing solutions for (2) or even solving (2)? Is
anyone working on this?
Thanks!
Sebastian
_______________________________________________
platform-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
