12 pass

Guri Bee

2 min read

·

19-10-2024

1

0

Share

Understanding "12 Pass" in Software Development: A Comprehensive Guide

"12 Pass" is a term that often appears in the context of software development, particularly in relation to building and deploying applications. It's a concept that can be quite confusing for beginners, but understanding it is crucial for anyone working in the field.

Let's break down what "12 Pass" means and explore its implications:

What is "12 Pass"?

"12 Pass" refers to a specific sequence of steps that are executed during the build and deployment process of an application. It's not a universal standard, but rather a common practice used by many software development teams.

The 12 Passes:

The exact steps involved in a "12 Pass" can vary, but they typically encompass the following:

1. Pre-build: Prepares the development environment for the build process.
2. Clean: Removes any existing build artifacts.
3. Compile: Compiles the source code into machine-readable instructions.
4. Link: Links the compiled code with libraries and other dependencies.
5. Package: Creates an executable or deployable package.
6. Deploy: Deploys the packaged application to the target environment (e.g., a server).
7. Post-build: Executes any post-build tasks (e.g., running tests).
8. Run: Starts the deployed application.
9. Test: Executes tests to validate the functionality of the application.
10. Package (Deployment): Creates a package specifically for deployment.
11. Deploy (Deployment): Deploys the final package to the target environment.
12. Post-Deploy: Executes any post-deployment tasks (e.g., configuration updates).

Why 12 Pass?

The "12 Pass" approach brings structure and consistency to the build and deployment process, ensuring:

• Repeatability: Each step is defined, minimizing human errors and ensuring consistent results.
• Efficiency: Automating the process reduces manual effort and allows for faster deployment cycles.
• Quality: Automated testing and thorough build processes improve code quality and reduce bugs.
• Scalability: The process can be easily scaled to accommodate larger and more complex applications.

Example: "12 Pass" in a Continuous Integration/Continuous Delivery (CI/CD) Pipeline:

A "12 Pass" approach is often integrated into CI/CD pipelines. This allows for automated execution of the build, test, and deployment steps. For example, a CI/CD pipeline might use tools like Jenkins or GitLab CI/CD to automate the following steps:

1. Code Commit: A developer commits changes to the code repository.
2. Build: The CI/CD pipeline triggers a build process (passes 1-5).
3. Test: Automated tests are executed (pass 9).
4. Deploy: The application is deployed to a staging environment (passes 10-11).
5. Manual Approval: A developer manually approves the deployment to production.
6. Deploy (Production): The application is deployed to the production environment (pass 12).

Beyond 12 Pass:

While "12 Pass" is a widely used approach, it is not a strict rule. The exact number of steps can vary depending on the project's specific requirements and the tools used.

Key Takeaways:

• "12 Pass" refers to a sequence of steps executed during the build and deployment process.
• It brings structure, efficiency, and quality to software development.
• It is often integrated into CI/CD pipelines for automation.
• The exact steps can vary depending on the project and tools used.

Further Resources:

• Wikipedia: Continuous integration
• Atlassian: Continuous delivery
• GitHub Actions: Workflow syntax

Note: While "12 Pass" is a helpful concept, it's essential to tailor the specific build and deployment steps to the unique needs of each project.