Mixing
Gradle: find and build all projects in folder
I have a folder with a lot of projects inside it (too much to manually write build files for them)
The projects are mostly in a flat layout:
root
-project 1
-project 2
-project 3
-project 4
-project 5
( -project 5.1)
But can be nested as shown above, and I need to account for this.
Ideally the following should happen:
I can run
user@user:/root gradle buildand every project in the directory shoudl be built as long as it contains a gradle build fileif a build fails just continue with the next one
How can I make this possible ?
gradle build
asked Nov 22 '18 at 10:08
zythonzython
4621726
add a comment |
I have a folder with a lot of projects inside it (too much to manually write build files for them)
The projects are mostly in a flat layout:
root
-project 1
-project 2
-project 3
-project 4
-project 5
( -project 5.1)
But can be nested as shown above, and I need to account for this.
Ideally the following should happen:
I can run
user@user:/root gradle buildand every project in the directory shoudl be built as long as it contains a gradle build fileif a build fails just continue with the next one
How can I make this possible ?
gradle build
asked Nov 22 '18 at 10:08
zythonzython
4621726
add a comment |
I have a folder with a lot of projects inside it (too much to manually write build files for them)
The projects are mostly in a flat layout:
root
-project 1
-project 2
-project 3
-project 4
-project 5
( -project 5.1)
But can be nested as shown above, and I need to account for this.
Ideally the following should happen:
I can run
user@user:/root gradle buildand every project in the directory shoudl be built as long as it contains a gradle build fileif a build fails just continue with the next one
How can I make this possible ?
gradle build
asked Nov 22 '18 at 10:08
zythonzython
4621726
I have a folder with a lot of projects inside it (too much to manually write build files for them)
The projects are mostly in a flat layout:
root
-project 1
-project 2
-project 3
-project 4
-project 5
( -project 5.1)
But can be nested as shown above, and I need to account for this.
Ideally the following should happen:
I can run
user@user:/root gradle buildand every project in the directory shoudl be built as long as it contains a gradle build fileif a build fails just continue with the next one
How can I make this possible ?
gradle build
gradle build
asked Nov 22 '18 at 10:08
zythonzython
4621726
asked Nov 22 '18 at 10:08
zythonzython
4621726
asked Nov 22 '18 at 10:08
zythonzython
4621726
asked Nov 22 '18 at 10:08
zythonzython
4621726
asked Nov 22 '18 at 10:08
zythonzython
4621726
4621726
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
How about this one-liner (not tested):
find . -maxdepth 1 -type d ( ! -name . ) -exec bash -c "cd '{}' && gradle build || true" ;
Or, more verbose:
dirs=($(find . -type d))
for dir in "${dirs[@]}"; do
cd "$dir"
gradle build || true
done
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
add a comment |
I came up with a working solution:
def flist =
// change to you workspace name
new File('./Workspace').eachDir {
//blacklist any folders you want
if (it.name !='.gradle' && it.name != 'master' && it.name!= 'Build-All') {
flist << it.name
}
}
// build task objects
flist.each { folder ->
task "${folder}"(type: GradleBuild) {
buildFile = "./Workspace/"+ folder + "/build.gradle"
dir = './' + folder
tasks = ['build']
}
}
// create super task
task (all, dependsOn: flist) {
}
You need to invoke it as such in the root directory: gradle :all --continue this has the benefit that any failing project builds will not halt the other builds.
Another bonus is that gradle gives a neat report about all failing builds.
answered Nov 26 '18 at 12:48
zythonzython
4621726
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%2f53428477%2fgradle-find-and-build-all-projects-in-folder%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
How about this one-liner (not tested):
find . -maxdepth 1 -type d ( ! -name . ) -exec bash -c "cd '{}' && gradle build || true" ;
Or, more verbose:
dirs=($(find . -type d))
for dir in "${dirs[@]}"; do
cd "$dir"
gradle build || true
done
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
add a comment |
How about this one-liner (not tested):
find . -maxdepth 1 -type d ( ! -name . ) -exec bash -c "cd '{}' && gradle build || true" ;
Or, more verbose:
dirs=($(find . -type d))
for dir in "${dirs[@]}"; do
cd "$dir"
gradle build || true
done
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
add a comment |
How about this one-liner (not tested):
find . -maxdepth 1 -type d ( ! -name . ) -exec bash -c "cd '{}' && gradle build || true" ;
Or, more verbose:
dirs=($(find . -type d))
for dir in "${dirs[@]}"; do
cd "$dir"
gradle build || true
done
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
How about this one-liner (not tested):
find . -maxdepth 1 -type d ( ! -name . ) -exec bash -c "cd '{}' && gradle build || true" ;
Or, more verbose:
dirs=($(find . -type d))
for dir in "${dirs[@]}"; do
cd "$dir"
gradle build || true
done
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
answered Nov 22 '18 at 23:32
madheadmadhead
14.7k1385124
14.7k1385124
add a comment |
add a comment |
I came up with a working solution:
def flist =
// change to you workspace name
new File('./Workspace').eachDir {
//blacklist any folders you want
if (it.name !='.gradle' && it.name != 'master' && it.name!= 'Build-All') {
flist << it.name
}
}
// build task objects
flist.each { folder ->
task "${folder}"(type: GradleBuild) {
buildFile = "./Workspace/"+ folder + "/build.gradle"
dir = './' + folder
tasks = ['build']
}
}
// create super task
task (all, dependsOn: flist) {
}
You need to invoke it as such in the root directory: gradle :all --continue this has the benefit that any failing project builds will not halt the other builds.
Another bonus is that gradle gives a neat report about all failing builds.
answered Nov 26 '18 at 12:48
zythonzython
4621726
add a comment |
I came up with a working solution:
def flist =
// change to you workspace name
new File('./Workspace').eachDir {
//blacklist any folders you want
if (it.name !='.gradle' && it.name != 'master' && it.name!= 'Build-All') {
flist << it.name
}
}
// build task objects
flist.each { folder ->
task "${folder}"(type: GradleBuild) {
buildFile = "./Workspace/"+ folder + "/build.gradle"
dir = './' + folder
tasks = ['build']
}
}
// create super task
task (all, dependsOn: flist) {
}
You need to invoke it as such in the root directory: gradle :all --continue this has the benefit that any failing project builds will not halt the other builds.
Another bonus is that gradle gives a neat report about all failing builds.
answered Nov 26 '18 at 12:48
zythonzython
4621726
add a comment |
I came up with a working solution:
def flist =
// change to you workspace name
new File('./Workspace').eachDir {
//blacklist any folders you want
if (it.name !='.gradle' && it.name != 'master' && it.name!= 'Build-All') {
flist << it.name
}
}
// build task objects
flist.each { folder ->
task "${folder}"(type: GradleBuild) {
buildFile = "./Workspace/"+ folder + "/build.gradle"
dir = './' + folder
tasks = ['build']
}
}
// create super task
task (all, dependsOn: flist) {
}
You need to invoke it as such in the root directory: gradle :all --continue this has the benefit that any failing project builds will not halt the other builds.
Another bonus is that gradle gives a neat report about all failing builds.
answered Nov 26 '18 at 12:48
zythonzython
4621726
I came up with a working solution:
def flist =
// change to you workspace name
new File('./Workspace').eachDir {
//blacklist any folders you want
if (it.name !='.gradle' && it.name != 'master' && it.name!= 'Build-All') {
flist << it.name
}
}
// build task objects
flist.each { folder ->
task "${folder}"(type: GradleBuild) {
buildFile = "./Workspace/"+ folder + "/build.gradle"
dir = './' + folder
tasks = ['build']
}
}
// create super task
task (all, dependsOn: flist) {
}
You need to invoke it as such in the root directory: gradle :all --continue this has the benefit that any failing project builds will not halt the other builds.
Another bonus is that gradle gives a neat report about all failing builds.
answered Nov 26 '18 at 12:48
zythonzython
4621726
answered Nov 26 '18 at 12:48
zythonzython
4621726
answered Nov 26 '18 at 12:48
zythonzython
4621726
answered Nov 26 '18 at 12:48
zythonzython
4621726
4621726
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%2f53428477%2fgradle-find-and-build-all-projects-in-folder%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
