Integrating Plastic into our Jenkins cloud has been difficult without this

+1

I can't add votes to indicate interest if the suggestion is closed, so what's the point in closing it if you're open to reconsidering in the future?

I second this. Well, what I would like to see, in the broadest sense, is a mechanism for downloading & installing the latest (and optionally, a specific, not necessarily the latest) version of the Plastic SCM Windows installer unattended.

This could be via Chocolatey. This could also be via a Rest API that offers download URLs to installers, and allows query with a static URL that tells you where to download the latest version (results in more glue logic but you can then point out your existing installers).

If this was not declined I'd vote for it.

I really think this is a good idea. Pipeline Engineering / Systems needs to get systems setup with automation. Many sysadmins use this in production, and it is the de-facto standard for Windows package management.

Hi Codice team! .. can we reconsider now ?

Wow, I'm a little surprised at this response. I think this tool is becoming more popular. Besides, what's it really going to take to create the package and keep it updated? It's also a good way for name recognition when people see it in the packages list. It's too bad. I think this is a bad decision.

Hey Diego,

We were checking today what to do with this one.

It sounds pretty exciting, but we're not sure if it will benefit a number of users. What do you think?

Hey, this is a pretty interesting suggestion!

Looks really promising.

Are you normally using it? I see tons of packages there, pretty interesting!