iAditya.com

Green grass and cows grazing - signs of spring.

Puppet Forge is an official PuppetLabs repository of modules written by the community. Modules available in Puppet Forge can be installed from command line. At the time of writing this post, there are 105 modules that are published by PuppetLabs in Puppet Forge and several other vendors and contributors. Let us try the Maestrodev/android module . Notice the OS compatibility list in the screenshot. Step 1: Virtual Machine with Puppet client Setup a new Nitrous.io VM or a Vagrant box with an OS from the list of OSes supported by the module. I executed this on a nitrous.io Ubuntu box. Android SDK takes up a lot of space. When the module is applied on the Ubuntu box, it will fill up the 5GB free space allocation. You will not be able to do anything more with this VM after installing Android SDK. Install the Puppet client from command line. Ubuntu: sudo apt-get install puppet -y RedHat/CentOs: yum install puppet -y Step 2: Install the modoule Run the following command ...

View from the window   Cherry blossoms, camelia, tulip magnolia and peach blossoms (from left to right) Camelia Cherry blossoms with tulip magnolia in the background. Tulip magnolia Camelia  Peach blossoms  Tulip magnolia petals  Camelia

A friend got himself a brand new Lenovo ThinkPad. He wanted to create new virtual machines to play with Puppet, Docker and other tools. Here you go buddy. We will start with some best practices. Best practices I recommend these best practices so that it will be easy to find all virtual machines you create, save disk space and you'll be ready to go in an instant when you want to do something new.  Workspaces Keep all your vagrant workspaces in one folder. I keep mine in c:\workspaces\vagrantWorkspaces because I have workspaces for Eclipse, Visual Studio and others. Surely do back up this folder frequently. Tracking Maintain an excel file or Google Spreadsheet file with a list of all virtual machines you create to reuse and wish to keep. Packaging If you wish to package any of the virtual machines as .box files, store them outside the workspace folders. Keep your workspace small so it is easy and quick to backup. Naming convention Choose a naming convention, so ...

Want to quickly setup Jenkins on the cloud? Try this on http://www.nitrous.io. See a prior post about setting up Dashing.io on Nitrous.io for basics of how to get started on Nitrous.io if required and then come back here. Advantage: If you want to experiment with something new on Jenkins before you run it in a production environment, this will get you going quickly. If you mess up, just re-install in Nitrous.io and start over. Step 1:  Copy the installation commands from this Jenkins-ci page - https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu to a shell script in the Nitrous.io IDE and run the shell script. You could just run them in the command line if you choose. Step 2:  View Jenkins in the browser by previewing port 8080 as seen in the screenshot Jenkins will show up on a new browser window. It works! 

I have been wanting to learn and develop iOS apps or a while. The price of a good developer's Mac was a little unreasonably high and I am quite sure I am not ready to switch over 100% to a Mac anytime soon. I found MacinCloud.com and their pricing is very reasonable. I didn't want to own a Mac, I didn't want to spend a lot of cash, but I wanted to use a Mac for a few hours a day just to learn iOS development. MacinCloud.com just worked out fine. I signed up for the $20 per month service to access a real Mac (not a Virtual Machine) for three hours a day. The device they gave me is a high end Mac Mini with 16GB of RAM and preloaded with all the popular app development tools and platforms out there, including XCode, PhoneGap and a lot of others that I am not even familiar with. Google drive and Dropbox are already installed and so is Chrome and Firefox. Save all your data in Google Drive or Dropbox, share with your team or move your content to your personal laptop. Too many ...

I have been doing a lot of work with presenting Jenkins data in dashboards. Jenkins by default does not come with a built-in database. All the data gets stored in the filesystem. However, Jenkins has a REST API that allows us to read data as json. I searched around the Googlesphere to see if anyone had figured out how to capitalize on this REST API for performing analytics and found almost nothing directly related to this. I was searching for open to public Jenkins instances to see how other people use Jenkins. I came across Elasticsearch's Jenkins site and I was pleasantly surprised. Elasticsearch is a json document storage application. There is a Jenkins plug-in that directly inputs data to Elasticsearch.  I implemented this proof of concept to perform Jenkins analytics with Elasticsearch as the document store and Kibana as the analytics engine. I automated the installation part using Docker. There are better ways to automate this. The steps given below do not require any...