►
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
B
A
One
of
the
things
we
were
just
discussing
is
the
thinking
how
we
can
bring
the
tekton
client
plug-in
project
forward
as
a
mentoring
program,
so
hopefully
we'll
get
that
get
that
done
what
has
been
done
recently
in
the
texan
client
plug-in.
I
feel
like
there's
continuous
work
being
done
and
I
have
not
been
able
to
track
it.
C
It
uses
deck
pipeline,
which
is
a
binary,
that's
kind
of
bundled
into
the
plug-in
itself,
which
I
think
is
okay,
short-term,
I
think
longer
term.
We
probably
want
to
make
a
an
actual,
your
implementation
of
that,
but
I
think,
for
the
time
being,
I
think
we're
probably
okay.
We
we
may
well
have
issues
running
this
on
funny
architectures
like
if
someone
tries
to
run
this
on
arm,
I'm
pretty
certain
it's
not
going
to
work
at
the
moment,
but
yeah,
it's
good.
C
C
C
So
you
can
do
this
kind
of
pipeline
library
stuff,
which
is
really
nice.
I
know
james
has
added
a
proposal
to
add
this
at
that
kind
of
functionality
into
cortex
on,
so
it
could
just
be
a
temporary
thing,
and
then
you
know
in
a
few
months
time
as
that,
as
that
proposal
proposal
progresses,
it
may
be
something
we
want
to
remove
or
re-implement
something
like
that,
but
as
a
sort
of
temporary
solution,
yeah,
it's
working
really
good
james
did
a
blog
on
that
on
that
that
was
this
week.
C
C
C
So
he
was
working
out
how
to
kind
of
chop
that
bit
up
to
use
it
in
a
in
a
way.
That
is
just
it's
something,
that's
usable
for
everybody,
so
it
doesn't
have
to
deal
with
like
credentials
and
all
that
kind
of
stuff.
So
it's
I
so
when
it
comes
to
if
that
gets
into
a
a
new
tech
and
release,
and
so
I
think
all
we
will
really
need
to
do
is
remove
the
logic
on
our
side.
C
A
C
C
A
C
Way
that
it
kind
of
works
at
the
moment
is
that
we're
either
assuming
you're
running
you're
running
jenkins
on
a
kubernetes
cluster
which
has
tecon
installed,
or
you
have
in
some
way
configured
access
to
that.
So
it
knows
about
how
to
get
to
the
kubernetes
cluster.
So
all
what
we're
really
doing
is
we're
locating
the
task
or
the
pipeline
or
whatever,
whatever
the
takedown
resources
and
we're
creating
it
in
that
cluster
and
then,
if
there
are
logs
or
anything
like
that,
that
we
do
we
stream
them
back.
A
D
D
In
the
plug-in
so
but
but
I
think
this
is
really
really
good
to
start
with-
to
use
like
catalog
tasks,
probably
at
some
point
what
we
could
do
is
we
could
query
the
catalog
api
and
like
pull
tasks
from
there,
and
I
think
there
is
some
work
going
on
in
tecton
to
like
make
for
this.
This
easier,
not
exactly
with
catalog,
but
you
know
about
like
pulling
pipelines
like.
D
D
It
starts
starts
using
it
from
there.
There
is
some
work
going
on
regarding
this
upstream
yeah.
This
is
if
this,
if
this
works
out
it'll,
be
like
very
cool,
because
then,
at
that
point,
from
like
a
jungle
pipeline
like
you
could
just
say,
okay,
I
need
to
use
this
catalog
task
and
I
want
to
make
a
task
run
out.
E
D
C
C
C
D
Yeah,
I
think
at
this
point
point
like
what
we'll
have
to
do
is
we
kind
of
have
to
properly
put
like
cube
context
and
then
do
it,
but
yeah?
This
is
a.
This
is
awesome
like
this
is
this
is
really
cool
like
now
we
can
just
run
pipelines
directly
off
of
plants,
nice,
okay.
I
can't
wait
for
this
to
get
merged.
C
It's
not
there's,
there's
some
issues
with
it
and
when
it
runs
on
a
remote
agent,
it
can't
find
the
task
that
I
have
actually
extracted
in
the
local
workspace.
So
there's
some
logic
in
the
code
that
isn't
quite
working,
but
I'm
just
gonna.
I'm
just
gonna
keep
on
iterating
on
this
I've
kind
of
been
given
that
all
clear
to
get
this
request
brushed
up.
So
that's
good,
so
yeah.
This
is
what
this
is.
What
I'm
going
to
be
doing
the
rest
of
the
day
really.
D
If,
if
that
is
the
issue,
that's
happening,
do
you
think
that
when
we
run
if
we
run
one
of
these
jenkins
files
in
the
future
with
the
what
was
the
feature
that
we're
talking
about
just
before
this,
with
the
js
jx
pipeline,
effective
like
if
we
had
to
run
the
jenkins
file
pipeline
with
some
with
the
code
that
is
using
jake's
pipeline
effective
on
an
agent?
So
in
that
case
also,
we
will
need
to
have
the
binary
on
the
agent
right.
C
C
So
that
that's
what
that's
actually
what's
happening
at
the
moment,
it's
whether
or
not
we
can
copy
the
binary
and
the
right
binary
onto
the
agent
to
execute
it,
but
that
is
that
is
also
an
option.
There
is
a
jenkins
has
a
way
of
doing
that.
I
think,
there's
like
a.
I
think
it's
called
the
master
slave
callback
that
you
can
write
that
goes
off
and
does
this
stuff
that's
one
area
they
haven't
renamed
yet
actually.
C
So
I
think,
let's
start
this
in
terms
of
the
renaming
that
they're
starting
off
doing
everything
that's
kind
of
visible
in
the
ui.
But
then
there's
actually
a
lot
of
code
in
there
that
if
they
rename
that
that
is
going
to
break
an
awful
lot
of
plugins
so
like
eventually
it's
yeah.
They
possibly
need
to
like
change
the
hierarchy
of
classes,
so
that
people
can
start
including
the
right
one
and
deprecate.
That.
D
C
Certainly
so
one
of
the
pr's
that
I
tried
to
I
just
pushed
up
it
isn't
there
is
something
else
going
on
with
this
kubernetes
mock
line
that
I
need
to
have
a
look
at,
but
it
was
based
on
the
recommendation
from
jesse
to
upgrade
the
core
jenkins
version
that
we
build
plug-in
against,
because
there
is
a
different
series
of
kind
of
apis
that
you
can
call.
So
it's
like
you
get
the
perform
method,
but
without
the
workspace,
so
it
means
you
can
kind
of
run
it.
C
D
B
C
C
You
always
kind
of
overload
the
methods
with
the
new
ones
that
you
need
and,
and
so
the
old
working
versions,
even
though
they're
marked
as
deprecated
still
exist
and
they
might
delegate
on
to
the
new
methods
or
something
you
know
there
is
a
way
of
modeling
it,
but
it's
quite
strict
in
terms
of
yeah.
You
don't
really
want
to
remove.
C
C
D
C
C
D
C
It's
something
that
the
spring
framework's
been
quite
good
at,
like
they're,
very
good
at
not
they'll,
mark
things
as
deprecated
for
for
quite
a
long
time
until
they
produce
a
a
new
major
release,
and
only
only
on
those
major
releases.
Are
they
actually
removing
those?
Those
are
functions
that
are
there
and
even
then
it's
they
they.
C
D
It's
it's
either.
If
the
developer
is
or
like
the
release,
team
is
lazy
to
take
care
of
the
bugs
that
will
come
yeah.
It's
I
have
noticed
this
like
deprecation
is
always
like.
If
they
say
something
is
deprecated,
but
it's
actually
in
use
for
like
a
longer
time
like
no
one
really
goes
to
the
newer
versions.
C
A
A
A
D
What
would
be
nice
to
see
is
if
the
next
version
of
jenkins-
probably
if
is
corker
staple-
I
don't
know
how.
What
is
what
is
the
support
right
now
for
jenkins
and
caucus
the
last
time
I
remember
it
wouldn't
compile
like
I
tried
compiling
it
with
corpus
yeah.
It
was,
I
think
it
was
like
a
year
and
a
half
ago.
C
Yeah
you
have
to
is
it
I
can
never
remember
which
one's
which,
but,
like
you
have
to
like
register
for
reflection.
Don't
you
think
a
little
compiled
time
that
this
cap,
this
class
can
be
just
a
reflection
so
that
you
can
do
that?
Otherwise,
yeah
you
can't
just
do
it
for
everything
like
you
can,
with
the
normal
baby.
D
C
Yeah,
so
I
I
actually
don't
know-
and
I
don't
know
whether
it
would
be
more
of
a
marketing
release
or
an
actual
like
functional
breaking
change
release.
But
I
suppose
this
is
these
are
the
things
that
will
come
up
in
the
contributor
summit
like
so
when
when
we,
when
they
start
having
conversations
there.
C
I
know
I
know
that
we've
had
quite
a
few
sort
of
requests
from
the
community
to
release
it
as
like,
even
like
what
we
have
today
as
a
jenkins
three,
because
we're
on
around
2.289.
So
it
implies
like
289,
minor
changes
that
have
gone
on.
So
it's
it's
quite
a
long
way
from
3.0
and
they
feel
it
would
be
quite
a
good
marketing
push
if
we
release
something
as
three
but
technically
you'd
probably
want
to
use
that
three
to
remove
or
upgrade
certain
components.
C
A
Maintained:
okay,
just
just
a
quick
shout
out
for
the
contributor
summit,
it's
on
the
25th
of
june
and
is
essentially
part
of
cdcon,
which
you
should
all
sign
up
for.
That's
going
to
be
awesome
and
I
put
a
link
in
the
chat
to
the
contributor
summary
and
there
is
a
draft
agenda,
but
it
is
still
looking
quite
right,
but
that
that
does
mean
you
are
more
than
welcome
to
add
topics
that
you
would
like
to
be
added
to
the
gender
and
there
yeah.
A
A
A
D
C
Not
through
the
jenkins
interface
or
not
through
the
jenkins
controller
anyway,
I'm
assuming
you
could
always
install
catalog
items
manually
in
the
namespace
that
you
have
picked
on
running
and
then
refer
to
them.
Yes,
but
I
I
mean
it's
something
that
I
haven't
I
haven't
tried,
but
I
don't
see
any
reason
why
that
wouldn't
work.
D
We
kind
of
just
store
all
store
the
entire
catalog,
like
all
the
yaml
files,
which
is,
I
don't
know
how
creative
an
idea
it
is,
but
kind
of
just
store
them
with
the
resources
in
tecton,
client
plugin,
and
we
kind
of
you
know
sync
the
catalog
once
in
a
while,
like
once,
every
day,
probably
to
like
keep
it
updated
and
what
we
can
do
in
the
create
task
like
create
draw.
Probably
we
can
give
one
of
the
items
in
the
catalog
over
there
like
just
reference.
D
D
D
A
D
Yeah,
actually
we
can.
We
can
do
it
right
now.
If
I'm
not
wrong,
we
can.
We
can
do
it
right
now.
We
can
reference
any
electron
task.
It's
like
an
act
like
you
have
to
kind
of
give
an
ad
slash
something
and
the
location
of
the
task.
That
is
that
you
want
to
use
yeah
it's
it's
there
right
now,
but
I
think
it
will
be.
It
will
still
be
like
a
long
time
until
we
kind
of
change
the
implementation
completely.
D
D
So
I
was
able
to
implement
that
on
the
global
plugin
configuration
side,
but
I
needed
some
help
with
referencing
that
in
the
job
itself,
so
I
was
able
to
reference
that,
but
the
the
data
that
comes
back
from
a
global
plugin
configuration
isn't
updated
like
if
I
go
back
to
global,
plug-in
configuration
and
see
that
okay,
these
things
are
here,
but
I'm
not
able
to
reference
anything
apart
from
default
in
the
in
the
job.
So
I'm
I
have
to
work
on
this.
So
after
merging
it,
I
opened
a
bug
with
this
gareth.
C
D
D
D
D
What
I'm
thinking
is
like
how,
if
so,
what
I've
done
is.
I
had
made
the
made
the
array
for
the
cube
configs
global,
and
I
tried
to
reference
that
from
the
from
the
job,
and
it
only
takes
so.
It
seems
like
the
state
of
the
array
is
what
it
was
initially
and
it
is.
It
is
like
localized
only
to
global
plug-in
configuration
right
now,
even
if
I
thought
it
was
global,
so
something
something
related
to
scope.
That
needs
to
be.
D
D
D
D
We
could
probably
write
an
example
where
all
of
the
change
we
have
different
jenkins
tasks
and
all
of
them
are
running
in
the
techno
pipeline.
But
then
I
was
thinking
of
the
openshift
sync
plugin,
and
I
was
thinking
that
in
openshift
sync
plugin.
They
have
something
called
build,
config
and
builds
so
build.
So
what
happens
is
exactly
build.
Configs
are
synced
into
or
into
the
jenkins
into
jenkins
as
jobs.
D
So
if
I
have
like
a
pipeline
and
sync
it
in
jenkins,
that
means
that
that
pipeline
would
be
completely
converted
to
that
pipeline
would
be
completely
converted
to
like
a
jenkins
file,
and
that
would
mean
like
we
need
to
have
like
a
dsl
ready.
At
that
point,
I
was
thinking
if,
like
it
sounds
like
it's
possible,
but
the
hurdle
for
this
one
is
the
dsl.
D
So
I
so
at
that
point
what
what?
What
is
possible
for
us
to
do
is
just
like
write,
a
jenkins
file,
completely
written
in
the
pipeline
step
with
tecton
client
plugin,
and
then
we
can
execute
or
like
if
we
install
jenkins
on
a
kubernetes
client,
which
is
also
if
we
install
jenkins
on
a
kubernetes
server,
and
we
turn
on
the
tech
on
whatever
sync
plugin
probably,
and
it
will
sync
all
of
the
tasks
and
task
runs
into
into
jenkins.
D
C
C
For
me,
I
think
the
the
kind
of
most
important
thing
is
to
get
it
to
get
this
to
a
point
where,
like
it
can
be
used
in
the
community,
and
we
start
getting
feedback
and
people
sort
of
like
real
world
use
cases
of
how
people
actually
want
to
interact
with
the
techno
client
plug-in.
I
think
that
would
be
really
cool,
because
at
the
moment,
it's
hard
to
see
how
people
would
want
to
use
this,
but
more
also
not
how
they
have
them.
D
Our
feeling
that
we'll
get
like
a
probably
a
good
spike
in
usage
one
once
we
have
the
dsl
ready
or
like
till
to
some
extent,
because
then
I'm
I'm
slowly
understanding
the
fact
that
not
a
lot
of
people
or
directly
use
the
like
there
are
a
lot
of
users
for
it.
Probably,
but
like
the
ease
of
use
with
jenkins
style,
is
much
more.
A
My
question
was
much
higher
level
and
conceptual,
and
you
you
a
bit
addressed
it
in
the
in
your
last
comment.
So
for
this
idea,
what
you
would
be
doing
is
something
quite
quite
different:
you'd
in
fact
be
taking
by
jenkins
pipeline
and
the
jenkins
file
for
that,
using
the
plug-in
and
be
able
to
take
that
and
then
run
that
within
tecton.
So
it's
the
inversion,
it's
just
like
the
flip.
D
D
D
Maybe
maybe
it
comes
off
incorrectly,
because
what
this
means
is
when
the
tasks
and
task
runs,
the
pipeline
pipeline
runs
are
synced.
So
what
will
happen?
Is
they'll
be
synced
by
namespace,
so
there
will
be
project
jenkins
project
called
with
the
namespace
name,
and
the
job
in
the
name.
Space
will
be
like
a
pipeline
like
it
will
be
now
that
I
think
about
it.
It
should
be
like.
D
D
A
No
that
that
was
that
was
very
good.
I
can't
answer
your
question,
but
it
was
a
very
good
explanation.
I
did
gareth.
Did
you
see
this?
I
think
there
was
once
a
pr
for
techton
about
running
jenkins
or
jenkins
jobs,
yeah
yeah
yeah.
So
I'm
just
wondering
about
how
that
relates
to
your
idea
and
how
much
overlap
or
how,
if
it
can
form
it
or.
D
What
like
a
tecton
resource
called
jenkins
job,
which
is,
which
is
a
tecton
resource,
and
this
jenkins
job
will
trigger
or
like
it
will.
It
will
do
something
on
jenkins
and
then
wait
for
that,
whatever
process
it
is
to
like
get
over
and
come
back
to
the
controller.
Usually
what
happens?
Is
that
there's
like
multiple
parts
for
like
each
of
the
pipelines?
D
So
in
this
case
that
won't
happen,
all
the
controller
would
be
doing
is
like
triggering
and
watching
those
task
and
probably
have
like
something
of
a
queue
to
manage.
You
know
keeping
keeping
in
touch
with
those
jenkins
jobs
which
are
happening
so
it
it.
That's
that's
the
idea,
basically
behind
it,
so
it's
basically
calling
jenkins
from
techno
and
managing
it
with
like
a
kubernetes.
D
But
you
know
what's
interesting
techtone
initially,
I
I
think,
as
we
started,
considering
like
abstraction
and
composability
was
such
a
big
thing
with
with
the
jobs
and
tasks
and
all
itself
the
I
mean
the
tasks,
pipelines,
pipelines
and
the
way
it's
created.
I
I
don't
know
like
it.
It
will
slowly
build
towards
this
like
more
interoperability,
and
you
know
having
like
something
like
a
plug-in
mechanism,
because
plug-ins
were
initially
discussed
quite
a
bit
in
tecton,
but
slowly.
D
The
discussion
moved
to
you
know
doing
so,
the
idea
of
plugins
and
how
it
would
be
implemented.
There
was
no
such
decision
made
on
that
as
such.
So
that's
where
the
catalog
project
started
in
the
first
place,
because
tasks
are
usable
and
if
some,
if
we
give
tasks
which
can
be
just
reused
by
and
just
some
parameters
need
to
be
given,
that
would
be
cool
right.
D
So
that's
how
it
kind
of
like
started
the
catalog
thing
and
but
but
if
you
notice
or
to
actually
extend
the
engine
to
support
something
somewhere
else,
there
is
a
need
for
doing
something
like
this.
That
has
been
mentioned
in
the
tecton
experimental
issue
that
you
that
we
are
talking
about
right
now,
where,
like
there
needs
to
be
a
different
controller
entirely,
and
this
controller
needs
to
then
watch
for
some
a
resource
like
jenkins,
job
and
yeah,
probably
on
the
jenkins
on
the
tecton
side.
This.
A
A
That's
all
right,
that's
good
for
when
we're
looking
at
cloud
event,
data
which
technology
supporting
and
now
jenkins
might
be
supporting,
is
that
would
that
also
be
a
way
to
link
up
very,
dare
disparate
pipelines?
Could
that
be
another
alternative
way
to
go
between
titan
five
lines,
jinx
pipelines,
second
pipelines
like,
however,
you
want
to
do
that?
A
D
Yeah
actually
yeah
what
the
kubernetes
con
I
was.
I
was
thinking
about
this
before,
like
you
could
just
you
know,
have
like
an
event
queue
on
the
jenkins
controller
on
the
other
side,
and
then
that
event
you
on
decked,
on
like
work
kind
of
do
all
this
like
manage
stuff
on
jenkins
through
cloud
events,
I
don't
know
like
probably,
we
will
have
to
pass
like
a
lot
of
data
and
like
how
will
the?
D
A
D
D
Fine
yeah,
but
I'm
very
excited
for
the
cloud
events,
proposals
and
what's
what's
gonna,
come
I'm
I'm
very
excited
to
see
like
the
infrastructure
that
will
be
spun
up
to
test
cloud
events,
because
it's
it's
something
it's
it's
more
of
a
so
the
implementation
itself
isn't
very
hard.
But
what
does
what?
What
would
be
interesting
is
to
like
how
how
the
students
will
use
it.
A
Yeah,
I
could
it's
a
very
exciting
project.
I
I
have
like
this.
We
have
had
a
good
conversation.
I've
let
this
meeting
drag
a
little
bit.
I
just
time-wise
it's
taking
up
more
time
than
I
had
expected,
but
thank
you
for
a
great
like
really
great
discussion
today.
That
was
really
helpful
for
me
and
hopefully,
for
others
and
really
enjoyable.