Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MarathonRunTask outputs are not defined #691

Open
ZakTaccardi opened this issue Oct 8, 2022 · 0 comments
Open

MarathonRunTask outputs are not defined #691

ZakTaccardi opened this issue Oct 8, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@ZakTaccardi
Copy link

I have to input Marathon's JUnit XML to another downstream finalizer task, but the MarathonRunTask does not make this easy because the output directory for it is not explicitly defined.

The following is defined, but it does not seem usable?

var fakeLockingOutput = layout.buildDirectory.file("fake-marathon-locking-output")

There's:

val extensionConfig = marathonExtension.get()
val baseOutputDir = extensionConfig.baseOutputDir?.let { File(it) } ?: layout.buildDirectory.file("reports/marathon").get().asFile
val output = File(baseOutputDir, flavorName.get())

Which I could duplicate the logic for, but it would be brittle. If the MarathonRunTask could expose a Provider<Directory> as output - that would be much preferred/appreciated!

@ZakTaccardi ZakTaccardi added the enhancement New feature or request label Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant