Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11641

when Rakefile is not in the default location, "Rake working directory" setting does not work

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • rake-plugin
    • Windows Server 2008 R2 Standard 64-bit
      Jenkins 1.437 (installed via native package for windows)
      Jenkins Rake plugin 1.7.7
      ruby 1.9.2p290 (2011-07-09) [i386-mingw32]
      rake 0.9.2.2

      • create new free style project
      • in git repository there are Rakefiles in root folder (workspace/Rakefile) and in spec folder (workspace/spec/Rakefile)
      • create "Invoke Rake" build step
      • click button "Advanced" for Rake
      • set "Rake working directory" to "spec"
      • Rakefile just outputs working directory, it looks like this:
       
      task :default do
        puts Dir.pwd
      end
      
      • save changes
      • run build
      • console output is:
      ...
      [spec] $ rake.bat
      C:/Jenkins/jobs/testjob/workspace/spec
      Finished: SUCCESS
      
      • so far so good
      • go to "configure build job" screen and change "Rake file" to "spec/Rakefile"
      • save changes
      • run build
      • console output is:
      ...
      [spec] $ rake.bat --rakefile spec/Rakefile
      (in C:/Jenkins/jobs/test/workspace)
      C:/Jenkins/jobs/testjob/workspace
      Finished: SUCCESS
      
      • when Rakefile is not in the default location, "Rake working directory" setting does not work

          [JENKINS-11641] when Rakefile is not in the default location, "Rake working directory" setting does not work

          +1 on this issue. I love the above description, and wish all my users were so good at stating the issue clearly. Could the issue be upgraded from Minor?

          Steve Eckhardt added a comment - +1 on this issue. I love the above description, and wish all my users were so good at stating the issue clearly. Could the issue be upgraded from Minor?

          <blush> I just figured out why this is minor. If you use the standard name for the rake file and just set the working directory, it works. In the above example, all the user would have had to do is leave "Rakefile" in the spec directory and set the working directory to "spec". It is not necessary to have the "Rakefile" in "workspace".

          Steve Eckhardt added a comment - <blush> I just figured out why this is minor. If you use the standard name for the rake file and just set the working directory, it works. In the above example, all the user would have had to do is leave "Rakefile" in the spec directory and set the working directory to "spec". It is not necessary to have the "Rakefile" in "workspace".

            david_calavera david_calavera
            zeljkofilipin Ċ½eljko Filipin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: