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

Doesn't work if the job is being built on a slave #63

Open
urjitbhatia opened this issue Jul 18, 2016 · 2 comments
Open

Doesn't work if the job is being built on a slave #63

urjitbhatia opened this issue Jul 18, 2016 · 2 comments
Labels

Comments

@urjitbhatia
Copy link

If I run my build job on a jenkins slave, the plugin still looks for the appspec.yml on the master. Is there any workaround for this?

@Jmcfar Jmcfar added the bug label Aug 17, 2016
@Dries-Vandenneucker
Copy link

I don't think this is a bug. We only run jobs on slaves and they all use codedeploy.

Is it possible you use the setting "Use own workspace" under General? "...If this path is relative, it's resolved against the "remote FS root" directory of the slave, or $JENKINS_HOME on the master." So maybe you are resolving against the master?

@delpinoconsulting
Copy link

Sorry to resurrect the thread, but I have the same issue. I'm building on a Jenkins node, but if I use Per-deployment appspec files, the job never finds it regardless if I specify the workspace. Would appreciate some configuration help.

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

No branches or pull requests

4 participants