Current State:
When using Artifactory download in generic build integration configurations (e.g. Command Line), the command line step happens after the Artifactory download while it happens before when using Artifactory upload. Not only it is not controllable, it is not specified/documented anywhere... only discoverable by experience.
Request:
Have an option (e.g. checkbox/combobox) to control whether Artifactory download and upload happens before or after the built-in step (e.g. Command Line).
Benefits:
This will address the non-documented behavior by itself (the default values/behaviors could be preserved). More importantly, this will give the right flexibility to add pre or post-process using, for instance, some JFrog CLI commands to complement the TeamCity Artifactory Plugin missing abilities in one self-contained TeamCity step (instead of requiring coupling with other steps which add unnecessary decoupled logic).
Current State: When using Artifactory download in generic build integration configurations (e.g. Command Line), the command line step happens after the Artifactory download while it happens before when using Artifactory upload. Not only it is not controllable, it is not specified/documented anywhere... only discoverable by experience.
Request: Have an option (e.g. checkbox/combobox) to control whether Artifactory download and upload happens before or after the built-in step (e.g. Command Line).
Benefits: This will address the non-documented behavior by itself (the default values/behaviors could be preserved). More importantly, this will give the right flexibility to add pre or post-process using, for instance, some JFrog CLI commands to complement the TeamCity Artifactory Plugin missing abilities in one self-contained TeamCity step (instead of requiring coupling with other steps which add unnecessary decoupled logic).