Child pages
  • Jenkins Artifactory Plugin - Release Management
Skip to end of metadata
Go to start of metadata

This page has been moved. The page is available here.

  • No labels

5 Comments

  1. Unknown User (ngrobisa)

    <please, erase this comment to avoid confusion. I've already posted in the Artifactory users list and now my problem is solved>

  2. Unknown User (tankertux)

    Is there a specific reason that this feature does not work with CVS? I'm attempting to update our technology stack, and I'm hesitant to throw git in the mix for team buy-in reasons.  I may try to implement it myself if I'm not missing some reason it cannot be accomplished.

  3. Unknown User (mmorizot42)

    Hi,

    I'm using version 2.0.4 of the artifactory release plugin with artifactory OSS 3.2.0.

    It seems that since i upgraded to jenkins 1.590, the build release page is no longer populated .

    Last build version is properly set, but all the other fields are empty.

    Can you reproduce?

    the plugin would at least display a target repo for deploying (the one set  for releases in the job configuration)

  4. Unknown User (mmorizot42)

    found this log in the jenkins system log when invoquing the "artifactory release staging" page :Nov 28, 2014 10:14:21 AM WARNING hudson.ExpressionFactory2$JexlExpression evaluate
    Caught exception evaluating: !it.artifactoryPro ? 'disabled' : null in /view/BUILD-COMMON_COMPONENTS/job/XXXXXX/release/. Reason: java.lang.reflect.InvocationTargetException
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)

  5. Unknown User (otinanism)

    In case of a multi-module project with a flat directory structure the plugin does not work. It does correctly tag and update the parent project but the child projects are not updated (poms reference old version of parent) and they are also not tagged. But the artifacts are correctly generated and deployed in Artifactory.