How-to test CMSSW data files

• Testing Data Files:

  • Begin by creating a CMSSW project area.
  • Check out the specific package to which the data files belong.
  • Place the new or updated data files inside the <subsystem>/<package>/data directory.
  • Run the necessary tests
  • Notice: FileInPath mechanism/utils can be used to load these data files. One can find many examples for FileInPath in cmssw github or in TWiki: 1 2.

• Publishing Changes:

  • If the GitHub repository <subsystem>-<package> under cms-data organization already exists:
    • Proceed with the PR to update the repository with the latest data files.
  • If the repository does not exist:
    • Open an issue for main CMSSW repo with the title: Create repository <subsystem>/<package>.
    • Once the issue is fully signed, the repository will be automatically generated.

Quick start

• Main page
• FAQ: CMSSW on Github
• CMS Naming, Coding, And Style Rules
• Proposing changes to CMSSW
• Setting up CMS environment using Singularity (new)
• Python virtual environment in CMSSW (new)
• CMSSW pull request approval workflow
• Collaborating with peers
• Working with CMSSW and UserCode
• Resolving conflicts & porting features
• How to use git through a proxy
• Building external packages (new)

Release Management

• CMSSW release notes
• Building a CMSSW release
• Integration Builds results
• Starting a new release cycle
• Forward ports
• Managing users and categories
• List categories and packages
• List of pending PRs
• Circle of pending PRs
• CMS-bot documentation
• CMS-bot commands

Infrastructure setup

• Monitoring
• Managing secrets with puppet
• Setting up builder machines
• Setting up builder machines [aarch64]
• Setting up builder machines [power8]
• Setting up cmsdev machines