I am trying to copy the artifact (i.e gchEar.ear shown in log file below)to remote server but getting the error like there is no file to upload
The log file of build containing the artifact, deployment log and configuration the scp task is as follow for your reference. Can any one help me to resolve this issue.
image2015-6-10 14:36:13.png
image2015-6-10 14:17:50.png
image2015-6-10 14:12:23.png
Hello Aakash,
Thank you for your reply.
If you EAR file can be located in the Build Working Directory for your deployment (/usr/appl/cie/home/uatcie/bamboo-home/xml-data/build-dir/6651906/13500417-14548993) and its full path is (/usr/appl/cie/home/uatcie/bamboo-home/xml-data/build-dir/6651906/13500417-14548993/gchEar.ear).
As our documentation Using the SCP task in Bamboo suggests:
The local path (relative to the Bamboo working directory) to the files you want to copy. Use commas to separate files and directories. You can also use Ant-style pattern matching to include multiple files, such as
**/target/*.jar
.
You could place *.ear or gchEar.ear in Local Path input field.
If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.
Thank you for your understanding.
—
Kind regards,
Rafael P. Sperafico
Atlassian Support
@ Rafael Aperafico :thankyou very much for your input:
Actually,above I provided you the path of Build working directory of Build plan not the deployment plan.
I tried with your suggestion, but again got the same error.
In "local path" I had given the path same (/usr/appl/cie/home/uatcie/bamboo-home/xml-data/build-dir/6651906/13500417-14548993/gchEar.ear) as shown in deployment log which has artifact also which I confirmed with ls -l command script task.
but still I am getting the error of there were no files to upload. am I missing something in Scp task configuration, Isn't the location of artifact?
Below is scp task configuration screenshot and deployment log screenshot for your reference:
Also the artifact named gchEar.ear and gchWeb.war can be seen clearly here belo:
image2015-6-12 16:34:27.png
image2015-6-12 16:2:33.png
image2015-6-12 16:0:10.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Aakash,
Thank you for your question.
Please, visit the Build Working Directory, 2nd line in the build log below and review where the artifacts are being downloaded to:
image2015-6-11 11:11:2.png
Please, make sure the "Local Path" given can be resolved based on the Build Working Directory above and its artifacts location.
If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.
Thank you for your understanding.
—
Kind regards,
Rafael P. Sperafico
Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the artifact is found here: i.e gchEar.ear /usr/appl/cie/home/uatcie/bamboo-home/xml-data/build-dir/6651906/JA1-GCHJAV-JOB1/gchEar/target/gchEar.ear and I provide the "local path" the same path. The is a artifact but the log gives an error saying there is no files to upload, what is the problem I am having just to copy this artifact to remote server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Aakash, Based on the screenshot you have provided for the "Deployment: release 28 on Staging", as mentioned in this thread, please look at the 2nd line in the screenshot which states: 10-Jun-2015 14:16:49 Build Working directory is /usr/appl/cie/home/uatcie/bamboo-home/xml-data/build-dir/6651905/13500417-14548993/ Please, notice the Build Working Directory you have provided (/usr/appl/cie/home/uatcie/bamboo-home/xml-data/build-dir/6651906/JA1-GCHJAV-JOB1/) is not the same as the screenshot suggests. — Kind regards, Rafael P. Sperafico Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.