Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

During CI - No such file or directory - var/jenkins/jobs/ruby/config.xml #13

Open
drnic opened this issue Apr 13, 2011 · 3 comments
Open
Labels

Comments

@drnic
Copy link
Contributor

drnic commented Apr 13, 2011

When the jenkins.rb feature suite runs in CI (both http://ec2-184-73-167-68.compute-1.amazonaws.com/job/jenkins.rb/4/console & http://jenkins.thefrontside.net/job/jenkins.rb/35/console) the features/manage_jobs.feature:47 feature fails with:

 No such file or directory - /data/jenkins-ci/jobs/jenkins.rb/workspace/var/jenkins/jobs/ruby/config.xml (Errno::ENOENT)
      ./features/step_definitions/jenkins_steps.rb:106:in `read'
      ./features/step_definitions/jenkins_steps.rb:106:in `/^the job "([^"]*)" config "([^"]*)" should be:$/'
      features/manage_jobs.feature:52:in `And the job "ruby" config "scm" should be:'

When the same scenario is run directly within a console on the CI server it works:

$ bundle exec rake jenkins:server:test &
$ bundle exec cucumber features/manage_jobs.feature:47
@drnic
Copy link
Contributor Author

drnic commented Apr 13, 2011

All the features pass inside the console if bundle exec rake is run directly. Not sure why this is failing when invoked from within Jenkins.

@cowboyd
Copy link
Member

cowboyd commented Apr 13, 2011

What is the current directory when executing from jenkins?

@drnic
Copy link
Contributor Author

drnic commented Apr 13, 2011

When I run it manually I run it from /data/jenkins-ci/jobs/jenkins.rb/workspace. I'm not sure what Jenkins is doing when it runs "bundle exec rake" itself.

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

No branches or pull requests

2 participants