Gradle Artifactory Integration with Jenkins Job DSL
goodav
We are using the Jenkins DSL to define our jobs and have had very good success with it. However, when writing a job for our projects that use Gradle, where a successful build publishes to Artifactory, we have to manually configure Artifactory on the jobs first run even though we defined all the Artifactory config in the DSL.
Our DSL job results in the following config.xml snippet for our job:
<details>
<artifactoryUrl>http://my.artifactory.server/artifactory</artifactoryUrl>
<artifactoryName>artifactory</artifactoryName>
<repositoryKey>libs-snapshot-local</repositoryKey>
<snapshotsRepositoryKey>libs-snapshot-local</snapshotsRepositoryKey>
<downloadReleaseRepositoryKey>libs-snapshot-local</downloadReleaseRepositoryKey>
<downloadReleaseRepositoryDisplayName>libs-snapshot-local</downloadReleaseRepositoryDisplayName>
<stagingPlugin>
<pluginName>None</pluginName>
</stagingPlugin>
<userPluginKey>None</userPluginKey>
</details>When we run the job for the first time it fails because the "Publishing Repository" has not been populated (see below).
After clicking the refresh button the "Publishing Repository" field is then populated with a value (although it is not the correct value from our DSL config: see xml above).
This seems like a defect with the plugin because after clicking the refresh button and saving the job configuration, there is not a single change the the above xml snippet. Comparing the config.xml for the job before and after results in no differences.
Has anyone else encountered this or found a way around it?
