7 ms·

Sounds like your problem is with your admin department and not jenkins...

• setquk 8y ago
  As the admin department of a company that runs Jenkins, it’s the second worst thing we have to keep alive (black duck software was the worst). Jenkins is leaky, unstable, unfriendly to the filesystem, buggy and poorly documented and tested. If you’re going to do anything like this it’s actually worth paying for team city or something else.
  • tslug 8y ago
    Agreed. In a gig last year, I needed to improve the build turnaround times on a Jenkins system. After learning everything I could about Jenkins, I realized the correct answer was to delete it and rewrite my own version that ran on the local system, which was way, way faster and much easier to debug and maintain. Not having to commit/upload your code to a build server and then wait to get an executable/package back is an enormous time-saver just in that overhead alone, but even the build itself was faster, even though it was written entirely in bashscript. Go figure.