Release management workflow

(Note almost all of this information is from the MicroBooNE instructions here (tagging), here (Jenkins build), here (CVMFS), and here.)

Required permissions

Multiple permissions are needed to perform all of the actions involved in release management, these include:

• Access to cvmfssbnd account on oasiscfs.fnal.gov
• Access to sbnd account on GPVMs
• Account on the Jenkins build server and a CILogon certificate loaded in your browser (Will need Fermilab VPN running if off site)
  • Relevant ticket to get Jenkins permissions: Modify user on Jenkins Cluster
• Access to scisoftgpvm01.fnal.gov

Creating a new release

1. Tag the release
2. Build on Jenkins
3. Upload release to SciSoft
4. Deploy on CVMFS
5. Update the wiki
6. Email users on sbnd-software

sbnd_data

• Updating sbnd_data

Code monitoring

• Commit emails
• Continuous integration

Mailing lists you should be on

• SBND-SOFTWARE
• SBN-SOFTWARE
• SBND-COMMIT
• SBND-SOFTWARE-BUILD
• BUILD-SERVICE-USERS
• LARSOFT
• ART-USERS

Legacy pages

• Deploy on /grid/fermiapp