Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41468

JobDSL of ArtifactoryRedeployPublisher failing due to missing customBuildName

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • artifactory-plugin
    • None
    • Jenkins 2.32.1
      Artifactory-Plugin 2.9.0

      Since updating from 2.8.1 to 2.9.0 the JobDSL for many of our jobs has begin failing with the following error:
      ERROR: (XXXscript.groovy, line 88) the following options are required and must be specified: customBuildName, overrideBuildName

      By definition these fields are optional, this is not expected;
      To work around this we have had to update a number of job configurations as follows, since the upgrade:
      artifactoryRedeployPublisher {
      customBuildName(null)
      overrideBuildName(false)
      ...
      }

          [JENKINS-41468] JobDSL of ArtifactoryRedeployPublisher failing due to missing customBuildName

          Tamir Hadad added a comment - - edited

          edrandall, we didn't manage to reproduce this issue executing Artifactory jobDSL configuration as mentioned here:

          job('example') {
              configure { project ->
                  project / publishers << 'org.jfrog.hudson.ArtifactoryRedeployPublisher' {
                      details {
                          artifactoryUrl('http://artifactory.server.com/artifactory')
                          artifactoryName('925330@138764814') // <= You will need to change that to fit your setup
                          repositoryKey('libs-release-local')
                          snapshotsRepositoryKey('libs-snapshot-local')
                      }
                      deployBuildInfo(false)
                      deployArtifacts(true)
                      evenIfUnstable(true)
                  }
              }
          }
          

          The job was created as expected.
          Can you please run the example and check if it works for you ?

          Tamir Hadad added a comment - - edited edrandall , we didn't manage to reproduce this issue executing Artifactory jobDSL configuration as mentioned here : job( 'example' ) { configure { project -> project / publishers << 'org.jfrog.hudson.ArtifactoryRedeployPublisher' { details { artifactoryUrl( 'http: //artifactory.server.com/artifactory' ) artifactoryName( '925330@138764814' ) // <= You will need to change that to fit your setup repositoryKey( 'libs-release-local' ) snapshotsRepositoryKey( 'libs-snapshot-local' ) } deployBuildInfo( false ) deployArtifacts( true ) evenIfUnstable( true ) } } } The job was created as expected. Can you please run the example and check if it works for you ?

            eyalbe Eyal Ben Moshe
            edrandall Ed Randall
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: