Hi, The Dutch Rabobank Organization is using Jenkins concerning Continuous Integration of mainly Java sources. With regards to afore mentioned the following. It is concerning to get two major problems solved in connection with our Jenkins CI system. The combination of the problems is hindering us from upgrading our Jenkins installation.
The problems are: - Windows crashing with a Blue Screen of Death - The Fortify plugin no longer works above Jenkins version 1.509.4 The context of our system is as follows. Configuration: - One Master: on a dedicated server - Two Slaves: each slave is using a separate server - Jenkins version 1.509.4 - The Operating System installed on each server is: Windows 2008 R2 Enterprise SP1 We are using Windows because of the enterprise Active Directory to authorize users in Jenkins using smart logon. Afore mentioned is no option with regards to our Unix/Linux systems. >From the Jenkins-ci.org website we understand that the BSoD problem has been >worked around in Jenkins version 1.580.x or higher. This means that upgrading >to one of the latest (non LTS) versions would be a (temporary) solution for >our problem. But, to solve BSoD's is not the only challenge. On our system Jenkins build jobs are also used for scanning sources using Fortify. Therefore the Fortify plugin is installed. At the moment we are using Fortify SSC web-application version 4.02. The Fortify client (SCA) application is installed on each Jenkins server. The version of the Fortify plugin is: 3.81. The Fortify plugin is working in Jenkins 1.509.4 using a workaround. The workaround is: renaming the fortify-common-4.02.jar file in the Fortify client installation ...\Core\lib folder to fortify-common-3.80.jar. If we upgrade Jenkins on the test system, than afore mentioned workaround is no longer sufficient. Additional the workaround concerning to using Fortify mentioned on the Jenkins-ci.org website does not work. The workaround meant is: https://issues.jenkins-ci.org/browse/JENKINS-21332. More specific: unpacking the classes.jar in WEB-INF\classes. One of the symptoms is: in the Jenkins configuration Jenkins is not going to connect to Fortify. With regards to the above described situation our question to you: how are we able to upgrade Jenkins on Windows to the latest LTS version and also use the Fortify plugin? Looking forward to your reply, kind regards, Gerrit Wessels Rabobank Nederland GICT ADM Development Support ====================================================== Rabobank disclaimer: http://www.rabobank.nl/disclaimer -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
