Thursday, February 13, 2014

DevOps - Automation and Continuous Testing is the Key

While leading the organization to adapt to continuous delivery and DevOps faced various challenges  where problem of many or 'automated' ---But'... or lengthy and sequential execution cycles with various reasons, not counting build size itself or network and geographical constraints. Test artifacts need to be copied across systems, components for different teams using varied test assets and if have to execute testes on frequently say hourly builds to identify failure immediately, quite challenging task. This holds the key to success though for both continuous integration and continuous delivery. Developer should get feedback on whether their code is "ok", using a quick personal build and test run immediately so developer can resolve it than working on something else (new function/logic), each line written impacts the system. On success, can run a complete set of tests to integrate the tested changes or integrate the changes and run the full set of tests based on time required. In any case quick turnaround is required and not possible to achieve it manually.

Now every one does automation, what is so special? Key is complete automation, with no 'But' or almost, system performing every task on its own and is various tools including of IBM hold the key here, providing seamless automation capabilities. It is for us to deliver the integrated Testing mechanism which not only perform tasks automatically but also reduce time required for testing even with increase in number of tests required to be executed.
 

 We tend to run everything but should be executed in the manner, run sanity test before full suite for individual components to ensure Build, Infrastructure, Configuration and other assets are working fine to minimal level of acceptance. Prioritize frequently failed test to be executed post Sanity to confirm current build is good for formal testing. It can lead to 'always working' test bucket with very little chance of failure, covering majority of bucket. With this we will have only a subset of test remain which either do not provide any major benefit or real time consuming and not required to run on every instance, reduce their execution frequency. DevOps also improve the process where we can  build and test the components separately and then perform integration testing enabling frequent testing of individual feature or component.


Concurrency or parallelism is another step where we can automate our Deployment of builds following DevOps model and automated provisioning/configuration enabling us to run tests across systems in parallel, providing results much faster. Following automated provisioning enable to use Template based approach, taking away need for install time and can snapshot areas where no new pieces need to be installed like databases / source systems.

 Stub(s) holds the key rather than for every small change we connect to external systems. This saves lots of time and tools like IBM Green Hat are great simulation tools. Consolidate Infrastructure using Cloud Based Deployment (Softlayer) to use local virtual systems where other test assets resided to remove network contentions and improve productivity.

 Will cover more of testing aspects and other DevOps related content including uDeploy, Chef, Softlayer in coming series.


-Ritesh 
Disclaimer: The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions

Tuesday, February 11, 2014

DevOps - Key to Continuous Delivery

While exploring Jenkins and continuous intergration pipeline thought of sharing on continuous development. Gone are the days of waterfall model where companies spend years to build products and clients further spend time in consuming them before moving to production. In the era of continuous change and need for something new every day, companies are moving towards quick release cycles. It started with mobile applications where new features gets delivered on regular basis on top of existing framework and can be seamlessly upgraded as well. With frequent release cycle requirements, an established mechanism need to be in place to avoid stress on resources and quality standards. It leads to a concept guided by open communication and  collaboration between software engineering and IT operation Experts.

DevOps is a model which enable enterprise to continuously deliver software to the market and seize  market opportunities by responding immediately to customer feedback or requirement with all quality checks in place. Following agile principles within software delivery life-cycle, DevOps enable organizations to achieve quicker time to value and provide scope for more innovation leading to easier maintenance cycles. Goal of DevOps model is move towards automation without need to enter anything manually and automation can be triggered by non-operation resources may be by system itself . It enable developers having more control on environment and can focus on research. DevOps leads to predictability, efficiency and maintainability of operational processes due to automation.

In the market different tools available to complete DevOps model including full set of DevOps offering from IBM which helps to achieve the process optimization and continuous development. IBM also offer DevOps as Service from Development to Deployment where developers can collaborate with others to develop, track, plan and deploy software. It is completely Cloud based and community based development via IBM BlueMix where can create applications with efficiency and deploy across domains. From planning to development and testing to release and deployment, all at 1 place following series of automation pieces to achieve machine based product delivery.

Will share more on steps and how to create Apps on BlueMix and following DevOps model along with Jenkins Series in upcoming blogs.


-Ritesh
Disclaimer: The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions

Thursday, January 23, 2014

Jenkins Series 2 - How to Create my First Job in Jenkins

Before share how to use Jenkins to build complex pipelines and create trends or build, sharing how to create your 1st Job in it.Click on the New Job. It will open a New Window with different Options.

Create a New Job




In the New Window you will see screen like below add the name of Job you want to create.
Provide the Name of the Job
Once Name is given, as a next step choose Add a Build Step. This is the place where you define what steps your Jenkins Job should perform. You can pick Windows or Unix Shell based on where you want to execute your command or scripts. In my example I have taken Windows. There are various other options available which you can play around once comfortable with Jenkins and you really need them.

Choose the Shell Want for Build Step

Once Shell is available add command or your batch file, shell script or any other steps want to perform. I have given only ls -l command and saved it. This is the place which really gets executed within the Slave (we discuss in other blog) a kind of compute node where process intended to be executed. In this case as you do not have anything registered other than master, it will run on the same machine where Jenkins is deployed and will provide you listing of workspace directory. It is a folder where Jenkins by default perform activities. You can use custom workspace as well (we discuss in other blog).




Once you click on Save will leads to following Screen and provide you Build Now Options
Click on Build Now to execute above step
On sucessfull execution you will see the results.
 Can click on the Console Output to see details of the Logs. Since we haven;t selected specific framework or selected reporting you will see console log by default for the steps executed above as it opens a Shell or Command Prompt and execute the steps.

Console Output

Hope now you have created your 1st Job on the Jenkins and ready for an interesting journey. Will discuss in coming blogs on how can register slave from the command line, what infect slave is, how we can consolidate results and run different kind of frameworks. So Stay Tuned.

-Ritesh
Disclaimer: The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions

Wednesday, January 22, 2014

Jenkins Series 1 - Create Trends for Existing Results - Using JUnit Publisher

After taking a long break on Non Information Server blogging thought of sharing my recent exposure to Dev Ops Model. 
Today I will share my experience how we can use Jenkins as a Dashboard to show trends of nightly build tests. You do not require to use Jenkins for executing these tests. Can simply use XML report files generated from your nightly build verification system  and produce these trends live instead of relying on Spread Sheets and their tabs.

Here are few steps need to use Jenkins to produce Trends on Dashboard when have test cases executed are based on JUnit framework or results produced are XML Reports adhering to JUnit Framework.

Step 1: Copy Report produced by your Build Verification Tests or Unit Tests into the Slave or machine where you want to run the process. You can even use Shared Folder for the same

Step 2: For Windows use Execute Windows Shell and for Unix use Shell

Step 3: With-in Windows or Unix see Image Below to copy the report file into workspace. Can use Custom workspace if do not want to copy these files. Can also use to write some script which can executed based on your build number can be supplied as Parameter. Below step can be used to copy any other files as well not required for reporting.
Copy XML Report Files to Workspace
Step 4: Use Publish JUnit Test Report to show these results on Jenkins dashboard for selected build. Jenkins plugin will parse the files and produce results on the dashboard.
Publish JUnit Test Result Reports to Jenkins Dashboard
Step 5: Save the Jenkins job

Step 6: Execute the Build with Build Now
Jenkins will process these XML files and produce a Trend Graph. Since it is only for 1 Build should get failure and success details. Repeat the process for different builds and can see trends like this below.
Chart showing Trends for different build on Dashboard


Now above trend you see shows red graph going upwards means have failure across builds reducing the confidence in the build. You can write the job once and can be triggered at different intervals or by external trigger. Can navigate the graph and see failures component wide. Will cover these details in Next Blogs on how to identify failures and see if any regressions or new failures and Fixed from previous build.


-Ritesh 
Disclaimer: The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions