The Probo team is excited to announce that the Probo Shell is live!
Previously, users could only run and change the code in the probo.yaml files and view the results from the outside.
Now with the Probo Shell, users can connect directly to their build container with SSH, as well as view logs quickly all within the Probo.CI App. This means developers can view or change settings even after the build has completed.
DevOps has grown in popularity over the last few years as companies continue to realize the advantages of unifying development and operations teams. The DevOps methodology aims at improving workflow and productivity by combining the efforts of operations people and developers. When both groups work together to solve problems, they’re able to deliver software features and updates more frequently and reliably.
We successfully completed the Probo Docker Images Restructure with minimal customer issues. The issues that have surfaced have workarounds in place for now. We'll be addressing any of the bugs we've encountered since the launch of the image restructure in the coming weeks when we release our Probo Beta Images.
We wanted to write a followup to our original post with some important details about the Probo Image Restructure. Several customers have already provided valuable feedback about our original plans and others are asking questions about the overall transition process. We want to ensure the least amount of confusion, issues, and downtime for our customers during this transition. Hopefully this post clears up some of the questions or concerns any of you may have.
As Zivtech’s Marketing Manager, I’m by far not the most technical member of our staff. Since the developers see our website from a different perspective than I do, it’s sometimes challenging to communicate the changes that the marketing team would like to see. I can explain an idea, but I won’t necessarily know how it will look once it’s executed. This is where Probo comes in.