\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Changing Scenario of Testing Paradigms Using DevOps -A Comparative Study with Classical Models},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2015-01-15 (revised: 15 January 2015)}
\def\TheID{\makeatother }
\def\TheDate{2015-01-15}
\title{Changing Scenario of Testing Paradigms Using DevOps -A Comparative Study with Classical Models}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Surendra Naidu  Mullaguru}

             \author[2]{Surendra Naidu  Mullaguru}

\renewcommand\Authands{ and }

\date{\small \em Received: 14 December 2014 Accepted: 4 January 2015 Published: 15 January 2015}

\maketitle


\begin{abstract}
        


Many organizations come across themselves in a challenging conditions with the increase of web applications which depend on cloud. As cloud applications are supportive for rapid releases with respect to the queries requested by the user community. Most of the software organizations expects to release the product in time as required by the end user hence, it pressurize functional teams of the organization to do the needful. As perfection is rare to achieve , it is obvious to commit more and more defects and consequent annoyance to the team. This paper discusses about a new paradigm i.e DevOps which tries to address the identified problem by integrating Development and Operations teams. In this model, the development team would take care of operational requirements like deploying scripts, debugging and performance testing from the scratch and the operations team take care of well-informed support and feedback before, during, and after deployment.

\end{abstract}


\keywords{}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
ost of the software development teams are moving towards a new trend of testing domain i.e DevOps. Organizations are given pressures to produce higher-quality code faster giving less time for Quality Assurance (QA). As it is emerging as prominent domain, the developers need to adjust themselves to gain more benefits. We cannot release the product quickly with timelines as persisting in compact and separated work teams. The DevOps promises to achieve this. With DevOps, team's participating skills are equally important as technical skills. This paper focus on how DevOps paradigm can change the testing set-up of conventional testing by integrating the development process and the QA with the operations functioning together to speed up development during problem resolution. The paper also focuses on the areas of application, its suitability wherein the conventional system fail to deliver testing inferences \hyperref[b5]{[7]}. DevOps is a rising methodology from two popular methods of software development. i.e the agile system administration or agile operations and the later is the integration of development and operations teams in all the phases of the development lifecycle for creating and using a service. The definition of DevOps according to Jez Humble is "DevOps is a cross-disciplinary community of practice dedicated to the learn building, evolving and operating rapidly-changing resilient systems at scale". DevOps is an effort to enable operations engineers and development engineers together in total service lifecycle, from design through the development process to production phase and support. DevOps is also characterized by operations by team making use of many of the techniques as developers to carry out systems work in a routine pattern. Those techniques can range from using source control to testing to participate in an agile development process. In the industry the tag DevOps is referred as the relationship between development and operations. The reason for this is to get the advantage of both development team and operations team together for the growth of the business. The DevOps improves the organization potential for nonstop software release that can facilitate organizations to capture market opportunities. It also helps in evaluating customer feedback, cost, quality and risk. As DevOps analyzes the code systematically and assist in reducing the coding errors. According to the present market trend in the near future Devops is expected to emerge as a vital tool for rapid process develop. In the past development employees are considered as "makers" and the "Ops" employees are considered as "people who deal with the creation after its birth. In this way, DevOps can be implemented as a outcome of Agile Computing. Agile software development stipulates close association of customers, product management, developers, and QA to fill in the space and rapidly iterate towards an improved product. But the aim of DevOps is not only increasing the rate of change but also to deploy the features successfully into production without causing disorder and trouble to other services, while rapidly detecting and correcting incidents when they occur. DevOps is a simple extension to agile principles beyond the boundaries of "the code" to the entire delivered service. DevOps is especially complementary to the agile software development process, as it extends and completes the continuous integration and release process by ensuring the code production and provide value to the customer \hyperref[b4]{[6]} \hyperref[b0]{[1]}.\par
The testing tool must ensure to provide some basic provision to carry out testing facilities which are being considered by DevOps as a vital aid . Following are the some basic capabilities extend by Devops \hyperref[b2]{[4]}.\par
? Testing early pieces of code often.  
\section[{Comparison of DevOps with Agile}]{Comparison of DevOps with Agile}\par
The origin for the development of DevOps is emerging technologies. The DevOps is derived from the Agile System Administration movement and Enterprise Systems Management (ESM) movement. The characteristic of agile process is that it shows us how to create adaptive software development for quick feedback cycles through early customer participation. The primary characteristic of DevOps is that it contemplates on business results rather than technical details. DevOps acquires lot of lean principles like deploying in smaller batches aiming at enhancing the communication between developers and operations teams[3] \hyperref[b1]{[2]}. 
\section[{a) Lean is the basis of Agile}]{a) Lean is the basis of Agile}\par
Lean signifies optimization from end-to-end process which produces value for your customer -from the original idea to generation of revenue. Lean philosophy focus on stream more than bottlenecks in the process and unproductive activities identification. Creating importance for your customers is all about judgment, validate product ideas, implementing these ideas and managing them to advantage the users. It is evident that many admirable schools of thought are there for structuring the processes such as Lean Startup and Running Lean to hash out product ideas. Scrum, and XP are used for creating features in an pliable manner. The DevOps enables the creation of a tradition of focusing on delivering worth for the customer instead of only concerning for technical issues \hyperref[b0]{[1]} \hyperref[b2]{[4]}. 
\section[{b) Lean Startup or Running Lean}]{b) Lean Startup or Running Lean}\par
Eric Ries and Ash Maurya reviewed about a learning cycle during feature discovery. From authenticating ideas to testing probable solutions, they teach to resolve problems worth solving and keep your solutions more directed.\par
? Scrum, XP and Kanban: Typical agile processes show how to arrange adaptive software development for speedy feedback cycles through timely customer participation. ? DevOps: It focus on cultural aspects of business results relatively than technical details. DevOps integrate lot of lean principles, focusing on improvement in collaboration between developers and operations folks.\par
Lean principles are the foundation of entire product development course. In order to incorporate path of improvement, one must consider the whole as sub-optimizing element and just one part will hurt the business. The developer circles are emphasizing on DevOps and the entrepreneur circles are focusing at Lean Startup. The term, coined by Eric Ries, is a startup that achieves validated learning through the buildmeasure-learn loop. With a notion of learning what the customer actually need so that a useful product and a profitable business model would emerge \hyperref[b1]{[2]} \hyperref[b6]{[8]}.\par
It may not appear that the Lean Startup and DevOps are related. Small batches of tasks are the way for cross-functional teams, which work together on the smallest units of work possible while pushing that work to the customer as soon as possible. This way, the product gets to the customer swiftly, allowing the business model or product to be validated.\par
The common model presently is large batches. Instead of a small team working across the modules to push a product towards the customer rapidly. The team specializes, with a range of team members completing their segment of the product before passing it on to the next phase in the chain. If at any point a fault is found, the product has be sent back down to the chain. This leads to speedy feedback and rapid turnaround times, resulting in an improved product. DevOps is about accepting small batches, but the batch in this case is a thin part of the overall process, pushing a product from development to deployment to see it in use. DevOps is about allowing production behavior to quickly fed back to developers so that development can adjust swiftly to the situations in production. With the lean startup, the potential competence of an individual unit such as operations might emerge to weaken. The efficiency of the system as a whole speeds up. When developing a system it is simple to foresee how a system should run, but that is not enough. Often inevitable differences in hardware and traffic escort to differences in how the system actually performs with how it was predicted. DevOps is about tightening the same loop as the Lean Startup. The only difference is the narrower focus of DevOps. With the loop as rigid as possible, knowledge gained from the real system is fed back into the next cycle of the product so the system becomes better in Year 2015 
\section[{Global Journal of C omp uter S cience and T echnology}]{Global Journal of C omp uter S cience and T echnology}\par
Volume XV Issue II Version I ( ) C small and tight increments. DevOps is a subset of the Learn Startup. Both are reactions to the today's fast changing world and require to produce a system that can optimize quickly, even if that means undercutting what appears to be the efficient in the entity unit. 
\section[{c) Jenkins -A DevOps tool}]{c) Jenkins -A DevOps tool}\par
Jenkins is a rapid Continuous Integration server. Continuous integration is a procedure in which all development work is integrated at as planned entity with a time constraint or event and the resulting work is routinely tested and built in automated environment as shown in figure \hyperref[fig_0]{1}. The idea is to development a scenario wherein errors are being identified at an early stage in the process. Jenkins is an open source tool to achieve continuous integration. The basic functionality of Jenkins is to perform a definite list of steps supported by a trigger. The trigger might be a change in version control system or a indication for time based trigger, e.g., a build every 15 minutes. To accomplish this the list of steps include:\par
? Perform a software build with Apache Maven or Gradle ? Run a shell script ? Archive the build results 
\section[{? Start the integration tests}]{? Start the integration tests}\par
Basically Continuous Integration is the mechanism of running tests on a non-developer machine routinely each time someone pushes a fresh code into the source repository. This has remarkable advantage of knowing that all the tests work and attain fast feedback. The fast feedback is vital to know right after breaking the build and based on that one would repair or revert it for improvement. The developer must be alert when running the tests occasionally, as the problem that has emerged due to change in code may have surfaced since the last time. As it is hard to figure out which change has induced such problem. Built on continuous Integration is the platform of continuous deployment/ delivery wherein, after a successful test run the system instantly would release the latest version of the codebase. This makes the deployment a non-issue and helps in pace up development. Jenkins is a one of the DevOps application tool which supervises regularly executed jobs, such as building a software project. Among those things, presently Jenkins focuses on building/testing software projects continuously and supervise executions of externally-run jobs, such as cron jobs and procmail jobs, even though that are run on a remote machine \hyperref[b3]{[5]}.\par
The following section demonstrates the steps of a sample Java application testing using Jenkins tool. The implementation steps are as follows. step1: Deploy Jenkins. war in web server step2: Create a new job. step3: Add build steps in job configuration. step4: From the job home page click on "Build Now" to start the build process. step5: Check the log for build status and then click1 on last run console output.\par
The following are the screenshots of a simple java application testing using jenkins tool. After deplyong the Jenkins. war in web server we create a new job. Then add build steps in job configuration. Once it is configured, we would get a resultant screen as figure  {\ref 2}.   Figure \hyperref[fig_3]{5} shows the successful execution of the application. In case if the java application is modified then automatically jenkins will trigger error report which is shown in the form of log report as depicted in the figure \hyperref[fig_4]{6}.  \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{23}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 2 :CFigure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{6}\includegraphics[]{image-6.png}
\caption{\label{fig_4}Figure 6 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.85\textwidth}}
II.\end{longtable} \par
 
\caption{\label{tab_0}?}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{I} \par 
\begin{longtable}{P{0.03148148148148148\textwidth}P{0.1948853615520282\textwidth}P{0.026984126984126982\textwidth}P{0.12742504409171074\textwidth}P{0.014991181657848324\textwidth}P{0.2518518518518518\textwidth}P{0.029982363315696647\textwidth}P{0.0029982363315696646\textwidth}P{0.1394179894179894\textwidth}P{0.013492063492063491\textwidth}P{0.016490299823633155\textwidth}}
Methodolgy\tabcellsep \multicolumn{2}{l}{Principles}\tabcellsep \multicolumn{2}{l}{Methods}\tabcellsep \multicolumn{2}{l}{Practices}\tabcellsep \tabcellsep \multicolumn{2}{l}{Tools}\\
Agile\tabcellsep Follows\tabcellsep strategic\tabcellsep XP, Scrum\tabcellsep \tabcellsep Standups,\tabcellsep \multicolumn{2}{l}{planning}\tabcellsep JIRA\tabcellsep Agile\tabcellsep aka\\
\tabcellsep approaches\tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{3}{l}{poker, backlogs, CI, all}\tabcellsep \multicolumn{2}{l}{Greenhopper}\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{3}{l}{the specific artifacts a}\tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep developer\tabcellsep uses\tabcellsep to\tabcellsep \\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \multicolumn{2}{l}{perform their work.}\tabcellsep \tabcellsep \\
DevOps\tabcellsep System\tabcellsep thinking,\tabcellsep \multicolumn{2}{l}{Same as agile but}\tabcellsep Automated\tabcellsep \multicolumn{2}{l}{Testing,}\tabcellsep \multicolumn{2}{l}{jenkins, travis, team city}\\
\tabcellsep \multicolumn{2}{l}{Amplifying feedback loops}\tabcellsep Scrum\tabcellsep with\tabcellsep \multicolumn{3}{l}{Integrated Configuration}\tabcellsep \multicolumn{2}{l}{puppet, chef, ansible,}\\
\tabcellsep \multicolumn{2}{l}{(Gene Kim), "Infrastructure}\tabcellsep \multicolumn{2}{l}{operations Kanban}\tabcellsep \multicolumn{3}{l}{Management, Integrated}\tabcellsep cfengine,\tabcellsep AWS,\\
\tabcellsep \multicolumn{2}{l}{as code "are commonly}\tabcellsep \multicolumn{2}{l}{with perations and}\tabcellsep \multicolumn{2}{l}{Deployment Planning}\tabcellsep \tabcellsep \multicolumn{2}{l}{OpenStack,}\tabcellsep vagrant,\\
\tabcellsep \multicolumn{2}{l}{cited DevOps principles.}\tabcellsep style\tabcellsep change\tabcellsep \tabcellsep \tabcellsep \tabcellsep docker\\
\tabcellsep \tabcellsep \tabcellsep control\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_1}Table I :}\end{figure}
 			\footnote{© 2015 Global Journals Inc. (US) 1} 			\footnote{© 2015 Global Journals Inc. (US)} 		 		\backmatter  			 \par
analyzers are utilized To face the today's cloud based environment DevOps is the right choice for better results and to speed up customer query processing. In this paper we addressed the issues related to agile method and how the DevOps resolved the problems of agile.			 			  				\begin{bibitemlist}{1}
\bibitem[Tsong Yueh Chen et al.]{b3}\label{b3} 	 		‘Automated software test data generation’.  		 			Fei-Ching Tsong Yueh Chen 		,  		 			Zhi Quan Kuo 		,  		 			Zhou 		.  	 	 		\textit{Proceedings of the Fifth International Conference on Quality Software (QSIC05) 2005 IEEE},  				 (the Fifth International Conference on Quality Software (QSIC05) 2005 IEEE)  		 	 
\bibitem[Zhao and Li ()]{b5}\label{b5} 	 		\textit{Automatic test generation for dynamic data structure},  		 			Rullian Zhao 		,  		 			Qing Li 		.  		2006.  		 			Beijing University of Chemical Technology 		 	 	 (Technical report) 
\bibitem[Qu et al. ()]{b4}\label{b4} 	 		\textit{Combinatorial Interaction Regression Testing: A study of Test Case Generation and Prioritization},  		 			Xiao Qu 		,  		 			Myra B Cohen 		,  		 			Katherine M Woolf 		.  		2007.  	 
\bibitem[DevOps Market -By Technology (Sonar Qube, Continuous Integration (CI), Lean startup, Agile software development ()]{b1}\label{b1} 	 	 	 		\textit{DevOps Market -By Technology (Sonar Qube, Continuous Integration (CI), Lean startup, Agile software development},  				 (Automation, Cloud Computing)  		2014 -2019.  	 	 (Advancements, Forecasts \& Analysis) 
\bibitem[Yuan and Memon ()]{b2}\label{b2} 	 		‘Iterative executionfeedback model-directed GUI testing’.  		 			X Yuan 		,  		 			A M Memon 		.  	 	 		\textit{Information \& Software Technology}  		2010. 52  (5)  p. .  	 
\bibitem[
			Harrold
		 ()]{b6}\label{b6} 	 		‘Testing: A Roadmap’.  		 			Harrold 		.  	 	 		\textit{ACM Trans. on Software Engineering}  		2000.  	 
\bibitem[Voce et al. (2015)]{b0}\label{b0} 	 		 			Christopher Voce 		,  		 			Michael Caputo 		,  		 			Megan Doerr 		.  	 	 		\textit{Top Technologies For The Infrastructure \& Operations BT Agenda},  				 (Laura Koetzle, Glenn O'Donnell)  		February 4, 2015.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
