►
From YouTube: Jenkins X Office Hours (2018-12-13)
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).
B
A
Are
green
and
we
were
talking
about
Jenkins
axe
we've
had
a
fantastic
week,
there's
been
a
huge
amount
of
excitement
around
Jenkins,
X
Carlos
did
a
fantastic
talk.
I
think
there
was
only
nine
hundred
people,
for
there
are
nine
hundred
people
for
Casas
talk.
It
is
being
pretty
huge,
we're
very,
very
excited
we're
going
to
have
a
little
write-up
as
well
when
we
come
back
and
kind
of
show
a
bit
more.
The
details,
Liam's
just
showing
some
of
the
the
conference
there.
Anybody.
A
B
A
They're
hugely
exciting,
the
energy
here
is
just
immense,
positive.
It's
very
all
around
a
fantastic
conference
and
yeah
we'll
do
a
bit
more
of
an
update
on
that
and
maybe
do
a
blog
on
the
Jenkins
X
website
and
we're
back
next
week
but
yeah.
So
far,
everything
has
been
positive.
There's
a
lot
of
excitement
for
for
Jenkins,
X,
and
so
we're
obviously
very
excited
to
accept
any
other
highlights.
Isn't
James
you
talk
or
anything
everyone's
headphone
and
Robbie
said
be
a
possible
highlight
for
you
keep
on
I.
C
Think
actually
the
highlight
for
me:
it's
really
seeing
pollicis
talk,
obviously
about
Jenkins
actor.
That's
really
really
good
I
mean
it's
just
the
general
positive.
The
real
excitement
around
here
and
people
are
really
infused
and
excited
about
kubernetes
in
general.
I
meant
about
think
inject
delivery.
It's
great,
actually,
I
we've
come
across
a
number
of
projects
which
we
think
is
gonna
work
really
well
with
drinking
jacks
and
that
accelerated
growth
around
that.
So
it's
good
we'll
enjoy.
A
Yeah
actually
so
there
was
some
caught
up
with
some
of
the
benami
folks
actually
yesterday
and
they
come
up
with
and
they've
actually
now
got
this
like
a
like
an
apple,
some
things.
It's
a
distribution
of
Prometheus
and
graph
on
a
number
of
metrics
our
to
the
pot
and
actually
they're
going
to
distribute
in
the
most
easy
way
to
consume.
So
that
seems
like
a
perfect
win
that
we
can
try
and
get
an
ad
in
as
soon
as
possible.
What
was
that
chap
and
James?
The
shipper.
A
Yeah,
and
so
this
chap
came
over
really
lovely
chap,
came
over
and
started
talking
about
what
they've
been
doing
around
canary
and
there's
a
product
there's
a
link
that
James
is
going
to
find
your
thing.
It's
called
shipper
and
it
looks
like
a
great
fit
for
Jenkins
X,
so
it's
kind
of
in
as
soon
as
possible.
Yeah
Bob
just
popped
it
in,
though,
and
that
hangout
link
and
can
add
it
to
the
Google
Talk
afterwards
as
well,
but
yeah,
maybe
I,
think
buddy's
interested
in
what
would
be
hopefully
doing
around
canary
employments
as
well.
A
D
Think
the
general
birds
about
well
Cubans
mayonese,
Jenkins,
xci,
CD
lots
of
people
asked
about
settle,
miss
Jenkins,
which
there's
been
a
lot
of
people
here.
Oh
they're,
maybe
not
ready
to
go
full
on
CI
CD
with
Cuban.
It
is,
but
they
they
I
using
lots
of
Jenkins
and
loss
could
be
being
very
excited
about
moving
to
service
Jenkins,
sir,
you
don't
have
any
drinkers
masters
to
manage
anymore,
which
is
awesome.
The
Milosevic's
I
don't
buy
that,
but
I
think
I.
D
A
And
one
probably
the
most
common
question
that
I've
had,
which
exact
mr.
Pozniak
asleep,
is:
how
do
we
build
the
our
docker
images
and
I've
kind,
packed
every
single
time
at
the
moment
where
you
amount
of
the
doctor
talking
courage,
be
looking
at
some
calico
and
people
contain
the
pills,
so
basically
I've
been
telling
everybody
and
it's
sort
of
I
do
if
that
leads
into
Garrett
yeah.
E
E
D
E
It's
you
as
soon
as
you
enable
the
cloud
builder
it
just
pushes
to
GTR.
That's
really
it
is
it's
really
cool
and
it's
super
fast.
It's
so
much
faster
than
building
on
our
own
images.
I
think
the
service
builds
I,
think
they
can
take.
They
create
that
mono
repo
or
each
of
the
my
repos
crates
about
ten
builds
I'm
about
to
get
each.
So
you
can
see
why
we
run
hard
disk
space
pretty
quickly.
A
So
so
good,
so
we
can
actually
continue
telling
people
that
that's
almost
it
I'm
just
chatting
to
down
at
some
I
think
he's
missing.
Managing
the
Kanaka
project,
I
think
and
he's
saying
that
he
they've
been
loads
of
cash.
Is
that
they
really
quite
shocked
at
how
fast
these
these
bills
are
actually
going.
So
that's
really
excited
acceptance.
Are
you
taking
advantage
of.
A
F
G
So
I'll
just
mention
briefly:
the
progress
on
adding
more
good
provider.
Support
to
prowl
is
coming
along
nicely
got
some
good
feedback
from
the
you
know.
The
prowl
cig
testing
community
about
that,
in
fact,
they
were
just
apparently
some
of
them
that
are
there
you've
kind
of
been
talking
about
it,
and
people
keep
asking
like
hey.
When
are
you
gonna
support
more
than
just
github,
and
so
it
sounds
like
there's
a
nice
groundswell
of
community
support
behind
this
and
they'd
asked
me
about
it.
So
I'm
gonna
present
it
the
next.
G
H
I
guess
in
the
installation,
it's
almost
there:
it
works
I
figure
on
some
issues
today,
the
upgrade
password
and
it
also
to
make
a
platform
working
with
volt
and
also
to
move
this
gbg
encrypted
secrets
to
vault
he'll,
say
and
then
in
the
pipeline.
We
need
to
fetch
series
from
vault
as
well.
Currently
we
use
kubernetes
secrets
for
them,
but
I
did
a
lot
of
refactoring
in
the
installed
recently.
Also
cleanup,
kids,
rework
the
entire
kid
stuff
now
make
it
clear
with
the
pipeline
and
normal.
D
D
B
Then,
for
me
also
kind
of
waiting
for
cosmic
because
again
I'm
trying
to
do
the
app
stuff
based
around
the
get-ups
for
dev
environments
and
almost
every
single
app
you
installed,
except
in
really
trivial
ones,
need
a
token
or
a
password
to
connect
to
the
service
they're
going
to
talk
to
so
I'm
kind
of
stalled.
A
bit
intentionally
intention
he's
still
a
little
bit
on
that
because
can't
make
much
progress,
but
I've
got
all
of
the
pieces
in
place.
So
we
have
a
working
either
working
tool.
B
That
will
ask
you,
questions
based
on
a
JSON
schema,
so
for
everything
that's
in
the
JSON
schema.
It
asks
us
as
a
question
and
I
have
all
the
basic
all
of
the
latest
graph.
The
JSON
schema
implements
the
accept
some
really
weird
educators,
which
I
don't
understand
how
to
implement
when
you're
asking
questions
like
you
know,
there's
some
odd
stuff
around
like
nested
schemas,
and
things
like
that.
I
didn't!
Do
that
rest.
B
It
kind
of
works
so
I'm
going
to
integrate
that
tomorrow
and
I
kind
of
took
a
detour
down
writing
an
app
for
slack,
which
is
based
around
the
slack
bot
that
James
originally
wrote,
which
now
working
quite
nicely.
So
it
will
direct
message
you
with
any
pipelines,
any
pull
requests
that
you
create
with
the
pipeline
and
then
it
can
also
tell
a
chatroom
when
a
new
pull
request
is
created
and
it
will
mention
anyone
you
put
as
reviewers
on
github
to
notify
them
that
there's
a
new
call
request,
created
and
I'll.
Do
that
I'll!
B
Do
that
as
early
as
a
room.
But
then
we
can
also
do
that
as
direct
messages.
So
I
can
literally
just
direct
message
any
reviewers
to
tell
them
that
there's
a
pull
request,
waiting
their
review
and
then
I'll
do
some
nice
filtering.
So
you
can
kind
of
filter
which
repos
you
want
on
which
rooms
and
things
like
that.
The.
B
I'm
gonna
do
that.
That's
the
last
one,
because
I
realized
really
to
do
that.
We
need
a
kind
of
history
because
it's
not
really
very
useful.
Just
notifying
the
person
who
last
committed
with
the
master
build
fail.
You
kind
of
need
to
notify
everybody
who
committed
since
it
last
passed,
because
it
might
be
any
of
their
fault
that
it
failed.
We
don't
really
have
that
right
now
in
Jenkins.
Excellent,
that's
a
really
classic
feature
in
Jenkins
right.
B
B
Get
slack
basically
identifies
people
by
email
address
its
slack
clearly
retrofitted
user
ident,
the
into
the
system
or
global
user
identity
right.
They
clearly
started
with
user
identity
per
workspace
and
then
retrofitted
the
whole
unique
stuff
in
because
actually
under
the
covers,
you
really
just
reference
everybody
by
some
kind
of
ID,
like
you
know,
ten
digit
alphanumeric
thing.
So
whenever
you
mention
someone,
you
can't
have
too
cool
a
method
on
the
slack
API
to
get
the
user
ID
out,
but
they
have
a
thing
called
get
user
by
email
address.
B
See
I
did
see
if
there's
an
alias
see
if
they've
got
their
get
user
name
on
the
user,
see
ID
and
if
they
have
override
it,
either
with
a
slack
username
or
email
address
from
the
user,
see
ID
and
just
as
a
backup
using
the
the
email
address
from
the
gate
provider,
which
I
think
I
think
that
will
work
for
most
people
but
like
for
us.
We
quite
will
often
have
our
personal
email
address.
As
oh.
B
B
So
because
the
way
it
works
with
gift
Ops
is
when
we
do
the
install
of
the
apps,
they
literally
get
installed
in
the
same
release
as
the
platform
and
all
the
platform
components.
So
to
me,
it
seems
to
make
no
sense
to
just
keep
that
consistent
and
install
them
all
into
the
same
place,
but
I'm
also,
you
know
open
to
ideas
on
that
and
the.
B
B
H
H
A
G
Yeah,
no,
it's
it's
going
well,
I
mean
there's
a
lot
of
there's
a
lot
of
pieces
to
that
I'm
kind
of
so
I
was
working
on.
I
was
kind
of
working
on
github
Enterprise
is
like
the
first
sort
of
I.
Don't
want
to
call
it
low-hanging
fruit,
because
I
feels
like
bad
luck,
but
I
kind
of
like
the
the
easier.
The
first
obvious
thing
to
do
is
add:
support
for
github
Enterprise
a
little
bit
stalled
on
that
at
the
moment.
G
Just
because
prowl
uses
prowl
assumes
a
version
of
or
it
uses,
there's
a
couple
places
where
prowl
uses
a
fql
api
that
only
works
with
a
version
of
github
enterprise,
that's
higher
than
the
current
version
that
we
have
at
cloud
bees
that
we
can
test
on
so
I'm
working
with
you
know
some
of
the
folks
here
at
cloud
B's
to
get
that
upgraded.
So
we
can
so
I
can
start
working
on
that.
So
that's
kind
of
Paul!
G
That's
a
little
bit
stalled
at
the
moment,
but
then,
while
that,
while
I'm
waiting
for
that
to
get
sorted
out,
I've
been
working
on
factoring
out
the
get
provider
logic
and
actually
moving
it
into
a
separate
repo
and
moving
each
individual
provider
into
its
own
package
and
kind
of
trying
to
clean
up
some
of
the
it
right
now.
Everything's
kind
of
just
in
one
package,
which
is
you
know
nice
and
convenient,
and
you
know
you
can
just
develop
really
quickly
with
all
this
stuff.
But
then
there's
some
there's
a
little
bit
of
leakage.
G
Some
of
the
abstractions
aren't
really
as
airtight
and
as
nicely
encapsulated
as
you
might
want,
and
so
I'm
kind
of
working
on
getting
all
that
taken
care
of
and
making
sure
that
you
know
that
those
are
all
nicely
encapsulated
in
that
the
individual
providers
aren't
coupled
to
one
another
and
that
the
provider
interface
isn't.
You
know,
coupled
to
any
of
the
implementations
and
that
kind
of
thing
so
been
working
working
on
that
trying
to
get
that
all
done.
G
A
That
sounds
fantastic.
I
also
want
to
give
you
a
shout
out,
so
we
had
some
amazing
feedback,
buckets
see
James
yeah,
so
somebody
came
up
to
the
booth
and
said
yeah.
They
were
there
using
Jenkins
eggs.
We
pick
a
kit
server
flawlessly,
so
am
our
civics.
You
were
doing
that
when
you
actually
as
a
community
contribution
that
was
before
you
come
through
particle
team.
Shuffle
just
really
wants
to
give
you
a
shout
out
and
yes
well
done.
That's
well.
A
F
Hi
there,
hello,
hi
mister
me
to
you
just
wanted
to
say
thank
you
for
this
really
great
project,
if
you're,
using
it
for
the
last
month
or
so
on,
some
new
stuff
and
might
work,
and
it's
really
sort
of,
let
us
stand
up
a
whole
new
team
and
get
sort
of
all
the
CI
CD
stuff
out
of
the
way,
which
is
something
that
we've
been
struggling
with
so
yeah.
Thank
you.
A
F
B
I've
get
the
reviewers
for
the
pull
request,
so
I
can
notify
them
on
slack,
and
you
know
yeah
sure
it's
fine,
if
you
don't
have
that
you
can
still
use
it.
It
just
won't
mention
anyone
for
your
review,
but
I
was
wondering
if
you
thought
about
how
we
want
to
handle
the
fact
that
these
api's
are
some
of
these
API.
So
I
say:
oh
one,
that's
really
bad
I
think
bit
buckets
pretty
crappy
right.
G
Yeah
a
little
bit
so
on
one
thing:
I've
thought
about
not
so
much
in
connection
with
bitbucket,
but
in
connection
with
with
Garrett,
for
instance,
yeah.
You
know
which
only
really
provides
the
code
review
features.
It
doesn't
really
have
very
many
of
the
social
features
that
github
has.
It
doesn't
have
it.
It's
not
an
issue
tracker.
G
One
thing
that
I
was
thinking
about
was
trying
to
figure
out.
Okay,
so
github
basically
has
conditioned
us
to
think
about
all
these
different
things
as
get
that
aren't
really
get
like
code
review
and
issue
tracking
and
all
the
social
things.
So
the
one
thing
I
thought
about
is
like
and
I've
been
thinking
about
off
and
on
is
how
could
we,
how
could
we
kind
of
like
decompose
all
of
the
components
of
get
that
make
up
github
and
try
to
figure
out
okay?
This
is
you
know
this
is
code
review.
This
is
issue
tracking.
G
This
is
whatever
you
know,
whatever
else,
those
other
things
might
be
so
that
we
could
do
something
like
in
the
case
of
Garrett.
You
could
have
here
it'd,
be
your
code
review
system,
but
then
you
could
use
it
with
an
issue
tracker.
You
know
JIRA
or
something
else,
and
that
essentially
it
would
be
to
the
other
components
in
Jenkins
X.
It
would
be
relatively
transparent.
G
You
would
still
do
things
like
update
issues
and
and
create
pull
requests
or
change
sets
or
whatever
they're
called
in
the
particular
gift
provider,
but
you
know
they
could
be
delegated
to
different
systems
and
have
that
be
kind
of
decoupled
and
and
those
different
components
be
pluggable
rather
than
just
assuming
that
it's
all
one
big
monolithic
thing
like
get
home
so
I,
don't
know
if
that
gives
us
to
where
what
you're
talking
about
Pete
but
I
think
that
kind
of
that
at
least
allows
us
to
start
reasoning
in
that
direction.
Where
we
can
think
about.
B
Know
that's
exactly
always
kind
of
thinking
right
because
justjust,
supposing
the
gate
provider
like
Derek's,
a
great
example,
you
actually
wouldn't
I,
mean
yeah,
we
could
support
Gerrit.
We
do
support
Gerrit
that,
like
98%
of
stuff,
won't
work
so
right,
you
know,
I,
guess
the
likely
the
other
kind
of
more
meta
question
was
well.
Is
it
worth
it
and
do
we
actually
kind
of
need
a
different
approach,
so
I
think.
D
As
well,
we're
currently
using
the
ability
to
sync
the
pipeline
status
to
commits
and
pull
requests,
we
use
that
quite
heavily
for
promotion,
and
maybe
we
should
default
to
using
just
pipeline
activities
instead
of
a
good
provider,
because
you
know
I
mean
a
lot
of
get
providers
you
you
can
get
cloning
than
a
pipeline,
but
recording
CI
statuses
on
a
good
provider
is
a
fairly
get
abuse
thing.
It
cook
it
kind
of.
D
Does
it
and
github
as
a
bit
of
that,
but
all
the
cloud
hosting
get
providers,
for
example
the
super
simple:
they
rarely
even
have
pull
requests
nevermind
all
the
other
features
so
I
think
having
a
generic
implementation
of
lots
of
the
bits
of
github
that
we
can
reuse
on
different
get
the
by.
This
would
be
really
useful.
D
B
Interestingly,
branch
protection,
which
is
kind
of
related
to
commits
that
is
actually
I,
did
look,
and
that
is
actually
a
really
common
feature.
I
think
LS.
Everybody
has
some
kind
of
branch
protection,
so
yeah,
okay,
yeah!
No,
that's
good
I'm
glad
we
think
about
it
was
something
that
was
vaguely
concerning
me.
Yeah.
A
Awesome
and
some
probably
close
time
at
that
up,
but
I
just
wanted
to
maybe
sitting
softly
the
remote
a
year
to
the
date
when
the
first
commits
for
Jenkins
X
happens.
I
honestly
am
confident,
they'll
be
exhaustive,
but
blown
away
first
from
the
curve
of
how
Jake
is
X
has
just
taken
off
it's
a
true
community
project,
as
now
I
mean
anybody's
watched
in
this
back.
If
they
get
to
the
end
of
this
core
big.
Thank
you
to
everybody.
This
it's
been
involved
and
encode.
A
Hopefully
we
can
encourage
more
people
to
continue
building
up
and
taking
takers.
X
further
this
year
is
just
blown
my
mind
and
I
suspect
next
year
is
going
to
be
even
be
even
better,
so
yeah
I
just
wanted
to
say
it
off
with
a
big
big.
Thank
you
to
everybody
and
I'm
looking
forward
to
the
new
year
new
new
features.