I am generating a file that captures all of the steps that occur during CI such that devs can grab the file login to a cluster and run the script to reproduce the environment, config, build etc. steps that occured during CI job. The only way I could think to do this is via a test with ATTACHED_FILES. I was told that I should generate a dashboard script and use the ctest_submit function. At this point, we don’t use any ctest scripts and propagate information using a CTestConfiguration.ini file. Is there file attachment entry that I could drop in the CTestConfiguration.ini file for this?
Is it possible for the two to coexist? For example, can I use ctest -T for everything up to the submission step and then call the a ctest script to handle submission - at least until I shift everything over to a ctest script?
Thanks Kyle. For starters, I am on 2.5.0 (perhaps that is the source of my problems) and I see a notes section when clicking on the build name in the list of builds. The notes section is empty as one would expect for the following case:
there is no corresponding build in the dashboard to dive into to find the notes. It is as if cdash doesn’t know where to file the build and the corresponding results so it just goes into some black hole.
I’m wondering about the presence/placement of the -- on that command line. I don’t normally invoke things this way, I use a dedicated ci_job.cmake script and invoke it with ctest -S ci_job.cmake, so I’d have to test further to confirm. But in the meantime, try putting -- before the --add-notes option or omitting -- altogether. I won’t know what’s the correct approach until I’ve had a dig through the source code.