When migrating from Artifactory Jenkins plugin to JFrog CLI in Jenkins, we can replace the pipeline stages with JFrog CLI commands as below :
'rtMaven.resolver ...' and 'rtMaven.deployer ...' to 'jf mvn-config ...'
'rtMaven.run ...' to 'jf mvn ...'
'publishBuildInfo ...' to 'jf rt bp ...'
But there is no separate stage for deploying the artifacts to the Artifactory. When we use jf mvn deploy command, it again compiles and builds the Maven project and only then it deploys to the repository. Hence, we need the JFrog CLI command equivalent to rtMaven.deployer.deployArtifacts buildInfo.
What is the expected behavior :
JFrog CLI command equivalent to rtMaven.deployer.deployArtifacts buildInfo , so that we can only deploy the artifacts to the Artifactory in this stage.
Description :
When migrating from Artifactory Jenkins plugin to JFrog CLI in Jenkins, we can replace the pipeline stages with JFrog CLI commands as below :
'rtMaven.resolver ...' and 'rtMaven.deployer ...' to 'jf mvn-config ...'
'rtMaven.run ...' to 'jf mvn ...'
'publishBuildInfo ...' to 'jf rt bp ...'
But there is no separate stage for deploying the artifacts to the Artifactory. When we use jf mvn deploy command, it again compiles and builds the Maven project and only then it deploys to the repository. Hence, we need the JFrog CLI command equivalent to rtMaven.deployer.deployArtifacts buildInfo.
What is the expected behavior :
JFrog CLI command equivalent to rtMaven.deployer.deployArtifacts buildInfo , so that we can only deploy the artifacts to the Artifactory in this stage.
Workaround :
None