You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On "Manage Jenkins -> Global Tool Configuration", I have set a JFrog CLI installation to always download the latest JFrog CLI tool available on releases.jfrog.io :
I have reproduced this issue in three different Jenkins instances (same version, same plugins and same version plugins): if I export the JCasC configuration, the exported section for the aforementioned JFrog CLI installation is incorrect, because it just exports the installation name. When importing it back, the JFrog CLI installation is partially restored in Jenkins, because it has no information that it needs to use the latest version from JFrog repository, hence jobs using jf fail with the following error: A 'jfrog' tool was not set. Using JFrog CLI from the system path.
As documented in the main page from this plugin and from #7, this is the right exported configuration for this case I have tested:
Install Jenkins and the following plugins: configuration-as-code and jfrog.
Go to "Manage Jenkins -> Global Tool Configuration"
Create a new JFrog CLI installation to always download the latest JFrog CLI tool available on releases.jfrog.io. A valid test name could be jfrog-cli-latest.
Go to "Manage Jenkins -> Configuration as Code" and click on the "View Configuration" button to export the JCasC confguration.
Search for the string jfrog: to see how the related configuration was exported.
Describe the bug
On "Manage Jenkins -> Global Tool Configuration", I have set a JFrog CLI installation to always download the latest JFrog CLI tool available on releases.jfrog.io :
I have reproduced this issue in three different Jenkins instances (same version, same plugins and same version plugins): if I export the JCasC configuration, the exported section for the aforementioned JFrog CLI installation is incorrect, because it just exports the installation name. When importing it back, the JFrog CLI installation is partially restored in Jenkins, because it has no information that it needs to use the latest version from JFrog repository, hence jobs using jf fail with the following error:
A 'jfrog' tool was not set. Using JFrog CLI from the system path.
As documented in the main page from this plugin and from #7, this is the right exported configuration for this case I have tested:
Current behavior
The JCasC configuration is partially exported:
Reproduction steps
Expected behavior
The JCasC configuration is correctly exported:
JFrog plugin version
1.4.0
JFrog CLI version
any
Operating system type and version
AmazonLinux 2
JFrog Artifactory version
No response
JFrog Xray version
No response
The text was updated successfully, but these errors were encountered: