CI Validation

This page describes SBND specific aspects of the SBN CI validation system.

To get back to the main CI wiki page, click here. There are also pages for developing new Validations and for those responsible for managing tests.

Available Workflows

• You can run the validation with any combination of feature branches from the following repositories: sbndcode, sbndutil, sbnci (and larpandoracontent if you use CI_VALIDATION_SBND_pandora as your workflow). If you require use of feature branch from any other repository contact Henry Lay or Vito Di Benedetto to have a custom repository added. Longer term there are plans to allow command line requests of any of the required products.

• I would recommend a test submission first, this will allow you to test that your combination of feature branches work together and don’t cause an easy-to-fix failure for all 10k events on the grid. Note that the validation plots will be meangingless, this is a test that the machinery works. This submission can be followed on the test dashboard.

• The test trigger uses the following command:

   trigger --build-delay 0 --jobname sbnd_ci --workflow CI_VALIDATION_SBND \
           --gridwf-cfg cfg/grid_workflow_sbnd_mc_reco_all_test.cfg --revisions "SBNSoftware/repo@branch" --testmode
  

• Once your test job has succeeded (or you’re feeling brave) then the full validation can be triggered with the following command:

   trigger --build-delay 0 --jobname sbnd_ci --workflow CI_VALIDATION_SBND \
           --gridwf-cfg cfg/grid_workflow_sbnd_mc_reco_all.cfg --revisions "SBNDSoftware/repo@branch"
  

READ THIS SECTION BEFORE TRIGGERING

• There are two key tags here that you will need to specify for your tests --revisions and --gridwf-cfg.
  • The --revisions tag is where you specify the branches you want to test. For example:

    --revisions "SBNSoftware/sbndcode@feature/hlay_vertexing henrylay97/LArContent>larpandoracontent@feature/hlay_vertex_bdt_changes"
    

    would provide the two custom branches for sbndcode and larpandoracontent respectively. Note the different syntaxes for specifying a branch in the main repository and for using a branch in a forked repository and directing it towards the correct product name.

  • The gridwf-cfg tag is where you determine which validation workflow you want to run

    Validation	test config	full config
    TPC Reco	cfg/grid_workflow_sbnd_mc_reco_all_test.cfg	cfg/grid_workflow_sbnd_mc_reco_all.cfg
    CRT Sim/Reco	cfg/grid_workflow_sbnd_crt_test.cfg	cfg/grid_workflow_sbnd_crt_all.cfg
    PDS Sim/Reco	cfg/grid_workflow_sbnd_pds_test.cfg	cfg/grid_workflow_sbnd_pds_all.cfg
    TPC Sim/Calib	cfg/grid_workflow_sbnd_tpcsim_test.cfg	cfg/grid_workflow_sbnd_tpcsim_all.cfg

• Other options for the trigger command can be found as usual by running trigger -h.
• The results of your trigger can be followed on the dashboard.