Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push artifact path problem when master is Windows and agent is Linux #73

Open
vladistan opened this issue Dec 7, 2019 · 0 comments
Open

Comments

@vladistan
Copy link

vladistan commented Dec 7, 2019

I have a master running on Windows machine, and one of the agents is a linux machine. I am trying to setup a job that will upload the artifact to S3 using this plugin. Unfortunately I see there is a problem with this type of setup. Apparently the master is trying to compose the string with the location of the and uses Windows path separator on linux box.

Here is what I see in the build logs

[go] Task: Plugin with ID: indix.s3publishtook: 0.447s
Pushing /var/lib/go-agent2/pipelines\with-manual-steps/base_ami.txt to s3://persyst-binary-repo/with-manual-steps/autoTrigger1/AutoJob1/56.4/base_ami.txt
Unable to calculate MD5 hash: /var/lib/go-agent2/pipelines\with-manual-steps/base_ami.txt (No such file or directory)
[go] Task status: failed, took: 0.447s

Look at the slash after the pipelines....

I think now all operating systems understand / as a path separator, so might be no need to use OS specific one.

My GOCD Version is: GoCD Version: 19.2.0 (8641-db17f5840f9d1c6838add93af050b812bbdf5c68).

Plugin version is : 5.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant