Re: [DISCUSS] Need feedback on Azure-based build system

2019-12-13 Thread Robert Metzger
Thanks for your feedback. I will then go for option B. On Fri, Dec 13, 2019 at 2:51 PM Till Rohrmann wrote: > Thanks for starting this discussion Robert. > > I can see benefits for both options as already mentioned in this thread. > However, given that we already have the profile splits and that

Re: [DISCUSS] Need feedback on Azure-based build system

2019-12-13 Thread Till Rohrmann
Thanks for starting this discussion Robert. I can see benefits for both options as already mentioned in this thread. However, given that we already have the profile splits and that it would considerably decrease feedback for developers on their personal Azure accounts, I'd be in favour of option B

Re: [DISCUSS] Need feedback on Azure-based build system

2019-12-13 Thread Aljoscha Krettek
It’s a though question. One the one hand I like less complexity in the build system. But one of the most important things for developers is fast iteration cycles. So I would prefer the solution that keeps the iteration time low. Best, Aljoscha > On 13. Dec 2019, at 14:41, Chesnay Schepler wro

Re: [DISCUSS] Need feedback on Azure-based build system

2019-12-13 Thread Chesnay Schepler
It depends on how to define "split"; if you split by module (as we do currently) you have the same complexity as we have right now; caching of artifacts and brittle definition of splits. But there are other ways to split builds, for example into unit and integration tests; could also add end-to

Re: [DISCUSS] Need feedback on Azure-based build system

2019-12-11 Thread Robert Metzger
Some comments on Chesnay's message: - Changing the number of splits will not reduce the complexity. - One can also use the Flink build machines by opening a PR to the "flink-ci/flink" repo, no need to open crappy PRs :) - On the number of builds being run: We currently use 4 out of 10 machines offe

Re: [DISCUSS] Need feedback on Azure-based build system

2019-12-11 Thread Chesnay Schepler
Note that for B it's not strictly necessary to maintain the current number of splits; 2 might already be enough to bring contributor builds to a more reasonable level. I don't think that a contributor build taking 3,5h is a viable option; people will start disregarding their own instance and j

Re: [DISCUSS] Need feedback on Azure-based build system

2019-12-11 Thread Arvid Heise
Hi Robert, thank you very much for raising this issue and improving the build system. For now, I'd like to stick to a lean solution (= option A). While option B can greatly reduce build times, it also has the habit of clogging up the build machines. Just some arbitrary numbers, but it currently