►
From YouTube: Jenkins X Office Hours (2018-07-26)
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).
C
Okay,
thanks
Liam,
okay,
hello,
everyone.
This
is
this
week's
jinkers
ex
office
hours.
We've
got
a
people
on
from
the
call.
We're
gonna
have
a
little
demo
from
Gareth
Evans
today,
which
is
gonna,
show
some
of
the
work
that
he's
been
doing
around
some
integration
with
coach.
It
I'm
Tara
form
as
well.
So
that's
pretty
pretty
exciting
stuff.
C
So
before
I
guess
we
do
that,
did
we
did
anybody,
have
any
questions
or
anything?
So
maybe
it's
worth
having
a
little
update
of
what
people
have
been
doing
this
last
two
weeks,
any
new
cool
things
that's
coming
up
in
the
Jenkins
ex-world
Cosme
new
just
popped
up
on
my
screen.
So
maybe
you
could
kick
that
up.
Do
you
get
up
to.
B
D
E
D
Directory
github
and
so
on.
Probably
we
will
start
with
github
first,
so
yeah
hi
I'm,
using
the
Jenkins
X
completely
to
manage
the
deployment
of
the
operator
like
I,
did
running
now.
I'm
trying
to
get
a
gr
PC
running
with
the
bags
I
have
to
have
some
secrets
to
move
them
from
one
nation,
a
space
to
another
and
so
on,
but
yeah
and
I'm
progressing
on
this
side.
C
C
G
Hear
you
can
hear
me
excellent?
Yes,
so
lots
of
testing
the
main
thing
that
I've
been
focusing
on
and
last
a
week
or
so
really
has
been
getting
parallel
bills
to
complete
without
any
kind
of
like
manual
sort
of
interference,
so
without
being
required
to
go
in
and
either.
You
know
either
retake
off
certain
bills
because
they
failed
because
of
clashes
or
to
going
and
reserve
like
resolve,
merge
conflicts
and
yeah.
G
There's
a
PR
for
that
now,
so
I
think
fingers
crossed
that's
done
and
works,
and
it
might
still
be
mid
case
were
to
lurking
in
there
somewhere,
but
it
seems
pretty
solid,
like
I've
been
testing
testing
it.
Quite
a
lot
and
yeah
I
get
to
a
consistent
passes
now
I
sort
of
I
kind
of
hardened
up
the
the
actual
sort
of
test
runners
themselves
as
well,
because
occasionally
they
just
get
like
a
and
network
disconnection
and
then
that
you
know
the
test
will
fail
just
because
the
Jenkins
client
got
disconnected
momentarily.
G
So
there's
like
a
retry
on
that
now.
So
you
know
if
there's
any
kind
of
like
flaky
network
or
anything
that
won't
just
filed
the
test.
You
get
a
force,
failure,
I,
suppose
the
most
interesting
sort
of
part
of
that
really
is
just
adjusting
the
adjusting
of
Jenkins
configuration
itself
just
to
make
it
do
sort
of
PR
builds
without
attempting
to
merge
like
on
one
sort
of
the
PR
site,
which
was
the
sort
of
blocker
really
oh
and
the
other
thing
was
adding
into
the
default
environments.
G
The
concurrent
concurrent
builds
only
option
which
just
prevents
sort
of
clashing
where
two
sort
of
competing
builds
of
both
trying
with
deploy
to
master.
At
the
same
time,
it's
possible
that
I
had
a
weird
edge
case,
where
basically
one
would
hang
forever,
because
it
was
waiting
for
something
that
had
been
declared
in
one
of
the
other
manifests
that
wasn't
actually
there.
G
It
would
just
sit
there
forever
and
just
kind
of
wait
so
in
add,
as
those
sequentially
and
I
guess,
with
the
prow
stuff
that
you're
working
on
sort
of
going
in
and
maybe
if
we
can
get
the
promotion
containers
down
so
like
a
smaller
footprints
that
they
can
kind
of
spin
up
real
real
fast.
And
you
know,
then
it
would
be
really
slick
and
and
just
really
sort
of
solid.
In
terms
of
just
being
able
to
push.
C
Things
because
it
just
to
jump
in
yeah,
probably
one
of
the
another,
given
these
stability,
things
that
we're
actually
looking
at
you're,
doing
a
great
job,
actually
just
looking
at
how
we
can
improve
stability
a
test,
but
also
then
services
were
actually
providing,
and
it's
quite
a
few
people
have
come
up.
I've
been
hit
with
issues
with
our
charming
Museum
is
down
so
yeah.
Just
maybe
give
a
bit
yes.
G
So
I
mean
so
basically
that
kind
of
like
a
single
point
of
failure
at
the
moment,
because
our
chart
museum,
you
know
if
we
need
to
tear
down
our
cluster,
there's
any
kind
of
issue
there.
Then
you
know
anyone
trying
to
pull
those
charts
is
basically
gonna
hit
problem,
and
especially
if
you're
testing
can
end
up
with
these,
you
know
end
up
with
failures.
Basically,
there
aren't
really
anything
to
do
what
they're
doing,
especially
if
you're,
trying
to
sort
of
test
something
that
potentially,
you
might
be
like
points
of
makeup
er.
Something
like
that.
G
So
even
if
chart
museum
isn't
actually
running
on
the
cluster,
it's
not
going
to
break
anything
and
we've
we've
basically
got
as
much
uptime
as
as
as
Google's.
You
know,
sort
of
cloud
implementation
which
hopefully
should
be
pretty
good,
and
it's
nice
and
simple
as
well.
I
mean
there
is
the
sort
of
sort
of
adjoining
issue
of
proxy
access,
and
if
you
can't
get
to
those
you
know
you
can't
get
to
those
addresses
and
sort
of
how
to
sort
of
mitigate
that.
G
But
I
think
we've
kind
of
broken
it
out
into
kind
of
like
two
separate
problems
now
and
we'll
probably
look
at
the
proxy
thing
separately
and
try
and
sort
of
solve
that
for
people
that
we've
got
you
know
really
restrictive,
firewalls
or
or
you
know
can't
do
that
for
whatever
reason
and
just
try
and
solve
that
separately.
But
that
should
really
firm
up
things
and
in
terms
of
the
bills,
then
obviously
we
can
other
James.
G
Mention
is
whether
that's
kind
of
our
goal
in
terms
of
switching
out
the
actual
Jets
deployments,
for
you
know
for
users
as
well.
So
you
know
you'll
have
like
a
persistent
volume.
Basically
it's
like
mounting
in,
and
you
know,
if
your
and
blowing
away
cluster
or
doing
anything
like
that,
bring
it
back
up
and
your
chart
museum
should
be
in
the
same
state.
We
had
it
out
before
yeah.
C
C
C
G
I
guess,
speaking
of
fault-tolerance,
let
me
talk
about
some
of
this,
not
fault-tolerant
so
well.
The
eks
is
an
amazon
is
and
cops
or
amazon
is
whether
this
always
been
a
bit
of
a
tricky
thing
with.
So
let
me
start
my
bike.
Using
Jenkins
X
on
Amazon
has
been
slightly
different
to
using
Azure
and
Google
with
both
of
those
two.
G
If
you
create
an
ingress
controller,
you
get
a
stable
IP
address,
so
we
could
do
the
ni,
p,
2,
io
kind
of
hack,
to
avoid
you
having
to
do
workout,
DNS
and,
strictly
speaking
in
a
real
production,
install
the
junkies
X.
We
should
all
do
work
at
the
NS,
so
we
get
in
the
multi
available,
easy
urns
and
all
that
kind
of
good
stuff.
Just
like
google
story
s3,
but
it's
one
of
those
things.
G
G
The
first
time
we
try
and
configure
it
and
then
nothing
would
work,
and
then
you
have
nothing
in
jinkies
ex
to
use,
because
if
you
can't
talk
to
Jenkins
you
kind
of
screwed,
so
we've
always
had
this
kind
of
deficiency
on
Amazon
that
we
couldn't
work
without
marketing
that's
properly,
it
could
cut
with
electric
elastic
load.
Balancer
ZL
B's
do
have
IP
addresses,
but
they
kind
of
change
randomly,
so
they
survive
for
a
few
hours.
G
So
for
a
few
hours,
you've
got
a
joggers
X
cluster
and
then
it's
completely
useless
because
you
can't
see
anything
anymore,
which
has
been
kind
of
a
bitter
worry
I
mean
it's
only.
It's
only
really
affects
folks
kicking
the
tires
really
like.
If
you're
doing
a
real
install.
You
should
always
use
DNS,
but
this
is
more
of
a
tyre
kicking
thing.
So
if
add,
lots
of
kind
of
emails
and
discussions
of
how
to
do
is
properly
and
lots
of
help
from
some
hammers
of
focus,
which
is
really
nice
yeah.
G
So
the
official
stories,
if
you
want
stable
IP
addresses
you,
have
to
use
the
new
load
balancers
in
Amazon
called
the
NL
B's
network,
Allah
pounders,
rather
than
to
elastic
load
balancers
of
the
old
ones
and
elby's
there
weren't
the
buses
of
the
new
ones
and
I've
got
a
pull
request.
I'm
just
about
to
submit
that
switches
to
NL
B's
by
default
for
Cox
and
eks
one
fly
in
the
ointment
was
it
was
it
an
L?
B's
worked
perfectly
today
with
Cox,
which
is
awesome.
G
They
do
well
with
eks
right
now,
because
of
rolls,
if
anything
doesn't
work
on
Amazon.
This,
usually
because
of
rolls
we're
using
eks
ETL
under
the
covers,
which
is
a
really
lovely
tool
from
the
weave
works
folks,
which
you
can
just
type
eks
ETL
create
cluster
and
it
creates
a
cluster
which
sounds
so
simple
and
trivial,
like
you.
Do
g-cloud
great
cluster
D,
just
crazy
cluster
on
Amazon.
No,
it's
a
totally
different
world
and
create
coaster
involves
all
kinds
of
things.
G
So
eks
quick
cluster
under
covers
creates
the
rose
and
the
BBC
in
the
back
playing
and
the
node
pools
and
all
the
various
things
you
need
to
do
boo,
PKS,
so
we're
using
a
care
CTL.
But
NLB
was
one
issue
that
you
care.
Ctl
didn't
support
the
roles
necessary
for
and
he'll
be,
unfortunately,
but
he
has
been
helping
us
really
well,
thanks
in
the
early
works
and
these
as
I
type
as
I
say
this
well,
a
done
typing
as
well.
That's
it's
over
as
I
talked
Italy
is
just
about
to
release.
G
Be
two
three
or
beautiful.
We
took
before
of
ek
CTL,
which
is
Sue's
us
available
as
a
binary,
I'm
gonna
Merc
will
submit
the
pull
request
to
use
it
so
by
say
tomorrow.
If
you
do
JX
create
cluster
EPS,
it
will
use
the
new
binary
of
ek
CTL
and
it
will
use
an
NL
B
and
then,
if
you
don't
use
well
count
the
NS,
your
UK's
cluster
should
survive
for
more
than
a
few
hours
like
the
next
day.
G
You
should
still
be
able
to
use
your
tickers
X
cluster,
which
would
be
awesome
because
that's
been
a
kind
of
a
slightly
embarrassing
issue
that
we've
had
ever
since
ur
pretty
much
this
week.
Cops
an
e
KS
should
work
awesome
for
jakey's
X
and
it
uses
elastic
container
registry
that
covers
by
default
as
well,
which
is
nice
so
actually
after
they
start
work
by
the
end
of
this
week.
G
Amazon
should
be
the
best
supported
pub
really
because
we
still
don't
automatically
the
registry
yet
or,
as
you
contain
the
registry
at
the
box,
which
I
hope
we
can
fix
that
pretty
sharpish,
because
it's
slightly
embarrassing
them
and
sorry
about
yet
all
the
bits
of
all
hard
works
done.
We
just
need
to
get
the
I
am
role
setups
on
GTV.
We
can
push
to
GCR
and
then
as
year.
G
You
can
I,
don't
want
to
have
to
do
the
whole
DNS
dance
just
to
try
it
out
for
a
couple
of
hours
and
then
tear
it
down,
but
in
a
real
install,
which
is
all
be
using.
Markup
DNS
I
have
added
the
kerb
to
set
up
route
53
on
Amazon
mark-up
DNS,
and
if
you
choose
to
do
that,
you
get
prompted.
Would
you
like
to
use
one
Guardian
s
and
yes
is
the
default?
And
if
you
say
yes,
it
tries
to
do
that.
I'm,
not
sure
that
they
actually
works
yet
I
haven't
tested
it.
G
It
compiles
but
I'm
hoping
to
test
that
the
ticket
works.
But
if
that
does
work,
it
would
be
nice
to
do
the
same
thing
on
Google
and
and
there's
you
because
they
all
have
at
the
NSE
kind
of
thing,
so
it'd
be
kind
of
nice
to
automate
setting
up
the
DNS,
because
it's
so
easy
to
mess
that
up.
And
you
know
people
often
pick
the
wrong
thing
that
the
the
Mantor
and
they
put
well
count
in
the
domain
name
and
when
it
shouldn't
and
all
this
kinda
stuff.
G
So
it'd
be
kinda
nice
to
automate
that
I've
seen
a
few
issues
lie
by
where,
when
people
try
to
do
work,
a
DNS
their
point,
the
worker
DNS
at
the
API
server,
not
the
ingress
controller.
So
the
more
we
can
kind
of
automate
that
bit
better
because
we
better
want
a
well-cut
DNS
that
resolves
to
the
hostname
or
IP
the
English
controller.
Then
we
can
get
in
from
the
outside
to
talk
to
any
services
in
community
yeah.
G
Sorry
for
that
big
ramble,
but
basically
eks
is
all
of
us
they're
like
within
within
24
hours
of
being
awesome
and
cops
he's
pretty
much
they're.
An
ingress
is
all
pretty
much
solid,
enamels
and
finally,
which
is
taking
way
longer
than
I
imagined
and
we're
really
close
on
ECR
and
sorry,
Asya
and
GCL,
which,
which
would
be
really
nice
having
really
nice,
out-of-the-box
container
registry
and
ingress
and
low
bouncer
support,
is
really
really
nice
for
the
for
the
big
three
cards
and.
G
H
G
Might
solve
like
as
a
sort
of
trickle
down
to
the
benefit
and
they'll
us
to
start
using
multistage
builds
as
well
for
for
our
images
yeah,
although
the
only
problem
is
because
you
every
was
is
always
using.
You
know
the
latest,
so
some
people
won't
have
you
know
some
people
who
is
using
the
internet
like
a
register,
you
probably
can't
use
multistage,
BAM
I'd
love
to
use
multistage
as
soon
as
you
got
canning
here
all
bets
are
off
no.
H
C
G
D
A
doctor
in
doc,
yeah
already
with
the
Builder
base
image
locally
I
write
in
a
docker
container,
not
in
a
kubernetes
job,
because
anyhow,
if
we
want
to
run
it
in
the
agents,
we
cannot
use
jobs
because
we
need
to
spawn
jobs
out
of
the
agent
and
my
guess
is
not
possible.
We
need
to
run
it
inside
of
the
agent.
You
know.
Container,
probably,
is
the
easiest,
but.
G
G
D
G
D
C
C
Nice
all
right,
we
eks.
C
So
as
you,
okay,
so
from
that
as
well,
then
something
I
guess
two
weeks
ago
was
the
last
one
we
do.
But
there's
now
a
few
people
have
asked
about
it.
There's
a
there
JX
upgrade
ingress
commands.
The
people
can
once
you've
actually
created
your
cluster.
You
can
switch
out.
You
can
change
your
DNS.
C
So
if
you're
using
the
ni,
p
de
io
wildcard
initial
thing
to
kick
the
tires
with
the
Custer,
if
you
then
want
to
switch
to
a
real
domain,
then
you
can
do
JX
upgrades
ingress
and
there's
a
little
wizard
in
there.
That
also
allows
you
to
enable
certain
manager.
So
we
have
integration
with
certain
manager
to
generate
signed
certificates
from
let's
encrypt,
so
you
can
switch
to
HTTPS
ingress
rules.
Jenkees
X
will
automate
everything
thing
will
recreate
all
the
ingress
rules
with
you
new
domain
and
signed
certificates,
which
is
pretty
cool
as
well.
G
G
G
C
H
I
can
so
that
was
like
like
two
three
weeks
ago,
so
it's
just
an
initial
repository,
but
I
mean
it
works.
It's
a
tray
application
in
a
sense
that
when
you
start
the
app
which
is
electron
base
is
the
same
as
your
code
and
a
drum
and
slack
and
uses
that
or
creating
the
native
app.
That's
a
tray
icon
at
the
top,
the
menu
bar
in
all
life.
H
You
could
build
basically
Windows
or
client
anything,
but
there
is
nothing
specific
to
to
make
I
mean
everything
is
kind
of
abstract
it
away,
but
basically
any
that's
tray
icon!
You
click
on
it
and
see
like
drop-down.
You
see
a
window
and
at
the
moment
is
it's
not
at
the
same
stage
as
the
video
code
plug-in.
But
the
code
is
the
same.
It's
gonna
add
a
watcher
and
then
it's
basically
print
out
the
pipeline's.
The
cool
thing
is
that
from
that
from
that
app,
you
can
also
execute
commands.
D
H
Commercial
side
that
we
are
working
on,
but
the
idea
is
that
you
can
is
the
same
as
your
visual
code,
where
you
basically
click
on
on
the
pipeline,
and
then
you
can
execute
that
in
the
terminal.
The
same
is
here:
you're
just
doing
that
behind
the
scenes
is
using
the
it
basically
opens
the
command
in
your
in
your
terminal.
Whatever
is
your
the
full
terminal
set
up
in
you
know
else
you
could
you
could
execute
anything
you
want.
You
could
also
like
our
stuck
in
with
the
rope
we
could
do
like
that.
H
You
can
grab
a
folder
and
then
drag
and
drop
on
that
icon
and
you
can
import
your
JSL
Jacksonport.
It's
it's
basically
I
had
a
bunch
of
problems
setting
everything
up,
because
everything
is
types
we've
been
with
electron.
This
cat
was
kind
of
messy
and
also
I
had
a
problem
with
kubernetes
client,
which
is
that
open
source,
one
from
kubernetes
project
doesn't
work
in
electron
environment,
so
I
had
to
touch
it.
Basically,
the
electron.
H
No
sorry,
the
kubernetes
client
is
using
shell
j
s,
which
is
like
a
wrapper
around
the
terminal
functions
and
I
had
to.
There
is
a
PR
which
fixes
that
I
have
it
locally.
It
works
and
I
also
created
the
PR
for
for
the
kubernetes
client,
which
I,
remember,
I,
remember,
I,
haven't
follow
up,
I,
have
to
sign
up
some
agreement
or
something
like
that.
But
it
looks
fine,
it's
basically
it
just
it's
just
a
patch.
H
Basically,
they
have
like
a
secret
API,
but
if
you
switch
to
acing,
then
it
works
also
in
an
Oracle
environment,
because
the
way
it's
wrapped
it's
some
certainly
ideas
are
not
available.
So
it's
just
that.
So
there
was
a
bunch
of
stuff
to
just
to
get
here,
but
then
the
idea
is
to
have
the
same
functionality
as
visual
code
extension.
You
can
run
it
locally.
H
You
just
npm
install
start
starts
the
app
and
then
you
can
have
an
app
which
is
you
can
update
it
on
the
fly,
because
electron
supports
that
you
can
update,
update
itself
when
you
create
a
new
release
and
github,
for
example,
and
like
I
said,
because
you
have
access
to
the
terminal
and
you
have
you
can
create
one
cat
or
whatever
you
are.
You
want
and
you're
not
locked
down
to
any
specific
IDE.
You
can
do
a
bunch
of
stuff
yeah.
C
That's
awesome
all
excited
to
see
how
that
goes.
I
am
keeping
an
eye
on
it,
but
yeah
nicely
done.
I
guess
before
we
go
on
to
the
guys.
I'll
give
a
quick
update
about
some
of
the
stuff,
so
I'm,
looking
at
integrating
crowd
into
Jenkins
X.
So
for
anybody
that
doesn't
know
what
plow
is
proud
is
part
of
the
test
of
researcher
project
on
the
committees
or
goetaborg.
What
they
do
is
proud
is
like
an
event,
webhook
thing
the
handles
when
webhook
events
from
github
and
then
updated
pull
requests.
C
You
can
actually
then
comments
you
can
actually.
So
if
you
have
a
comment
on
the
pull
request,
if
that
will
send
the
webhook
event
and
trowel
intercept
this,
and
then
it
can
trigger
jobs,
so
in
Cuba
thirties.
What
we're
looking
at
doing
is
using
that
for
the
promotion
at
the
moment
for
when
your
folks
are
using
github
will
get
AB
Enterprise
while
then
using
Jenkins
to
do
the
promotion
of
an
application
into
a
staging
or
production
environment
are
actually
going
to
use.
Prowl
and
what's
really
cool
about
prowess
is
it
seems
to
be
so.
C
Many
of
other
projects
are
actually
using
it.
History
o
is
one
and
most
of
the
kubernetes
projects
are
actually
using
prowl.
So
it
seems
to
be
a
bit
of
consistency
about
a
common
way
of
working
for
developers.
You,
if
you
have
a
pull
request
with
w8
IP
in
it,
for
example,
it'll
automatically
add
a
label
to
your
pull
request
of.
Do
not
merge
various
other
things
like
this
and
then
when
you,
you
can
trigger
your
CI
tests.
If
you
have
so
many
ways
of
paw
requests,
you
don't
know
you
might
want
to
validate
there.
C
Isn't
anything
dangerous
in
that
pull
request
before
triggering
your
CI
tests,
for
example,
and
then
you
also
set
things
up
like
you
have
all
to
merge
as
well,
so
that
if
it
passes
all
you
see,
ID
checks
and
LGM
t
comment
will
actually
Ottoman.
You
can
have
our
leases,
so
it's
a
real
great
way
that
developers
and
the
focus
source
projects
were
on
coupon.
The
t's
are
using
and
it
looks
like
a
great
fit
for
actually
having
a
a
developer,
workflow
pray
way
being
Jenkins
X,
so
very
excited
about
that.
E
C
E
E
So
I'm
just
gonna
put
this
little
slide
up
here,
so
this
this
is
basically
just
an
overview
of
what
I'm
doing
so.
If
I'm
gonna
run
three
commands
and
what
that's
gonna
do
is
we're
gonna
first
create
a
Teke
Teke
service
account.
We're
then
going
to
create
some
terraform
configure
the
crates
repository
populates,
that
repository
with
the
config
that
we've
requested,
and
the
third
step
is
to
create
a
code
ship
built
that
will
automatically
trigger
that
and
start
applying
a
cluster.
E
E
E
E
E
E
That's
chosen
the
Google
Cloud
project
that
we're
gonna
use.
It's
now
going
off
to
try
and
understand
if
we've
got
enough
permission
to
create
that
account
and
I
think
it's
the
set.
I
am
policy
role
that
it
looks
for
that's
the
key
one
and
it
goes
through
and
assigns
their
particular
roles
that
it
needs
to
be
able
to
administer
a
cluster
and
manage
the
storage
in
the
way
that
we
need
to
do,
and
at
the
end
of
this,
it's
going
to
download
that
service
account
key
yeah.
E
So
I'm
one
out
of
three:
that's
good
I'll,
clear
this.
So
the
next
step
is:
are
we
going
to
create
some
terraform
config?
So
we
have
a
clone
for
this
I
can't
give
it
an
augment,
also
going
to
call
office
hours
and
I'm
going
to
tell
it
to
extra
things.
So
I'm
gonna
pass
in
the
GK
service
account
to
make
sure
the
permissions
are
correct.
E
E
E
C
E
Terraform
by
default,
you
know
it's
a
state
file
and
it
well.
It
needs
to
stall
that
state
somewhere
by
default.
It
will
just
use
the
local
file
system,
but
if
you're
trying
to
trigger
this
from
a
CI
server
or
from
multiple
machines,
you
want
to
put
that
somewhere
in
the
cloud.
So
there's
a
terraform
that
gets
generated
it's
automatically
configured
to
use
a
Google
Storage
bucket
at
the
backend.
E
Listen,
you
can
I
put
this
in
Belgium
your
machine
size
and
with
the
defaults
with
the
size.
This
is
going
to
start.
Creating
this
that's
complete.
If
I
just
show
you
what
the
structure
of
that
looks
like
a
directory,
they
have
an
organ
that
inside
ujx
folder
you
have
an
organization's
directory
and
so
about
your
half.
E
There'll,
be
one
for
the
name
of
the
organization,
and
that
way
this
you'll
see
it'll
saw
we
have
a
basically
build
SH,
which
is
what
code
ship
is
going
to
use
to
apply
the
changes
we
have.
A
cluster
clusters
directory
meant
a
bit
a
subfolder
for
each
cluster
that
you
want
to
create
and
then
sort
of
suppose
the
main
important
one
is
this
terraformed
or
tier
FAR's
file,
which
is
here,
which
is
where
all
of
your
actual
configuration
for
that
cluster
is
stored.
E
E
And
now
it's
going
to
prompt
for
us
to
log
into
code,
shell,
we
don't
persist
this
information
anywhere.
It's
anything
it's
only
for
the
initial
job
creation.
It's
not
required
anywhere
else,
speaking
to
James,
about
putting
this
in
mind,
are
they
sort
of
secret
files
or
the
earth
files
at
some
point
run
log
in
with
my.
E
Yeah,
okay,
they
again
knows
about
quantization
exist
and
the
build
has
been
triggered
and
that's
the
trigger
ID.
So
if
I
just
move
out
my
main
window
here,
if
I
refresh
this
screen,
we
can
see
that
organization
office
hours
has
been
as
a
build
has
been
created
and
that
build
is
now
triggered.
I
give
it
a
few
seconds,
it's
cloning,
the
repository
and
it
will
start
doing
a
JX.
E
This
works
with
more
than
one
cluster.
We've
still
got
the
prowess
off
problem
to
solve,
so
that
I
wouldn't
suggest
using
this
for
more
than
cast
at
the
moment,
and
but
because
it's
because
it's
actually
looking
at
the
github
repo
that
contains
the
organization
config
if
you'd
make
a
pull
request
off
the
merger
committing
to
that
repo
to
ultra
great
new,
builds
and
and
effectively
an
upgrade.
G
E
C
So
this
solves
the
problem
of
currently
when
we
first
created
the
agencia
life,
the
wizards
and
everything
which
is
great,
but
to
kick
the
tires
creating
the
custer,
but
when
in
any
enterprise
organization
or
any
anybody
that's
going
to
be
using
in
the
team
for
real
kind
of
creating
that
configuration,
have
it
stored
locally,
it's
just
not
ideal.
So
having
all
of
this
actually
manage
full
get
ops
for
the
dev
environments
as
well
and
for
your
clusters
is,
is
practicing
what
we
preach.
So
this
is.
C
E
Gonna
take
about
20
minutes,
unfortunately,
and
actually
there
is
a.
There
is
a
slight
bug
at
the
moment
in
in
the
checks
install
afterwards
there's
this
one.
We
were
looking
at
the
other
day,
James
to
do
with
the
git
or
server
it's
this
drain.
Just
like
the
second
time
around
you
get
like
a
partially
complete
think
so.
I
have
a
poor
request
in
that
should
fix
that,
but
I
just
have
enough
time
to
get
it
merged
and
test
it
fully.
D
E
E
G
G
It's
not
quite
ready
yet,
but
I've
almost
got
that
Jenkins
extra
phone
provider
yeah
one
of
the
parameters
is
the
version
under
the
covers-
is
kind
of
doing
a
Jake's
installed
with
the
versions
on
I'm
hoping
like
once.
This
is
kind
of
working
with
the
prowl
and
everything
I'm
hoping
we
could
try
out
the
terraform
provider
for
JX
and
do
things
like
defined
environments
in
terraform
defined
the
version
of
jxe
wish
to
use
and
then
do
upgrades
of
jenkees
X
via
terraform
yeah.
E
G
Yeah
one
thing
that
we
that
was
always
on
the
road
not
provoked
a
but
that
we'd
never
got
around
to
build
a
thing,
but
we're
almost
at
the
stage
with
whether
we
really
need
it.
So
you
might
end
up
building
something
is
how
can
anybody
subscribe
to
be
like
right
now
we
push,
but
we
want
people
to
subscribe
to
pol
updates,
there's
various
different
things
we
could
do
like
the
people.
People
could
pull
or
something
like
that
or
people
could
register.
G
Please
pull
request
me
and
here's
a
github
organization
or
whatever
we
just
need
to
figure
out.
What's
the
right
way
of
doing
the
pub
sub
kind
of
thing
it
doesn't
have
to
be
super
time
critical.
You
know
you
could
make
sure
that
every
day
we
run
update
but
to
push
changes
to
everybody's
and
things.
But
if
it's
like
5
million
people
want
to
generate
pull
requests
on
their
own
organizations,
it
might
be
benefit
them
to
pull
rather
than
those
push.
G
But
some
kind
of
way
like
right
now,
already
update
both
can
pull.
You
can
say
things
like
pull
any
new
versions.
You
can
find
for
my
stuff,
and
you
could
do
that.
You
know
every
day
or
every
hour,
so
there's
a
pull
option,
but
it's
it's
not
quite
awesome.
Yet
I
mean
what
would
be
really
really.
Nice
is
if
we
could,
if
you
could
add
into
this
CI
job,
an
automatic
pull
of
versions
of
Jenkins,
X
I.
Don't
think
that
would
be
part
of
the
code,
ship,
CI
or
something
like
that,
but
I
mean.
G
Well,
one
day
we
might
want
to
place
it,
you
can
go
so
just
a
quick
of
bit
of
dirty
laundry
for
a
second
so
waiting
up
there,
but
inside
Jenkins
X
to
push
version
changes
or
anything
like
a
very
major
library
it.
The
Jake
is
X
binary.
Whenever
we
release
the
binary,
we
do
a
pull
request
on
docket
images
to
use
the
new
binary
version,
all
this
kind
of
stuff,
so
we're
using
loads
of
up
there.
But
what
are
the
slight
issues,
though,
is
up
there,
but
right
now
polls.
G
So
whenever
you're
pushing
doing
pull
requests
he's
polling
to
city
are
the
pull
requests
merge,
so
it
can
kind
of
complete
the
build
once
we're
using
prowlin.
We've
got
that
kind
of
sorted
it'd
be
kind
of
nice
to
stop
update
pop
up
the
polling
is
right.
Now
we
keep
running
out
of
github
API
tokens,
even
though
we're
off
that
decade,
but
you
get
5,000
an
hour
a
week.
G
We
burn
through
those
really
really
create
things
up
dip
off,
but
I
think
we
almost
need
to
reimagine
update
inside
a
prow
kind
of
world
yeah,
because
I'll
be
one
of
the
main
things
the
only
real
things
update
what's
doing
like
okay.
So
if
we're
updating,
say
I'll
build
a
base,
they
build
a
base
Tucker,
it
means
once
that's
released.
G
We
have
to
do
pull
requests
on
like
ten
git
repos,
but
we
want
to
fail
the
release
of
build
a
base
if
any
of
those
pull
requests
fail
to
give
that
feedback
to
the
team
that
build
a
base
is
never
broken
or
build
a
base.
Broad
something
all
we
really
want
to
do
is
two
things:
Auto
merge
all
those
pull
requests
and
deal
with
most
conflicts,
which
prowl
can
kind
of
do
all
that,
and
then,
when
the
merge
is
completed
trigger
something
so
that
we
can
know,
do
we
mark
this?
G
The
build-a-bear
Solis
is
completely
don't
know
if
you
can
get
all
that
working,
then
just
the
web
hooks
coming
from
github
will
be
enough
to
trigger
all
of
this
flow,
and
we
can
stop
all
this
poling
kind
of
crap
and
everything
will
be
faster
and
everything
could
be
kind
of
parallel
and
comparing
everything
and
then
we
could
do
better
feedback.
So
you
can
kind
of
do
things
like
you
know,
raise
an
issue
if
a
build
a
base
call
request
failed,
you
know
failed
to
merger
whatever,
so
we
can
get
much
better
feedback.
I
mean
feedback.
G
And
I
break
a
downstream
repo.
We
should
both
hear
about
it.
You
know
the
upstream
team
and
the
downstream
to
ancient
should
get
feedback,
so
yeah
I
think
soon
we
might
have
to
do
significant
engineering
on
the
river,
possibly
rewriting
it
in
go,
possibly
so
it's
easier
to
use
in
prow
and
inside
pipelines
and
everything
like
this
right
now,
it's
right
now.
Okay,
here's
another
bit
of
dirty
laundry.
We
install
the
JVM
in
all
of
our
builder
images.
Just
so
we
can
read
update
but
I
brought
the
pipelines.
So
we
have
to
be
writing.
G
D
G
What
I'd
really
love
to
see
so
imagine
the
builder
based
example:
we're
doing
a
release
to
build
a
base
and
we're
doing
pull
requests
and
see
if
I've
get
repos.
We
kind
of
want
to
see
a
visual
check
box
of.
What's
this,
what
are
all
the
PRS
that's
being
generated
like
a
little
table
on
a
like
on
a
pull
request
or
a
github
pages
name
or
an
issue.
G
G
H
D
Crazy
stuff,
if
you
connect
my
people
repose
in
prowl,
you
can
aggregate
events
from
different
rappers
and
they
kind
of
have
a
overview
over
all
key
drivers.
Like
you,
you
send
some
PR
in
one
rep
or
let's
say,
and
this
has
dependencies
to
other
repo
see
if
you
break
them,
you
can
go
and
see.
Okay,
you
just
look
to
the
events
and
what
happened
if
it.
If
we
collect
all
the
events
and
then
we
just
put
them
either
in
elasticsearch
or
somewhere
and
then
just
have
a
dashboard,
maybe
a
little
could
be
amazing.
Yeah
yeah.
C
I
Yes,
hey
yes,
so
I
am
trying
to
set
up
Jenkins
X
to
configure
with
Maya
my
enterprise
get
I.
Have
the
I
created
a
Jenkins
X
git
server
on
my
enterprise
get
and
I
also
created
a
the
token
for
that
enterprise.
But
when
I
run
GX
install
specifying
that
Enterprise
get
provider
URL,
it
still
tries
to
create
the
spring
environments.
On
a
personal
I
mean
a
public
github,
so
github
calm
with
my
personal
username.
Do
you
know
why
this
is.
G
I
G
H
C
Even
though
we're
using
github
Enterprise
for
our
BDD
test,
the
environments
are
actually
on
github
right,
so
I'm,
guessing
this
exact,
the
same
issue
that
you've
got
here
when
we
created
it,
it's
actually
not
using
the
correct
get
provider
great.
It's
falling
back
to
the
defaults.
That
sounds
like
a
book
there,
yeah
okay,.
E
G
D
D
G
D
G
Why
the
beginning
I
think
so
if
we
just
tried
debugging
that
there's
a
doc
on
how
to
debug
it,
if
you
can,
if
you
can
bear
the
setup
of
a
go
on
your
laptop
okay,
which
is
fairly
sped
us,
it's
pretty
easy
to
debug,
and
then
we
could
just
will
show
you
where
the
code
is.
You
can
just
put
a
great
point.
We
can
you
see
what
the
codes
doing
wrong
and
all
one
of
us
could
duplicate
when
we
get
a
chance.
G
C
G
There
was
the
be
go
stuff,
that's
pretty
sweet,
I'm
I
think
that's
big
in
in,
like
I
was
just
gonna
show.
I
was
literally
just
gonna,
show
in
I.
Don't
know
if
anyone's
like
played
around
with
it
or
anything,
but
I
was
amazed
that
it
literally
it
worked.
It
works
out
Jax's
depths
first
time
without
any
kind
of
happy
which
I
thought
was
pretty.
G
Well,
you
know
if
we
just
have
sort
of
versioned
module
imports
and
we
didn't
need
to
actually
kind
of
resolve
inversions
of
something
to
one
thing
somewhere,
you
know
in
your
vendor
directory
or
whatever.
Then
this
will
make
everyone's
lives
easier
and
Vigo
is,
is
basically
their
sort
of
release
of
that
prior
to
it
getting
sort
of
released?
Actually
in,
though
itself,
so,
if
you're
interested
in
sort
of
taking
it
for
a
spin,
you
can
you
know
you
can
clone
or
go
get
Vigo,
and
then
you
can
actually
run.
G
You
know
go
as
if
it
was
using
modules
by
just
using
the
ego
command
instead
of
go
and
so
far
I
mean
I've
only
been
messing
with
it.
The
Jenkins
X
or
you
know,
sort
of
I
haven't
really
spent
much
time
with
it.
But
initial
sort
of
signs
are
that
it's
pretty
awesome,
so
I
just
got
like
a
quick
thing
that
I
can
like
acting
show.
If.
G
G
Okay,
so
basically,
this
is
just
master
branch
of
I
think
his
ex
as
it
counts
down
to
the
vendor
directory,
so
all
I'm
gonna
do
is
just
would
remove
vendor
and
I
need
to
quickly
change
this
line,
so
basically
in
the
night
file
of
the
go
around
just
reach
out
to
this,
and
basically
all
these
go
is
just
means
inside
all
of
the
mic
scripts.
It's
going
to
use
Vigo
instead
of
go
and
if
it
doesn't
exist
already,
it's
going
to
go
and
get
it
for
you
and.
G
D
G
G
And
we're
now
be
going,
so
it
is
pretty
smart.
It
sort
of
figures
out
basically,
if
you're
using
some
other
sort
of
vending
tool.
Obviously
the
there's
a
go
package
got
Tomalin
and
I've
got
lock-in
in
this
in
this
project,
so
it's
kind
of
using
it
from
there
and
using
the
existing
versions
that
we've
we've
got
in
yeah
right
yeah,
but
it's
basically
it's
doing
like
her.
It's
kind
of
like
a
slightly
different.
It's
a
slightly
different
approach
to
like
sort
of
package
sort
of
version
resolution.
G
It
seems
in
that
it
is
basically
take
the
the
least
up-to-date
version,
the
wall
that
will
result
in
success.
So
you
can
see
now
it's
that's
it.
Basically,
that's
as
if
you'd
never
run
it
before.
It's
downloaded
all
of
the
things
and
it's
now
running
the
tests.
So
it's
we
now
we
now
fee
going
and
we
go
modulating
depending
and
if
you
look
at
what
it's
actually
done,
it's
just
create
these
two.
G
To
files
on
in
the
project,
Godot,
mod
and
goats,
and
basically
the
idea
is-
is
that
more
packages,
libraries
projects
that
basically
switch
over
to
this
you're,
basically
going
to
be
able
to
you're
you're
sort
of
responsible
only
for
resolving
your
dependencies
in
such
a
project.
So
you
know,
if
you're
feels
kind
of
downstream
of
that
and
you're
not
going
to
get
all
of
these
clashes
where
you're
trying
to
sort
of
combine
two
subsets
of
n
during
and
those
different
versions,
and
it's
just
a
nightmare
because
you
have
to
build
it.
G
So
pretty
standard
stuff,
just
a
big
old
list,
and
if
you
do
read
a
list,
you
can
just
tell
you
what
you've
actually
got.
So
you
can
see
that
it's
now
recognizing
that.
Basically,
this
project
is
Jenkins,
X,
/
JX
and
you
know
anyone
importing
anyone
importing
us
from
from
anywhere
is
basically
going
to
have
an
easy
bride
in
terms
of
who's
opening
the
dependencies
with
anything
else
they
do
and
so
yeah.
G
That
was
it
basically
just
as
like
a
really
quick
little
thing,
but
it
works
really
well,
and
it's
gives
me
a
step
in
the
right
direction.
Awesome.
G
C
There
yeah
I
saw
I
saw
in
hopes
it
was
so
yes,
I
saw
some
all
right.
Well,
we
just
passed
just
gone
five
o'clock,
so
I
think
I
was
pretty
good.
Our
thanks.
Everybody
guys
cracking
job
on
the
air
on
your
demo
and
I
was
good,
involving
fairphone,
so
yeah
I
guess
until
next
time,
thanks
seriously
to
the.