Strategy for removing continouous integration on a repo - Githubissues

Overdrivr / micro-ci

Continuous Integration for embedded platforms

0 stars 0 forks source link

Strategy for removing continouous integration on a repo #43

Closed Overdrivr closed 8 years ago

Overdrivr commented 8 years ago

If a users wants to remove micro-ci on a repo, there are different possible use cases:

Users delete a repo through REST API. This means removing all repo/commit/job/build data from the database
Users activate and deactivate a repo through REST API. First time a repo is activated is it persisted into the database. Concretely, this means the user cannot remove its data from the database for now

Which one do you think we should implement @DanFaudemer ? I personnally have a preference for the second

Overdrivr commented 8 years ago

To be listed in official integrations, Github recommends deleting all user information 60 days after a user leaves micro-ci. Repositories should be kepts inside the database and deleted 60 days after a user leaves the platform. In the meantime, an activate / deactivate api should be implemented.

This is done in #54 and #111