ProGet: Feature Request: Customizable Notifications on events

MaxCascone

As a ProGet user performing Package Promotions/Repackaging,
I want to see a popup showing a custom message when I complete a Promotion/Repackage action,
So I can be reminded to go into GitHub and tag the source commit appropriately.

As a ProGet Admin,
I want to set up custom notification messages that are shown in popups when specific actions are performed by users,
So I can remind them of any other actions they need to take relating to that action.

stevedennis

Hi @mcascone ,

Thanks for this suggestion, too! Along the same vein as ProGet: Feature Request: native integration with GitHub to perform automated tasks, this is more "process control/workflow management", and not something ProGet is built for.

If you develop a Manual Package Promotions/Repackaging Process (for example, when automation doesn't make sense), then that process should be a SOP document/checklist that lives somewhere (wiki, sharepoint, etc), along side other change management processes.

A bit outside our scope, but I always recommend SOP for organizations of all sizes (even 1). Helps with everything from onboarding to consistency to process improvement. Doesn't need to be anything more than a simple .txt file on Sharepoint with some basic instructions. It can always be improved later.

BuildMaster does have this built-in for CI/CD-related processes, so a lot of SOP we see are mostly "follow the pipeline/prompts in BuildMaster", etc.

MaxCascone

Yuck, sharepoint?

I hear you; SOPs tend to wither and gather dust as the processes evolve, though, in my experience. That's why, while we get some real-world use of the manual promotion and versioning processes, in the hope that repeatable, reliable patterns emerge that we can then automate, we want to remind people in-flight what the process is supposed to be, so they don't make mistakes.

thanks for the reply!

stevedennis

@mcascone ha! I guess I should say "Onedrive" or whatever it's called -- basically a place to version it as simply as possible.

Just FYI --- we're a pretty small team here, and had that same "gathering dust" worry. But our SOP are a collection of .txt and .ppt files in one of two places:

"training" folder, which new staff use to follow common process (e.g. change management process)
"program" folder, which describes a process someone is owns and is responsible or reporting/improving upon (e.g. release process)

It was a little bit of a culture shift for everyone, but now it's great to "not have to think" about the steps (just jump back to the folder), which also benefits new staff learning process (or someone covering for another person).

MaxCascone

Thanks for the insight into your process on this. It's interesting.
For our part, I put everything I can on Confluence. I probably like Confluence as much as I hate Sharepoint and OneNote. (At least with OneNote I can actually create a document successfully.)

Flow charts help a lot, which are super easy to create and maintain with the Draw.io integration into Confluence.

I like confluence for its deep-linking into Jira as well.