Release Automation

Expand all | Collapse all

Uploading Artifacts & Registration Failures

Jump to Best Answer
  • 1.  Uploading Artifacts & Registration Failures

    Posted 12-16-2016 09:12 AM

    Hello Members,

     

    I see below errors for artifacts creations and uploads to Nolio repo.

    Artifact [ArtifactTypeName. war ArtifactDefinitionName. acknowledgementService.war Ver. 21] was created successfully, but failed to upload to Nolio default repository
    Internal Error:
    Artifact [ArtifactTypeName. war ArtifactDefinitionName. acknowledgementService.war Ver. 21] upload failed, Download failed on artifact retrieval agent: Retrieval action failed - Source file does not exist - /apps/tes/jenkinsworkspace/workspace/CARA_ELMSUIServices_AcknowledgementService/target/*.war

     

    Can you help me on the same?

     

    Few Points Noticed:

    a) Tried all options by specifying name of artifact in CREATE LOCAL ARTIFACT action task

    b) I am using the same server as an RETRIEVAL AGENT for fetching/uploading artifacts

    c) After clicking on EDIT option and simply saving the artifacts works well. Not sure, why packaging process is failing!

    This something weird.

     

     



  • 2.  Re: Uploading Artifacts & Registration Failures

    Broadcom Employee
    Posted 12-16-2016 09:31 AM

    Hello,

     

    It looks like you are using a wildcard in the /path/to/file: /apps/tes/jenkinsworkspace/workspace/CARA_ELMSUIServices_AcknowledgementService/target/*.war

     

    Does it work if you point it to a single file that does exist on that retrieval agent machine/path?

     

    Regards,

    Gregg



  • 3.  Re: Uploading Artifacts & Registration Failures

    Posted 12-16-2016 11:35 AM

    Yes, it works by pointing an actual artifact name in task.

    However, the .war file name changes for every build. How can we handle this scenario after hard coding the artifact name?

    /apps/tes/jenkinsworkspace/CARA_ELMSUIServices_AcknowledgementService/target/acknowledgementService-2016-12-16-07.50.30.war



  • 4.  Re: Uploading Artifacts & Registration Failures

    Broadcom Employee
    Posted 12-16-2016 03:35 PM

    There are some actions that you can use to first get the file names in a given folder and then, via other actions, create the artifact with the filenames you have found. Prior to 6.3 it looks like artifact packages had to be assigned prior to running a deployment plan (for example: during the pre-plan). With the release of 6.3 it appears that they have given the ability to add a package during the pre-deploy step/phase:

     

    o   Add package at the Pre-Deployment stage per environment – Users can define and add an environment package within a pre-deployment step

     

    I hope this helps.

     

    Regards,
    Gregg



  • 5.  Re: Uploading Artifacts & Registration Failures
    Best Answer

    Posted 12-23-2016 04:11 AM

    Thanks! Made a small change in Jenkins shell execution script to copy war file into temp directory and renamed it to a specific name! Meanwhile, pointed/provided this name in Create Artifacts Action view and build a simple flow for packaging step!

     

    Sample:

    mkdir -p /tmp/CARA_ELMSUIServices_AddProductService/artifacts
    cd /tmp/CARA_ELMSUIServices_AddProductService/artifacts/
    rm -rf /tmp/CARA_ELMSUIServices_AddProductService/artifacts/*.war
    cp /apps/tes/jenkinsworkspace/workspace/CARA_ELMSUIServices_AddProductService/target/*.war .
    mv *.war addProductService.war