Force publish lower version number

General
1

Hey!

Is there a way to ignore the “version number lower or equal” error when publishing?
I am having a multicam shot in solaris and it would be a good case to be able to render out cams without having to wait that previous renders are completed.
I don’t mind having “cam030_v009” being published after “cam050_v011”.

thanks!

2

Reading through this post makes me think of:

  1. Does AYON allow publishing version with arbitrary numbers? without the number be the next version. I think it’s possible create_version.
  2. Does the version being published know which version it is?
    • I think for local publishing, it doesn’t, it just publish the next version (without locking it)
    • For farm render, I saw this PR to match the behavior of local rendering. Add farm version locking enable/disable setting #1767
      So, for your example I think the newer one you are publishing will be the v009 and the other one when finished will be v011.

Tagging @BigRoy for further insights.

3

Hey,

I think this is accurate, but I am also getting slightly confused at the same time.

But my problem is indeed what is being described by Roy in the PR.
When I did render something that rendered well, but somehow it can’t publish because of the versioning (either something happened during publish and failed, or an additional version was indeed submitted) and I can’t figure out how to force the publishing of that said version without having to re-render (which isn’t ideal).

It would kind of be like having the “use existing frames” but with a version option to choose from.
Because use existing frame will expect the frames to be at the correct current version.
Being at v5, force publishing v2 will make it v6, and it’s fine. It would also be fine if it were forced publish at v2, my issue is just that I can’t publish it at all without having to re-render.

If that makes sense?

Thanks

4

I gave it a quick look.

In deadline log, I found the version was resolved in CollectAnatomyInstanceData when it displays the template data.
And, I couldn’t figure out where the version number comes from.

Anyways, I was going to suggest to change it and re-running the publish job.
but, it seems one needs to modify the job environment as the output directory includes the version number.

OutputDirectory0=H:/AYON/projects/Experiments/random/houdini/publish/render/renderTest_renderMain_Beauty/v019

It’s turning into a chicken and egg situation where the next version is computed on job submission to fill in the envs but at the same time the job might be able to publish a different version other than the specified one.

Maybe locking the version or having it in the render job metadata can help. but, I guess we need also to send a signal to the server backend to inform it that version xx is reserved and consider the next version is xx+1.