Re: [papyrus-rt-dev] Concurrent Hudson builds

[Peter Cigéhn <peter.cigehn@xxxxxxxxx>]

Hi,

I really don't have any opinion (or insight) regarding we need concurrent builds or not. But something needs to be done with the build structure. The major flaw that whenever a change only impacts tooling, then the final product build is never triggered. So you always have to manually trigger the product build (or wait for something else to trigger the product build). So, whatever is done with build structure, I really think that this issue needs to be resolved as well.

/Peter Cigéhn

On 17 June 2017 at 13:21, Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Team,

In looking at the Disk Usage Report in our Hudson instance, it occurred to me that the report only counts the size of artifact and workspace storage for every build job. The shared Maven repository is not included in the report, nor anything else in the genie user's home directory.

We can easily maintain clean and evergreen workspaces if every build starts by wiping the workspace (a standard Hudson build option) instead of just doing a git clean. We can also try to get clever by deleting the builds' private Maven repositories on some interval so that not every build has to download all of the Tycho tooling and dependencies.

But the private Maven repositories are only necessary because we have concurrent builds on three executors. If we had only a single executor, then all of the builds could use the shared Maven repository for maximal space efficiency and that could easily be purged from time to time by a scheduled build job. They would also save some time by not having to re-download every dependency.

Do we really need concurrent builds?

Cheers,

Christian

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev