Modify things so that you can have two forks of the same project in the same Octopusci

[drewdeponte]

Right now we can technically do this now that @jbaugh has added his git clone fix so that repos are cloned to reponame-owner instead of reponame. However, this doesn't help organize the data correctly in terms of owners. Therefore, we need to update the URIs and the data storage to store info about the owner of the repository as well.

This is necessary right now because if you have two forks of the same app running in the same octopusci they will fall in the same list in the data store. That means when we go to check status on the most recent build of a repo we won't necessarily get the correct data.

@jbaugh maybe we need to fix this before we add your feature.

[kfatehi]

Ah yes this is important.
Currently I am using the workflow of having my collaborator fork the main project and make commits (which I would like to also track on octopusci) so now I know it will fail.

[drewdeponte]

Actually, if you read above it will currently work. It is just that some of the features don't support it. They are not critical features anyways. We have our designers setup with forks at RealPractice and their changes on their forks go into Octopus-CI just like everyone else's. Just have to add another entry to the projects list with the repo url of the fork and a different owner.

[kfatehi]

Which features?

[drewdeponte]

Functionally everything works, the only thing that is kind of off is that the logic for determining if the master branch was pushed to is triggered in both cases. If the actual root repos master branch is pushed to or the fork of the root repos master branch is pushed to.

This basically means that the e-mail you have setup as the default e-mail will get the notifications if the forks push to their masters.