Project state

[yafanasiev]

First of all, let me say that the project is just amazing. It is very elegant in a way it uses Github's Deployments API.

We are considering deliverybot as our main CD tool (as well as migrating to Github Actions from Jenkins). But it is not clear if it is still alive or kind of left out after going open source. It will be a shame to see such a great idea to die.

I am willing to contribute, having some experience with JS and TS, and mostly with ops side of things. We are going to try to host deliverybot in AWS, so if it works, I will be happy to add guides and scripts to the repository.

@colinjfw @imella mentioning you as the project contributors.

[missedone]

i have the same concern, would like see what's the plan of deliverybot?
we're going to migrate to Github Actions.

[colinjfw]

Thanks for reaching out @yafanasiev. Since going open source I haven't had as much time as I originally planned to really work on the core of Deliverybot as much as I wanted. However, the app is still functioning day to day and people are using it to deploy code, it would be great if we could get it working on AWS!

As far as the project state I don't think it will die really ever, that's the beauty of open source, it will live as long as people want to come to the repository and contribute. I myself have not had the time commitments to invest in it though.

I'm happy to invest time in helping you get started as a contributor, let me know what I can do.

[porterde]

I echo the thanks to @colinjfw and @imella. I've been using Deliverybot across several small projects since the beginning of the year. I like the simplicity and single focus, and it has worked perfectly. It was always surprising that this isn't a native feature of GitHub Actions, and I'd almost expected GitHub to buy you out!

@yafanasiev I agree it would be great to get some public information on self-hosting ahead of September. I've had a lot of success using AWS CDK to automate AWS infra deployments and I'd be happy to contribute.

@colinjfw Are you able to share anything about how app.deliverybot.dev is setup currently?

[spawn-guy]

i'm willing to contribute. 'cause just a few months ago i migrated Jenkins workloads to GH-Workflows and deliverybot acts like a charm :) but this deprecation message bothers me and i see not so much progress here :/

looking forward helping out with this project (if needed)

[tapsboy]

Excellent project. Disappointed that it is going away soon.

Some of the functionality here can be replaced with Slack Slash commands + workflow_dispatch and repository_dispatch, but the whole UI, metrics and an integrated solution this tool provides is solid

happy to help in any way I can

[porterde]

The blog says app.deliverybot.dev goes away in September, and is fast approaching.

@yafanasiev did you have any success running on AWS?

@colinjfw could you share anything about the current app.deliverybot.dev infra setup, and would you be able to set me up as a contributor to the project?

[spawn-guy]

here is a list of current system parts

• Frontend
  • trigger deployments manually
  • needs User Auth (GitHub)
• Backend
  • trigger deployments automatically
  • needs machine-to-machine Auth (GitHub + API-layer). possibly, GitHub-WebHook Integration is sufficient
• slack DeliveryBot
  • deployment process notification
  • trigger deployments manually
  • SlackApp Auth
  • SlackUser-to-GithubUser Auth???

am i missing something?

[colinjfw]

Hi everyone, sorry for the delay in responding here.

@porterde yes I can definitely set you up as a contributor to the project and happy to share whatever information needed for other contributors to get ramped up.

Unfortunately the setup was really designed around GCP from the start, it probably will be always easier to run there, but I think a port to AWS would really help the longevity of the project.

[colinjfw]

I will also mention on this thread: If anyone is very concerned and has a key production use case where deliverybot turning off would impact them, please reach out to me personally at [email protected].

I will be able to discuss timelines and work out a solution with you individually for migrating to an open source version and agreeing on how long we would be able to keep the public version going.

[donaldpiret]

@colinjfw just a quick clarifying question. What timeline are you currently looking at for the shut down of the hosted service? Beginning of September or more towards the end of it?
We (Sephora SEA) are currently using the hosted version of one (soon 2) of our production workloads and would love to continue using it moving forward. We're also interested in getting this set up on AWS and happy to contribute some engineering time towards making this happen.

[colinjfw]

@donaldpiret as I mentioned above I want to work out timelines with key customers individually, please reach out to me at [email protected].

[davidkarlsen]

+1 to all that's said. This project is truly awesome!
I could help out terraform a setup (a tf module) to run on AWS, but need to understand the architecture and security-model first.