Difference: GitRepositories (1 vs. 10)

Revision 102015-05-05 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Changed:
<
<
To allow LHCb users to manage special projects with GIT, we set up a small infrastructure to host user repositories.
>
>
To request git repositories, go to https://gitlab.cern.ch.
 
Changed:
<
<
In any case, since GIT is not officially supported by LHCb, you should not expect to get much help about how to use it, but here are a few useful resources:
>
>
Since GIT is not officially supported by LHCb, you should not expect to get much help about how to use it, but here are a few useful resources:
 
Line: 12 to 12
 
Changed:
<
<

Guidelines

>
>
-- MarcoClemencic - 2015-05-05

Guidelines (Obsolete)

To allow LHCb users to manage special projects with GIT, we set up a small infrastructure to host user repositories.
 

Requesting a repository

Users wanting to host a project on GIT will have to send a mail to lhcb-git-librarians@cernNOSPAMPLEASE.ch with the name they want for the repository, a short description of the project and the AFS username who should own the repository.

Revision 92013-02-14 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.

To allow LHCb users to manage special projects with GIT, we set up a small infrastructure to host user repositories.

Changed:
<
<
In any case, since GIT is not officially supported by LHCb, you should not expect to get much help about how to use it.
>
>
In any case, since GIT is not officially supported by LHCb, you should not expect to get much help about how to use it, but here are a few useful resources:

 

Guidelines

Requesting a repository

Revision 82013-01-16 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Line: 37 to 37
 

Create a new repository

Once the repository is approved, a librarian will have to issue the following commands:
Changed:
<
<
git init --bare /afs/cern.ch/lhcb/software/GIT/.git cd /afs/cern.ch/lhcb/software/GIT/.git
>
>
project= owner= repo=/afs/cern.ch/lhcb/software/GIT/${project}.git git init --bare ${repo} cd ${repo}
 git update-server-info
Changed:
<
<
afs_admin set_owner -r /afs/cern.ch/lhcb/software/GIT/.git afs_admin set_acl -r /afs/cern.ch/lhcb/software/GIT/.git rlidwka
>
>
afs_admin set_owner -r ${owner} ${repo} afs_admin set_acl -r ${repo} ${owner} rlidwka
 
Changed:
<
<
Check that the file .git/hooks/post-update.sample is executable and contains the line exec git update-server-info, then do
>
>
Check that the file ${project}.git/hooks/post-update.sample is executable and contains the line exec git update-server-info, then do
 
Changed:
<
<
cd /afs/cern.ch/lhcb/software/GIT/.git/hooks
>
>
cd ${repo}/hooks
 mv post-update.sample post-update (this last step is needed to automatically create the special files required to allow HTTP access).

Revision 72012-08-08 - ThomasHartmann

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Line: 55 to 55
 
Added:
>
>

Repository details

 -- MarcoClemencic - 14-Mar-2012 \ No newline at end of file

Revision 62012-07-19 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Line: 22 to 22
  Note that the HTTP access is read-only.
Added:
>
>
Suggestion: with git it is possible to use two different URLs for fetch and push operations, which is very handy with our setup. What you have to do is:
git clone http://cern.ch/lhcbproject/GIT/<Project>.git
cd <Project>
git remote set-url --push origin ssh://lxplus.cern.ch/afs/cern.ch/lhcb/software/GIT/<Project>.git
 

Infrastructure

The AFS directory /afs/cern.ch/lhcb/software/GIT will point to a dedicated backed up volume and will be writeable only to Librarians.

Revision 52012-06-29 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Line: 20 to 20
 
Changed:
<
<
Note that the HTTP access is read-only, and, because of the limitations of GIT over HTTP, the pushed commits may not be visible for some time (~1-2h).
>
>
Note that the HTTP access is read-only.
 

Infrastructure

The AFS directory /afs/cern.ch/lhcb/software/GIT will point to a dedicated backed up volume and will be writeable only to Librarians.
Line: 36 to 36
 afs_admin set_owner -r /afs/cern.ch/lhcb/software/GIT/.git afs_admin set_acl -r /afs/cern.ch/lhcb/software/GIT/.git rlidwka
Changed:
<
<

Regular tasks

The following regular (ACRON) tasks need to be run:
  • once a day (night), a script is run to produce a file called index.html in /afs/cern.ch/lhcb/software/GIT, containing the list of projects and their owners.
  • every 1-2 hours a script should enter each and every project calling "git update-server-info" to make the latest changes accessible via HTTP.
>
>
Check that the file .git/hooks/post-update.sample is executable and contains the line exec git update-server-info, then do
cd /afs/cern.ch/lhcb/software/GIT/<Project>.git/hooks
mv post-update.sample post-update
(this last step is needed to automatically create the special files required to allow HTTP access).
 

Informations

A PHP script (/afs/cern.ch/lhcb/software/GIT/index.php) shows a list of the currently hosted repositories.

Revision 42012-03-22 - ThomasHartmann

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Line: 17 to 17
 The created empty repository will be accessible directly via AFS, via SSH and HTTP with the following commands:
  • git clone /afs/cern.ch/lhcb/software/GIT/<Project>.git
  • git clone ssh://lxplus.cern.ch/afs/cern.ch/lhcb/software/GIT/<Project>.git
Added:
>
>
    • with another user: git clone ssh://USERNAME@lxplus.cern.ch/afs/cern.ch/lhcb/software/GIT/<Project>.git
 

Note that the HTTP access is read-only, and, because of the limitations of GIT over HTTP, the pushed commits may not be visible for some time (~1-2h).

Line: 44 to 45
 

Informations

A PHP script (/afs/cern.ch/lhcb/software/GIT/index.php) shows a list of the currently hosted repositories.
Added:
>
>
 -- MarcoClemencic - 14-Mar-2012 \ No newline at end of file

Revision 32012-03-16 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Changed:
<
<
To allow LHCb users to manage special projects with GIT, we set up a small infrastructure where to host user repositories.
>
>
To allow LHCb users to manage special projects with GIT, we set up a small infrastructure to host user repositories.
  In any case, since GIT is not officially supported by LHCb, you should not expect to get much help about how to use it.
Line: 37 to 37
 

Regular tasks

Changed:
<
<
Two regular (ACRON) tasks need to be run:
>
>
The following regular (ACRON) tasks need to be run:
 
  • once a day (night), a script is run to produce a file called index.html in /afs/cern.ch/lhcb/software/GIT, containing the list of projects and their owners.
  • every 1-2 hours a script should enter each and every project calling "git update-server-info" to make the latest changes accessible via HTTP.
Added:
>
>

Informations

A PHP script (/afs/cern.ch/lhcb/software/GIT/index.php) shows a list of the currently hosted repositories.
 -- MarcoClemencic - 14-Mar-2012

Revision 22012-03-15 - BenjaminCouturier

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.
Line: 30 to 30
 Once the repository is approved, a librarian will have to issue the following commands:
git init --bare /afs/cern.ch/lhcb/software/GIT/<Project>.git
Changed:
<
<
afs_admin afs_admin set_owner -r /afs/cern.ch/lhcb/software/GIT/.git
>
>
cd /afs/cern.ch/lhcb/software/GIT/.git git update-server-info afs_admin set_owner -r /afs/cern.ch/lhcb/software/GIT/.git
 afs_admin set_acl -r /afs/cern.ch/lhcb/software/GIT/.git rlidwka

Revision 12012-03-14 - MarcoClemencic

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbComputing"
The GIT version control system is gaining more and more momentum also in the HEP community. For small/medium projects that do not fit in the regular LHCb develompent infrastructure and policies (see SVNUsageGuidelines), GIT seems to be a good alternative to Subversion.

To allow LHCb users to manage special projects with GIT, we set up a small infrastructure where to host user repositories.

In any case, since GIT is not officially supported by LHCb, you should not expect to get much help about how to use it.

Guidelines

Requesting a repository

Users wanting to host a project on GIT will have to send a mail to lhcb-git-librarians@cernNOSPAMPLEASE.ch with the name they want for the repository, a short description of the project and the AFS username who should own the repository.

IMPORTANT: only projects that do not fit in the regular LHCb development model will be accepted.

Everybody will have read access to the newly created repositories, but write access will be limited to the owner and the users that the owner requested to be added. It is possible to foresee write access to AFS groups.

The created empty repository will be accessible directly via AFS, via SSH and HTTP with the following commands:

Note that the HTTP access is read-only, and, because of the limitations of GIT over HTTP, the pushed commits may not be visible for some time (~1-2h).

Infrastructure

The AFS directory /afs/cern.ch/lhcb/software/GIT will point to a dedicated backed up volume and will be writeable only to Librarians.

A link in /afs/cern.ch/lhcb/project/web pointing to /afs/cern.ch/lhcb/software/GIT enables the HTTP access.

Create a new repository

Once the repository is approved, a librarian will have to issue the following commands:
git init --bare /afs/cern.ch/lhcb/software/GIT/<Project>.git
afs_admin afs_admin set_owner -r <owner> /afs/cern.ch/lhcb/software/GIT/<Project>.git
afs_admin set_acl -r /afs/cern.ch/lhcb/software/GIT/<Project>.git <owner> rlidwka

Regular tasks

Two regular (ACRON) tasks need to be run:
  • once a day (night), a script is run to produce a file called index.html in /afs/cern.ch/lhcb/software/GIT, containing the list of projects and their owners.
  • every 1-2 hours a script should enter each and every project calling "git update-server-info" to make the latest changes accessible via HTTP.

-- MarcoClemencic - 14-Mar-2012

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback