Diagnose WMI problems

Related Posts

• Case Study: PlateSpin and FinalBuilder

  Adam White, Manager of Test Engineering at PlateSpin talks about how FinalBuilder revolutionized their build process.

• A One Day Special

  The story of running a one day special of Automise via Bits du Jour.

• Fun and games with HTML email

  FinalBuilder has been able to send HTML emails for some time, but it's not as flexible as some users required.

• Creating a self-signed SSL certificate for IIS

  We recently had a bug report in the Vault support of FinalBuilder. The bug was that if SSL encrypted client to server communication was enabled...

• Code Signing with USB Tokens

  Big changes are coming for OV (Organisation Validation) code signing certificates - from (1 June 2023, extended from 15 November 2022), new and reissued publicly trusted organization validation (OV) and individual validation (IV) code signing certificates will have to be issued or stored on preconfigured secure hardware by the issuing certificate authority (CA) and the device must meet FIPS 140 Level 2, Common Criteria EAL 4+ or equivalent security standards.

• Continuous Integration Server performance

  Continuous Integration Servers are often underspecified when it comes to hardware. In the early days of Automated Builds, the build server was quite often that old pc in the corner of the office, or an old server in the data center that no one else wanted. Developers weren't doing many builds per day, so it worked, it was probably slow but that didn't seem to matter much. Fast forward 20 years, and the CI server is now a critical service. The volume and frequency of builds has increased dramatically, and a slow CI server can be a real problem in an environment where we want fast feedback on that code we just committed (even though it "worked on my machine"). Continuous Deployment only adds to the workload of the CI server. In this post I'm going to cover off some ideas to hopefully improve the performance of your CI server.