What is trunk-based development?

Trunk-based development is a software development approach where all developers work on a single branch (often called the “trunk” or “mainline”) of a version control system, such as Git. In trunk-based development, developers commit their changes directly to this mainline branch without creating long-lived feature branches.

Key characteristics of trunk-based development include:

  1. Single Branch: There is only one mainline branch, which serves as the primary development branch. All changes, including bug fixes and new features, are committed directly to this branch.
  2. Frequent Commits: Developers commit their changes to the mainline branch frequently, often multiple times a day. This ensures that changes are integrated and tested continuously.
  3. Continuous Integration (CI): Continuous Integration practices are typically used to automatically build, test, and validate changes as they are committed to the mainline branch. This helps identify issues early and ensures the mainline branch remains stable.
  4. Feature Flags: Feature flags or toggles are often used to hide incomplete or experimental features from end-users until they are ready for release. This allows developers to merge changes to the mainline branch without affecting the user experience.
  5. Rolling Deployments: Changes are continuously deployed to production or staging environments as they are merged into the mainline branch. This enables rapid feedback and allows teams to respond quickly to issues.

Trunk-based development promotes collaboration, reduces integration overhead, and fosters a culture of continuous delivery. However, it requires strong discipline, automated testing, and effective use of feature flags to ensure that changes are always deployable and that the mainline branch remains stable.

30-Day Free Trial

Get Started

What are the benefits of trunk-based development?

How does trunk-based development differ from feature branching?

How do teams manage long-running features or experiments in trunk-based development?

What challenges might teams face when adopting trunk-based development?

How does trunk-based development support continuous delivery and continuous deployment?

A

B

Birthright Access

Bastion Host

C

California Consumer Privacy Act

Cloud Access Policies

Connect Azure AD with Mongo Atlas

Cloud Security Posture Management (CSPM)

Cloud Workload Protection (CWP)

Cloud Security

Cloud PAM

Credential Stuffing

Continuous Adaptive Risk Trust Assessment (CARTA)

Credentials Rotation

Cloud Infrastructure Entitlement Management (CIEM)

Cloud Access Management

Cloud Privileged Access Management

Credential Theft

Context-Based Access Management

Cloud Access Management

Cloud Governance

D

DevOps vs DevSecOps

Data Access Management

DevSecOps

F

Federated Access

Fedramp Compliance

G

Gramm-Leach-Bliley Act (GLBA)

Group Based Access Control (GBAC)

H

Honeypot

HIPAA compliance

I

IGA (Identity Governance Administration)

Identity Governance

Identity Provider (IDP)

Identity-as-a-Service (IDaaS)

Identity Governance Administration

IT Security Policy

Incident Response

Insider Threats

Identity Sprawl

Identity Threat Detection and Response (ITDR)

L

Log Analysis Management

Least Privilege Principle

Lightweight Directory Access Protocol (LDAP)

M

Man-in-the-Middle Attack

Multi-cloud Security

O

Open Authorization (OAuth)

On-call Access Management

P

Permissions Management

Phishing

PAM vs IAM

Privileged Access Management as a Service (PAMaaS)

Password Vaulting

Privileged Identity Management (PIM)

Privilege Creep

Password Spraying

PCI Compliance

R

Relationship-Based Access Control (ReBAC)

S

Standing Privileges

Shadow Access

System for Cross-domain Identity Management (SCIM)

Security Assertion Markup Language (SAML)

Security Information and Event Management (SIEM)