There are a variety of ways to do this, but not by using the environment.
You can configure SUBMIT_ATTRS to add attributes to each job before the submit file is processed. The submit file can override job attributes set in this way.
You can append statements to a job submission by passing the -append argument to condor_submit. these statements will override equivalent statements in the submit file.
See the condor_submit man page in the the HTCondor manual for more information about these options.
if you control the configuration of the condor_schedd, you can use a JOB_TRANSFORM_* to modify the job classad as it is submitted. You can also use SUBMIT_REQUIREMENT_* configuration to reject jobs that do not have certain attributes set.
See the configuration section of the HTCondor manual for more information about these options.
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Chun-Yu Lin <lincy@xxxxxxxxxxxxxx>
Sent: Tuesday, November 16, 2021 7:48 PM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Append job classAd to a certain group of jobs?
I am planing to restrict the number of running jobs from a specific group (from the grid), while allow other local submissions without limit. A simple test works if I add "concurrency_limits" job classAD in the job description file.
My question is: is it possible to assign job classAd via exporting some bash environment variable (say, in the runtime wrapper script of a grid submission framework, rather than from job description file itself), such that it can be appended to every job from grid ?