Project

General

Profile

Feature #18378

Add a LArSoft-based workflow pulling in nusimdata and nutools sources

Added by Gianluca Petrillo about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Vito Di Benedetto
Target version:
-
Start date:
11/27/2017
Due date:
% Done:

100%

Estimated time:
Duration:

Description

This is a request for a special workflow based on the standard one which includes experiment code, which in addition pulls in and builds nusimdata and nutools repositories to compile them all together in the MRB environment.
The workflow should be able to fulfill the request for a branch of these repositories other than develop.
This should allow to test changes to basic data products in the simb namespace and to nutools code, by verifying that it does not break experiment test results.

Related issues

Blocks NuTools - Bug #12067: Add move operations to simb::MCParticleClosed03/25/2016

History

#1 Updated by Vito Di Benedetto about 3 years ago

  • Status changed from New to Assigned
  • Assignee set to Vito Di Benedetto

#2 Updated by Gianluca Petrillo about 3 years ago

  • Blocks Bug #12067: Add move operations to simb::MCParticle added

#3 Updated by Vito Di Benedetto about 3 years ago

  • Status changed from Assigned to Work in progress

#4 Updated by Vito Di Benedetto almost 3 years ago

  • % Done changed from 0 to 40

I have a test CI workflow that builds NuTools (nusimdata and nutools) and LArSoft independently.
The built code is stored as tarball and made available as Jenkins artifact to be used by the experiment CI builds.
The next step will be to instrument the experiment workflows to access those tarballs.

#5 Updated by Vito Di Benedetto almost 3 years ago

  • Status changed from Work in progress to Resolved
  • % Done changed from 40 to 100

The CI workflow is ready to be used.
It checkout/build/test nusimdata and nutools in a sub-shell, then LArSoft is checkout/build/test in a new sub-shell on the top of the just built nusimdata and nutools, finally it triggers independent CI builds for each experiment code on the top of the just build nusimdata, nutools and LArSoft.

Assuming you set up lar_ci and have a valid proxy, the command to use this workflow is:

trigger --build-delay 0  --workflow nutools

You can use an option to choose a specific revision/branch/tag for each module involved using (the default is the develop branch):

--revisions "module1@revision1 module2@branch2"

you can also choose the platform where to run the CI workflow (the default is slf6, slf7 d16):

--force-platform slf6,slf7

#6 Updated by Vito Di Benedetto over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF