Jacamar CI v0.23.0
Release: v0.23.0
Date: 10/16/2024
User Changes
Dynamic
SCHEDULER_PARAMETERSvia script (!535)This feature is now available for all users of batch executors (e.g., Flux, Slurm, PBS, and Cobalt). It enables scripts to be included in your repository and referenced by the
SCHEDULER_PARAMETERSto drive specifics of the arguments. For example:#!/bin/bash # Additional logic/checks... echo '{"args":"-N1 -A stf040 -t 00:30:00"}'
You would include this
args.shfile in your repository and update your CI job like this:job: variables: SCHEDULER_PARAMETERS: args.sh script: - make test
The userspace Jacamar application will detect this proposed parameter is a file and execute it, parsing the returned output for an acceptable JSON structure.
It is also possible to simply skip the job, useful if you wish to end a job successfully if a scheduler is too busy to complete your job within an acceptable time frame:
#!/bin/bash # Additional logic/checks... echo '{"skip":true}'
Please note this script has several limitations including the duration it can run (90 seconds). It is only meant to preform minimal logic and return details via stdout. If more comprehensive operations are required we advise doing so in an earlier job and providing the necessary details via an artifact.
Runner administrators can disable this with the
batch.disable_user_argsconfigurations.
Admin Changes
Improved support for
limit_build_dirconfiguration (!533)The goal with this feature it to allow for the use of file locking (fcntl) to claim build directories within the need to runner specific identification. This is useful for deployment with a large number of runners all configured to utilize the same
data_dir.Complete details can be found in the configuration documentation
Optional user driven
SCHEDULER_ACTIONSfor Slurm (!513)The Deploying and Using Scheduler Actions guide has complete details. We are excited to hear if this new feature can be value for your deployments.