-
Notifications
You must be signed in to change notification settings - Fork 22
Happy Users Page
Here is the place to declare your usage of Git Octopus and how your using it.
Quotes:
At LesFurets we were looking on how to migrate from a svn-like usage of git to a more modern one, and looking to go on daily deployment, git-flow pattern was not ideal because we wanted to have all current developments in develop but not manage the removal of problems manually and be able to not ship some work. So Arnaud had the crazy idea to recreate the develop branch continuously by merging it each time a branch changes. And I (Dimitri) had the crazy idea to let him try this with our team, and now we're Happy Octopus users, with still a lot to do, but confident to have the simpliest way to work from a developer perspective : branch from master, code, push in the branch, and that's all (merge is done automatically when the feature is verified). It's only when a conflict is detected that I'm warned. The simple dev is dead simple. Dimitri BAELI, LesFurets.com
Arnaud, and other devs : put your comments here !
Facts:
- Number of repos with git-octopus: 1 with 80 maven modules, 500k LOC
- Number of coders interacting: 25 within 4 teams (same repo)
- Number of branches in parallel: 30-50 usually
- Branches Pattern: none, we're repo based to select the features
- Specific Git setup: 1 repo for studies (non octopus), 1 repos for feature branches (all merged in octopus)
- Main satisfactions: fast to remove a blocking branch (push to studies) -- "I studified your branch"
- Main pain points: sometime octopus fails if branches are too old (and not rebased on master recently)
- Next best feature: 1 repo for releases (push to deploy)
- Fun facts: No yet (guys I need your input !)
Quotes:
Coming sun.
Facts:
- Number of repos with git-octopus: 1
- Number of coders interacting: 20 (Paris and Bangalore)
- Number of branches in parallel: 40
- Branches Pattern:
- Specific Git setup:
- Main satisfactions:
- Main pain points:
- Next best feature:
- Fun facts:
Quotes:
Why and how did you went to use git-octopus ?
Facts:
- Number of repos with git-octopus:
- Number of coders interacting:
- Number of branches in parallel:
- Branches Pattern:
- Specific Git setup:
- Main satisfactions:
- Main pain points:
- Next best feature:
- Fun facts:
Post this as an issue if wiki is not opened for modification/comment
Thank you !