Stride API support

[vkotovv]

Since Atlassian encourages all teams to migrate to Stride, I think it's pretty important to support new API. Looks like HipChat is deprecated, after you migrate your Jenkins plugin integrations with HipChat will not work with Stride.

[aldaris]

Pull requests welcomed

[vkotovv]

@aldaris ok, I see. What do you think, should this be a separate plugin or just additions to this? Because the name will be confusing I suppose.

[aldaris]

The card concept exists in Stride as well, but probably the JSON schema is going to be different. I think first the two APIs should be compared, and then see how well the new impl would fit into the existing code.

[vkotovv]

@aldaris I dig a bit into it and I think it is somewhat different. For example, we can send private messages to users through the API.

[aldaris]

That was also possible with the old API, but had some additional authorization requirements. See PR #19 for further discussions on that topic.

[vkotovv]

One major change that I've found is that it is no longer possible to send messages in HTML format anymore in Stride. Instead, you'll need to use plain text, or craft cumbersome JSON (pretty similar to Cards JSON that existed in HipChat) even for simple rich text formatting.

[kmadel]

I would think it should be a new Stride plugin

[tcrusson]

Hi all,
Tanguy from the Stride product team.
Stride is a fundamentally different product to Hipchat, and as such the APIs are very different. This definitely calls for a separate plugin. Based on user demand we've decided to build it ourselves. You can track the progress in this ticket: https://jira.atlassian.com/browse/STRIDE-1973

[aldaris]

Closing this issue, nothing to do in hipchat-plugin.