Text output from build.ps1 after summary?

[boernsen-development]

Is it somehow possible to produce text output from inside the build.ps1, which will be placed after the summary?

Example:

Build Hello ...\Hello.build.ps1
Task /Hello
Hello, World!
Done /Hello 00:00:00.01
Build succeeded. 1 tasks, 0 errors, 0 warnings 00:00:00.02

MY OUTPUT SHOULD BE HERE...

[nightroman]

Hi @boernsen-development. Do you mean with something defined in a script? This is not possible at the moment, I think.

This is probably doable as a new feature. I am very careful about adding something new, do not want IB to gradually become bloated.

Have you tried Exit-Build? It is close to what you need.

Exit-Build {
	'MY OUTPUT IS HERE'
}

task Hello {
	'Hello, World!'
}

produces:

Build Hello ...\Hello.build.ps1
Task /Hello
Hello, World!
Done /Hello 00:00:00.0099486
MY OUTPUT IS HERE
Build succeeded. 1 tasks, 0 errors, 0 warnings 00:00:00.1513418

[nightroman]

Can I somehow configure the repeated output of warnings?

Not at the moment. Let me think a little bit about this. I'll get back.

[nightroman]

I think, we may have the output of Exit-Build printed after warnings if any and right before the final summary line. There is some logic in arranging output this way. And this should not be configurable.

I'm not yet fully committed to this, there are minor drawbacks.

[boernsen-development]

I see. That would help a lot for my specific issue.

I don't know about the other use cases of the repeated warnings. The first time I saw these warnings printed again, I was confused as I am used to have console output in the order of execution. To me personally, the warnings counter in the summary would be enough to hint me to the warnings. I can see the benefit of the WARNING: <file>:<line> info though, which is very handy. Still, I would not consider this common for my daily PowerShell programming where I am used to search for the warning's text in my code base to investigate its cause if required.

Caveat: There might be other use cases I'm not aware of.

[nightroman]

Having considered so far available reasonable options, I am not going to change anything, for now at least.

In the meantime, here is the solution that should fit your requirements. It uses some IB internals but they will hardly change.

Use Exit-Build and ${*}.Warnings = @() in it. This effectively discards the collected warnings and their unwanted output.
In addition to discarding you may also have your own custom processing, e.g. still print warnings but before your final output.

[boernsen-development]

Thank you for that! This helps. Only downside is that the warnings counter in the summary becomes zero. Can I somehow maintain that by custom processing without printing the warnings?

[nightroman]

Right... well... you may print ${*}.Warnings.Count before discarding. If I have better ideas, I'll post.

[boernsen-development]

Good enough for now!

Thank you very much for your time thinking about my issue and for your project in general! 👍