►
From YouTube: Jenkins X Office Hours (2018-09-06)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right:
okay,
hello,
everyone!
So
this
is
this
week's
open
office
hours
for
Junkers
X,
it's
probably
gonna,
be
a
bit
of
a
short
one.
Ham
got
too
much
and
we're
all
gearing
up
massively
for
Jenkins
world
which,
if
you
haven't
already
signed
up
to
go
along,
go
and
do
it
that's
seeing
a
week
week-and-a-half.
It
is
so
lots
of
exciting
things
in
strong
tecna's,
X
presence
as
well,
so
come
along
and
find
out
what
we've
been
doing
so
James
s.
A
Also
another
shout
out
food
because
James
S
is
not
on
this
call
today,
because
he
is
doing
webinar
for
the
cow
bees
at
the
moment,
as
well
as
Jess,
humble
and
Ben
Williams,
as
well
from
cloudBees.
That's
on
the
in
an
hour's
time,
so
people,
if
they
haven't
already,
they
should
actually
sign
up
for
Mesa
for
that
webinar
on
the
karbix
websites.
They
celebrate
stated
DevOps
report
which
starts
in
now.
It's
going
to
do
that
as
well.
All
right,
so
it's
just
before
kickoff
I
only
got
something
to
demo.
A
A
Share
screen,
so
one
of
the
things
I've
been
looking
at
is
around
as
previous
sessions
in
talking
around
the
crowd
in
tweeting
crowd
in
YouTube,
Jenkins
X,
so
I've
got
a
demo
here.
It's
still
a
little
bit
work
and
focused
code
is
going
to
be
checked
in
over
the
next
couple
of
days
now
with
all
to
meet
a
lot
of
it.
But
I
wanted
to
show
a
quick
demo.
So
I've
created
I've
got
two
anchors.
X
running
and
I've
created
a
quick
start
on
the
spring
boots.
A
A
A
I'm
called
a
pull
request:
it's
gonna
have
a
look
at
this
again
loses
previous
commits
that
I've
been
trying
this
out
through
the
day.
I've
got
a
pull
request,
and
this
is
just
sitting
there
waiting
to
be
to
be
merged.
What's
interesting,
is
we've
had
an
update
now
to
say
that
it
hasn't
been
approved
by
like
the
bot
user?
This
is
the
the
users
when
the
pipeline's
are
so
so
we
haven't
got
hasn't
been
proved.
Yet
it's
just
that
refresh
the
page.
A
Okay,
we've
also
had
a
label
added
to
it
for
the
size,
it's
a
medium.
So
this
is
one
of
the
plugins
for
the
prowl.
It's
just
have
a
little
chat
to
see
how
heavy
are
big.
This
changes,
alright,
what
we're
going
to
do?
We
haven't
had
any
CEO
bill
triggered
yet
so
this
is
kind
of
cool.
We've
got
some
control
over
when
things
like
triggered.
So
if
you
have
contributions
from
other
people,
for
example,
might
want
validate
the
tax
code.
Changes
from
it
hasn't
done
anything
malicious
that
you're
gonna
run
on
your
CI
infrastructure.
A
Well,
before
I've
done.
That
you've
noticed
actually
something
called
tied
is
saying,
is
popped
up,
so
there
hasn't
been
a
check.
So
what
it's
saying
these
tides
is
something
again
from
flowerless
will
automatically
merge,
pull
requests
if
the
all
their
checks
have
passed.
Now
you
can
configure
these
and
set
these
up.
This
particular
one
is
saying:
well,
it
hasn't
been
approved
and
and
also
well
yeah.
That's
the
main
music.
It's
not
mutable,
and
also
extra
things
like.
A
A
Now,
if
I
do
a
Google,
ETL
and
get
pods,
let's
see
what's
actually
happening.
Well,
we
can
see,
we've
got
a
pod
that
actually
being
started.
Okay,
that's
good!
That's
what
we'd
expect
and
it's
actually
you've
got
an
init
container.
We
put
two
out
of
three
in
it
containers
running
this
is
because
this
is
a
came
native.
Build
so
prowl
has
truth,
has
received
a
web
hook.
A
A
It
should
work
with
yep
spacing
as
well,
but
we
can
actually
go
and
have
a
look
at
the
rocks
magnet
container.
You
could
see
that
this
is
this,
is
our
Jenkins
locks
and
which
is
which
is
great
going
to
Nexus
and
putting
down
okay.
So
that's
actually
building
now
well,
I.
Guess
you're,
probably
wondering
you've
seen
this
before.
Why
am
I
so
excited
about
this?
Well,
I
will
show
you
yes,
Walter.
Look
at
our
deployment,
cube
Cpl,
see
PL
get
deployments.
A
Now.
Here's
Jenkins,
you
can
see,
we've
actually
scaled
it
back.
Jenkins
isn't
running,
we
don't
have
a
Jenkins
master
running.
What
we
have
is
the
awesome
work
from
cos.
K
and
Oleg
have
been
doing
in
the
Jenkins
community.
A
Jenkins
file
runner
so
that
in
the
Jenkins
in
the
key
native,
build
pod
is
a
one-shot
Jenkins
that
is
being
started
and
running.
A
Our
pipeline,
you
can
actually
see
this,
is
it's
a
slightly
modified
Jenkins
file,
but
here
it
is
here
we're
going
to
clean
this
up
a
little
bit,
but
this
is
just
an
average
Jenkins
file,
that's
being
run
inside
that
one-shot
master
and
then
go
back
to
our
pull
request.
We
should
probably
have
a
look.
That's
probably
the
finish
shortly.
A
It
is
running
and
then
there
we
go.
We
see
it's
been
built
and
preview,
a
fireball
if
it
started
up
as
well
I'll
refresh
a
couple
of
times,
but
that
will
actually
then
be
running
in
the
few
sources
we
all
promised.
You
also
do
that.
We'll
just
finish
it
off,
not
the
developer,
workflow
we're
actually
advocating
is,
is
around
from
the
Cuban,
the
speaker
system.
So
this
is
very
familiar
that
people
have
been
developing
in
open
source
project
around
Cuban
ities
and
using
comments
over
pull
requests
to
actually
control
your
pipelines.
A
Let's
prove
this,
we
have
this
ability,
and
what's
that's
going
to
do?
Is
that
that
go
back
to
prowl,
it's
going
to
say:
okay,
let's
add
the
approved
label
to
this.
That's
maybe
well
there
we
go!
Oh
because
I
haven't
been
added
so
in
the
owners.
Okay,
scrap
that,
but
that
would
have
done
these
out
a
if
the
owners
file
inside
the
get
repository.
You
had
my
name
without
a
label
there
and
then
tied
what
they've
gone
on
to
to
automatic,
nurture
I'm.
Just
for
completeness
there
we
go
start.
A
B
Was
that
doing
questions
on
them?
Oh,
that's
great!
When
do
you
think
it'll
be
sort
of
integrated
in
its
so.
A
A
We're
gonna
have
to
figure
out
and
early
next
week,
but
yeah.
The
idea
is
to
get
something
in
will
probably
do
it
with
your
along
with
your
work
earth
around
terraform,
so
that
will
enable
it
through
j:x,
create
the
terraform
with
the
prowl
and
then
we've
got
that
flow
and
make
sure
that's
kneel
before.
Let
me
switch
over
everyone
over,
but
it
was,
but
what
it
means
is
that
Jenkins
just
being
fired
one
shot.
We
gather
all
those
test
results
and
everything
like
that.
A
We
will
do
we
Jenkins
isn't
always
running
so
we've
got
a
lightweight
hook
and
point
which
is
scalable
as
well,
so
it's
widely
available
and
then,
when
the
builds
finished
Jenkins
goes
away,
then
Jenkins
entity
goes
away.
So
it's
pretty
pretty
pretty
exciting
stuff
that
were
actually
doing
and
working
with
the
Jenkins
community
as
well
to
make
sure
that
bring
it
come
together
and
align
it
yeah.
A
A
Pressures,
let's
say
for
the
Dinkas
world,
which
is
in
a
week
and
a
half
so
I
wonder
if
maybe
we
should
leave
it
there.
If
nothing
else,
I
know
next
week
we're
expecting
some
there's
going
to
be
a
checks.
Logging
that
cos
means
working
on,
so
that's
really
exciting
as
well.
We've
got
a
team
controller
that
Garris
working
on
as
well,
which
again
so
we
can
actually
split
up.
A
There's
multiple
teams
nice
and
easily,
and
the
roles
are
then
they're
coming
as
well
also
Ian's
than
some
cracking
workers,
while
making
sure
that
the
I'm
going
to
uses
secrets
in
cluster
you're
just
using
pipeline
tokens.
So
there's
lots
of
lots
of
cool
stuff,
that's
kind
of
coming,
and
hopefully,
by
the
end
of
next
week
or
have
it
all
committed
and
usable
resin
or.