In a previous job I was asked to set up CI & (almost) automatic deployment for a financial pricing library + UI which had a large multi-step build and an annoying test-routine - which included loads of regression tests which had been written in MS-Excel.
This was a desktop application used by a few hundred commodities traders. The deployment was an utter nuisance because of the number of components involved (eggs, XLLs, DLLs, configuration files). The structure of the project was set in stone. My job was to make the test & deployment process better. One of the things I built to make this happen was a Python API for easily getting at stuff built in Jenkins. I'd set up a pipeline of jobs which might build and then test each component of the build. Furthermore, the API could reliably query Jenkins, and perform tasks such as retrieving a set of artifacts from the most recent run with no test-failures. I was able to use my JenkinsAPI to fetch the component built in the previous stage (stored as a Jenkins Artifact) and then quickly deploy that into the into the Jenkins workspace downstream. You can get it here: https://github.com/salimfadhley/jenkinsapi ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. _______________________________________________ python-uk mailing list python-uk@python.org http://mail.python.org/mailman/listinfo/python-uk
