Gradle Build Cache after gradle clean
According to Built-in cacheable tasks the gradle task "test" supports build caching. I wonder how the build cache works, if I run gradle clean between 2 gradle test executions. Since gradle clean deletes the test results (assuming these are parts of the output of gradle test in the build cache context), the cache won't work here. Is that correct?
Some background:
We've got a multi-project setup in gradle and would like to skip tests in subprojects, when there were no changes.
caching gradle
asked Nov 22 '18 at 13:05
ndueckndueck
107111
add a comment |
According to Built-in cacheable tasks the gradle task "test" supports build caching. I wonder how the build cache works, if I run gradle clean between 2 gradle test executions. Since gradle clean deletes the test results (assuming these are parts of the output of gradle test in the build cache context), the cache won't work here. Is that correct?
Some background:
We've got a multi-project setup in gradle and would like to skip tests in subprojects, when there were no changes.
caching gradle
asked Nov 22 '18 at 13:05
ndueckndueck
107111
add a comment |
According to Built-in cacheable tasks the gradle task "test" supports build caching. I wonder how the build cache works, if I run gradle clean between 2 gradle test executions. Since gradle clean deletes the test results (assuming these are parts of the output of gradle test in the build cache context), the cache won't work here. Is that correct?
Some background:
We've got a multi-project setup in gradle and would like to skip tests in subprojects, when there were no changes.
caching gradle
asked Nov 22 '18 at 13:05
ndueckndueck
107111
According to Built-in cacheable tasks the gradle task "test" supports build caching. I wonder how the build cache works, if I run gradle clean between 2 gradle test executions. Since gradle clean deletes the test results (assuming these are parts of the output of gradle test in the build cache context), the cache won't work here. Is that correct?
Some background:
We've got a multi-project setup in gradle and would like to skip tests in subprojects, when there were no changes.
caching gradle
caching gradle
asked Nov 22 '18 at 13:05
ndueckndueck
107111
asked Nov 22 '18 at 13:05
ndueckndueck
107111
asked Nov 22 '18 at 13:05
ndueckndueck
107111
asked Nov 22 '18 at 13:05
ndueckndueck
107111
asked Nov 22 '18 at 13:05
ndueckndueck
107111
107111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The build cache does not store the task outputs in the project workspace, but in a local or remote build cache. The local build cache lives in the Gradle user home.
So the cache will work, even if you run clean, since the outputs of the test task are stored in the build cache and are not removed from there by running clean.
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53431688%2fgradle-build-cache-after-gradle-clean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The build cache does not store the task outputs in the project workspace, but in a local or remote build cache. The local build cache lives in the Gradle user home.
So the cache will work, even if you run clean, since the outputs of the test task are stored in the build cache and are not removed from there by running clean.
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
add a comment |
The build cache does not store the task outputs in the project workspace, but in a local or remote build cache. The local build cache lives in the Gradle user home.
So the cache will work, even if you run clean, since the outputs of the test task are stored in the build cache and are not removed from there by running clean.
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
add a comment |
The build cache does not store the task outputs in the project workspace, but in a local or remote build cache. The local build cache lives in the Gradle user home.
So the cache will work, even if you run clean, since the outputs of the test task are stored in the build cache and are not removed from there by running clean.
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
The build cache does not store the task outputs in the project workspace, but in a local or remote build cache. The local build cache lives in the Gradle user home.
So the cache will work, even if you run clean, since the outputs of the test task are stored in the build cache and are not removed from there by running clean.
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
answered Dec 12 '18 at 22:34
wolfs42wolfs42
49625
49625
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53431688%2fgradle-build-cache-after-gradle-clean%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
