Date: Thu, 28 Mar 2024 18:52:22 +0100 (CET) Message-ID: <1281873744.1245.1711648342728@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1244_524781401.1711648342727" ------=_Part_1244_524781401.1711648342727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This section will introduce you to the Kiuwan Life Cycle module. = p>
Contents:
To see an explanation of the dashboard, please go to Deliveries Management
Kiuwan provides support for the Application Life Cycle, allowing you to run an analysis based on the application's Ba= selines and Deliveries.
Baseline
An application's Baseline is a specific versi= on of an application that is relevant enough to be considered as a referenc= e to track further changes to it.
This version might be a production or a development version of the appli= cation, depending on its life cycle stage:
Whatever the reason to consider a concrete version as the baseline, that= version will be considered as the reference to track (and compare) any new= distribution of the application.
Deliveries
A new distribution of the application contains changes to the baseline. =
The new distribution will contain a set of source files that modify the sou=
rce code of the application baseline.
In Kiuwan terminology, those changes to the application baseline are consid=
ered as a Delivery.
Depending on the content, the delivery can be Partial (only a subset of application files is delivered) or Com=
plete (the complete application source code is delivered).
Kiuwan's functionality on Baseline and Deliveri= es allows you to fully manage the complete application's life cycl= e:
Kiuwan Life Cycle is commonly used tightly-coupled with existing Continu= ous Integration, Deployment and Development systems.
Although variety can be infinite, there are two typical scenarios of usi= ng Kiuwan Local Analyzer together with existing systems.
These two scenarios are based on subjacent technology :
In the case of Three-Tier applications, with a continuous integration development process in place, where develop= ers are continuously working on code and generating builds, Kiuwan=E2=80=99= s flexibility is ideal.
First, developers can analyze their code during development, while codin= g in Eclipse (for example) giving them a chance to fix the flaws in their c= ode before uploading it to the CI tool (Jenkins, TFS or Bamboo for example,= in this case, we=E2=80=99ll assume that it=E2=80=99s Jenkins).
Once the code reaches Jenkins, after having been inspected already, anot= her analysis can be run, automatically deciding whether the code is accepte= d for the next step in the development process (moving it onto a deployment= stage for example).
This decision can be made automatically using Kiuwan=E2=80=99s a= udits, which are tests done to the source code, based on checkpoin= ts, to decide whether the code passes or fails (OK or KO) the audit, based = on the results of the analysis. The type of analysis run at this point depe= nds on the development process of each company and can be either a delivery= analysis or a baseline analysis. Usually, a delivery analysis is run when = the code is not ready yet to become a new baseline, and Kiuwan offers diffe= rent types of delivery analyses, each with different properties, to adapt t= o each company=E2=80=99s particularities.
Since Kiuwan Local Analyzer is fast at performing analyses (especially w= hen compared to other static analysis tools), it can be added as another st= ep in the CI process, without adding the hassle of having to wait long peri= ods of time for the results of the analysis to continue to the next step of= the CI process.
In the case of mainframe applications, where the deploy= ment method is usually different, Kiuwan offers the possibility to = analyze applications incrementally, meaning that not all of an app= lication=E2=80=99s source code has to be analyzed on each analysis so that = only the modified files have to be analyzed whenever changes are made.
This is achieved by performing partial delivery analyses when changes are made, and only occasionally performing complete delivery= or baseline analyses, reducing analysis times considerabl= y, and not needing access to all of the code when an analysis is to be made= , but only the modified files.
Delivery analyses can also be promoted to baseline leve= l, meaning that whenever we are sure that our delivery code is ready to bec= ome a baseline, we can simply indicate this to Kiuwan, and there is no need to re-analyze all of our code as a baseline analysis.
Therefore, the source code management tool being used does not need to p= rovide Kiuwan Local Analyzer all of the code every time, but only the code = to be analyzed.
Again, promotion between stages (pre-production, production=E2=80=A6) ca= n easily be automatically managed using Kiuwan=E2=80=99s audits, which will return an OK or KO status for each analysis.