Help documentation

Troubleshooting

Please check out the support forums on the Cruise website.

Scheduling problems

If your changes do not get detected by Cruise, or they come in several batches, then you may have a scheduling problem. Always make sure the computer on which your version control system sits has a synchronized clock. Also make sure it is in the same time zone as Cruise Server.

Sometimes you may get security problems when scheduling. Apart from the usual suspects of using the wrong username or password, security errors can also get caused by problems like not having a valid certificate (if you're using https to connect to your version control system) or by network connectivity problems between Cruise and your version control system.

GIT Integration on Windows

Cruise does not support plain GIT on windows. You have to install msysGit 1.6.0.2 instead. You should add the directories 'bin' and 'cmd' under '${GIT-installed-path}' to the end of the system path. If you have just installed Git, you should restart the server or agents so they can detect the changed system path.

Modification tab shows a single modified file as several files.

This only happens when the name of the file in the Mercurial repository includes whitespace. Mercurial shows them as multiple files in modification information.

Cannot see the artifacts or console output in the job details page

  • If someone deleted the artifacts of the job from the filesystem, you won't see them on the job details page. Cruise will still remember the details of the job however.

    • Job is still shown as running even though it has finished.

  • If there is no disk space on the Cruise Server, Cruise will not work as expected. Jobs are built and finished but the server cannot accept any artifacts from the jobs, and they appear to hang. This is a known issue. The solution is to clean up the server to get more disk space, and restart it.
  • There is a limitation on the number of files or subfolders in a folder. On linux, the max number of files in a folder is 31999. Please check the number of artifacts folder (/var/lib/cruise-server/logs by default) present. If you have reached the limit, you can either delete the older subfolder or change the location of artifacts folder in cruise-config.xml.

    • Cannot see the newly added pipeline

    You can see them when the pipeline gets triggered. Specially for big repository in Git and Mercurial, it takes longer. Because of how these two SCMs work, Cruise server checks out the code locally and hence takes a longer time.

    Stages are not executed after adding a new stage or changing the order of the stages

    Problem description:

    Lets say you want to execute the stages in the following order: setBuildEnvStage -> preBuildStage -> buildStage -> postBuildStage -> unitTestStage. The pipeline is correctly configured. If I trigger the pipeline manually the first two stages are executed, but the others are not. The first two stages succeed and the pipeline activity page is strange.

    What would lead to this situation?

  • The stage name has been changed and nothing has been committed yet, after the change in the configuration.

    • How does Cruise work?

  • Cruise does not support renaming pipelines, stages and jobs yet. If the you rename, Cruise will not show the history for the old stage and/or job. The history is actually still present but it does not show up. If you change the name back, the history would show up again.
  • Suppose you triggered the pipeline manually and there are no new modifications in the repository, Cruise would re-run the latest stage, not trigger a new one, even though the configuration is changed.
  • For this case, since the stage 'unitTestStage' was the end of the current config file, Cruise thought it should be the end of the pipeline. So Cruise stops after it runs stage 'unitTestStage'.

    • How to fix it?

  • Commit something into the repository to force the new pipeline to start.

    • Failed to install Cruise on Windows Vista

    Vista has a different user management strategy. So please make sure that the directory Cruise is installed on is owned by the Cruise service owner.

    Job passed but 'java.exe' was not in the path of agents while building using ANT on Windows

    Cruise identifies whether tasks passed or not by their exit code. However, even if ANT could not find 'java.exe' in the path, it returns '0' rather than '1' on Windows. Hence the job appears as passed. This is an issue with Ant.