[GRADLE-335] Gradle Hudson plugin issue Created: 27/Dec/08 Updated: 24/Jan/17 Resolved: 24/Jan/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.5 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Tom Eyckmans | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 2 |
| Issue Links: |
|
||||||||
| Description |
|
I tried the Gradle Hudson plugin and stumbled upon an issue. Hudson jobs are run from a <job-name>/workspace directory. Because of this the Gradle way of working (depending on the directory name for the project name) is broken; the archives that are created by libs/ dists won't get the correct name (if you don't set the archiveBaseName). As I mentioned earlier, the solution is simple set the archiveBaseName if you can't rely on the directory name, but perhaps we want to make sure builds are repeatable/ consistent without knowledge of the directory that is used. Any thoughts/ ideas on this would be appreciated. |
| Comments |
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Benjamin Muschko [ 24/Jan/17 ] |
|
I'd suggest you open the issue here if you still encounter a problem: https://wiki.jenkins-ci.org/display/JENKINS/Gradle+Plugin. |