![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
gradle |
|
Created:
|
07/Apr/13 7:14 AM
|
|
Description:
|
When I configure a job to use the gradlewrapper gradlew gets changed (and possibly a bunch of directories created).
This is a problem at least to me, since I'd like to use the job for releasing and the release plugin checks that the workingcopy is unmodified (which I can disable, but which is actually a useful and important feature to get reproducable builds)
Here is a stackoverflow question, created by myself regarding the issue ( http://stackoverflow.com/q/15847518/66686 ):
The plugin starts by checking if my working copy is clean, so that only properly versioned stuff gets released.
This works just fine on my local machine. But when I try the same thing in a Jenkins job, the build fails complaining various stuff is changed in the workplace. I decided that a lot of stuff was just internally used by jenkins and added it to `gitignore`:
caches/
native/
wrapper/
But it also considers `gradlew` as changed:
FAILURE: Build failed with an exception.
- What went wrong:
Execution failed for task ':checkCommitNeeded'.
> You have uncommitted files:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
M gradlew
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Environment:
|
Cloudbees Jenkins; Gradle Plugin Version 1.22
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jens Schauder
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
