When it comes to flexibility and ease-of-use in a CI/CD platform, I'm a huge fan of Wercker Steps.
I won't lie, I love Wercker. While continuous delivery is a popular topic these days, you'd be hard-pressed to find a higher quality platform that seems to be built specifically with individual users in mind.
Changelogs are awesome.
Since our acquisition announcement in April the Wercker team has worked non-stop with our colleagues at Oracle to build our shared vision.
By design, DevOps is supposed to minimize the risk of errors and mitigate their impact when they occur. But mistakes are still inevitable.
In this post, we'll try to give you a clear picture of Wercker pipelines—what they are, how they operate in Wercker, and how you can make the best use of them.
Companies that think that DevOps is a technology-only endeavour are set up for failure. At best, they will create some short-lived automation, and will not support a delivery chain of an ever-changing application—which is just Waterfall 2.0.
When implementing a container environment, one of the worst things you can do is to complete the implementation and call it done. After all, few things in the world of IT can truly be managed with a “set-it-and-forget-it” mindset. There is always room for further improvement and optimization.
Microservices are all the rage these days. But are they really a new idea?
If you were around and kicking in the 2000s, you may also remember when Service-Oriented Architecture, or SOA, was the cool way to design apps. In some respects, SOA is very similar to microservices.
In today’s highly dynamic IT environments, DevOps transformations are all the rage. Yet DevOps transformations do not always go according to plan. Any number of things can completely derail a DevOps transformation. When issues occur, it’s important to take decisive action to get things back on track.
Build, test and deploy like never before with the power of Wercker
Oracle Open World
Third party Integration