Increment independently version (work and publish)

pierrelucb · July 30, 2019, 2:56pm

Hi,
By default, there is a coherency between shotgun save version and publish version. Is there a way we can break that and have publishing version with is own increment and work too, without any jump between version?

thanks

Pierre-Luc B.

philip.scadding · July 30, 2019, 3:34pm

Hi Pierre-Luc

Thanks for posting this here!

You should be able to achieve this by taking over and modifying the publish hooks.
Using Maya as an example, it works out the next publish version here:

github.com

shotgunsoftware/tk-maya/blob/master/hooks/tk-multi-publish2/basic/publish_session.py#L272-L293


(next_version_path, version) = self._get_next_version_info(path, item)
if next_version_path and os.path.exists(next_version_path):


    # determine the next available version_number. just keep asking for
    # the next one until we get one that doesn't exist.
    while os.path.exists(next_version_path):
        (next_version_path, version) = self._get_next_version_info(
            next_version_path, item)


    error_msg = "The next version of this file already exists on disk."
    self.logger.error(
        error_msg,
        extra={
            "action_button": {
                "label": "Save to v%s" % (version,),
                "tooltip": "Save to the next available version number, "
                           "v%s" % (version,),
                "callback": lambda: _save_session(next_version_path)
            }
        }

This file has been truncated. show original

Which calls the _get_next_version_info from the base publish hook.

github.com

shotgunsoftware/tk-multi-publish2/blob/master/hooks/publish_file.py#L844


            raise Exception(
                "Failed to copy work file from '%s' to '%s'.\n%s" %
                (work_file, publish_file, traceback.format_exc())
            )


        self.logger.debug(
            "Copied work file '%s' to publish file '%s'." %
            (work_file, publish_file)
        )


def _get_next_version_info(self, path, item):
    """
    Return the next version of the supplied path.


    If templates are configured, use template logic. Otherwise, fall back to
    the zero configuration, path_info hook logic.


    :param str path: A path with a version number.
    :param item: The current item being published


    :return: A tuple of the form::

This attempts to work out the version from the workfile and then see if that publish version is available to use.

You could modify the Maya publish hook so that it doesn’t call this method and instead uses a different approach to figuring out the version. You could, for example, create a new method based off _get_next_version_info that gets the version using the publish template instead.

Thanks
Phil