https://dchua.com/tags/cicd/ Recent content in cicd on davidchua Hugo -- gohugo.io en-us Fri, 10 Jun 2016 00:00:00 +0000 https://dchua.com/posts/2016-06-10-getting-started-with-jenkins-using-docker/ Fri, 10 Jun 2016 00:00:00 +0000 https://dchua.com/posts/2016-06-10-getting-started-with-jenkins-using-docker/ $ docker run --user root --privileged -p 8080:8080 -p 50000:50000 -v /path/to/host/volume:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock jenkins Lets break it down. -p 8080:8080 What we’re doing here is to expose the Jenkins port on the container out to the host. Jenkins uses 8080 by default so you may want to change the host port to a port that you find comfortable. -p 50000:50000 Jenkins uses port 50000 for its REST API. Expose this too. https://dchua.com/posts/2016-06-02-installing-jenkins-plugins-with-their-dependencies-in-one-step/ Thu, 02 Jun 2016 00:00:00 +0000 https://dchua.com/posts/2016-06-02-installing-jenkins-plugins-with-their-dependencies-in-one-step/ Assuming that your Jenkins server is listening at port 8080, all you need to do is to run the following curl command: $ curl -X POST -d '<jenkins><install plugin="[email protected]" /></jenkins>' --header 'Content-Type: text/xml' http://localhost:8080/pluginManager/installNecessaryPlugins Replace [email protected] with the name of your plugin you’re trying to install by looking for the plugin-id in the plugin’s page. ie for Docker Build Step, the Plugin ID listed on the page is docker-build-step So your curl script should look something like: https://dchua.com/posts/2010-05-04-getting-integrity-up-and-running-w-email-notification-and-test-database-raking/ Tue, 04 May 2010 00:00:00 +0000 https://dchua.com/posts/2010-05-04-getting-integrity-up-and-running-w-email-notification-and-test-database-raking/ After spending a couple of hours trying to get integrity setup, I thought I’ll share and document my process for future reference. So what is Integrity? From their website: “As soon as you push your commits, Integrity builds your code, run your tests and makes sure everything works fine. It then reports the build status using various notifiers back to you and your team so everyone is on the same page and problems can be fixed right away.