DPM Collaboration
DPM Collaboration
hello
How to mark a tag/branch as part of the candidate release
How to mark a tag/branch as part of the candidate release
The basic requirement is that the component, when built, produces a packaged file (.rpm) that contains the version number in its filename. In other words, the package file must be recognizable.
Using the continuous builds
How we use the builds
The build of the SVN trunk is used to feed our nightly tests and our stable test infrastructure.
Its main goal is to produce feedback that is useful for the developers and maintainers of the various components. If you are a developer then you should consider the SVN trunk build to verify your work in the shortest possible time.
Continuous Builds
Continuous Builds
The LCGDM software development process is based on the idea of continuous builds. Whenever there is a change to the source code, in any of the components, a build system updates the installable packages in a shared directory. Anyone can install those packages, which represent the trunk release and the candidate release.
Our continuous integration process is built on Bamboo Bamboo
Info for developers
Here's some information on the tech mailing list and the source code repositories:
- Mailing List: dpm-devel@cern.ch(link sends e-mail)
- SVN Repository Access
svn co svn+ssh://svn.cern.ch/reps/lcgdm
svn co https://svn.cern.ch/reps/lcgdm
Lcg-DM
The project name Lcgdm comes from the first Grid-related projects, and originally meant LHC Computing Grid Data Management.
Nowadays the project evolved from its initial roots, and is composed by a set of sub projects facing different aspects of data management for high throughput, widely distributed computing