@greg any chance of this happening within the next month? If not what can be done to speed that up? I have no knowledge of the deploy process so have no idea how trivial this would be nor whether it needs to be manual. I'm keen to report back to the reading team whether we can expect this to happen any time soon.

It all depends on what you mean by "this". :) What'd you have in mind with "generating a url we can share with each deployment"? A jenkins build URL? or something fancier?

Since this is new and unplanned work, and we're already rushing to finish everything we've committed to (with other interruptions along the way) before the EOQ (aka EOM), I can't make a commitment for any ETA right now (just like any other team has to say when new unplanned work comes up). But...

I'll talk with the team today and see what they think.

I think right now something simple along the lines of this would be a good start:

"mediawiki 1.26 was deployed today to the cluster. At the time of deployment 3/200 browser tests were failing: <link>"

(either posted to wikitech or on a wiki page somewhere that we can subscribe to)

Ah, I see.

We'll put this in our "best effort, but no promise" category for the next couple months; I really don't want to jeopardize our other work right now that we've made commitments to. (/me stops repeating himself)

I think we all agree it's a great idea, though, which is why we're even putting it in the "best effort" category :)

@greg replaced by release pipeline?

In T111545#3298099, @zeljkofilipin wrote:

@greg replaced by release pipeline?

Not entirely.