title: Gradle Project Not Naming Archives Properly Under Jenkins
body: <p>I have a number of Gradle builds that work very well from the command line, from buildship, etc.</p>
  
  <p>However now I am porting them to a Jenkins system. And it is producing some very strange results. I'm pretty much a total newbie to Jenkins, so this may have an easy answer. So far I haven't found it.</p>
  
  <p>I am using the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Gradle+Plugin" rel="nofollow">Gradle Plugin for Jenkins, v.1.24</a> to configure my build in Jenkins. However, Jenkins (at least as I have it configured) organizes its build structure as <code>{jenkins root}/data/jobs/{project_name}/workspace</code>. When code is checked out of source control it is deposited in that directory, not in a directory named <code>{project_name}</code>.</p>
  
  <p>Gradle seems to assume that the directory in which it is running names the project, and when I'm running outside of Jenkins this assumption is true. The name of the project that Gradle sees is the name of the project that was checked out from source control. Project.name is a gettable but not a settable property of a gradle Project. So in the Jenkins case, the archives that gradle builds are named <code>workspace*</code> rather than <code>{project_name}*</code>. It is also named <code>workspace</code> in the repositories it publishes into. I must be missing something very obvious but for the life of me I cannot figure out what it is.</p>
  
  <p>Has anyone grappled with this?</p>
  
  <p><strong>UPDATE</strong> - It appears that the problem is that the people who designed my Jenkins instance knew nothing about Gradle. The <code>{jenkins root}/data/jobs/{project_name}/workspace</code> layout that I described above is not required by Jenkins, but apparently was felt to be useful for some reason in some other, non-Gradle context.  So the question becomes, where is the project layout set up in the Jenkins configuration - OR - can Gradle be modified somehow to assume a different project layout/naming strategy.</p>