Skip to content
This repository has been archived by the owner on Mar 8, 2018. It is now read-only.

Vagrant file is not checked properly on build slave #37

Open
pnuz3n opened this issue Mar 4, 2014 · 2 comments
Open

Vagrant file is not checked properly on build slave #37

pnuz3n opened this issue Mar 4, 2014 · 2 comments

Comments

@pnuz3n
Copy link

pnuz3n commented Mar 4, 2014

When using vagrant plugin and running job in jenkins slave, following error is reported:

There is no Vagrantfile in your workspace!
We looked in: /var/lib/jenkins/workspace/korppi-openuniv-studyright-service-vagrant-2
Recording test results
No test report files were found. Configuration error?
Finished: NOT_BUILT

However slave contains Vagrantfile in the given location.

It seems that the check is performed in the code is not properly using slaves resources:

unless FilePath.exists? FilePath.join(path, 'Vagrantfile')
    listener.info("There is no Vagrantfile in your workspace!")
    listener.info("We looked in: #{path}")
    build.native.setResult(Java.hudson.model.Result::NOT_BUILT)
    build.halt
end
@rtyler
Copy link
Owner

rtyler commented Mar 13, 2014

@pnuz3n The problem is that the Ruby plugin code for Jenkins only executes on the Jenkins master. As of right now there is no means of executing Vagrant on a slave :(

@pnuz3n
Copy link
Author

pnuz3n commented Mar 19, 2014

Good to know. We have to find alternative solution then.

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

No branches or pull requests

2 participants