Details
-
Improvement
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
all
Description
it would be desirable for full cross-platform scripting of bigger cmake-projects to be able to run cmake scripts (cmake -P <script file>).
This is not possible at the moment as the plugin fails the build if it doesn't find a CMakeCache,txt, so even though the script file specified with a -P command-line option runs properly, the build will always fail.
Even though it would be possible to launch cmake via a shell command, this is not desirable as it requires cmake to be in the PATH of the build slave, creating conflicts as soon as multiple cmake installation are present. I believe it would be advantageous if the CMake tool configuration could be reused for this.
Attachments
Activity
Martin Weber
added a comment - Existing build steps will loose their cmake-argument and working dir settings.
Martin Weber
added a comment - Existing build steps will loose their cmake-argument and working dir settings. Code changed in jenkins
User: 15knots
Path:
src/main/java/hudson/plugins/cmake/AbstractCmakeBuilder.java
src/main/java/hudson/plugins/cmake/CmakeBuilder.java
http://jenkins-ci.org/commit/cmakebuilder-plugin/7d548881b1b7b91c61b9dfd4b61ebfb5bd23ccb5
Log:
FIXED JENKINS-32657: (Reopened) Existing build steps will loose their
cmake-argument and working directory settings.
Jörg Ziegler
added a comment - thanks for the quick fix. Now that I had already renamed the tags manually, is it safe to upgrade to 2.4.1?
Jörg Ziegler
added a comment - thanks for the quick fix. Now that I had already renamed the tags manually, is it safe to upgrade to 2.4.1? Martin Weber
added a comment - It is safe.
The fix in 2.4.1 just renames the tags, nothing more 
Thanks for reporting the cmakeArgs/toolArgs issue.
This is serious, as it causes existing buildsteps to forget part of their configuration.
I´ll prepare a fix ASAP.