►
Description
In this video, Veer Muchandi demonstrates how to configure automated OpenShift builds and deployments using a GitHub webhook.
NOTE: This demo is based on a beta version of OpenShift 3 - features and content are subject to change prior to release. For the latest information on OpenShift 3, please visit http://openshift.com or subscribe to the OpenShift Blog (https://blog.openshift.com).
A
In
the
last
video,
we
have
seen
an
example
of
how
you
can
take
your
source
code
as
and
deployed
it
on
to
OpenShift,
by
using
a
process
called
source
to
image
where
we
picked
up
a
builder
image,
which
is
a
PHP,
and
we
put
the
source
code
together.
Openshift
built
an
image
for
your
application,
based
on
your
source
code
and
the
build
and
the
build
image.
A
It
pushed
the
application
image
into
a
repository
that
is
running
on
this
open,
shipped
environment,
and
then
it
took
that
same
a
same
application,
image
docker
image,
and
it
deployed
that
as
a
part.
So
we
have
an
application
that
has
the
PHP
fronting
running
as
a
single
part,
and
this
is
that
part
right.
This
is
running
your
application,
the
front-end,
and
we
also
have
a
database
part
that
is
running
your
my
sequel,
8.
A
So
now,
let's
look
at
how
this
whole
thing
comes
together,
like
as
a
developer,
you
need
an
experience
where
you
can
make
code
changes
frequently
and
you
want
to
push
those
core
changes
into
openshift
and
let
OpenShift
deploy
those
core
changes
seamlessly
without
worrying
about
all
these
things
that
are
happening
behind
the
scenes
right.
So,
let's
see
how
the
entire
workflow
from
a
developer
standpoint
would
look
like
in
this
video.
A
First
thing:
we'll
go
to
bills
and
let's
look
at
what
is
here
so
the
source
control
repository
is
mapping
to
your
github
and
then
what
you
see
here
is
triggers,
and
here
you
will
find
a
github
webhook
URL,
let's
copy
that
now
take
this
web
hook.
You
are
all
go
to
your
source
control
repository
and
configure
it
there.
So
I'm
I'm
on
the
github
for
my
project
and
I'm
going
to
settings
here
and
in
settings.
A
I
see
the
webhooks
auction
and
I
want
to
add
a
book
now
I'll
place
my
URL
here
and
then
I
want
to
visible
as
a
cell
and
I
want
to
add
the
webhook.
Now
we
have
configured
our
github
repository
now
to
push
the
code
changes
in
if
any
or
commits
to
this
repository,
if
any
to
the
openshift
environment.
Now,
let's
just
that
I'm
going
back
and
let's
look
at
the
application,
it
looks
very
bland.
There
is
no
it's
just
displaying
the
users
from
the
database.
There
is
no
formatting
nothing.
A
So
let
me
make
some
small
change
to
this.
Db
test
or
PHP
I'll
go
to
the
place
where
it
is
displaying
this
data
and
I'll
edit.
It
make
some
small
changes
like
I
want
to
say
the
user
ID
I
want
to
display
this
before
each
user,
ID
and
username
for
each
user
name,
and
there
is
a
mistake
here:
I
want
to
fix
that
I
want
to
include
a
line
break
here.
So
let
me
commit
this
genius.
I'll
say
added
labels
and.
A
A
Github
has
pushed
those
changes
to
openshift
using
that
web
hook
URL
and
it
automatically
triggered
a
new
bill
here.
Yeah
now
this
bill
process
will
happen
just
like
before
so
I
can
the
bill
name
is
DB
test
too.
So
I
can
look
at
the
logs
here
and
see
what's
going
on
it
has
by
this
time
it
has
actually
built
the
image,
and
it
has
successfully
pushed
that
newly
built
image
into
the
open
shifts
docker
registry,
once
the
build
is
complete.
The
for
is
updated
with
the
new
co
genius.
A
So
if
I
now
refresh
my
application,
my
kenya's
are
here
it's
as
simple
as
that.
So,
to
summarize,
what
we
just
did:
I
took
the
webhook,
URL
and
I
configured,
that
in
my
source,
control
repository
and
as
I'm,
making
the
core
changes
and
committing
those
core
changes
to
the
github,
which
is
my
source
control
repository
using
that
web
hook.
The
source
control
repository
Earth
is
pushing
the
changes
to
open
shift
and
open
shift
automatically
triggers
a
new
build
and
it
uses
the
same.
A
Php
build
build
image
to
complete
the
new
build
and
it
will
push
that
application
image
into
the
open
shifts,
docker
registry
and
once
it
is
pushed
it
will
trigger
a
deploy
process
again
and
once,
and
it
will
take
the
new
image
of
this
application
and
it
will
deploy
it
onto
onto
this
part.
And
the
new
changes
are
seen
here
thanks
a
lot
for
watching.