Defining the model - Githubissues

paztek / ci-boulette

The goal is to make a simplistic web app running on the server receiving these web hooks concerning one or many Github repositories. This app would respond by running system commands locally to help continuously deploy apps on the server or maintain up-to-date dependencies to libraries used by apps running on the server.

1 stars 0 forks source link

Defining the model #5

Open paztek opened 11 years ago

paztek commented 11 years ago

We need to complete the design of the model to implement new features.

"Commands" are the system commands the app should execute after receiving a push. A repository should be related to N Commands.

"Pushes" from Github should be stored in the DB (with all the objects it is composed of : Commits, etc...). A repository should be related to N pushes.

"Executions" are individual report of the execution of a command (status : SUCCESS / FAILED, exec time, etc...). Each Push relates to N Executions each one related to a Command.

paztek commented 11 years ago

Make sure (with the command orm:validate-schema) that your mapping is valid.

DamnDam commented 11 years ago

and each Command relates to N Executions, each one related to a Push, I presume.

paztek commented 11 years ago

Closed by e284a06ed1a8a1aa36f3ac31e8861a09ad4ed685

DamnDam commented 11 years ago

Github may send pushes relating to the same commits. The model should be designed to avoid creating commits duplicates.

The ID for commits should be the hash, as it is used by git.
Commits may link to many pushes
On push, the model should try to find the existing commits on DB, link the new push to them, and add the remaining commits.

paztek commented 11 years ago

I can't see how different pushes can relate to same commits. In which scenario ?
I agree with the hash of a commit being its ID.