You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am facing an issue now while executing the 'candidate' task with a Jenkins pipline. The issue is:
The jenkins job is running on a master node. While executing the job with the candidate task, I first have to give the access using chmod command to gradle wrapper script file('/gradlew') which resides in the root folder of project. I believe the plugin is considering this as a change to a file and asks it to be committed to execute candidate task.
The steps in my build script are: stage('Build') {
steps {
script {
sh 'chmod +x gradlew'
sh './gradlew clean build candidate -x test'
}
}
}
The error thrown by plugin is:
What went wrong:
An exception occurred applying plugin request [id: 'nebula.release', version: '13.0.0']
Failed to apply plugin 'nebula.release'. > Final and candidate builds require all changes to be committed into Git.
Found unstaged changes:
[M] gradlew
Is there any way around it?.
The text was updated successfully, but these errors were encountered:
You can do chmod +x gradlew and commit/push the change into the repository. That way you don't need to do it as part of your build every time and you will also solve the error.
Hi
I am facing an issue now while executing the 'candidate' task with a Jenkins pipline. The issue is:
The jenkins job is running on a master node. While executing the job with the candidate task, I first have to give the access using chmod command to gradle wrapper script file('/gradlew') which resides in the root folder of project. I believe the plugin is considering this as a change to a file and asks it to be committed to execute candidate task.
The steps in my build script are:
stage('Build') {
steps {
script {
sh 'chmod +x gradlew'
sh './gradlew clean build candidate -x test'
}
}
}
The error thrown by plugin is:
An exception occurred applying plugin request [id: 'nebula.release', version: '13.0.0']
Is there any way around it?.
The text was updated successfully, but these errors were encountered: