Pause and Resume Jobs later in a different agent

[Yeikel]

In my company, we have a Jenkins instance that procures new agents dynamically at runtime. These agents have a one hour limit but I can use as many as I want.

For long running pipelines, is there any mechanism to serialize the status of a job and resume it later in a different node? Or do I need to involve some sort of external service/artifacts?

I understand that the easy win would be to increase the time limit , but that's not an option I have as I don't manage the servers and they are not willing to remove the limit.

What else do you recommend for this scenario?

Thanks!

[JonathanRRogers]

You can directly control which steps execute on which agents via node() in a scripted Pipeline job. Pausing in the middle of a step or moving execution to a different agent is a whole other ball of wax that Jenkins doesn't address at all AFAIK. A typical long-running step executes an external process, so all state of that process would have to be dealt with. There are ways to checkpoint and migrate processes, but Jenkins doesn't provide any help with that.