How can I run a gradle build across multiple servers?
Our team has a gradle multiproject consisting of well over 100 projects and growing.
This causes two problems:
- The box we run gradle build on does not have enough disk space to store all the projects in a built state at the same time
- The build takes several hours to complete
We have 16 servers at our disposal that we would like to use to reduce the build time and individual disk usage by distributing the load. After reading gradle documentation we haven't been able to find a way to do this, or find anyone else in the same boat.
We have mitigated the first problem by creating a custom task:
task release(type: GradleBuild){
tasks = ['clean', 'build', 'deploy', 'clean']
}
Running gradlew release
runs all 4 tasks for each project before moving on to the next project (though I feel like there should be a better way). Without this task, clean would run for all projects, then build would run for all and die due to lack of disk space before ever getting to deploy.
We have not found a way to mitigate the build time issue.
Is there any way for us to utilize all of our servers to distribute this massive build?
gradle
add a comment |
Our team has a gradle multiproject consisting of well over 100 projects and growing.
This causes two problems:
- The box we run gradle build on does not have enough disk space to store all the projects in a built state at the same time
- The build takes several hours to complete
We have 16 servers at our disposal that we would like to use to reduce the build time and individual disk usage by distributing the load. After reading gradle documentation we haven't been able to find a way to do this, or find anyone else in the same boat.
We have mitigated the first problem by creating a custom task:
task release(type: GradleBuild){
tasks = ['clean', 'build', 'deploy', 'clean']
}
Running gradlew release
runs all 4 tasks for each project before moving on to the next project (though I feel like there should be a better way). Without this task, clean would run for all projects, then build would run for all and die due to lack of disk space before ever getting to deploy.
We have not found a way to mitigate the build time issue.
Is there any way for us to utilize all of our servers to distribute this massive build?
gradle
add a comment |
Our team has a gradle multiproject consisting of well over 100 projects and growing.
This causes two problems:
- The box we run gradle build on does not have enough disk space to store all the projects in a built state at the same time
- The build takes several hours to complete
We have 16 servers at our disposal that we would like to use to reduce the build time and individual disk usage by distributing the load. After reading gradle documentation we haven't been able to find a way to do this, or find anyone else in the same boat.
We have mitigated the first problem by creating a custom task:
task release(type: GradleBuild){
tasks = ['clean', 'build', 'deploy', 'clean']
}
Running gradlew release
runs all 4 tasks for each project before moving on to the next project (though I feel like there should be a better way). Without this task, clean would run for all projects, then build would run for all and die due to lack of disk space before ever getting to deploy.
We have not found a way to mitigate the build time issue.
Is there any way for us to utilize all of our servers to distribute this massive build?
gradle
Our team has a gradle multiproject consisting of well over 100 projects and growing.
This causes two problems:
- The box we run gradle build on does not have enough disk space to store all the projects in a built state at the same time
- The build takes several hours to complete
We have 16 servers at our disposal that we would like to use to reduce the build time and individual disk usage by distributing the load. After reading gradle documentation we haven't been able to find a way to do this, or find anyone else in the same boat.
We have mitigated the first problem by creating a custom task:
task release(type: GradleBuild){
tasks = ['clean', 'build', 'deploy', 'clean']
}
Running gradlew release
runs all 4 tasks for each project before moving on to the next project (though I feel like there should be a better way). Without this task, clean would run for all projects, then build would run for all and die due to lack of disk space before ever getting to deploy.
We have not found a way to mitigate the build time issue.
Is there any way for us to utilize all of our servers to distribute this massive build?
gradle
gradle
asked Jan 18 at 18:57
backcabbackcab
61
61
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110962%2fhow-can-i-run-a-gradle-build-across-multiple-servers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110962%2fhow-can-i-run-a-gradle-build-across-multiple-servers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown