cet-is

Note that you will need to build larg4, larsim, and larreco together. Use "mrb uv nug4 v1_07_00" to change the build to use nug4 v1_07_00.

Lynn

I have made the necessary modification in larreco. How should I proceed? Make a PR on the larreco github right?

[Edit] I have made a PR in larreco: https://github.com/LArSoft/larreco/pull/28

Thank you. I'll provide PR's for larg4 and larsim to enable testing.

Unfortunately, the gensingle test fails with the following error. Would you please fix? Thanks

%MSG-s ArtException:  Early 25-Feb-2021 12:25:14 CST JobSetup
cet::exception caught in art
---- Configuration BEGIN
  Library specification "MagneticField" does not correspond to any library in CET_PLUGIN_PATH of type "service" 
---- Configuration END
%MSG

I noticed that I needed to modify the mag field fcl in lardata to specify the service provider.
See lardata PR: https://github.com/LArSoft/lardata/pull/14

Trying to trigger a build following the tutorial (https://cdcvs.fnal.gov/redmine/projects/lar_ci/wiki/How_to_trigger_the_default_CI_build) with a certificate. I cannot manage it for some reason.. Getting

Triggering CI build
workflow: default_wf
trigger attempt # 1/10
curl: (22) The requested URL returned error: 400 Bad Request
curl: (22) The requested URL returned error: 400 Bad Request

Command used on dunegpvm machine:

trigger --build-delay 0 --cert /tmp/x509up_u54588 --version develop --workflow default_wf --revisions "LArSoft/larg4#22 LArSoft/larsim#65 LArSoft/larreco#28 LArSoft/lardata#14" 

Thanks for all your work fixing build problems. I have a question about fcl files. There are a number of them with the line below. Does that line need to change?

 MagneticField:                @local::no_mag_larsoft

@Eldwan,
most likely the reason why your trigger command fails, is because the certificate you are providing is not accepted by Jenkins build service.
By running:

CI_CERT=/tmp/ci_cert.pem
kx509 -o ${CI_CERT}

you are supposed to get a certificate from CIlogon CA:

voms-proxy-info -all -f ${CI_CERT} | grep issuer
issuer    : /DC=org/DC=cilogon/C=US/O=CILogon/CN=CILogon Silver CA 1

In your trigger command I see you refer as certificate the file /tmp/x509up_u54588, that is the default place pointed by X509_USER_PROXY.
In case you run a voms-proxy-init command, the original cert is converted in a proxy grid certificate that is issued by incommon CA.

Probably for /tmp/x509up_u54588 you are getting something like this:

voms-proxy-info -all | grep issuer
issuer    : /DC=org/DC=cilogon/C=US/O=Fermi National Accelerator Laboratory/OU=People/CN=Vito Di Benedetto/CN=UID:vito
issuer    : /DC=org/DC=incommon/C=US/ST=Illinois/L=Batavia/O=Fermi Research Alliance/OU=Fermilab/CN=voms1.fnal.gov

and this certificate is not accepted by Jenkins build service.
That's the reason why the tutorial use a custom file to store the certificate, this way it is detached by the proxy grid certificate usually stored in a path like /tmp/x509up_u$(id -u).

In case you still need to trigger a CI build to test this combination of PRs, please, try the trigger command with the dedicated certificate file to verify this works for you.

Hopefully this helps to clarify the issue.

@Lynn,

It does not need to change. I modified the corresponding fcl entry in lardata so that there is no need to modify all other fcl that uses

MagneticField:                @local::no_mag_larsoft

@Vito,
Thanks for the details.

nug4 v1_07_00 is used by larsoft v09_17_02.