Source Code & Software Build Management

Last published posts

Mobile Application Testing: 10 Steps Approach
Posted on

Mobile application testing is crucial in order to create a reliable product. In this post, we’ll go over the entire testing process step-by-step. Testing is a crucial part of the mobile application lifecycle. However, due to all the time and effort, it takes to complete the full cycle of app testing, it gets overlooked by…
Read more…

Real Agile Approach to Performance Testing
Posted on

Performance testing helps to determine if a system is reliable and comfortable to use. In this post, we’ll explain the main principles of Agile performance testing as well as its benefits. Before launching an app or a website, it’s crucial for a developer and admin to know how the entire system behaves under stressful situations….
Read more…

THE MAIN ESSENCE OF DEVOPS
Posted on

In the development and delivery of software, the most important contribution of DevOps is the elimination of the time lag between project phases: development, testing, trial operation, and delivery of the product to the final consumer. The time2market indicator is one of the key indicators of the competitiveness of products and the success of companies…
Read more…

SOURCE CODE & SOFTWARE BUILD MANAGEMENT

Implementation of the automated source code and software build management system allows the setup and management of the processes of storing the initial codes, software builds, and installation packages, as well as the conducting of the technical control of the initial codes’ quality.

Problems it will solve

  • Minimizing the risks of functional bugs in the software;
  • Cutting the time frame for defect discovery and elimination; and
  • Lowering the costs and work load for the implementation of new updates or system releases by cutting the number of defects during the integration of the system into a unified programming complex.

Deliverables

  • A deployed and tuned initial code and software build management system;
  • Regulations for requirements management that contain the roles and responsibilities of the participants and the manual of how to use the requirements management system; and
  • Distributives (executable files).

Scope of work

  1. Analysis
    • Determine the criteria for choosing the tools for the initial code and software build management system;
    • Determine the tools and required infrastructure;
    • Coordinate the choices above with the customer;
    • Set up infrastructure; and
    • Write and coordinate requirements to the initial code and software build supply package.
  2. Implementation phase
    • Install and tune the version control system (storage);
    • Install and tune the initial code and software build management system;
    • Install and tune the initial codes technical analysis system;
    • Integrate above systems with other contiguous systems;
    • Write the manuals and regulations; and
    • Educate customer’s employees to work with system.
  3. Pilot launch
    • Pilot launch using the system;
    • Analysis of pilot launch; and
    • Following setup and improvement of the tools and regulations.
  4. Distribution of the other software releases to the initial code and software build management system.

Tools and licences

  • Version control system
  1. SVN
  2. Git
  3. PVCS
  • Static code analysis system
  1. Sonarqube
  2. FindBugs
  3. PVS-Studio
  • Continious integration systems
  1. Jenkins
  2. TeamCity
  3. PVCS
  • Installer build systems
  1. Install Anywhere
  2. Nullsoft
  3. manual labor