►
Description
In this video, Veer Muchandi demonstrates editing an existing pipeline for use across multiple projects in OpenShift 3.3.
This is a follow-up to Part 1 (https://youtu.be/07-Xx73y3zA) which walks through the creation of a build pipeline for an application on OpenShift 3.3.
A
A
Hello
welcome
to
the
second
video
on
using
pipelines
with
openshift
version
3.3.
In
the
last
video
we
have
seen
how
to
create
a
simple
pipeline
within
the
scope
of
a
single
project
and
create
an
application
and
deploy
it
in
OpenShift,
3
or
3
in
this
video,
we'll
edit
that
pipeline
a
little
bit
to
go
across
the
projects.
So
we'll
have
a
development
project
where
we
will
do
a
build
and
deployment,
and
we
will
have
a
testing
project.
We
will,
where
we'll
just
pull
the
image
that
was
built
in
the
development
project
and
deployed
there.
A
So
in
order
to
do
that,
the
stretching
project
would
need
image
full
access
from
the
development
projects,
image
stream.
Now.
Last
time
we
had
a
CI
CD
project
where
the
Jenkins
pipeline
was
running.
That
pipeline
will
continue
to
run
at
the
same
place,
so
we'll
have
Jenkins
running
there,
and
the
Jenkins
would
require
edit
access
to
both
the
development
project
and
the
testing
project
to
be
able
to
do
a
build
and
deploy
in
the
development
and
the
deployment
in
the
testing
product.
So
now,
I
am
in
the
CI
CD
project.
A
A
I
will
add
another
stage
called
stay,
deploy
in
testing
I
change,
the
name
of
the
build
conflict
of
my
app
just
to
show
that
we
can
use
any
name
you
want,
and
while
we
are
working
the
development
project,
we
want
the
Jenkins
running
in
the
scope
of
the
CI
CD
project
to
initiate
a
build
in
the
development
namespaces.
So
we
are
going
to
load
double.
A
And
Fred
applaud
a
QA
I'm,
adding
a
couple
of
steps
here.
First,
we've
tagged
the
email
stream
in
the
development
namespace
the
source
image
stream
is
my
app
we'll
pick
up
the
latest
one
and
we'll
tag
it
as
my
AB
column,
promote
to
QA.
Once
the
tagging
is
complete,
we
will
deploy
in
the
testing
namespace
a
deployment
configuration
with
my
app
and
we'll
create
this
deployment
configuration
using
the
promoter
cue
attack
once
the
deployment
is
complete,
we'll
scale
up
this
application
to
three
instances.
So
those
are
the
few
changes
we
made
to
this
pipeline.
A
So
we
have
three
stages
in
the
pipeline:
building
development,
deploying
development
and
then
take
the
same
image
and
deploy
in
testing.
Now,
let's
create
the
development
and
testing
pilots.
I
am
creating
a
project
with
the
name
development
now
I
am
calling
providing
access
to
a
service
account
with
named
Jenkins
in
the
scope
of
that
is
in
the
scope
of
CI
CD
Projekt.
This
service
account
is
used
to
run
Jenkins
application
in
the
CI
CD
project.
A
So
we
are
giving
this
Jenkins
service
account
and
edit
role
to
the
development
project,
which
means
Jenkins
service
account,
can
initiate
the
bills
and
deployments
in
the
development
project
in
the
same
way,
I'll
create
a
project
call
testing
and
provide
Jenkins
service
account
edit
role
to
the
testing
project
as
well.
We
also
need
to
provide
image,
fuller
access
to
the
testing
project
to
be
able
to
pull
from
the
development
project.
Now,
let's
go
back
and
check
on
the
console.
We
have
the
two
projects,
development
and
testing
the
new
ones
that
we
added
this
time.
A
So
the
development
project
is
just
created
and
it
is
empty.
So,
in
order
for
the
pipeline
to
work,
the
pipeline
is
expecting
a
build
configuration
and
the
deployment
configuration
here
just
like
in
first
video,
so
I
am
going
to
do
the
same
exact
thing
as
what
we
did.
The
first
video
add
the
build
configuration
deployment
configuration
for
that
my
app.
A
I
have
the
service
here:
I
have
the
route
I
have
built
configuration
I,
have
image
stream
I?
Have
the
deployment
configuration
now?
Let's
move
on
to
the
testing
product,
the
testing
project
is
also
empty.
The
pipeline
is
expecting
a
deployment
configuration
with
the
name,
my
app
in
the
testing
project
as
well,
and
this
my
app
should
pull
the
image
that
is
tagged
as
promote
to
QA
from
the
development
project.
So
in
order
to
create
the
deployment
configuration,
let's
use
command
line.
A
First
I'll
switch
through
the
testing
project
now
we'll
type
in
a
command
that
creates
a
deployment
configuration
with
the
name.
My
app.
This
is
what
the
pipeline
is
expecting,
and
this
uses
the
image
my
app
with
the
tap
remote
QA
from
the
development
projects,
image
stream.
So
this
is
the
image
stream
from
which
it
will
try
to
pull
and
deploy
the
application.
A
When
I
create
this,
it
will
immediately
try
to
start
deploying
it,
but
it
will
fail
because
there
is
no
my
app
there
with
a
promoter
queue
attack
now
I'll
create
a
service
and
create
a
route
by
exposing
the
service.
Let's
go
back
to
web
console.
Here
is
a
service,
my
app
and
the
route
for
that
service
is
trying
to
do
a
deployment.
I
am
going
to
cancel
this
build.
A
We'll
also
make
a
couple
of
small
changes
to
this
deployment.
Configuration
first
I
will
remove
this
trigger.
So
whenever
there
is
a
config
change,
it
will
not
automatically
figure
in
your
deployment
and
I
will
change
this
image
full
policy
to
always
so
that
it
doesn't
use
the
image
from
cache
when
Jenkins
invokes
this
deployment
configuration
tool
for
a
new
deployment.
Now,
let's
switch
over
to
the
CI
CD
project
and
start
a
pipeline
here.
I'll
start
this
pipeline
now.
A
Starting
a
new
build
the
building
deployment,
which
is
a
first
stage
just
got
started.
This
should
invoke
a
new
build
in
the
development
project.
So
let's
switch
over
to
the
development
project
and
see
look
at
the
bills.
There
is
a
new
build
that
got
started
here.
Are
the
logs
it's
trying
to
download
the
source
code,
so
this
bill
was
started
by
Jenkins
from
the
CI
CD
project
in
the
development
project.
A
A
The
deployment
of
testing
is
also
complete.
So
let's
go
and
look
at
the
testing
project.
Here
are
our
three
parts.
So,
let's
test
it
again
in
the
testing
product,
so
this
testing
URL
is
also
pointing
to
the
green
part.
Now,
let's
go
back
to
our
pipeline
and
actually,
let's
see
in
the
core
I'm
painting,
this
tribute
rose
now
commit
the
changes
and
will
initiate
the
pipeline
again.
The
build
in
development
has
started
again.
A
A
The
second
build
is
also
complete
all
the
three
stages,
so
it
was
a
simple
example
of
how
you
can
edit
your
pipelines
to
go
across
different
projects,
I'll
post
the
build
configuration
file
and
the
jenkins
file
that
I
used
both
in
the
previous
video
in
this
video
on
github,
and
I
put
it
along
with
the
blog
post
that
accompanies
this
video.
I
hope
you
have
enjoyed
this
video
thanks
a
lot
for
watching.