Automic Continuous Delivery Automation

Expand all | Collapse all

Jenkins Action Pack


JagdishGidwani60906904-02-2018 10:14 AM

  • 1.  Jenkins Action Pack

    Posted 03-07-2018 05:33 AM


    I am using PCK.AUTOMIC.JENKINS but it fail to execute as the parameter has restricted characters (&) . Can you please help me with an example how to use this action pack.



  • 2.  Jenkins Action Pack

    Posted 04-02-2018 10:14 AM
    Tran-Hoang_Hau_348  - Please help here.

  • 3.  Jenkins Action Pack

    Posted 04-03-2018 12:10 AM
    Jagdish Gidwani said:
    Tran-Hoang_Hau_348  - Please help here.
    I am gonna send you an email :smile:

  • 4.  Jenkins Action Pack

    Posted 03-08-2018 06:22 AM

    But when I try in URL in browser I didn't find any issue like this.

  • 5.  Jenkins Action Pack

    Posted 03-07-2018 05:34 AM

    Here is the URL from where I downloaded the pack

  • 6.  Jenkins Action Pack

    Posted 03-07-2018 10:13 PM

    Hi Martin,

    I used parameter in below way:

    In Jenkin url::

    Parameter :: token=AUTOMIC_TEST_123456&cause=Automic_test

    tried with && as well I got error

    'cause' is not recognized as an internal or external command,



  • 7.  Jenkins Action Pack

    Posted 03-08-2018 04:04 AM


    We don't have access for dropbox can you please paste it without using dropbox.



  • 8.  Jenkins Action Pack

    Posted 03-08-2018 04:14 AM

    I used Parameter :: token=AUTOMIC_TEST_123456,cause=Automic_test

    and getting below text and it is in loop. Please share the image and help me to resolve this because I need this to work on

    09:11:50.995 [main] INFO  c.a.a.feature.jenkins.TriggerBuild - Sleep for 5 seconds...

  • 9.  Jenkins Action Pack

    Posted 03-08-2018 05:36 AM
    Are you sure that it didn't trigger the requested build?
    Because this looks to me as if the build was in fact triggered and that there is a step within that build to "sleep" for 5 seconds. The message you pasted is comming from Jenkins, not from ARA.

  • 10.  Jenkins Action Pack

    Posted 03-08-2018 07:38 AM
    But did it start? Can you check in Jenkins directly (logging into the UserInterface of Jenkins and looking at the build process)? Does the build complete? If so, can you check the "console" output?


  • 11.  Jenkins Action Pack

    Posted 03-15-2018 10:45 AM
    Hello martin_polak_automic
    Yes it did start and completed successfully on Jenkins , but on Automic it keeps running / polling for status.

    On failed / cancelled builds it is able to successfully capture the status and end with appropriate failure.

    Additional information on building with parameters in case the parameter name has space one should use + sign in the name. e.g. Parameter+Name=Value

  • 12.  Jenkins Action Pack

    Posted 03-07-2018 07:56 AM
    Hi Jagdish,

    have you tried "escaping" the & by another &, so "&" -> "&&" and "&&" -> "&&&&" etc.

    Also, it would be interesting to see exactly
    * Which Variables you filled into the Promptset
    * Which Values these Variables have
    * A screenshot of the Promptset.


  • 13.  Jenkins Action Pack

    Posted 03-08-2018 04:12 AM

    hovering over that label (The word "Parameters" in the Promptset) shows:
    "A comma-separated list of parameter=value pairs used to pass to a parametrized job.myParameter = value1, myParameter2=value2"


  • 14.  Jenkins Action Pack

    Posted 03-08-2018 03:46 AM

    you need to separate the parameters by a comma (",").

    This can be found out by hovering with the mouse cursor over the label of the respective field, see