Closed peterz84 closed 2 years ago
It doesn't look like it, but combining a filter with the batch-publish, is very complex. The batchpublish is going to figure out the order by analyzing the dependencies, but now we would have to only consider a certain selection of apps .. . And there are more caveats.
I would suggests to work with folders, and copy artifacts to folders first, and then batch-publish per folder. That gives you much more control and debug-scenarios.
Every compile-step introduces a variable (you can find them in the log):
this you can use to copy to a new folder if necessary with simple powershell in the next step.
Hope that helps.
As issue #204 is closed and seems to be missing a solution, I have this question too. Is this still on the agenda? And the solution you mentioned... working with multiple folders, how to do this in the build pipeline? Is there a parameter in the ALOpsAppCompiler step to tell which folder it will be stored in as artifact?
Originally posted by @peterz84 in https://github.com/HodorNV/ALOps/issues/426#issuecomment-1085999985