[Music]
hi I'm David Johnson and I'm a
consultant for Red Hat specializing in
openshift container platform and CI CD
I'm velocity a senior middle work on
that and focusing on cloud native
application development containers have
definitely change the way how we run our
applications simply by providing
services as load balancing and scaling
out of the box as a developer at the
beginning I believed that this was just
an other infrastructure to run my code
but eventually it's much more than that
well it certainly changed CI CD as well
we still use the good old Jenkins
workflow tool but now we can spin it up
dynamically to save resources when it's
not in use also we still can do our
traditional pipeline as always where we
get the source code run the unit test
bake the binary into a container image
and then deploy it into our open shipped
environment but with the dynamic
provisioning of containers we can save
more time and resources than ever before
yes one one thing how I realized to
extend this basics pipeline is to add
integration testing we used to have
dedicated environments for integration
tests you know so your application being
deployed somewhere having all your
dependencies services after running
simply just maintaining such an
environment can be a hassle hassle
what kind of branches do you have you
know typically if you have an
application it requires the database
maybe a message broker if you do
asynchronous messaging distributed in
memory cache especially if you do micro
services then your application probably
requires a bunch of other dependencies
services just simply to do its job with
tools like OpenShift and arquillian cube
you can create the whole integration
test environment on demand what's great
about containers is we have images for
pretty much any application you could
possibly need you could go to
Hubb or you could go to clay to AIA or
if you need supported versions you go to
the Red Hat container catalog within 60
seconds you could push a button and have
an entire integration environment yes
your application is deployed by using
the same image that you will use in
production once you have your dependency
containers up and running now you can
run your test simply by calling your
REST API or dropping messages on a queue
you can also interact with the whole
test environment dynamically on the fly
during your integration test so you're
saying you could bring containers up and
down as needed to simulates a database
downtime or something along those lines
exactly and once you are done with your
test the whole environment disappears
the next time everything starts from
scratch okay what's the advantage of
that well you don't need to clean up
after your tests you don't need to worry
about patching your services as long as
you get the latest image from a trusted
and secured container image registry and
honestly it enforces you to do
automation to script everything from day
one so simply those manual temporary
hacks don't work here so it sounds like
you're gonna have a lot more free time
to focus on the important thing which is
the business requirements and that's
already complex enough if you want to
get started with bringing up an
integration environment with containers
then reach out to your Red Hat Account
Executive or go to Red Hat comm slash
services to get started