Rename drone-cache to something more generic

[spier]

drone-cache cache is not actually limited to caching workspace artifacts just for drone.

So other docker-based CI solutions can use this out of the box.

As drone-cache is just a static binary, you could even use this with other CI solutions (although we have not tried this yet).

To make it easier for users to find this tool, we would have to do some work though. e.g.

• renaming drone-cache to something more generic
• distributing drone-cache to other package management solutions, so that users out side of the container ecosystem would also find out about this

[spier]

@soundmonster Kemal mentioned that you are also using drone-cache, but not with drone?

[soundmonster]

I was checking out the new notification UI on GitHub and came across your comment 🙈 @spier

Yes, we're using drone-cache with TeamCity, and it works well! It took me an hour or so to get it running without Drone - no modifications were needed, I just had to figure out how to pass it all the configs it needs. I can contribute a short section about this for the readme.

I'm not sure this warrants a rename though, maybe adding something about "you can run this with any CI system, this is how: ..." would already be sufficient?

As for distribution outside of Docker images: the releases page has static binaries, which is already sufficient for most use-cases (and platforms). I tried the last two releases right now, but I can't get them to run on my machine. 🤔

Also, seems like adding deb/rpm generation to the GoReleaser config file is possible, albeit not straightforward.

[kakkoyun]

@soundmonster Thanks a lot for the great feedback. And I'm very happy that you utilize it :)

If we decide to rename the project for more general-purpose use, we can redirect the registry access to newly named this would keep older user CIs intact. Or we can totally fork it :) Github Actions are on the rise, even though GitHub has a built-in mechanism to cache workspaces, drone-cache still has its uses cases.

As for distribution outside of Docker images: the releases page has static binaries, which is already sufficient for most use-cases (and platforms). ... Also, seems like adding deb/rpm generation to the GoReleaser config file is possible, albeit not straightforward.

I have created an issue for possible other ways to distribute the binary, that's a great idea! #95

I tried the last two releases right now, but I can't get them to run on my machine. 🤔

We haven't released a stable version for awhile. The images that you have accessed probably just master builds. There will a new stable release v1.1.0 soonish 🤞

[spier]

@soundmonster good to see that the new GitHub Notification UI seems to have the desired effect then :)

And yes, a PR with "TeamCity setup" for the README would be awesome!

[bdebyl]

We would like to have a larger discussion surrounding usage of the plugin outside of a Drone environment (e.g. TeamCity, Jenkins, Travis/Circle CI, etc.)

[spier]

@bdebyl what did you have in mind, where do you want to have that discussion?