Git

From ago control wiki
(Difference between revisions)
Jump to: navigation, search
m (Hari moved page Git Branching to Git)
Line 1: Line 1:
http://nvie.com/posts/a-successful-git-branching-model/
+
= Account =
 +
To request an account join #agocontrol-devel on freenode and talk to one of the [[Core Developers]]. We'll add self-enrollment soon. If you had an account on the old git, please go here to reset your password (this is needed because the old apache md5 hash can't be used with the new system): http://agocontrol.com/account
 +
= Services =
 +
== Repository ==
 +
The new repository runs on our local gitlab installation. You can currently access it here:
 +
http://agocontrol.com:8081
 +
== Continuous Integration ==
 +
=== Buildbot ===
 +
Buildbot is currently used to build packages on every commit. It runs on our builder system: http://builder.aboliton.at:8010
 +
=== Gitlab CI ===
 +
Gitlab-CI runs here: http://agocontrol.com:8082
 +
This has integration into Gitlab. The nice thing is that every commit will have a build status (success/pending/failed). The downside is that it is far not as flexible as Buildbot. So this will not replace buildbot but augment it for quick testing of change sets.
 +
=== Jenkins ===
 +
A test installation is set up and allows login with the developer account. Contact hari on irc for further details.
 +
= Branching =
 +
I'd propose to adopt the branching model explained here: http://nvie.com/posts/a-successful-git-branching-model/
  
 
[[File:GIT_Branching.png]]
 
[[File:GIT_Branching.png]]
 +
 +
Further discussion pending.

Revision as of 11:41, 5 April 2014

Contents

Account

To request an account join #agocontrol-devel on freenode and talk to one of the Core Developers. We'll add self-enrollment soon. If you had an account on the old git, please go here to reset your password (this is needed because the old apache md5 hash can't be used with the new system): http://agocontrol.com/account

Services

Repository

The new repository runs on our local gitlab installation. You can currently access it here: http://agocontrol.com:8081

Continuous Integration

Buildbot

Buildbot is currently used to build packages on every commit. It runs on our builder system: http://builder.aboliton.at:8010

Gitlab CI

Gitlab-CI runs here: http://agocontrol.com:8082 This has integration into Gitlab. The nice thing is that every commit will have a build status (success/pending/failed). The downside is that it is far not as flexible as Buildbot. So this will not replace buildbot but augment it for quick testing of change sets.

Jenkins

A test installation is set up and allows login with the developer account. Contact hari on irc for further details.

Branching

I'd propose to adopt the branching model explained here: http://nvie.com/posts/a-successful-git-branching-model/

GIT Branching.png

Further discussion pending.

Personal tools