Uploaded image for project: 'Jenkins Artifactory Plug-in'
  1. Jenkins Artifactory Plug-in
  2. HAP-743

Artifactory Release Build API does not work



    • Type: Bug
    • Status: Resolved
    • Resolution: Not a Bug
    • Affects Version/s: 2.4.7
    • Fix Version/s: None
    • Component/s: Maven2, Release Management
    • Environment:

      Jenkins 1.647 and Artifactory Plugin version 2.4.7 ( latest


      Hi Allen,

      Thank you for that information. We were able to reproduce this issue locally with your instructions and do not see an obvious solution. We will need to discuss this internally with our plugin expert and will get back to you soon. In the meantime, you can create a JIRA ticket on our system and vote and watch it for future progress.

      Best Regards,

      Daniel Augustine
      JFrog Support

      On Mon, 16 May at 9:01 PM , Allen Paul <allen.paul@netapp.com> wrote:
      Hello JFrog team,

      Here is the response to the information you requested.

      1) Steps to reproduce the issue
      Essentially, we are trying to group several java based projects as a multi module Maven project so as to minimize the number of Build jobs we need to create in Jenkins. We want to perform Release builds for individual modules rather than the entire group. I created a simple Multi Module Maven project, and configured a Maven Jenkins job to build this. I?ve also enabled Artifactory Release Management for this job ( Job config.xml is attached ). When I do a release build using Artifactory Release Build button, and provide individual module versions ( Select ???Version per module? ), the Release build works fine. When I do the same using the Artifactory plugin API, it fails ( error in Jenkins job console is attached ). Here are the steps that you can use to reproduce.
      a. I?m attaching a zip file which contains the source code I?m building. We use Perforce as our SCM, but I think you should be able to see the issue with GIT or SVN as well.
      b. Please use the attached job config ( MultiModulePOC ) for Jenkins. We are using Jenkins 1.647 and Artifactory Plugin version 2.4.7 ( latest ). You may remove the Environment variable injection script, and the groovy script in the end, as these are pertaining to the POC I???m doing, but irrelevant to the issue we are facing.
      c. Please trigger a release build from Jenkins with Individual modules chosen ??? verify that this runs successfully.
      d. Now trigger the release build from the API . The URL I used is this:
      e. The attached error log is what I see in the Jenkins job console.

      2) Artifactory logs and system info from the Support Zone ( We are currently at the latest in our STG environment ??? 4.6.7 ). Attached.
      3) I don???t have any client errors to show. I used Postman ( on Chrome ) to call the Rest API, and I get a 200 ok from Jenkins since the build does get triggered, but fails eventually.

      Let me know in case of questions or clarifications. Looking forward to a solution for this.


      From: JFrog Support support@jfrog.com
      Sent: Saturday, May 14, 2016 4:58 AM
      To: Paul, Allen <Allen.Paul@netapp.com>
      Cc: service@jfrog.com; Parthasarathy, Gopal <Gopal.Parthasarathy@netapp.com>; beni@jfrog.com
      Subject: Re: 40055 Jenkins Artifactory Plugin

      Hi Allen,

      Thank you for the update. We will keep this ticket open.



      JFrog Support

      On Sat, 14 May at 4:44 AM , Allen Paul <allen.paul@netapp.com> wrote:
      Hi Omar,

      I???m in the process of compiling the information that you requested, and will revert back to you by Monday.


      From: JFrog Support support@jfrog.com
      Sent: Friday, May 06, 2016 10:15 PM
      To: Paul, Allen <Allen.Paul@netapp.com>
      Cc: service@jfrog.com; Parthasarathy, Gopal <Gopal.Parthasarathy@netapp.com>; beni@jfrog.com
      Subject: Re: 40055 Jenkins Artifactory Plugin

      Hello Allen,

      We would be happy to assist you in using the Artifactory Release API. Could you please send us the following so we can investigate further:

      1. Detailed steps to reproduce the issue (If not reproducible, time/date/timezone that can be used to identify the incident in the logs)

      2. Artifactory logs containing the entire event

      If you are using Artifactory 4.3.0 and above,
      Please omit passwords and private information by Enabling 'Scrub Passwords and Private Information' at [Artifactory UI] ??? [Admin] ??? [Advanced] ??? [Support Zone] ??? [Scrub Passwords and Private Information].

      Afterward, save the support package and send us using the instruction below ("Send us the logs")

      If you are using any versions of Artifactory below 4.3.0,
      Enable Master Key Encryption to mask any passwords in the configuration files then send us:
      ??? Version number of your Artifactory
      ??? $ARTIFACTORY_HOME/etc/artifactory.config.latest.xml
      ??? $ARTIFACTORY_HOME/etc/security.<LATEST_TIMESTAMP>.xml
      ??? $ARTIFACTORY_HOME/logs/artifactory.log
      ??? $ARTIFACTORY_HOME/logs/request.log
      ??? $ARTIFACTORY_HOME/logs/access.log

      3. Client input and output with debug information
      If applicable, please send us the complete debug output of the client that you have the issue with (e.g. npm install -dd , Docker -D -d ...)

      4. Send us the logs
      If it is less than 5 MB, you may send the files directly to us using Support Portal or email. Otherwise, you may upload files for us using cURL to our Artifactory SaaS account, using the following command (replace texts in blue with your own):

      curl -i -T filename.ext "https://supportlogs.jfrog.com/logs/40055/"

      No username and password are required.

      Best Regards,
      JFrog Support




            eyalbe Eyal Ben David
            allenp Allen Paul (Inactive)
            0 Vote for this issue
            1 Start watching this issue