-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add templates for Stride #100
Comments
woot! Issue number 100. Lucky you. Yeah. I had started working on custom headers, and also a project to allow sharing of templates. But then forgot to push to github before I left for six weeks travelling for work. The plan for that project is to be able to share your templates with other users via a pull request. I have made some small tweaks to the API and written an export script (an early version was pushed). I have started on the import script, but it's not ready yet. obviously I didn't get to work on that whilst away either due to lack of a push :-( Whilst away I did do some work on the testing ticket #79 but I'm back now (albiet a bit jet-lagged), so will dig out the branch for #95 and rebase that on top. I might get some time on the weekend to progress it, but the code is pretty yuck at the integration point, so I am needing to do some cleanup there. |
If you see a nice looking Stride message, can you add screenshot of it, and I could try to replicate it. |
This is useful for building payloads: |
I think the "Panel" node type seems appropriate for these sorts of notifications. However, for whatever reason, it doesn't look like Stride has implemented the "error" or "success" panel types in the Stride client yet (even though they are supported according to the documentation). However, the warning, info, and note types are implemented. Here's what that looks like in the room: Here's the JSON I'm sending the Stride API:
|
Thanks. I will play with that over the weekend if I get chance. |
Here is a first go at a simple stride template. Not a box model, but certainly something we can build on. The test version I just posted on the other ticket works for import/export via the REST API, and has support for Bearer auth, and Headers. I imagine a full version of the box one would have content more like this one I did for slack: |
Can you have more than one column in the Stride box? |
I don't think you can have columns. There is a table type (that may even work inside a panel), but it looks like client support for the table is bad. That said, I think the simple template you have that utilizes an emoji works just fine. I'm using that now, with the only modification being the addition of the Project Name (and link). |
Cool. That's a nice addition. Do you want to export it and submit a pull request or attach it to this issue? |
I've attached the templates here. I'd have preferred an Export, but I can't get curl to work against your REST API on my server due to some weird https/certificate issue I haven't been able to figure out yet - so I had to copy them manually. It'll be nice when there is UI support for importing/exporting templates. The minor modifications I made:
|
Curl -k tells it to ignore cert checking. |
Added issue #101. Will be on milestone 1.2 |
Created issue tcplugins/tcWebHooksTemplates#1 to allow setting of Also updated the curl example in the readme to include |
I have pushed your changes and a few other bits to the tcplugins/tcWebHooksTemplates repo .
|
Great! By the way, you may want to update your description in the TeamCity plugin repository to mention the sorts of things you have templates for. I was searching for phrases like "TeamCity Stride" for a couple of months with no luck - it took me a while to find your plugin because I wasn't necessarily thinking of using webhooks (even though it seems obvious in hindsight). I think there will be a lot of people searching for this solution for Stride now that their HipChat systems are being deprecated. |
Ah. Yeah. That's a good point. I'll do that and then write a blog post about it. |
It looks like you're already working on a customizable header to allow Stride's API token authorization, but it'd be really nice if you provided us with some nice Stride templates at the same time :-)
The text was updated successfully, but these errors were encountered: