6. Devops is an idea.
Close the gap between software and the
systems that run it.
Create a culture of mutual ownership.
Involve more stakeholders in the process.
36. a277cf0 Ticket #1, adding an image content type.
4483681 Ticket #3, adding view for the news section.
a65c40e Ticket #1, creating the homepage slider.
1a1df95 Ticket #4, making name required on registration.
0dbe2e6 Ticket #1, updating the image style.
24b55b6 Ticket #4, adding middle initial field.
0dbe2e6 Ticket #5, adding login rule for redirect.
But it was all merged to get it to the dev
environment
37. a277cf0 Ticket #1, adding an image content type.
4483681 Ticket #3, adding view for the news section.
a65c40e Ticket #1, creating the homepage slider.
1a1df95 Ticket #4, making name required on registration.
0dbe2e6 Ticket #1, updating the image style.
24b55b6 Ticket #4, adding middle initial field.
0dbe2e6 Ticket #5, adding login rule for redirect.
The client wants to deploy only one feature
they need and are happy with
54. - The in-progress application has a mix of thingsâ¨
that are and are not yet vetted by clients
- Testing a feature branch is complex
- Devs waste time switching tasks.
- It is difďŹcult to share in-progress features.
- Useful test content gets lost before feedback comes in.
Without Probo.CI
55. With Probo.CI
- In-progress application has only work approved.â¨
by the client and is always ready for deployment.
- Every team member and client can see each feature.
- Reviewing is easy and can be done by non developers.
- Test content needed for review doesnât get wiped.
- Deployment steps have always been veriďŹed.
59. Runs fat containers
- A node.js process manager runs child
processes
- Multiplexes the log output
- Allows us to easily treat an environment as a
single unit
62. Github Handler
- Responsible for receiving GitHub Webhook calls
- Responsible for sending status and deployment
updates back to Github
- Retrieves .probo.yaml conďŹguration
63. Container manager
- Drives docker
- Starts and stops containers
- Runs build steps
- Sends messages to loom
- Reports on containers running on the system
64. Loom
- Receives any kind of arbitrary stream and stores
it with metadata
- Supports tailing these streams
- Supports stream multiplexing
65. Web Proxy
- Fetches the container address and port
- Proxies the web request to the proper container
- Supports Drupalâs domain access
- Supports Drupal multi-site setups
66. Asset Receiver
- Receives uploads and puts ďŹles in a bucket
- Supports access tokens
- Stores, compresses, and encrypts ďŹles
- Allows them to be downloaded
69. Coordinator
- Proprietary part of SaaS service
- Only responsible for enforcing resource restrictions
- Enables massive deployments with multiple Container
Managers