Gradle commands run via gradle task does not honor logging option

Help/Discuss
1

Hi,

I have a gradle task that clones a remote repository and executes gradlew assemble in that directory. I want to change the logging level of those assemble tasks to quiet. I tried passing -q in args section but that does not seem to work at all.

project.exec {
      workingDir = tempDir
      def stdout = new ByteArrayOutputStream()
      executable = (OperatingSystem.current().isWindows()) ? 'gradlew.bat' : './gradlew'
      args 'assemble' , '-q'
      standardOutput stdout
   }

I cloned that repository and tried running gradlew assemble -q seems to quiet down the logs but does not work via above gradle task.
Is there any other way to change the loglevel for this task?
Thanks!

2

While giving -q like that should work I think, calling gradlew like that is most probably not a good idea.

If you want to use the result of that build as library, have a look at composite builds.

If you just want to start that build for some reason, better use the tooling API which is automatically available withing one build. (The tooling API, not a GradleBuild task, I wouldn’t use those for several reasons)

3

Thanks for the reply @Vampire
I tried running below as well (not using gradle executables)

project.exec {
    workingDir = tempDir
    def stdout = new ByteArrayOutputStream()
    def executableGradleCommand = (OperatingSystem.current().isWindows()) ? 'gradlew.bat' : './gradlew'
    commandLine executableGradleCommand, 'assemble', '-q'
     standardOutput stdout
  }

Still -q does not take effect.
To give you the gist the gradle task is checking compatibility with downstream projects where the upstream project publishes to maven local and then just clones remote downstream project and runs gradle assemble via gradle task.

4

That is exactly the same as you did above.
Setting commandLine sets executable to the first argument and all others as args.

With “like that” I meant the whole idea of using exec which is a very bad one.
I still recommend using the tooling API instead.