Site Tools


Hotfix release available: 2024-02-06a "Kaos". upgrade now! [55.1] (what's this?)
New release available: 2024-02-06 "Kaos". upgrade now! [55] (what's this?)
Hotfix release available: 2023-04-04a "Jack Jackrum". upgrade now! [54.1] (what's this?)
New release available: 2023-04-04 "Jack Jackrum". upgrade now! [54] (what's this?)
Hotfix release available: 2022-07-31b "Igor". upgrade now! [53.1] (what's this?)
Hotfix release available: 2022-07-31a "Igor". upgrade now! [53] (what's this?)
New release available: 2022-07-31 "Igor". upgrade now! [52.2] (what's this?)
New release candidate 2 available: rc2022-06-26 "Igor". upgrade now! [52.1] (what's this?)
New release candidate available: 2022-06-26 "Igor". upgrade now! [52] (what's this?)
Hotfix release available: 2020-07-29a "Hogfather". upgrade now! [51.4] (what's this?)
internal:dev_w:continuous_integration_process

Continuous Integration Process

Objective

  1. To enable continuous integration of development changes into product baseline.
  2. To ensure that development changes goes through standard development testing/coding criteria for integration.

Process Description:

  1. Developer Changes:
    • Developer completes unit testcase, code change and source level documentation changes.
    • Developer verifies if all unit testing passes and source code documentations are parsed appropriately as per coding standard in local development environment.
    • Peer review is performed on code changes
    • Developer commits the changes into version control repository with review status and appropriate checkin comments as per check-in process.
  2. CI Server Deployment:
    • CI Server automatically picks up the modifications and deploy at CI server.
    • Performs unit testings
    • Generates build as incrementally deployable package
    • Deploys the build at iDev Server instance
    • Displays build status (as passed/failed and build log details) at dashboard for team reference.
  3. CI Server Force(On Demand) Build:
    1. Open CI Website url: Cruisecontrol CI Server
    2. It will list all build jobs.
    3. start force build by clicking build button (green/orange color) against specific build Job listed according to your project.
      1. for eg, click on build-button of ExpertusONE for building ExpertusONE project.
      2. for eg, click on build-button of WellsFargo for building WellsFargo project.
    4. It will complete build and deploys at respective iDev env / publishes the resultset according to the nature of the CI job.
    5. Click the hyperlink of respective CI-Job-Titles listed for getting the details of build and result set.

CI Server Environment Tools:

  • CI Server URL: Cruisecontrol CI Server
  • List of tools installed at CI Server.
    1. CruiseControl CI Server Application
    2. phpUnderControl CI Server Applicaiton
    3. phpunit tool
    4. phpdoc tool
    5. Jasmine test suite API tools
    6. Database(stored procedures) test suite – outstanding item that we need to figure out

CI Build Jobs (presently supported):

  • ExpertusONE - for ExpertusONE iDev build (using CVS repository, will be decommissioned after migration to SVN)
  • ExpertusONE_SVN - for ExpertusONE iDev build using SVN repository
  • ExpertusONE_Documentation - for ExpertusONE Source Code Documentation project
  • ExpertusONE_CodeSniffer - for ExpertusONE Code Sniffer project
  • WellsFargo - For WellsFargo iDev build
  • Autodesk - For Autodesk iDev build

:-P For Any Queries, Contact Release Management Group

Prabhu 2011/02/23 10:04

internal/dev_w/continuous_integration_process.txt · Last modified: 2024/06/03 00:53 by 47.128.29.5