- Documentation
- OpenShift Enterprise
- Architecture
- Additional Concepts
- Source Control Management history
- OpenShift Documentation
- What's New?
- Getting Started
- Architecture
- Installation and Configuration
- Administration
- Overview
- Master and Node Configuration
- Managing Nodes
- Routing from Edge Load Balancers
- Aggregating Container Logs
- Configuring Authentication
- Configuring Service Accounts
- Managing Authorization Policies
- Managing Security Context Constraints
- Scheduler
- Pruning Objects
- Monitoring Routers
- High Availability
- Self-Provisioned Projects
- Persistent Storage Using NFS
- IPtables
- Native Container Routing
- Securing Builds by Strategy
- Building Dependency Trees
- Customizing the Web Console
- Working with HTTP Proxies
- Revision History
- CLI Reference
- Developer Guide
- Overview
- Authentication
- Projects
- Service Accounts
- Creating New Applications
- Templates
- Builds
- Deployments
- Routes
- Integrating External Services
- Secrets
- Image Pull Secrets
- Resource Limits
- Quota
- Managing Volumes
- Using Persistent Volumes
- Executing Remote Commands
- Port Forwarding
- Shared Memory
- Application Health
- Events
- Downward API
- Managing Environment Variables
- Revision History
- Creating Images
- Using Images
- REST API Reference
×
Source Control Management
OpenShift takes advantage of preexisting source control management (SCM) systems hosted either internally (such as an in-house Git server) or externally (for example, on GitHub, Bitbucket, etc.). Currently, OpenShift only supports Git solutions.
SCM integration is tightly coupled with builds, the two points being:
-
Creating a
buildconfigusing a repository, which allows building your application inside of OpenShift. You can create abuildconfigmanually or let OpenShift create it automatically by inspecting your repository. -
Triggering a build upon repository changes.