Re: [HTCondor-users] Removal of PreCmd and PostCmd from the 25.11.0

Hi Cole,

>From my PoV that two alternatives answer different things:

- The first one allows the user to define boundary actions inside the container, under his control and limitations.

- The second one allows the administrator to offer "special boundary actions" (optional or mandatory) that are not limited by the container.

For me the first one will be a problem except if it is using a different container (something like a side-load pod)

In our case the container images are many times wrapping ancient satellite data processors, that other teams have been hammering for months to make them work and is a hostile territory, where I only dare to run the entrypoint they told me....

Nevertheless, knowing that the ideas are still in discussion it is not a problem, I will try to follow this point to help with our use cases.

Thanks!

Andrés

De: Cole Bollig <cabollig@xxxxxxxx>
Enviado: viernes, 19 de junio de 2026 16:32
Para: Andres Ayala <Andres.Ayala@xxxxxxxxxxxx>; HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Asunto: Re: Removal of PreCmd and PostCmd from the 25.11.0

WARNING: This email originated outside the organisation. Treat links and attachments with caution.

Hi Andrés,

The two concepts we have been discussing (not guarantees on implementation or final design) are:

EP side job sequences that the user defined (would run inside container)
Administrator controlled Pre/Post Cmds

This is all in the discussion stage right now and not concrete at all. The current code should be available until we do decide on what we are doing.

-Cole

From: Andres Ayala <Andres.Ayala@xxxxxxxxxxxx>
Sent: Friday, June 19, 2026 3:52 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Cc: Cole Bollig <cabollig@xxxxxxxx>
Subject: RE: Removal of PreCmd and PostCmd from the 25.11.0

Hi Cole,

The reason I use Pre/Post is because they run outside of the container, a space that is under my orchestrator control, to avoid adding requirements to the container images.

If I describe the usage of Pre and Post in terms of requirements it will be:

- prepare the job working directory before running the main command (PRE) or collect the job working directory once the main command has finished (POST)

- run with the same user that will run the main command (at least with the capability to alter the working directory).

- have access to the job classads, including the exit status of the main command for the POST.

The current pre/post commands fit well, with only one aspect that I found insecure. I would prefer that only condor administrator can define the available Pre and Post commands.

The job submit can request to use them or not but not set the actual binary to run.

Andrés Ayala

PS: I have found in 25.11.0 the flag to enable the Pre and Post commands again, for the moment it is enough for me.

In the long term I need to switch to something Condor can also maintain, but I have no special attachment to the Pre/Post commands...

De: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> en nombre de Cole Bollig via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Enviado: jueves, 18 de junio de 2026 19:10
Para: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Cc: Cole Bollig <cabollig@xxxxxxxx>
Asunto: Re: [HTCondor-users] Removal of PreCmd and PostCmd from the 25.11.0

WARNING: This email originated outside the organisation. Treat links and attachments with caution.

Hi Andrés,

I have been informed that the Pre/Post Cmds have actually been disabled by default by a configuration option (I would have to figure out its called). A related note, in the case of jobs executing within a container, do your pre/post commands need to be executed outside of the container? This will help us in our planning of the replacement of the Pre/Post Cmd once we do decide to officially remove it.

-Cole Bollig

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Cole Bollig via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Sent: Thursday, June 18, 2026 10:28 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Cc: Cole Bollig <cabollig@xxxxxxxx>
Subject: Re: [HTCondor-users] Removal of PreCmd and PostCmd from the 25.11.0

Hi Andrés,

We have ideas but no concrete plans on how we are going to replace Pre/Post Cmd's. Currently they are only removed from the documentation to prevent newer use of them, but they should still be functional in the code currently.

-Cole Bollig

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Andres Ayala <Andres.Ayala@xxxxxxxxxxxx>
Sent: Thursday, June 18, 2026 10:11 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Removal of PreCmd and PostCmd from the 25.11.0

Hello,

I am testing the HTCondor version 25.11.0 to use it in our system and I found that the PreCmd and PostCmd actions for the jobs are not longer usable.

At EUMETSAT we heavily use this functionality to integrate condor with our orchestrator, and it will be complex to stop using the functionality they provide (running a task before and after the execution of the main job)

Tracking the JIRA I found HTCONDOR-3635, that is speaking about removing that options from documentation.

Does this mean these options will disappear?

Do you have plans to provide an alternative option? (in this case I can migrate our systems, but is going to take time)

If the plan is to keep these options behind some "advance mode" is also not an issue, for the moment I will keep our systems in 25.8.2 or in the 25 LTS branch.

Best Regards,

Andrés Ayala

Any email message from EUMETSAT is sent in good faith but shall neither be binding nor construed as constituting a commitment by EUMETSAT, except where provided for in a written agreement or contract or if explicitly stated in the email. Please note that any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of EUMETSAT. This message and any attachments are intended for the sole use of the addressee(s) and may contain confidential and privileged information. Any unauthorised use, disclosure, dissemination or distribution (in whole or in part) of its contents is not permitted. If you received this message in error, please notify the sender and delete it from your system.