Scribd
Upload
7 views5 pages

Jenkins Flow Architecture

Uploaded by

chalasanikamesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
7 views5 pages

Jenkins Flow Architecture

Uploaded by

chalasanikamesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Continuous Integration (CI) Process using Jenkins as To: Devops

the automation server

1
Continuous Integration Process

Developer

Pull Request

SCA SAS_Jobs Stage Artifacts


Validate Commit Builds

Unit Test Cases

Hardware Automation

04/28/2025 2
Continuous Integration (CI) Process using Jenkins as the automation server

1. A developer initiates the process by creating a pull request (PR) and submitting code changes.
2. Before merging, Static Code Analysis (SCA) is performed to check for code quality, security vulnerabilities, and adherence to best practices.
- If the code passes SCA, it is pushed to GitHub for version control.
3. Jenkins, an automation server, detects the commit and triggers the CI pipeline.
- The process moves to the commit validation stage to ensure that the submitted code follows predefined rules and standards.
4. After validation, the build process starts, compiling the source code.
- The CMake tool is used to configure the build system.
5. Once the code is built, unit tests are executed using Google Test (GTest) to verify functionality and correctness.
- Any failures at this stage require developers to fix the issues and restart the process.
6. The pipeline then moves to SAS Jobs
- The output is then moved to the Staging Environment for further verification before deployment.
7. If the build and tests pass successfully, the artifacts (compiled binaries, reports, or packaged software) are stored.
- These artifacts are then uploaded to a Samba server, ensuring accessibility and storage.
8. The stored artifacts are further used for hardware automation, ensuring they function correctly in real-world environments.
- The final step involves publishing the artifacts for release or deployment.

04/28/2025 3
Develop pipeline runtime on success

Projects Jenkins runtime(min-max)


IPC 20-25 mins
RCC 25-30 mins
FCC 25-30 mins
RTOS 25-30 mins

UPDATER 5-10 mins

04/28/2025 4
Thank you

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy