►
From YouTube: Open Source Online DevOps Dojo - GitHub Universe 2020
Description
Presented by Chris Swan,. CTO Modern Apps & Cloud Native, DXC Technology
This talk will take you through the version control module of DXC's recently open-sourced online DevOps Dojo. The journey will begin by explaining the need for version control and getting the environment set up by connecting to GitHub. We'll show you how to make changes to code, and run through to a pull request that's then edited to account for (bot-based) peer review before being merged in preparation for the next steps.
For more from GitHub Universe 2020, visit https://githubuniverse.com
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
Hi
there,
so
thanks
for
that
very
kind
intro.
It
touched
upon
dxe,
which
is
a
company
that
some
people
have
heard
of,
but
not
everybody.
So
I
thought
I'd
start
out
by
just
briefly
introducing
the
company
to
give
you
an
idea
of
the
things
that
we
do,
which
will
set
the
scene
for
what
we've
been
doing
in
terms
of
this
devops
dojo.
A
So
at
dxe
we
run
the
mission
critical.
I
t
systems
for
thousands
of
companies
across
the
planet
and
we
talk
about
ourselves
as
a
full
stack
services
company,
so
that's
represented
here
and
so
on.
The
right-hand
face
it's
showing
the
types
of
services
that
we
do
so
it
outsourcing
modern
workplace
cloud
and
security
applications
and
then
finally
analytics
and
engineering
and
then
on
the
left,
face
it's
going
through
all
of
the
industries
that
we
serve
and
there's
really
too
many
for
me
to
spend
time
running
through
right
now.
A
The
number
of
employees
that
we've
got
worldwide
is
over
138
000
and
in
our
delivery
organization,
which
was
the
target
for
a
lot
of
this
devops
dojo
training
that
we've
been
developing.
That's
over
a
hundred
thousand
employees
and
then
looking
at
the
applications
area
that
I
now
focus
on.
65
000
application
professionals.
A
A
A
They
were
doing
their
first
playbook
on
a
config
management
tool
and
building
their
first
ci
and
cd
pipelines
using
jenkins,
and
I
had
a
team
of
people
going
all
over
the
planet
delivering
these
workshops.
They
would
typically
take
about
half
a
day
and
it
was
designed
to
be
viral
as
well,
so
that
people
who'd
taken
the
workshop
could
go
back
and
teach
another
one
with
their
colleagues
and
at
the
end
of
the
year,
we'd
had
something
north
of
a
thousand
people
had
gone
through.
That
workshop,
which
you
know
in
one
way
was
great.
A
A
A
I
was
at
the
monkey
grower
event
run
by
the
the
red
monk
analysts
and
bumped
into
luke
marston
there
who
was
at
weave
works
at
the
time,
and
he
showed
me
the
samples
and
examples
and
demos
that
he'd
built
to
show
off
what
weaveworks
was
doing
using
catacoda
and
I
kind
of
saw
that
and
thought
wow.
This
is
going
to
be
the
thing
that
will.
Let
me
take
this
workshop
and
make
it
web
scale.
A
So
we
took
the
workshop
and
put
it
onto
catacoda
and
that
then
allowed
us
to
address.
What's
subsequently
become
28
000
people
across
the
organization,
then
2018
an
inner
source
team
had
started
to
form
around
this
and
they
had
lots
of
plans
about
more
advanced
topics
to
address
and
so
from
the
white
belt.
We
grew
the
the
yellow
belt
and
there
were
so
many
modules
that
the
team
wanted
to
build.
A
We
split
it
down
into
different
stripes,
so
on
our
internal
learning
management
system,
there's
a
yellow
belt
stripe,
one:
a
yellow
belt
stripe.
Two
then
later
on,
they
also
had
some
ideas
about
doing
different
types
of
dojo.
So
we've
built
things
like
the
product
management.
Dojo,
which
is
intended
to
help
people
who've
traditionally
been
in
project
management
roles,
think
about
the
difference
of
doing
product
management
and
then
we'd
always
plan
to
do
this,
and
we
finally
got
there.
A
A
That
should
turn
up
at
least
one
of
these
links,
and
so
I'm
going
to
be
diving
into
the
home
page
in
just
a
moment
which
is
there
on
github
pages,
and
you
can
see
also
links
there
to
the
source
code,
that's
running
on
the
cadacoda
platform
and
then
the
source
for
the
github
pages
presenting
the
the
environment
that
we've
wrapped
around
that
when
you
get
there.
You're
gonna
see
a
webpage
that
looks
something
like
this,
and
so
it's
introducing
the
the
storyline
behind
the
dojo.
A
So
we
do
a
lot
of
stuff
with
continuous
delivery
pipelines
and
those
pipelines
need
to
be
built
around
applications,
and
so
for
that
we've
used
the
spring
pet
clinic
application,
because
it
gives
us
a
sort
of
flexible
and
well-battled
tested
sample
app
that
we
can
do
interesting
things
with,
but
to
complement
that
we've
built
a
cast
of
characters
and
a
storyline
about
the
the
pet
clinic
and
the
people
that
are
working
there.
And
you
can
see
here.
A
So
it
begins
with
a
story
in
setup,
and
that
is
all
about
getting
the
pet
clinic
app
into
your
own
github
user,
so
that
you
can
start
doing
things
with
it
and
also
setting
up
the
bot.
That's
going
to
be
used
as
part
of
the
version
control
module.
So
I'm
now
going
to
jump
into
a
screen.
Share
and
get
to
the
version
control
module
itself.
A
And
so
I'm
going
to
launch
get
the
version,
control
module
and
that
tab
is
now
going
to
take
me
into
the
catacoda
platform
and
all
of
the
catacota
modules
begin
with
a
splash
screen
like
this.
You
can
see
that
the
estimated
time
for
running
this
module
is
30
minutes.
As
I
glance
at
the
clock,
I've
only
got
about
13
minutes
left
for
my
slot,
so
this
is
going
to
be
a
bit
of
a
speed
run.
A
So
I'm
going
to
hit
the
start
scenario
button
here
and
that's
taking
me
into
the
cadacoda
platform
and
what
you
can
see
is,
on
the
left
hand,
side.
I've
got
a
storyline
which
is
telling
me
what's
going
on
and
then,
on
the
right
hand,
side.
I've
got
a
shell
where
I
can
actually
run
commands
and
one
of
the
things
that's
useful
here
is:
this
is
a
real
live
container
based
environment.
So
people
can
come
here
and
ski
off
piste
from
the
modules
and
try
things
out
in
the
safety
of
the
training
environment.
A
Should
they
want
to
do
that?
I'm
going
to
stick
for
the
script
for
the
time
being,
and
so
I
hear
the
scripts
explaining
the
sort
of
scene
set
on
why
some
changes
need
to
be
made
and
why
git
is
being
used
to
track
them
and
github
is
being
used
for
the
collaboration
around
that.
And
so
it's
telling
me
that
the
team's
choosing
a
branching
model
and
if
I
press
continue
it's
going
to
take
me
then
into
the
section
of
the
storyline,
where
I
can
start
actually
interacting
with
the
environment.
A
So
we
begin
with
this
preparation
script
and
that
takes
me
into
a
place
where
it's
asking
for
me
to
paste.
In
a
github
token,
I've
just
added
a
minus
s
there.
So
I
can
paste
that
in
without
it
being
echoed
to
the
screen,
because
we
don't
want
the
the
github
personal
access
token
to
be
shared
during
a
demo,
but
normally
it
would
be
probably
not
too
much
for
a
problem
for
that
to
be
echoed
on
the
screen
there.
A
A
But
caracoda
gives
me
the
lazy
option
of
just
clicking
on
the
button
and
that's
going
to
run
the
command
there
for
me
and
then
I
can
do
the
same
to
check
out
a
branch
which
I'm
gonna
call
us
horse
one
and
it's
now
time
to
make
some
changes.
So
it's
telling
me
to
navigate
into
this
source
main
resources,
database
hsql
and
the
data
sql,
and
I
then
need
to
go
to
line
23
and
add
an
extra
line.
So
let's
do
that.
A
So
I've
added
the
text
for
horse
and
I've
put
the
different
index
there
for
it
and
that's
all
set
to
go.
So
if
I
now
run
git
branch,
I
can
see
that
I'm
on
the
us1
horse
branch
and
if
I
run
git
status,
I
can
see
that
I've
modified
the
file.
So
there's
a
live
update
happening
from
that
editor
above
the
terminal.
A
A
A
A
I'm
just
going
to
accept
the
defaults
here
and
create
that
pull
request
and
sort
of
normal
stuff
happening
here
in
terms
of
merge
ability,
but
I'm
not
going
to
just
click
merge
there,
because
the
storyline
has
us
going
somewhere
else.
So
we're
simulating
peer
review
here
with
the
bolt,
and
so
what
I
need
to
do
is
ask
paulo
the
product
manager
if
he
can
do
that
peer
review.
So
let's
take
that
and
paste
it
in
and
I
didn't
get
the
copy
there.
A
A
A
A
A
A
We
kind
of
close
out
here
by
saying
that
the
the
user
story
is
ongoing
and
there's
more
still
to
be
done
with
the
underlying
issues.
If
I
glance
at
my
third
screen,
I
can
see
emails
popping
in
about
that.
Merge
has
already
taken
place
and
I
could
continue
now
and
it's
giving
me
the
congratulations
splash
screen
and
inviting
me
to
carry
on
with
dojo.
So
at
this
stage,
I'm
going
to
go
back
to
my
slides
and
jump
out
of
the
screen
share.
A
Now
one
of
the
things
that
happens
quite
frequently
is
people
run
into
trouble
as
they're
going
through
the
modules,
and
you
know
that
can
be
problems
with
the
underlying
platform.
It
can
be
issues
with
just
their
browser
or
something
like
that,
and
it
can
sometimes
be
especially
with
jenkins
issues
around
plugins,
having
drifted
away
from
behavior
that
we're
expecting
so,
we've
got
the
get,
help
button
that
people
can
use
and
when
they
press
that
that's
taking
them
into
github
issues
where
we've
got
as
you
can
see,
a
pre-populated
form.
A
A
A
A
The
second
part
of
the
call
to
action
is
to
please
contribute
so
we're
happy
to
take
pull
requests.
This
is
one
of
the
things.
That's
really
helped
us
polish
up.
The
modules,
as
we've
been
using
the
platform
internally,
is
people
spot
things
that
you
know
they'd
like
to
improve,
and
they
let
us
know
about
it
through
the
medium
of
pull
request
and
some
folk
sort
of
early
on
in
our
journey
were
coming
along
to
the
dojo
and
yeah.
A
Often
they've
been
pushed
by
the
manager
to
do
it,
and
you
know
thought
that
the
whole
thing
was
a
waste
of
their
time
and
as
soon
as
they
got
involved
with
it
they're
kind
of
okay.
I
can
see
the
point
of
this
now,
but
I
kind
of
hate
these
bits
or
this
this
thing
could
be
made
better,
and
so
you
know
many
of
those
people
contributed
internally,
and
you
know
we
did
that
through
their
pr's,
but
a
lot
of
them
also
became
part
of
the
inner
source
community.
A
A
So
we
just
wanted
a
license
that
made
sure
that
dxe
had
some
kind
of
acknowledgement
for
originally
creating
these,
but
we
really
do
hope
that
it's
useful
to
other
organizations-
and
you
know
they
can
potentially
build
that
around
their
own
tool
chains.
So
yeah
we've
originally
done
this
with
our
enterprise
github
and
some
of
our
practices
around
that
and
our
own
use
of
jenkins
and
some
of
the
associated
tools.