Skip to content
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.

Add container for shipit_upliftbot, or kill it #216

Closed
bhearsum opened this issue Mar 9, 2017 · 1 comment
Closed

Add container for shipit_upliftbot, or kill it #216

bhearsum opened this issue Mar 9, 2017 · 1 comment

Comments

@bhearsum
Copy link
Contributor

bhearsum commented Mar 9, 2017

The docker-compose being added in #207 doesn't do anything for shipit_upliftbot, because I was told that it might be going away. If it is, this is a no-op. If it's going to continue to exist, we should run it as part of the shipit family of apps. This might not be easy, because part of its job is to make changes to external production servers...so we may need a way to mock those parts out.

@La0
Copy link
Contributor

La0 commented Mar 9, 2017

I don't think it will be killed anytime soon, as @sylvestre wants to add more features and even expand towards multiple bots (static analysis, automated merge tests, bugzilla reports through comments, ...).
However, it may evolve into a separate project at some point.

@garbas garbas closed this as completed Jul 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants