Deploy IS package with jenkin error

, ,
1

When I follow tutorial in Demo: Continuous Integration with webMethods - YouTube
I have error log in projectAutomatorReport.xml file :

<Messages type="ERROR">
        <message category="environment" errorCode="-99">Error updating Repository Alias esb-autobuild/angelSAGRepo</message>
        <message category="environment" errorCode="-86">Error retrieving repo objects from Repo Server esb-autobuild/angelSAGRepo</message>
        <message category="projectError" deploymentCandidate=""
            deploymentMap="" deploymentProject="esb-autobuild/angelSAG"
            deploymentSet="myDeploymentSet" errorCode="-102">Error adding asset * from esb-autobuild/angelSAGRepo to the Deployment Set myDeploymentSet. The asset is not present on the source</message>
        <message category="projectError" deploymentCandidate=""
            deploymentMap="" deploymentProject="esb-autobuild/angelSAG"
            deploymentSet="myDeploymentSet" errorCode="-102">Error adding asset * from esb-autobuild/angelSAGRepo to the Deployment Set myDeploymentSet. The asset is not present on the source</message>
        <message category="projectCreation" deploymentCandidate=""
            deploymentMap="" deploymentProject="esb-autobuild/angelSAG" errorCode="-59">Error creating Project esb-autobuild/angelSAG : [DEP.0002.0012] Project name esb-autobuild/angelSAG contains illegal characters.</message>
        <message category="projectError" deploymentCandidate=""
            deploymentMap="" deploymentProject="esb-autobuild/angelSAG"
            deploymentSet="myDeploymentSet" errorCode="-31">Error creating set myDeploymentSet of type Repository in Project esb-autobuild/angelSAG : [DEP.0002.0000] Project esb-autobuild/angelSAG does not exist.</message>
        <message category="projectError" deploymentCandidate=""
            deploymentMap="" deploymentProject="esb-autobuild/angelSAG"
            deploymentSet="myDeploymentSet" errorCode="-33">Error adding source server aliases esb-autobuild/angelSAGRepo, to deployment set myDeploymentSet in Project esb-autobuild/angelSAG</message>
        <message category="autoResolve" deploymentCandidate=""
            deploymentMap="" deploymentProject="esb-autobuild/angelSAG"
            deploymentSet="myDeploymentSet" errorCode="-58">Error auto resolving dependency for Repository set myDeploymentSet in Project esb-autobuild/angelSAG</message>
        <message category="projectError" deploymentCandidate=""
            deploymentMap="myDeploymentMap"
            deploymentProject="esb-autobuild/angelSAG" errorCode="-63">Error creating map myDeploymentMap in Project esb-autobuild/angelSAG : [DEP.0002.0019] Deployment map myDeploymentMap already exists in project esb-autobuild/angelSAG.</message>
        <message category="projectError" deploymentCandidate=""
            deploymentMap="myDeploymentMap"
            deploymentProject="esb-autobuild/angelSAG" errorCode="-67">Error adding server aliases to deployment map myDeploymentMap in Project esb-autobuild/angelSAG : [DEP.0002.0021] Deployer could not load deployment map myDeploymentMap from project esb-autobuild/angelSAG.</message>
        <message category="projectError"
            deploymentCandidate="myDeployment" deploymentMap=""
            deploymentProject="esb-autobuild/angelSAG" errorCode="-65">Error creating build myDeployment in Project esb-autobuild/angelSAG</message>
    </Messages>

What is “The asset is not present on the source”?
I dont know how to continue, please help me, thank you

2

Hi Vu Hoang,
“asset is not present on the source” shows that it’s an operation that tries to deploy an asset using a source repository or server but there are a lot more errors in the messages snippet. Most of these contain angelSAG in the name. While following the tutorial please make sure you have the corresponding file structure and update folder / project / asset names accordingly.
Best Regards,
Veselin

1 Like
3

I checked and found this because I config wrong assest directory , thank you for your response

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.