Add subsection how to do a full build with ctest+CITest

Add a subsection how to do a full build with ctest+CITest.

Tagging @jchapman and @jcatmore for feedback.

added 1 commit

• e08c1d0d - Fix typo

Compare with previous version

resolved all threads

Why do you need to source build_env.sh here?

For the CITest I'd like to have the same environment as used in the CI.

But all our tests are run within atlas_build_run.sh which already sources the setup script. So this should not be needed.

The history of this choice is in https://its.cern.ch/jira/browse/ATEAM-1000 - so let's keep it.

We need to understand this. When you are setting up a nightly via asetup you are not sourcing build_env.sh either. So I don't understand why it's needed when setting up a standalone build. Maybe @akraszna has some insights?

After some delay...

Ahh... The problem here is that all environment setup beyonf the basic asetup none... stuff at the beginning, is happening inside of the build_externals.sh and build.sh scripts. And for the CI tests to be able to run, you have to be in an environment in which you built "the project".

Sourcing the build_env.sh script is I believe the most straight forward way of getting into that environment. (Remember, build_env.sh is mainly setting up the externals project, plus a few bits and bobs. It's not setting up the runtime environment of the top-most project.)

What's the main goal of this section? (Sorry, didn't bother reading the whole thing... ) If this is mainly about being able to run the tests, and developing code "in a full build", then I would approach things differently. Since when I develop code like that myself, I follow a different set of steps. (But not worth going into it if running the tests here is more of a side-project.)

Do we really need to specify the cmake version here? This will get outdated so better to just stick with the default.

The default version in ALRB is currently 3.27.5 - see /cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase/x86_64/Cmake - we also manually select the respective version in Jenkins.

But I assume 3.27.5 still works?

Not sure, I have not used it for a while with the main branch - 3.29.5 will not work with AnalysisBase and the latest ROOT version.

I suggest we change the default then. Can you open an ATLINFR ticket? Having a fixed version here really just means these instructions will no longer work at some point in the future.

If we changed the default, would we then have to override it for builds with the 24.0 branch? (Or is this already the case?)

Clicking through all 24.0 Jenkins configurations linked from https://atlas-jenkins.cern.ch shows

(a) all x86, 24.0 builds use:

asetup none,$comp,$mode --cmakesetup --cmakeversion 3.27.5

(b) all aarch64,24.0 builds use

asetup none,$comp,$mode --os=el9
lsetup git
lsetup "cmake 3.27.5"

Thanks for the info @elmsheus. OK, so we would not need to update anything if we change the default.

left review comments

added 1 commit

• d3408d6b - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

Let's close, since I will not spend more time on this.

closed