►
From YouTube: Jenkins X Office Hours (2018-07-12)
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
If
anybody's
got
anything
any
thoughts
or
questions
as
we're
going
along,
then
we
pop
them
in
this
has
docked
to
the
Google
Docs
and
we
can
we
don't
have
media
answers.
Then
we
can
follow
up,
never
got
much
evil
agenda.
Today
there
was
more
odd
person
was
trying
to
get
something
to
show
I
made
wine
addiction
a
live
demo
or
something
but
not
brave
enough,
we'll
see
if
we,
if
we
think.
A
C
So
there
are
a
few
things
about
like
the
existing
tests,
which
were
kind
of
like
I
found
hard
like
hard
to
kind
of
work
with,
like
one
of
the
things
was
the
vendor
in,
like
the
vending
of
the
dependencies
actually
for
the
harness
itself,
was
kind
of
hard
to
work
with
in
terms
of
trying
to
fit
because
we're
sort
of
dogfooding
and
we're
using
a
bunch
of
the
commands
from
within
Jake's
itself
in
the
harness.
In
order
to
like
pie.
C
Someone's
dog-
it's
not
happy
about
this
at
all,
yeah,
yes
yeah
they
were,
they
were
kind
of
a
lot
stick
with
the
actual
main
project
itself.
So
one
of
the
things
like
I
wanted
to
do
is
like
the
end
of
the
dependencies
in
a
way
so
that
they
matched
basically
whatever
was
in
what
currently
and
mastering
the
natural
Jack's
project
itself
and
then
use
those
you
know,
use
those
dependencies
use
those
methods
actually
in
the
test
time.
C
The
other
thing
that
I
think
is
like
a
big
thing
will
probably
become
even
bigger.
As
we
add
you
know,
more
and
more
tests
is
a
whole
sort
of
parallel
execution
of
the
of
the
test.
Suite
because
running
that
many
sort
of
quick
starts
sequentially
just
takes.
It
takes
forever
to
run
basically
so
I
kind
of
got
around
that
before
with
the
old
test,
honest,
but
I
kind
of
rolling
in
parallel,
which
you
know
is
like
a
little
binary
that
you
can
use
to
execute.
C
But
you
don't
really
get
any
control
over
and
you
know
streaming
output
of
logs-
or
you
know,
like
all
of
the
all
of
the
log
output
will
be
in
to
leave
so
you'll.
See
kind
of
you
know
the
output
on
sort
of
any
different
things
at
the
same
time,
really
difficult
for
debugging
all
that
kind
of
stuff,
so
switch
over
to
Junko
and
Junko,
basically
how's
the
whole
sort
of
handles
the
hopes
of
parallel
parallelism.
C
It's
hard
to
say
thing
by
effectively
compiling
is
it
kind
of
splits
up
the
tests
at
runtime
and
then
kind
of
compiles
them
into
their
own
binaries
and
then
executes
them.
You
know
from
like
a
sort
of
centralized
place
using
like
a
sort
of
status,
but
it
gets
spun
up
as
well
too
record
like
the
output
and
thank
you
lots
of
like
cool
options
like
you
know,
only
output,
the
log
if
the
test
actually
files
so
you're,
not
just
seeing
you
know,
reams
and
reams
of
sort
of
logs
for
things
that
are
just
passing.
C
Normally,
you
only
actually
see
the
log
output.
If,
if
you
know
that
execution
comes
back,
is
fine,
yeah
I
have
like
a
internally
inside
the
library
there's
a
thing
called
G
exec,
which
is
basically
just
a
wrapper
around
exec,
and
that
enables
you
to
kind
of
control,
control
execution
from
external.
You
know,
commands
and
also
right
expectations,
specifically
against
those
commands.
So
you
can
say
you
know
like
I'm,
expecting
this
process
signal
or
I'm.
C
A
C
I
mean
the
other
thing.
That's
quite
cool
is
there's
that
I
have
a
sort
of
an
abstraction
quarter.
Look
like
a
reporter
and
obviously
like
the
the
basic
default
and
test
suite.
You
know
has
a
default
reporter,
but
you
can
write
your
own
as
well
and
then
you
can
kind
of
make
it
do
you
know
whatever
you
want
another
really
cool
thing
about.
C
So
what
I'm
actually
doing
is
basically
marshaling
every
nodes,
sort
of
test
results
into
sort
of
JSON,
writing
that
out
to
the
file
system
and
then
reading
those
all
back
in
compiling
it
together
and
then
writing
it
out
again
as
HTML.
But
you
know
you
can
conceivably
output.
You
know
JSON
output.
If
you
want
it's
sort
of
you
know
like
database
reporting
or
whatever
format
you
want
really
and
I've
just
hooked
that
up
with
Jack's
Docs.
So
you
know
just
it's
out:
it's
actually
an
MD
MD
file,
but
it
lacks
it's.
C
You
know
valid
HTML
as
well,
so
it's
just
got.
You
know,
sort
of
the
time
that
that
feel
completed
and
then
sort
of
programmatic
listing
of
all
of
the
sort
of
top
level
description
blocks.
So
you
know
you're
describing
Jack's
QuickStart
whatever
or
just
describing
a
certain
feature.
It's
just
going
to
output.
B
B
C
Bbd
just
JX
and
it
should
be,
and
it
should
be
a
lot
easier
as
well.
If
anyone
you
know,
students
get
involved
in
the
project,
wants
to,
and
the
tests
totally
in
stock
and
there's
really
only
kind
of
like
one
thing
that
you
need
to
to
kind
of
have
SEC,
which
is
just
your
people
of
innovation.
You
know
basically,
you'll
get
username
in
an
environment
variable
and
at
the
start
of
all
of
the
test
runs,
it
will
actually
stay
out
a
little
things
saying
what
you've
got
that
set
to
and
what
needs
a
set.
C
So
the
sort
of
intention
is
there
I
guess
to
sort
of
encourage
people
to
kind
of
you
know,
try
to
themselves
and
and
report
things
that
they've
got
problems
or
you
know
just
generally
kind
of
helped
with
the
sort
of
contribution
of
getting
things
really
sort
of
solid
and
working
really.
My
solution
so.
C
C
You
know
like
mitigations
for
merge
conflicts
which
I
think
when
in
morning,
James
little
messy
James
merged
that
this
morning.
So
that's
that's
my
unofficial
name
for
in
order
to
differentiate
the
two
James's
legal,
messy,
James
and
other
James
I
probably
need
a
better
like
the
other
James
like
Ronaldo
JIT,
Ronaldo
James,.
C
Yeah
so
I
think
I
mean
that's
pretty
much
where
it's
at
I
mean
it's
the
so
just
to
you
know,
for
anyone
for
something
out
a
conversation
this
morning.
Basically
the
sometimes
the
issue
can
be.
If
you
kick
off
a
bunch
of
different,
you
know
app
creations.
At
the
same
time,
you
can
get
most
conflicts
into
the
requirements
yeah
more
because
you
know
all
of
the
piles
are
hanging
at
the
same
time,
and
basically
it's
the
same
three
lines
that
it's
trying
to
write
against,
doesn't
know
what
to
do.
C
You
get
conflict
so
I'm
it
occasionally.
That
is
basically
to
reorder
the
requirements,
by
name
the
intention
being
that
the
insurgents
will
come
at
different
line
numbers
and
therefore
you
won't
get
as
many
conflicts,
so
it's
definitely
possible
to
still
create
conflicts.
Anything
there's
any
way
around
that
and
there's
some
really
nice
code
that
does
like
rebasing.
C
A
A
C
C
This
is
kind
of
amazing.
It's
doing
all
this
stuff
for
me,
which
you
know
if
you're
kind
of
really
excited
about
it.
You
come
to
it,
and
the
first
thing
you
see
is
some
sort
of
error
and
get
blocked
in
some
way
kind
of
a
bit
deflating
so
yeah.
It's
really
just
kind
of
exposing
people
to
the
awesomeness
of
Jenkins
X
without,
like
you
know,
teething
trouble.
C
B
B
C
C
C
C
Stable
ones,
I
think
that's
like
the
key
to
it
as
well,
is
to
really
you
know,
there's
obviously
a
bunch
of
domain-specific
experts.
You
know
that
we're
talking
about
elixir
this
morning
haven't
had
an
enormous
amount
exposure
to
elixir
myself
I
think
it's
really
cool,
but
bunny
just
sort
of
played
around
with
it.
C
They're,
probably
people
using
it
and
you
know
sweet
very
kind
of
you
know:
production-grade
elixir,
sort
of
environments
that
have
got
a
bunch
of
this
practices
about
how
to
bootstrap
an
elixir
at
and
encouraging
contributions
so
that
we
can,
you
know
we
can
kind
of
use
best.
You
know,
sort
of
in
that
specific
domain.
C
We
can
use
like
the
best
practices
for
this
specific
thing
without
having
to
be
kind
of
experts
and
everything
ourselves
and
make
it
really
easy
for
people
to
contribute
in
that
way,
I
think
I
think
that
would
be
really
awesome
and
we'll
get
like
a
much
broader
range
and
the
quality
would
be
a
bit
higher
than
if,
where
each
of
us
trying
to
figure
out,
you
know
like
how
on
earth
do
you
know
how
on
earth
is?
What
is
the
best
practices
of
for
analytics
project?
C
C
A
Be
good,
longer-term
ease.
These
quick
starts
actually
meant,
rather
than
just
a
basic
page
at
hello.
World
it'd
be
nice
to
actually
offer
some
links
to
training,
both
information
so
that
people
could
try
out
different
languages.
Have
that
ultimately
see
ICD
pipeline
set
yeah,
nothing
in
it
and
then
kind
of
maybe
links
to
wizards
or
something
how
they
can
start
building
on
top?
It's
also
might
like
a
training,
evolving
new
languages,
yeah.
C
I
mean
it'd,
be
great,
I
mean
that's,
I
mean
he's
so
easy
to.
You
know,
for
instance,
rust
and
played
around
with
rust
a
little
bit,
but
we've
got
a
great
quick
start
for
rust.
You
know
it's
like
boom.
There
you
go,
you've
got
a
rust
up
up
and
running,
it's
live.
You
can
query
it.
You
know
you
can
play
around
with
it.
You
can
put
it
in.
You
know,
put
it
through
that
whole
process
straightaway
and
it's
you
know
it's
very
difficult
to
you
know.
C
C
A
Can
contribute
because
I
think
a
lot
of
those
quick
starts.
People
have
been
contributing.
If
people
do
have
a
quick
start,
then
we
can
just
fall
back
into
the
repo
and
we
can
tie
that
in
tot
automated
tests.
So
that's
kind
of
another
way
that
if
people
from
an
organization
or
from
their
team,
they
have
yeah
either
a
boiler
plate
QuickStart
that
uses
the
same
typical
way
they
package
or
build
their
applications.
If
we
have
a
quick
start
and
that
gets
tied
into
our
BDD
test,
they'll
get
run
on
every
single
PR
yeah.
B
A
C
I
was
at
this
also
yeah.
Definitely
the
spoilt
using
GK,
which
is
so
easy
to
get
stuff
done,
and
Allison's
powerful,
but
different,
yeah
slightly
harder
to
use,
but
yeah
we've
got
eks
he's
just
about
working.
I
haven't
really
blogged
about
it.
Yet
because
it's
not
a
hundred
percent,
we've
got
JX.
Let
me
show
you
the
CM.
I
refresh
my
screen.
C
C
If
you
haven't
already
downloaded
and
installs
a
new
path
and
all
that
kind
stuff,
then
it
uses
that
to
spin
up
the
UK's
cluster,
then
it
installs
Jenkins
X
on
top
and
it's
surprisingly
complicated
to
create-
and
you
guess,
cluster
there's
all
kinds
of
different
things.
There's
a
VP
see,
there's
a
service
role,
there's
a
there's,
a
node
policy
thing,
anyways
I
know
node
pool,
and
then
you
create
the
UK's
cluster,
so
there's
all
kinds
of
different
Amazon
resources,
but
all
appear
in
cloud
formation.
C
So
another
covers
EP
SCT,
others
using
confirmation
which
is
kind
of
cool,
so
he's
kind
of
working
there
and
by
the
way
it
uses
Ethier
by
default.
So
I've
switched
Amazon
and
EPS
providers
to
use
easier
by
default,
elastic
content
of
registry,
which
is
cool.
The
one
weird
thing
is:
whenever
you
create
a
project
and
Amazon,
you
can't
just
push
to
an
Abba
Dabba
to
docker
image
to
ECR.
C
You
have
to
create
an
easier
registry,
repository
I
think
is
called
for
every
dock
and
name
you
make
so
whenever
you
do,
JX
import
or
JX
great
spring
or
Jake's,
create
QuickStart
I've
hacked
that.
But
if
your
cluster
is,
if
you're,
if
you're
using
ECR
as
your
docker
registry,
then
we
do
the
address
Korea
easier
thingy.
C
C
The
only
thing
that's
missing,
which
I've
been
playing
with
now
for
a
few
days,
is
by
default.
When
you
install
Jenkins
X,
we
we
install
an
ingress
and
then
we
find
the
host
name
of
the
ingress
where
and
we
use
a
load
balancer
like
a
single
node
answer
for
the
cluster,
and
then
we
generate
ingresses
to
to
all
the
different
services
in
all
the
different
nose
faces
using
that
ingress
controller.
The
current
issue
I'll
stop
sharing
my
screen
actually
in
video.
C
Instead,
the
only
issue
is
when
you're
using
ELB,
amazon's
electric
elastic
load,
balancer,
there's
no
single,
canonical
IP
address
each
zone
gets
its
own
IP
address
internally,
so
there's
three
IP
addresses
and
those
IP
addresses
change
all
the
time
every
day.
So
once
you
could
be
close
to
the
next
day
disappears
again,
which
is
not
brilliant,
so
you
can
manually
set
up
route
53
yourself
by
hand,
but
that's
kind
of
painful,
so
I'm,
just
hacking
exposed
controller
so
that
we
can
use
paths
based.
C
Let
me
pop
my
screen
back
and
hide
hide
Rob's
face
if
I
open
the
window
I'm
using
I'm
using
an
Amazon
the
camera
right
now,
an
Amazon
cluster,
they
exceed
the
X
I'm
using
a
cops
cluster
right,
the
second.
So
this
is
cops
if
I
do
JX
open
note.
Where
do
my
window
go
here?
We
go
legs
open
notice,
the
half
base,
dns-based
ingress,
so
we're
using
a
single
domain
and
then
we're
using
paths
afterwards.
So
now
we're
using
paths
it
means,
rather
than
using
the
IP
address.
We
could
use
the
ELB
hostname.
C
The
only
problem
is
using
path
base,
bricks,
everything
so
if
I
open,
Nexus
Nexus
doesn't
work
and
you
can't
look
into
Jenkins
because
Jenkins
doesn't
know
it's
at
these
paths
so
now
I
need
to
go
through
all
of
our
charts
and
inject
the
path
into
all.
The
charts
is
horrible,
but
yes,
which
is
really
unfortunate,
but
there's
I
can't
really
see
another
way
forward.
I
think.
C
A
C
C
A
A
A
C
Was
scared
by
happy
to
go
around
and
fix
every
application?
That's
broken
sounds
a
much
better
idea.
Thank
you
here.
That's
awesome.
I,
owe
you
lots
of
videos
I'll,
try
that,
after
this
that's
brilliant,
yes,
so
I
was
at
the
course
like
he
is,
and
the
copses
plus
supposed
to
be
an
awesome.
So
we
think
we
can
switch
back
to
using
the
ELB
host
name
for
Amazon
ones.
This
path,
stuff
works,
which
would
be
awesome,
yeah.
A
C
Was
just
gonna
mention
one
other
thing:
I
finally
documented
how
to
change
the
configuration
in
Jenkins
X,
of
course,
in
this
slack
I
put
C
on
the
chat
room
only
today,
but
the
other
thing
is
we've.
We've
now
got,
you
can
specify
the
docker
registry
now
as
you
installing
by
a
docker
registry,
which
I
documen
on
there.
So
just
if
you
don't
wanna,
do
that
my
values,
dance,
you
can
specify
on
the
command
line
as
well
and
GCR
should
work.
There's
just
an
iamb
thing.
A
B
B
Before
you
say
anything
I'm
just
taking
down
a
very
trivial,
but
it's
critical
bug
caused
me
a
bit
of
heartache,
the
at
that
Sun
helm.
When
you
do
so
a
B
and
L
go
to
town
I've
seen
you
commit
to
a
to
X
and
we're
now
a
29.1,
so
Jake's
version,
but
out
it
just
tell
to
accept
tension,
use
a
client
and
a
server
both
the
same
version,
which
is
clearly
wrong.
I,
really
just
discovered
I
go
I,
try
and
find
out.
B
B
C
A
The
pain
so
I
did
the
little
thing
of
base.
One
of
the
things
we've
struggled
with
in
the
past
is
our
ingress
rules
so
be.
If
you
need
to
change
the
domain.
For
example,
we
out-of-the-box
we
create
a
cluster
and
we
default
to
ni
p
wo.
Now,
if
you
want
to
change
to
a
real
domain,
it's
kind
of
quite
tricky
to
be
able
to
start
to
do
this
quite
thing
number
of
things
you
have
to
change.
You
have
to
delete
your
ingress
rules.
You
then
have
to
update
the
configuration
for
expose
control.
A
You
have
to
remove
annotations
from
the
service
so
that
the
external
URL
is
updated
and
there's
also
one.
The
other
things
we
wanted
to
do
for
ages
is
enable
certain
manager
so
that
you
can
get
turn
on
HTTP
and
TLS.
So
you
can
get
automated
signed
certificates
generated
for
your
ingress
rules.
It's
pretty
much
well
done.
A
I've,
just
I've
been
testing
and
just
caught
a
couple
of
bugs
which
I'm
deciding
some
tests
in
I've
said
it
the
last
three
days
I'm
that
close,
but
I
really
feel
it
is
I'm
not
going
to
sleep
tonight
or
there's
gonna.
Be
a
bit
of
wine
they'll
help
me
tonight,
not
sure!
Well,
I'll
fix
it,
but
then
once
that's
done,
then
it
is
gonna
be
fully
focused
on
trying
to
get
help.
Oh.