►
From YouTube: CDF SIG Interoperability Meeting 2020-04-02
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
A
B
C
D
C
A
A
E
A
A
All
right,
well,
I
think
we
have
quorum,
let's
go
ahead
and
start
yes,
I
should
introduce
myself
I'm
not-
and
this
is
my
first
time
facilitating
this
meeting.
So
please
bear
with
me-
and
let
me
know
if
I've
missed
out
on
anything
or
got
something
wrong,
I'm
happy
to
take
feedback
on
that.
I'm
Eric
I
work,
a
puppet
and
you
know
once
again
see.
We've
got
a
few
things
on
the
agenda.
A
F
Know
I
think
I
have
an
action
item.
If
you
go
to
the
previous
meaning
is
I.
Think
Raman
mentioned
that
we
should
reach
out
to
matrix
armory
folks
because
they
are
doing
good
work
with
vinegar
and
so
on
and
I
reached
out
to
Isaac
Mosca
writing
for
memory,
but
I
own
heard
from
him
yet
and
I
will
reach
out
to
and
the
glower
from
Netflix
and
try
to
get
some
representation
from
spinnaker
to
this
group.
So
they
contribute
to
the
work
we
are
doing
here.
Hopefully
that
was
the
only
action
item
from
last
week.
A
Are
there
other
avenues
that
we
should
try?
I
mean
if
it
feels
like
that
I
agree
that
that's
an
important
thing
to
do.
It
seems
like
we
should
be
able
to
get
in
contact
with
somebody
over
there.
I.
F
A
E
Actually,
just
as
a
general
thing,
it
just
occurred
to
me
that
we
could
do
a
shout
out
at
the
the
next
talk
meeting.
I
know:
there's
some
screw
driver
CD
folks
in
there
and
other
folks
from
other
communities
pop
in
and
out.
So
that
might
be
a
good
place
but
yeah,
if
any
any
other
forums.
We
think
we
should
be
going
to
to
do
some
outreach
if
folks
have
ideas
good
to
hear
them.
E
F
D
A
A
A
D
E
I'll
give
a
brief
update
so
for
folks
who
haven't
seen
this
it's
starting
to
put
together
a
kind
of
a
road
map,
so
a
basic.
Now
next
later
so
people
can
sort
of
say
where
they
want
to
work
on.
We
can
highlight
efforts
that
we
can
coalesce
around
and
I
had
some
fat.
He
went
through
and
made
some
contributions,
so
that
was
pretty
great
I.
Have
some
additional
work
I'll
be
doing
on
it
once
I
figure
out
how
to
cope
with
my
kids
at
home,
but
yeah?
E
So
ongoing
action
for
everyone
is
to
have
a
look
at
this
document.
Give
some
comments
put
in
ideas
of
things.
You'd
be
interested
in
working
in
or
things
new
things
you
want
to
suggest
and
I'll
have
another
pass
before
the
next
meeting
start
to
work
out
how
to
make
it
prettier
and
have
a
way
to
share
it
on
on
the
website.
Oh
and
github.
Somehow,
so
we
can
then
use
it
to
go
talk
about
and
just
get
more
people
involved
with
the
activities.
E
E
E
So
if
you
go
ahead
and
click
on
that,
so
there's
a
lot
of
activity
happening
on
the
outreach
part
of
the
CDF
and
one
of
the
conversations
there's
a
project.
Outreach
subcommittee
is
that
we
want
to
drive
more
conversations
around
specific
monthly
themes,
and
so
one
of
the
main
vessels
for
this
will
be
the
newsletter
and
so
April's
theme
for
this
month,
and
this
is
the
first
time
we're
trying
it
out
is
going
to
be
interoperability.
E
So,
in
terms
of
new
letter
were
looking
to
curate
about
for
articles
about
interoperability
and
actually
I
was
going
to
I
saw
both
yours
Eric
article
and
undress
your
article,
so
I
have
it
on
my
list
to
have
a
look
to
read
through
those,
but
if
you'd
be
interested
either
to
have
those
republished
or
do
a
slight
different.
Take
on
that
which
fits
with
this
theme.
I'd
love
to
have
like
Jackie
reach
out
to
you
and
discuss
how
that
might
work.
A
Sure,
absolutely
from
my
perspective,
I'll
include
I
have
andreas
in
another
window.
So
I
can
add
that
link
in
here
as
well
as
well-
and
you
know,
mine
was
I
had
one
that
was
like
kind
of
overview
of
it's
mostly
tacked
on
focus.
But
I
talked
a
lot
about
the
other
projects
that
make
use
of
tacked
on
and
that
and
some
what
new
developments
like
triggers
and
the
dashboard
and
pipeline
conditionals
and
stuff
that
people
might
not
know
about
yet
yeah.
E
So
I
think
for
that
one
I,
actually
the
talking
about
like
how
that's
related
to
the
vocabulary
and
focusing
a
bit
on
that
would
be
key
and
then
having
some
articles
I
know,
we've
got
some
other
folks
who
can
I
lined
up
to
write.
You
know
like
how
Jenkins
works
at
spinnaker,
how
attacked
on
works
with
Jenkins
X
and
things
like
that
so
yeah.
Let
me
connect
up
with
Jackie
and
with
you,
and
we
can
drive
that
further
to
see
how
to
you,
reuse
those
articles
and
also
open
it
up
to
anybody
else
here.
E
E
E
Opps
you're
gonna,
throw
that
to
the
ml
ops
sig
to
do
a
call
for
articles,
but
also,
if
you
know
anybody
or
you
want
to
write
stuff
and
in
June
we're
looking
for
articles
about
security
bit
kind
of
wide
open,
but
it
will
be
probably
related
to
the
projects
and
sort
of
emerging
practices
and
kind
of
very
current.
Looking
for
kind
of
current
thinking
that
drives
industry
forward.
E
E
A
Yeah
I
guess
so
maybe
we
can
just
chat
on
on
CDF
slack
or
something
like
that
to
get
more
more
details
and
and
that
that
that
timeframe
should
be
fine
from
from
my
perspective,
is
it
written?
I
have
lots
of
time
to
write
these
days,
which
is
why
I
wrote
it.
That
was
it
ten
thousand
words
about
Tech
Talk.
A
B
Go
ahead
and
stop
sharing
too
so
I
actually
I
forgot
about
this
until
this
morning.
So
all
good
but
I've
got
sir
I've
got
some
some
kind
of
slides
just
to
talk
to
a
little
bit,
not
gonna,
go
to
too
much
detail
but
and
put
a
little
demo
as
well.
If
that's
interests,
folks,
okay,
sure,
yeah,
all
right,
cool
I
guess
they
seem
to
be
quite
a
bit
of
time.
So
it's
no
I'm,
never
gonna
fill
the
whole
amount
of
time.
B
B
B
B
That's
including
the
t's,
is
the
check-ins,
X's
and
sometimes
I
think
there's
a
bit
of
confusion.
We've
always
had
that
where
we
have
the
name
of
Jenkins
in
the
Jenkins
X
name
and
the
house
called
confusion
over
the
time.
But
really
am
we
just
really
wanted
to
highlight
the
values
that
we
have
from
the
project
of
Jenkins?
We
really
wanted
to
have
it
fresh.
Look
at
this,
what
that
means
for
developers,
and
so
we
can
have
a
solution
within
the
cloud
within
kubernetes.
B
B
But
the
idea
is,
we
actually
install
a
number
of
different
micro
services
as
part
of
Jenkins
X
into
a
Cuban.
This
is
cluster
and
we
use
we
can't
provide
a
lot
of
automation
and
to
provide
my
solutions
so
that
developers
can
very,
very
quickly
get
up
and
running
and
building
and
developing
software
on
the
cloud
mentions
developers.
That's
really
the
key
word
for
us.
We
really
want
to
try
and
take
the
heavy
lifting
for
developers,
massive
massive
fans
of
communities
and
various
different
technologies
or
open
source
projects,
but
it's
a
pretty
it's
a
minefield
right.
B
So
what
we
want
to
do
is
within
Jenkins
X's
triumph.
It's
quite
opinionated
using
recommended
well
used
bad
practices,
also
open
source
projects
to
can't
tie
them
all
together
to
provide
an
experience
that
developers
are
really
familiar
with,
but
it
also
helps
them
get
ups
from
running
very,
very
quickly
to
start
adding
value
themselves
very
very
quickly.
So
we
also
have
the
experience,
the
developer
experiences
and
this
really
kind
of
key
to
the
Jenkins
X.
B
The
James
X,
actually
is
CLI
based.
So
we
have
a
CLI
that
we
call
JX
and
that's
what
meanwe
touchy
interact
with
the
an
installation
of
Jenkins
X
and
we
have
a
number
of
different
commands:
there's
a
ton
of
commands
there,
but
it
helps
you
not
only
install
and
set
up,
but
also
then
interact
with
the
installation
as
well.
If
you
want
to
trigger
builds
well,
if
you
want
to
create
a
quick
start
or
if
you
want
to
look
at
build
locks
as
well
what
different
applications
in
different
environment.
B
We
really
are
heavily
influenced
by
the
efforts
around
the
state
to
DevOps
reports
and,
more
recently,
the
accelerate
book.
So
we're
not
trying
to
say,
we've
tried
to
implement
the
book.
It's
not
really
that
at
all.
It's
just
we're
very
aware
of
the
hard
work
that
people
have
been
doing
around
the
data
scientists
around
gathering
a
lot
of
information
about
how
we
can
deliver
how
successful
teams
build
better
software.
So,
where
possible,
we've
tried
to
make
those
defaults.
I've
got
a
couple
there.
B
Ok,
so
we
didn't
want
to
do
this
just
build
out
Jenkins.
We
wanted
to
integrate
as
many
awesome
open-source
projects
as
we
could
has
that
made
sense
to
provide
a
solution
for
developers
only
mine.
You
know
we
know
that
when
you
people
have
come
to
Kuban
at
ease,
they
may
not
know
about
Tecton.
They
may
not
know
about
any
other
audio,
CD
or
various
other
projects.
B
We
wanted
to
try
and
find
a
good
way,
a
native
way
that
we
can
actually
we
can
provide
this
experience,
but
behind
the
scenes,
potentially
it's
using
good
practices
and
using
the
cloud.
Well
so
just
to
say
there
is
no
Jenkins
actually
in
Jenkins,
X
I.
Think
I'll
mention
that
before
this
is
a
Java,
we
really
can
extend
cubing
the
season,
the
ways
it's
expected
to
be
extended
using
controllers
and
formulas
operators,
and
there
are
some
things,
but
open-source
projects
work
make
sense
as
well.
B
So
we
when
Tecton
came
along,
we
were
jump
straight
on
that
because
they
not
only
they're
awesome
people,
but
it's
an
awesome
community
and
this
project
itself
is
really
fantastic.
It's
really
what
we
see
is
core
to
being
actually
providing
good
sort
of
project
in
Jenkins
X.
You
know
working
well
with
these
other
open-source
projects,
they're
designed
specifically
to
do
this
job.
B
What
is
it
hazy?
So,
in
my
eyes,
a
bit
friendly
there.
We
also
use
up
the
projects
like
helm
for
packaging
applications.
A
developer
may
not
know
how
to
package
an
application
and
run
it
on
communities.
We
want
to
automate
the
setup
of
all
of
this.
What
makes
the
creation
of
helm
templates,
but
not
necessarily
FRA,
get
away
from
them,
because,
as
developers
get
more
familiar
with
working
in
these
new
technologies,
they
won't
do
more
as
well,
so
we
actually
set
them
up
with
everything
like
scaffolding.
B
It
takes
time
to
understand
it,
takes
time
to
in
install
and
work
out
what
the
configuration
is
you
need
when
we
I've
gone
with
Jenkins
X's,
we
kind
of
automate
this
as
a
developer.
If
you
want
to
automate
to
TLS
for
your
application,
it's
it
just
happens,
it's
a
flag
that
you
enable,
and
then
you
get
this
things
like
custom
domains.
It's
good
very!
These
are
kind
of
from
a
developer
point
of
view.
It's
not
bad
I,
guess
interesting,
but
you
would
expect
it
as
a
developer.
This
is
what
we're
really
trying
to
do
so.
B
External
DNS
is
a
great
integrates
with
other
cloud
providers
to
be
automatically
create
a
records
and
the
Nabal
automated
the
DNS,
so
people
will
want
their
own
custom
domains
and
TLS
as
well
for
their
applications.
So
we
make
that
super
simple
to
things.
Like
sequence
management,
we've
got
vault
here
and
wondering
whether
the
source
project
or
other
in
a
even
open
source
projects,
it
might
be
if
you
have
account
in
from
clouds
implementation
for
google
secrets
manual,
AWS
secrets
as
well.
B
Looking
at
more
the
deployment
side
of
things
once
you've
actually
have
wanted
me
to
see
ICD
and
you
gots
a
preview
environments
and
you
were
able
to
test
not
changes
before
their
most
master.
Okay.
Well,
you
have
this
automated
deployments
into
your
into
different
environments.
Well,
we
want
to
actually
even
better
capabilities.
Progressive
delivery,
for
example,
so
you
know
and
I
couldn't
find
an
icon
for
a
flagger
or
what
the
icon
is
basic.
Great
open
source
project
interacts
with
other
service
matches
that
people
again
from
a
developer's
point
of
view.
B
B
B
I
think
that's
good,
though.
Maybe
if
you
got
one
question,
that's
good
already,
so
there's
quite
a
lot
of
demos
that
are
out
there
and
the
things
that
we've
done
blogs
and
various
things
that
love
community
been
around
installing
the
setting
up
cluster
so
right
now,
I
just
wanted
to
come
jump
to
as
something
more
about
the
integrations
that
we
have
and
using
some
of
those
projects
the
that
I
saw
on
slides.
G
B
Have
other
providers
and
homegrown
one
space
just
we
are
probably
a
bit
more
reserved
in
that
saying
how
how
well
that
is
just
because
of
our
automated
testing
continue.
Building
it
but
or
support
is
growing
every
every
week
every
month,
so
I've
got
a
Google
if
I
do
alias,
keep
CTR
Casey
get
nodes,
so
I've
got
a
cluster.
B
Well,
yes,
okay,
it's
just
a
small
cluster,
so
let
me
have
I've
got
number
namespaces.
Actually
let
me
just
do
one
thing:
either
straight:
go
straight
to
JX,
o
JX
get
the
violence
now
out
of
the
box
yeah,
but
that
default
installation
would
come
with
three
environments.
A
dev
environment
staging
in
the
production,
Dave
is
where
we
did
install,
though
the
tooling.
So
this
would
be
tectonic,
for
example,
see
what
we've
got
in
store
here.
B
So
yeah
we've
got
text
on
controller.
We've
also
got
Nexus
anybody
doing
Java
development.
They
want
to
be
able
to
cache
job
at
the
pendant
sees,
for
example,
or
shared
built
artifacts
with
their
team.
We've
also
got
SCM
handler
as
well,
so
you
know
triggering
build
from
web
hooks.
For
example,
let's
skip
over
that
one,
and
just
even
though
a
couple
of
controllers
we've
got
chart
museum
they're
at
moment
as
well:
external
DNS,
I'm
having
installed
sip
I
did
set
manager,
but
you
just
get
to
see
they're
out
of
the
box.
B
We
want
to
kind
of
install
everything
and
we've
wired
everything
absolutely
works
nicely
together.
So
back
to
the
environments,
that's
the
dev
environment.
We
also
have
a
staging
on
a
production
environment.
Now
currently
this
is
these
are
just
namespaces
in
that
in
this
cluster,
we're
actually
working
on
having
remote
environments
at
the
moment.
B
So
that's
going
to
be
next
big
thing
that
we've
been
doing
so
you
could
actually
have
your
dev
cluster
or
your
build
tools
be
more
clustered,
but
you,
the
pointman
target,
your
environment
is
actually
in
a
different
cluster,
even
a
different
cloud
provider
as
well.
So
but
yes,
they
say
this
is
all
you
running.
We
have
we
practiced
something
called
git
hops,
so
the
idea
is
any
change
that
we
do
to
an
environment
actually
goes
via
a
pull.
B
B
That's
our
very
basic
Quick
Start.
Then
we've
got
four
go
down.
So
let
me
take
you
back
and
show
you
what
a
little
bit
more
about
that
I
created
that
quick
start
using
JX
create
quick
starts
before
and
it
took
basically
I
created
the
repo
for
me
in
my
github
accounts.
It's
going
to
have
a
look.
Yeah
created
this
repo
yeah
other
than
the
very
basic
QuickStart,
but
you
could
import
your
own.
Go
projects,
no
DES
Java
projects.
B
The
idea
is,
if
you
have
it,
we
have
a
base
project
and
then
we
actually
enrich
that
with
Helen
charts,
doctor
file
and
the
pipeline
as
well.
So
this
really
so
you've
got
everything.
That's
set
up.
You've
also
got
web
hooks
that
are
registered
automatically
as
well.
So
when
you
change
the
you
know,
make
to
that
application
then
starts
affecting
triggering
builds
for
any
new
pipelines.
B
Kids
check
out
working
progress
took
a
new
branch.
Sorry
about
the
noise
we've
got
a
pipeline
now
mentioned
about
Tecton
and
what
we're
using
Tecton
under
the
hood.
We
actually
have
for
Jenkins
developers,
traditional
Jenkins
developers.
They
were
using
a
DSL.
It
was
actually
probably
a
bit
higher
level.
So
what
we
did
with
Jenkins
X's
we
wanted
to
make.
We
were
using
a
DSL
that
is
a
bit
more
familiar
further
Jenkins
users.
The
idea
is
that
we
can
then
gently
generate
the
Tecton
resources
for
the
Teflon
controller
to
rent
to
use.
B
So
you
actually
inherit
from
a
build
pack
on
this
one
you
don't
have
to
you
could
remove
that,
but
bill
Pakistan
is
a
shared
group
of
only
shared
group
of
pipelines.
They've
had
100
micro
services
that
all
did
the
exact
same
thing
rather
than
duplicating
the
pipeline
in
each
everyone.
You
can
just
inherit
it
from
that
single
bill
pack.
So
it's
used.
B
B
So
what
we
can
do
is
we
can
save
this.
We
can
actually
generate
what
that
pipeline
might
look
like
so
sin
always
synthetics.
We
have
a
jet
steps,
syntax
effective,
which
literally
will
go
and
combine
the
changes
that
I've
added
with
the
bill
pack
that
we've
got
there
ensure
the
effective
pipeline
for
this
up
flat
application
for
that
change.
B
Okay,
so
you
can
see
here,
this
is
the
actual
pipeline
that
is
used.
You
can
see
here
here.
We've
got
some
volume
variables.
We've
got
a
calico
step
to
build
the
application
Christie's
up
to
GCR.
We've
also
got
promoting
as
well
and
building
packaging,
the
helmet
charts
as
well.
So
this
is
all
the
actual
steps
that's
needed
to
be
able
to
build
package
rather
than
promote
that
application
to
a
stage
and
environment.
That's
their
big
game.
It's
kinda!
It's
still
in
this,
this
power
level.
Do
yourself
that
you
can
see
here.
B
B
So
I
shouldn't
see
yeah
I
got
a
change
here,
create
a
pull
request.
When
what
creates
this
Quick
Start?
You
can
create
your
quick,
stop.
You
2jx
import
to
import
an
existing
one.
You
get
the
automated
web
books
that
I
mentioned
before
and
you
can
see
I've
created
with
pull
request.
We've
got
the
old
icon
and
what
we
can
see
here.
We've
got
a
notification
because
we've
got
to
chat
ops,
crown-like
Fenway's
worked
on
every
single
community,
repo
and
most
project.
B
This
is
ecosystem
news
protocol
prowl
we've
got
something
not
probably
usual
heavily
prowl
and
it's
more
of
a
cut
down
version
of
proud
something
called
lighthouse.
So
this
is
actually
commented
back
on
the
project
on
the
repo.
It
says
it's
a
small
change
and
it's
now
building.
So
let's
go
ahead
and
GX
get
build.
B
B
So
what
it
does
it's
fit
to
start
with,
and
this
is
a
bit
more
lower
level
than
we'd
ever
do
normally
it
would
it
processes
the
we
have
some
kind
of
meta
pipeline,
so
it
takes
that
higher
level.
There's
the
pipeline
that
we've
got
and
then
processes
generates
all
of
the
Tecton
resources.
So
here
we
can
see,
we've
created
the
task
pipeline
pipeline
man
and
pylon
resources
as
well,
and
that's
now
being
processed
by
the
Tecton
controller.
So
if
we
wanted
to,
we
could
go
kacy,
get.
B
B
B
And
you
should
have
probably
had
hello,
and
this
is
you
can
see
why
we've
extended
our
build
pack
that
we
had
before
we've
added
in
that
echo
commands
and
that
that's
that
run
before
any
other
steps
within
our
build
pack
again,
you
don't
have
to
use
a
build
pack.
In
fact,
you
know
what
projects
do.
Here's
an
example
of
some
of
ours:
we've
got
using
the
Jenkins
xorg
or
the
tanks
xlab's
org.
B
B
Okay,
so
that
ran
you
can
see
the
kind
of
code
built
there.
It's
pushing
a
snapshot
image
up
to
GCR.
It's
then
actually
because
of
DNS
we'll
see
if
this
works,
because
it's
using
external
DNS,
it's
actually
Excel
DNS-
is
recognized
that
we've
created
a
brand
new
namespace
deployed
that
change
for
that
preview
into
that
namespace.
We
call
it
preview
environment
and
now
the
pipeline
is
waiting
for
to
be
able
to
access
that
application.
That's
in
RPE
environment,
but
because
we're
using
DNS
it
just
takes
a
little
while
for
dns
to
propagate
around.
B
So
external
DNS
is
going
off
to
Google,
Google's
DNS
and
saying
here's
a
brand
new
a
record
now
and
create
this,
and
so
that
we
can
actually
then
access
our
application.
So
at
some
point,
hopefully
you
should
well
that
might
that
can
take
a
little
while.
So,
let's
see
if
we've
got
it
quite
yeah
there.
Yet
we'll
come
back
to
this,
but
what
I'll
actually
do
is
you'll
make
a
comment
onto
the
pull
request.
You'll
see
a
movie
yet
to
go
ahead
and
access
that
I
think
probably
I
mean
that's.
B
I
mean
I've
talked
quite
a
bit
there
boss.
Whilst
that's
actually
happening
I'm
wondering
it's
a
super
super
high
level
and
then
dropping
into
some
more
of
the
interactions
we
have.
The
projects
was
that
kind
of
useful
I
didn't
know
what
level
to
pitch
this
and
how
you,
how
far
to
go
so
I
mean
I,
guess
yeah
I,.
C
Actually
it
is,
it
is
very
useful
on
a
few
different
levels:
I
just
have
some
I
guess
questions
and
some
concerns.
As
someone
you
know,
working
at
a
company,
that's
heavily
invested.
First
of
all,
completely
agree.
You
guys
should
have
called
this
something
else.
I
really
wish
mad
because
it
really
does
not
have
much
to
do
with
with
with
Jenkins
other
than
the
DSL.
B
Not
the
exact
same
the
main
developer
rounds
that
were
before
that
was
Angie,
bear
and
he's
was
heavily
involved
in
in
this
new
one,
because
it
is
not
exactly
saying
because
of
some
of
the
semantics
that
we
had.
We
were
working
with
root
exon,
and
some
of
it
was
quite
hard
to
replicate.
So
we
want
it's
as
close
as
we
could
get
it,
but
it's
not
an
exact.
B
C
The
part
that
that
is
extremely
important
to
me
as
far
as
CDF
is
the
definition
part.
The
implementation
right
now
is
Tecton,
but
I
mean
other
systems
can
come
along
and
take
the
definition
of
a
pipeline.
You
know,
meaning
the
pipeline
pipeline
run
the
and
implement
their
own
way
of
doing
it,
but
still
the
same
standardized
definition,
and
here
comes
Jenkins
X
that
is
layering
top
of
a
DSL
which
then
it
takes
and
translates
to
a
Tecton
the
Tecton.
C
Yes,
in
one
way,
it's
it
helps
to
developer
and
I
agree
with
you
completely
humiliated
myself,
and
it
helps
the
developer
to
a
DSL.
That's
one
good
thing,
but
it
also
at
the
same
time.
It's
a
double-edged
sword.
You
are
now
produced
you
you're
now
creating
a
and
a
translator
that
it
by
definition,
always
behind,
as
as
the
Tecton
DSL
morphs,
which
is
I,
mean
it
and
I've
been
I've
been
involved
with
with
Tecton
since
late
last
period.
C
It
has
changed
quite
a
bit,
I
mean
it's
it's
in
in
flux
and
it's
continued
to
be
in
flux
for
a
while.
How
are
you
guys
planning
on
keeping
up
with
the
the
latest
tech
thanh
DSL
generation,
because
I
can
already
see
them?
We
get
this
from
other
worked
on
inside
ebay
or
we
say
hey.
Are
you
compatible
with
this
version
of
you
know
XYZ
and
we're
like
no,
and
we
haven't
updated
to
that
yet,
and
this
is
something
you
got
to
run
into
all
the
time
you
can
speak
to
that
yeah.
B
B
We've
keep
true
to
Jenkins
users,
whilst
we
think
can't
go
all
the
way,
but
have
some
kind
place
where
people
are
familiar
trying
to
build
out.
We
found,
though,
that
all
the
resources
which
we
absolutely
love
from
Tecton
well
having
those
that
there's
tons
of
those
specifications,
is
absolutely
fantastic.
Exactly
what
I
think
that
CDF
should
be
doing.
But
having
that
experience
on
top
of
developers,
it
was
what
we
were
finding
it
for
ourselves
very,
very
hard.
B
So
this
is
something
that
we
wanted
to
be
able
to
help
the
Jenkins
community
not
go
a
million
miles
away
from
them,
because
we
need
to
have
one
mind
on
them
as
well,
but
also
have
something
that
we
can
embrace
going
forward.
I
mean
it's
not
a
out-of-the-box
answer,
but
it's
something
I
guess
to
try
and
explain
more
than
the
weeks
and
the
reasons
we
believe.
C
A
C
E
E
C
Of
kohsuke,
those
guys
are
great
I've
watched
them
conferences.
You
guys
are
doing
awesome,
work,
I,
just
I'm,
very
much
about
interoperability
as
well,
and
then
this
this
is
obviously
a
grand
scheme
of
interoperability.
You
guys
are
hooking
in
so
many
other
things,
excellent
for
or
helm
by
the
way
which
version
of
helm
is
it
3
or
2.
That's
a
very.
B
Good
question
so,
in
the
we
have
very
very
quickly,
we
have
something
that
starts
this
year.
We
initiated
something
called
Jenkins
exit
labs
and
because
one
of
the
things
we
want
to
do
is
keep
Jenkins
X
on
the
stable
bathroom,
keeping
people
you're,
improving
and
then
rolling
out
more
support,
different
cloud
providers
different
SCM
providers,
but
we
also
needed
a
place
where
we
can
actually
embrace
these
new
technologies,
newer
versions.
So
in
labs
we've
been
working
on
and
some
experiments
around
the
town
3,
which
is
awesome.
B
We
absolutely
love
it,
but
they
said
made
a
change
right
away:
the
move
from
town
to
town
3.
It
has
a
big
impact,
so
we've
got
also.
We've
got
another
from
the
other
side,
looking
about
our
users
of
Jenkins
X
and
how
we
actually
move
those
users
and
grade
in
a
nice
way.
So
it's
not
an
easy
problem
to
solve,
but
it's.
B
B
C
A
C
Very
much
so
and
I'm
I'm
a
and
I'm,
not
sure
about
that
yet,
but
I
may
have
to
disappoint
you
guys,
there's
just
that
that
demo
and
and
presentation
may
not
happen
I'm
being
hit
with
so
many
other
requests
right
now
that
having
to
do
with
the
fact
that
we're
all
working
from
home
and
and
we've
we've
lost
some
personnel
so
I'm
having
to
support
other
things
right
now,
so
I
may
not
be
able
to
go
forward
with
that.
I
may
not
have
it
ready
in
time.
So
what
I'll?
A
A
It
looks
like
that's
the
the
last
one
that
is
you've
confirmed
or
is
actually
signed
up,
for,
although
Kristy
may
talk
about
detect
on
catalog
and
hub
in
the
future,
so
we
could
either
swap
those
if
she's
ready
to
talk
or
or
just
don't
not
do
demos
next
time
and
push
everything
out
about
two
weeks.
Please
please
do
let
us
know
before
the
as
far
in
advance,
as
you
can
sure
thing
and
I
guess
just
in
conclusion.