Teams. Jenkins has plug-ins for all major team
management tools and allows for easy
integration. If the build fails, the developer can
use links to the information on what failed and
why, make changes to the code, and restart the
process.
Step 8. If the build process is successful and all of the
tests pass, Jenkins can deploy the new code to
an artifact repository (just a fancy name for the
place finished software is stored). The software
is not able to be deployed in production.
Step 9. Jenkins signals the infrastructure that an
updated version of software is ready. For
example, there may be a new container ready to
be deployed into a Kubernetes platform. The
updated container replaces the existing
containers with the new code fully tested and
ready to go. Now the application is updated
with minimal (or no) disruption.
The nuts and bolts of building a DevOps pipeline are
beyond of the scope of the 200-901 DevNet Associate
DEVASC exam. There are simply more tools than grains
of sand at the beach, and luckily you are not going to be
tested on all of them. For technologists, it’s easy to focus
on the tools and technology, but honestly that’s the easy
part of DevOps. Changing culture and implementing
Lean methodologies are where many companies have
struggled. Focus on streamlining your processes and
implement technologies that help accelerate your efforts.
DOCKER
Some of the best innovations come from reusing older
technologies and bringing them forward in a new way.
That’s exactly what Solomon Hykes and Sebastien Pahl
did back in 2010 when they started a small platform as a
service (PaaS) company called dotCloud. They were
looking for a way to make it easier to create applications