• Aucun résultat trouvé

The TAG Collector - A tool for ATLAS code release management

N/A
N/A
Protected

Academic year: 2021

Partager "The TAG Collector - A tool for ATLAS code release management"

Copied!
3
0
0

Texte intégral

(1)

HAL Id: in2p3-00023989

http://hal.in2p3.fr/in2p3-00023989

Submitted on 6 Apr 2005

HAL is a multi-disciplinary open access

archive for the deposit and dissemination of

sci-entific research documents, whether they are

pub-lished or not. The documents may come from

teaching and research institutions in France or

abroad, or from public or private research centers.

L’archive ouverte pluridisciplinaire HAL, est

destinée au dépôt et à la diffusion de documents

scientifiques de niveau recherche, publiés ou non,

émanant des établissements d’enseignement et de

recherche français ou étrangers, des laboratoires

publics ou privés.

The TAG Collector - A tool for ATLAS code release

management

S. Albrand, J. Fulachier, J. Collot, F. Lambert

To cite this version:

(2)

CHEP04

Contribution ID : 133

The TAG Collector - A Tool for Atlas

Code Release Management

Thursday 30 Sep 2004 at 10:00 (00h00')

The Tag Collector is a web interfaced database application for release management. The tool is tightly coupled to CVS, and also to CMT, the configuration management tool. Developers can interactively select the CVS tags to be included in a build, and the complete build commands are produced automatically. Other features are provided such as verification of package CMT requirements files, and direct links to the package documentation, making it a useful tool for all ATLAS users.

The software for the Atlas experiment contains about 1 MSLOC. It is organized in over 50 container packages containing about 500 source code packages. One or several developers maintain each package. ATLAS developers are widely distributed geographically.

The Tag Collector was designed and implemented during the summer of 2001, in response to a near crisis situation. It has been in use since September 2001. Until this time the ATLAS librarian constructed a build of the software release after a cascade of e-mails from developers; communicating the correct CVS code repository version tag of their respective packages. This was subject to all sorts of human errors, and

inefficient in our multi-time zone environment. In addition, it was difficult to manage the contents of a release. It was all too easy for a prolific developer to introduce a well-intentioned change in his package just before a build, often with unsuspected border effects. Developers were also asking for regular, and frequent developer builds.

The tool has proved extremely successful, and features that are outside the scope of the original design have been requested. Requirements for a new version were

collected during 2003, culminating in a formal review in December 2003. The new version is currently being designed. It will be more flexible and easier to maintain.

Primary authors : ALBRAND, S. (LPSC) ; FULACHIER, J. (LPSC) ; COLLOT, J. (LPSC) ; LAMBERT,

F. (LPSC)

(3)

Presenter : ALBRAND, S. (LPSC)

Session classification : Poster Session 3

Références

Documents relatifs

However, when looking at the average user ratings of Open Source projects and the number of tweets, number of tweets con- taining positive signals and number of tweets

The total sample time for SMPS has been kept at 235 s (scan time 215 s, retrace time 20 s) whereas for other instruments, it has been kept at low values. For validating the scan

To assist a human expert to document the mined feature implementations, we propose an automatic approach which associates names and descriptions using source code ele- ments of

The current version of the code comprises various nuclear models concerning the light-particle emission, fission process and statistical properties of excited nuclei.. General

To better understand why the different release phases were observed from the investigated caffeine-loaded PLGA microparticles (and why there was a moderate difference in

Our rich description on how OpenStack implemented its six-month, time-based release cycle with frequent development milestones should increase our ability to understand and

When it comes to reducing software energy consumption, we believe that develop- ers’ efforts should be directed towards other software aspects and implementation optimizations

A case study of the metaphor usage in popular scientific texts from Scientific American following the establishment of the metaphor network of the genetic code (Knudsen,