BuildState with message

[BlythMeister]

Description

• Update BuildState to include a string option for a message
• Update all listeners to work with new TraceData

This should not be considered a breaking change since the code itself states that changing TraceData is not considered a breaking change.

/// Note: Adding new cases to this type is not considered a breaking change!
/// Please consider not using a match on this type in code external to the fake repository.

Extends #2138 to prevent later conflicts on the TeamCity code so includes all commits from that PR.

[matthid]

The build is red an I noticed

apparently we shouldn't trace processes used for ci messages...

[BlythMeister]

Did I cause that...

[BlythMeister]

Oh I see the error, I backed a bit out...and missed this.

[matthid]

Can you please merge latest (build should be green again)?
I guess I should open my own PRs such that release/next is always green :/

[BlythMeister]

Hehe, it will have to wait until monday. I've not got access to my laptop until then

[matthid]

Ok, maybe I'm trying to help by sending a pr to your branch, last time I tried merging directly it looked weird in the pr...

[matthid]

(I'm also trying to debug why azure pipelines are red on all prs with this)

[BlythMeister]

I guess worst case, you could create a pr off the head of my branch and enhance like you did with the nunit one?

[matthid]

@BlythMeister not sure if you meant that but I already opened BlythMeister#2

[BlythMeister]

Merged...I hope

[matthid]

@BlythMeister almost... let me try again with BlythMeister#3 :)

[BlythMeister]

Merged again 😂

[matthid]

Lol now the diff apparently fixed itself and is now small again oO did you do things differently this time?

[BlythMeister]

I choose merge...not rebase

[matthid]

Thanks for helping out, now stuff is green again :)

[BlythMeister]

Wooooo

[matthid]

Will send a pr for all your open prs, go through all of them and start the 5.9 release

[matthid]

looks good, thanks!