►
From YouTube: 2021.2.12 Discussion on Tekton Client Plugin
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
Feature
event,
sourcing
and
even
notification
and
cqrs
and
other
one
is
event:
state
transfer,
carrier,
yeah
and
yeah
and
gate
is
based
on
kind
of
event,
sourcing
which,
after
I
mean
learned
about
it.
It
sounds
like
amazing.
B
A
C
That
is
is
really
interesting.
I
look
forward
to
watching
that
talk
a
lot
actually,
because
I
think
the
the
tectonic
client
plug-in
is
really
interesting
and
then
all
the
cloud
events
like
the
cloud
events
plug-in
is
really
interesting
and
then
there's
a
number
there's
a
number
of
areas
where
cloud
events
and
trying
to
standardize
on
cloud
events
in
ci
cd
pipelines
is
really
coming
forward.
So
it's
helpful
for
me
even
to
have
this
resource,
I'm
quite
excited
actually.
Thank
you.
C
C
Do
you
have
any
questions
on
the
work
you're
doing
for
gsoc.
C
B
B
I
added
your
link,
so
I
created
a
pr
just
right
now
for
study
links
for
the
cloud
events,
plugin
and
now
open
the
pr
to
the
idea
dock.
So.
B
I
also
just
opened
a
pr
for
a
proposal
for
cloud
events
plug-in
sorry.
I
mean
tecton
client
plug-in.
So
that
is
also-
and
I
did
a
bit
of
brainstorming
over
the
week
like
not
too
much
but
of
how
this
tectonic
support
could
that
format
could
help
us.
I
got
a
bit
of
understanding
of
how
the
tech
town
of
the
code
worked.
B
So
it's
actually
pretty
straightforward
and
most
of
the
action
items
I
think
are
almost
covered
so
for
today
I
just
wanna
want
to
get
the
discussion
ahead
with
text
on
client
plugin.
Maybe
so
we
could,
you
know,
set
in
stone
what
would
be
the
aim
for
the
gsoc
project
and
also
probably
if
we
could
discuss
the
timeline
for
g-shock,
because
yesterday
I
looked
at
the
timeline
for
research
seems
like
it's
close
to
three
months
for
coding.
C
Yes,
so
g
sock
will
be
over
a
10-week
coding
period,
but
the
amount
of
hours
demanded
of
students
is
is
greatly
reduced
this
year,
so
it'll
be
175
hours,
which
is
roughly
half
what
it
usually
is,
and
that's
just
kind
of
acknowledging
that
this
year
is
very
different
and
I
think
the
gsoc
organizers
wanted
to
try
something
different.
That
could
make
the
time
of
gsoc
more
flexible
for
students
and
mentors.
C
So
the
idea
is
that
there
isn't
a
lot
of
flexibility
built
into
that
10
weeks.
So
if
students
have
exams,
they
can
take
a
couple
weeks
off
for
exams
if
they
have
a
personal
event
or
something
they
need
to
spend
time
on.
They
can
do
that
and-
and
the
idea
is
that
students
and
mentors
would
work
together
to
decide
when
would
be
the
focused
work
during
that
10-week
period.
C
The
only
constraints
on
that
are
that
g-suck
does
want
to
see
a
halfway
point.
They
would
like
review
the
students
work
and
they
would
like
roughly
half
of
the
work
to
be
done,
so
the
mentor
and
student
can't
decide
to
basically
end
load
the
work
so
the
last
five
weeks.
All
the
work
would
get
done
and
that
wouldn't
work
from
g
sock's
point
of
view,
but
other
than
that
constraint.
There's
a
lot
of
flexibility
within
those
ten
weeks.
B
Okay,
I
was
under
the
impression
that
it
is
weak
based
and
I
didn't
consider
the
hour
based
yeah,
then
yeah
that
makes
sense
and
there's
a
there's
still
a
lot
less.
The
time.
C
A
mentor's
perspective
it
makes
sense
to
think
of
it
weak
based
because
you're,
probably
thinking
I'll,
see
my
mentee
once
or
twice
a
week,
but
maybe
some
weeks
you
won't
and
then
I
guess,
as
a
mentor
too,
you
can
say
look.
I
have
to
do
this
thing
this
week,
so
we
can
meet
this
week.
So
you
have
some
flexibility
as
well,
but
yeah.
It's.
I
think
the
125
hours
is
important
to
keep
in
mind
when
thinking
about
what
your
student
will
realistically
be
able
to
get
done
during
that
time.
C
C
Yes,
we
will
I'm
just
pulling
up
your
excellent
your
proposal
and
then
I'll
share
my.
C
C
C
C
B
Let
me
fix
this,
so
I
need
to
fix
this
and
the
links
I
didn't
copy,
the
quick
start
properly.
Let
me.
A
So
yeah
like
when
I
started
with
jugging
like
jenkins.
First,
I
like
made
my
like
scratch
plugin
using
tutorial
on
jenkins
and
today
I'm
just
playing
first,
then
I
learned
about
this
even
driven
architecture
and
today,
I'm
playing
with
the
cloud
cloud
events
java
sdk
as
per
doc.
A
A
It's
on
the
dock:
if
you
see
it's
on
the
dog.
A
Oh
yeah,
so
I
find
one
discord
server
of
java
where
I'm
just
posting
my
question
and
they
are
helping
me
also,
but
speaking
of
that
other
than
that
I
never
worked
with
networking
in
java.
So
it's
also
new
for
me,
but
it's
interesting
because
I
love
java.
There
is
java
networking.
C
B
That's
a
good
start.
The
cloud
events
so
community
is
really
good,
even
though
I
haven't
interacted
with
them
enough.
They
have
a
discord
channel.
No,
no!
That's
just.
A
Javascript,
this
is
a
java
server.
I
mean
just
a
normal
java
server
from
discord,
not
from
cloud
events
ex
specifically.
B
Oh
okay,
oh
you're,
talking
about
the
community
on
discord
right,
yeah,
yeah,
yeah!
That's
what
they're
saying
so
they
are
a
great
community
and
probably
we'll
interact
with
them
at
some
point
to
understand
some
best
practices
for
cloud
events.
B
C
No
there's
the
cloud
events.
Does
this
sig
has
a
getter
channel.
B
Yeah,
so
cloud
native
site
would
be
where
we
could
discuss
everything.
A
So
can
I
get
that
link
if.
C
B
For
the
tecton
plant,
plugin
yeah,
so
for
this
proposal
yeah,
I
I
was
thinking
of
how
we
could
narrow
it
down
earlier
this
week
until
later
and
later
today,
not
later
today,
early
today,
so
I
was
thinking
of
focusing
on
one
particular
aspect
of
the
cloud
events
plugin-
and
this
is
the
this
part
we
we've
been
discussing
for
a
long
time
about
the
dsl
bits,
the
tech,
dot,
tecton
folder
bits
which
can
be
used.
B
You
know
to
track
trigger
tecton
pipelines
through
jenkins,
so
I
was
thinking
of
narrowing
it
down
to
the
dsl
for
tecton
and
having
dot
tecton
folder
support.
So
what
tecton,
as
a
code,
does?
Is
it
when,
when
a
pr
is
open,
it
checks?
B
So
if
there
is
a
dot,
tecton
folder,
so
a
trigger
first
of
all,
what
it
does
is
if
there
is
a
techno
trigger
enabled
for
the
repo
it
the
trigger
will
trigger
a
tecton
task
which
will
check
if
there
is
a
dot,
tecton
folder
in
the
repo
and
then
it
will
apply
all
those
yamls.
The
pipeline
yummels
pipeline
runyon.
A
B
Are
needed
to
run
the
tecton
pipeline,
so
I
was
initially
thinking
that
you
know
it's
it's
it
isn't
as
straightforward,
but
turns
out.
It
is
pretty
straightforward
of
how
it
works.
What
we
could
do
is
we
could
keep
the
electron
folder,
but
in
the
jenkins
file
we
we
can
provide
parameters
for
what
the
what
what
will
actually
happen.
B
So
we
can
provide
parameters
with
that.
That's
something
we
have
to
figure
out,
but
if
we
narrow
it
down
to
this
bit
for
the
tecton
plant
again,
I
think
this
will
be
pretty
nice,
so
basically
we'll
be
narrowing
it
down
to
the
dsl
for
technon
in
jenkins
file,
and
if
that
ds
in
the
dsl,
we
say
something
like
text
on
bracket
name
of
the
tekton
server,
like
name
of
the
kubernetes
server
and
then
under
the
brackets.
So
in
the
close
brackets
we
say.
B
We
say
something
like
push
enabled
or
something
so
the
tecton
tasks
will
get
triggered
when
there
is
a
push
or
a
pull
request
based
on,
like
whatever
parameters
we
provide
in
the
second
step.
This
is
how
it
could
work
and
it
it
it
would
it
shouldn't
be
that
hard,
because
it's
a
simple
configuration
given
in
the
jenkins
file
number
one
number
two:
we
have
to
apply
the
tasks
and
number
three.
The
jenkins
would
already
be
connected
via
webhook,
so
this
this,
and
so
we
could.
D
Would
you
say
kind
of
returning
control
to
the
jenkins
file
after
the
task
is
completed.
D
Yeah,
because
I
was
thinking
like
one
of
the
things
that
jenkins
is
very
very
good
at
is
visualizing
test
results
and
outputs
from
files
and
stuff
like
that.
That
might
be
a
you
know,
a
really
nice.
You
know
you
run
the
text
on
task.
It
produces
some.
I
don't
know
junit
test
results,
but
you
actually
want
to
visualize
them
in
jenkins.
D
C
So,
for
me
to
clarify
for
myself
the
one
of
the
main
tasks
for
the
student
will
be
creating
a
dsl
for
techton
in
order
to
align
tacked
on
tasks
with
what
jenkins
needs
is
this
correct?
Is
this
a
fair
way
to
put
that.
D
Yeah,
probably,
I
suppose,
the
scope
of
the
dsl.
What
yeah,
I
suppose
again,
you
could
say,
like
you
want
to
provide
you
know
every
language
feature
in
tecton,
a
way
of
invoking
that
from
the
jenkins
valve,
but
that
you
that
may
not
be
required
for
this.
For
this,
you
may
just
need,
like
a
limited
number
of
things,
again,
not
sure
what
they
are
yet.
D
B
A
B
Restart
I
I
missed
out
when
gareth
you
were
asking
about,
would
the
control
be
passed
back
to
jenkins.
D
Whether
or
not
we'd
see
you
pass
control
back
at
the
end
to
the
jenkins
file,
so
that
if
there
were
after
after
a
tecton
pipeline
is
run,
if
there
were
additional
stages
of
steps
that
you
wanted
to
run
in
sort
of
pure
jenkins.
Using
you
know,
jenkins
plug-ins,
you
could
still
do
that.
An
example
was
like
archiving
junit
test
results,
or
something
like
that.
B
Do
that
with
the
dsl
like,
if
like
it
should
be
a
way
to
integrate
with
tecton
but
but
not
necessarily
move
entirely,
because
I'm
not
sure
if
tecton
can
do
everything
that
jenkins
can
do.
There
are
a
lot
of
plugins
and
stuff
which
probably.
B
Which
have
tasks
with
which
probably
cannot
be
replaced
entirely,
so
you
integrating
with
tecton
this,
will
allow
integrating
with
tecton
but
not
necessarily
replace
jenkins
with
tecton
itself.
So
that's
what
that's
what
we
should
go
for
right
here,
so
in
that,
in
that
case,
in
that
sense,
the
controller
will
be
passed
back
to
the
jenkins
file
and
everything
else
that
runs
after
the
tecton
dsl
bit
would
run.
B
We
need
to
define
what
syntax
and
what
the
dslr
everything
can
do
before
we.
B
C
In
conjunction
with
the
mentors
for
sure,
and
in
terms
of
do
you
mean
when
the
student's
actually
doing
the
coding
work,
or
do
you
mean
in
advance
when
the
student
is
designing
their
project
proposal.
A
B
C
Okay
for
the
students
when
they
create
their
proposals,
they
take
and
they're
recommended
to
take
the
project
ideas
that
are
listed,
although
they
are
not
actually
constrained
to
them,
but
it
is
generally
helpful
for
them
to
do
so
to
take
the
project
ideas
and
then
to
create
their
own
proposal
based
on
those
project,
ideas
so
focusing
on
what
really
interests
them
and
if
they're
they
should
be
doing
this
sort
of
as
a
process
with
the
jenkins
community.
C
So
you
know
double
checking
their
ideas,
getting
guidance
from
future
potential
mentors
things
like
that.
So
if
the
student
is
developing,
this
dsl,
I
think
giving
them
a
pretty
strong
hand
in
it
is
great,
but
it
will
be
done.
You
know,
under
with
supervision
and
mentors
and
with
feedback
from
the
community.
B
Yes,
yeah,
oh
what
gareth
have
you
worked
on
jenkins
dsm
before
by
anyone
nope?
No.
C
No,
no,
not
not
at
least
now
would
andrew
bear
be
a
good
person
to
get
feedback
from
yeah.
I
think
you
would
actually
okay,
okay,
I
might
try
and
pull
him
in
then
good.
How
soon
would
his
involvement
need
to
happen?
Certainly
when
the
dsl
is
being
designed
and
written
it'd
probably
be
good
to
get
his
feedback,
but
I'm
just
wondering
how
far
in
advance
of
that
we
should
start
pulling
him
in.
D
I
think
the
sooner
the
better
really
even
if
he
can
just
you
know,
get
him.
Maybe
thinking
about
it.
A
little
bit
great.
You
may
go
away
and
then
come
back
with
ideas,
yeah
like
a
point,
because
I'm
not
sure
how
it
may
have
been
a
bit
of
a
while,
since
he's
worked
on
something
like
this.
C
Yeah.
Okay,
great,
that's
that's
helpful!
Thank
you
for
doing
the
pr
flip
up,
because
then
I
can
point
him
to
this
and
then
yeah
get
wider
involvement,
which
is.
B
Good
yeah,
I
I
will
update
this
pr
after
the
meeting
yeah.
Well,
there
is
a
openshift
client
plugin,
which
houses
soon
dsl,
which
we
maintain,
but
it's
been
a
long
time
since
I've
read
that
code
and
there
is
a
little
bit
of
technical
debt
over
there.
B
So
yeah,
I
I
think
getting
andrew's
her
earlier,
would
be
better
or
to
see
how
we
should
design
that
part
of
the
plugin,
because
the
way
we've
done
it
in
the
openshift
client
plugin.
I
feel
it
could
have
been
done
better,
but
it's
it's
still
like
a
lot
of
hard
work
that
goes
into
it
for
creating
a
dsl.
C
For
sure
we
definitely
want
it
well
designed
otherwise
it's
just
clunky
afterwards,
so
yeah.
Absolutely.
We
want
lots
of
feedback
on
the
design,
great,
so
I'll
I'll,
try
and
get
anders
feedback
on
this
and
and
put
him
in
contact
with
you
above
and
maybe
have
him
come
here
and
speak
if
he
has
time
in
in
the
meantime,
for
today's
meeting
is
there
is
there
another
thing
that
we
should
be
discussing
on
this
proposal?
C
B
Element
so
so
the
main
thing
main
thing
we
we
should
discuss
is
so
which
we
already
kind
of
covered
was
like
narrowing
down
to
the
scope
of
the
project.
B
B
Yeah,
that's
okay,
so
a
scope
of
tecton
plant
plugin
would
be
to
in
this
case
would
be
okay.
Give.
B
B
B
So
what
I'll
do
is
I'll.
So
initially
I
I
wasn't
understanding
like
what
we
should
do
like
last
week.
I
wasn't
understanding
what
we
should
do
exactly
and
because
just
creating
a
design
doc
doesn't
make
sense
like
it
needs
to
have
something
that
makes
sense
and
has
a
vision.
So
I
what
I'll
do
is
I'll
try
to
create
a
initial
design
dock
for
the
tecton
plant,
plugin
and
gareth.
With
your
help,
I
think
we
can.
B
B
Because
of
the
dsl,
we
could
do
a
lot,
but
we
should
know
for
the
project.
How
much
is
enough
so
yeah.
B
Even
even
something
like
minimum
compatibility
with
dot,
tecton
folder,
I
think,
is
a
good
place
to
start
after
that
we
can
have
stretch
goals,
but
I
think
this
is
a
good
starting
point
like
minimum
compatibility
with
dot
tecton
folder
and
doing
what
our
tecton
as
a
code
already
does,
but
through
jenkins.
B
It
shouldn't
be
no,
but
it
will
end
up
being
like
so
what
I'm
thinking
is
basically
like
currently
how
technology
code
works
is
it
is
directly
connected
to
tecton
and
all
the
the
task
triggering
directly
happens
in
tecton,
so
the
task
is
triggered
in
tecton
and
all,
but
with
this
dsl
bit,
what
we
would
be
doing
is
we'd
be
using
a
jenkins
file.
Configuring
configuring
that
having
a
dot,
tekton,
folder
or
even
it
should
be
possible
for
the
user
to
configure
whatever
pipeline
or
whatever
they
want
to
do
in
the
jenkins.
A
B
Itself
without
a
dot
technum
folder,
if
there
is
a
dot
technology,
pick
up
those
channels
from
there
applied
through
the
tecton
client
plugin
into
in
tecton
and
then
do
whatever
tasks
but
yeah.
I
think
with
this,
it
will
provide
flexibility
for
the
users
to
use
doc,
tecton
or
not,
or
not,
used
or
tecton.
So
if
there
is
a
point
where
there
is
a
user
who
says
that
okay,
I've
been
using
tech
honors
code,
but
I
also
need
some
jenkins
compatibility,
because
I
need
to
do
some
other
tasks.
B
Probably
techno
can't
do.
They
should
be
able
to
easily
integrate
into
a
tecton
plan
plug-in
with
the
same
configuration
that
they've
already
got
so
that
would
be
that
would
be
nice
to
have.
B
But
if,
if
we
are
able
to
restart
we,
I
think
we
can
keep
that
as
a
minimum
as
a
minimal
goal
for
the
project
and
I'll
try
to
sketch
out
a
design
dog
which
tries
to
cover
this
but
I'll
yeah
I'll.
Try
to
I'll
try
to
sketch
a
design
dock
for
this
one
I'll.
Take
that
as
an
action
item
for
next
week.
C
D
No,
it
sounds
good
I've.
I've
got
a
meeting
on
monday,
which
will
decide
exactly
how
much
time
I
can
dedicate
to
this.
So
I'm
kind
of
hanging
back
a
little
bit
until
after
that
meeting,
but
that
should
give
me
some
clarity.
B
Okay,
that
sounds
good.
I
wanted
to
ask
ask
if
so,
how
do
we
go
about
proposing
an
architecture
in
the
cloud
name
cloud?
Sorry
in
the
cloud
events.
B
C
I
think
bringing
it
forward
to
that,
to
that
sake
is
a
great
idea
and
they
may
be
very
interested
in
it
as
especially
as
it
begins
to
be
developed
and
put
into
production.
As
a
case
study,
I
think
that
that
could
be
really
interesting.
B
Yeah,
it
would
be
good
to
have
a
few
more
eyes
on
the
design
dock
kara.
Can
you
suggest
how
can
we
get
like
more
people
to
review
the
design
dock.
C
The
the
email
channels
where
you
have
posted
it
is
tends
to
get
would
be
the
most
obvious
place
to
post
it.
You
may
want
to
post
it
as
well
on
jenkins,
ci
dev,
just
because
I
think
there
are
many
more
people
on
that
email
list,
so
that
might
be
a
good
place
and
if
you
are
interested,
although
this
feels
a
little
early
to
do
it,
but
it
would
be
great
to
have
a
blog
post
on
this.
C
At
some
point,
I
would
really
like
to
see
that
those
are
the
most
obvious
ways
I
can
think
of
getting
more
engagement
from
people.
Do
you
have
any
other
ideas?
C
Certainly
after
I
think
it
would
be
great
to
announce
it,
but
if
you
want
more
engagement
and
feedback
and
kind
of
get
momentum
on
it,
I
would
certainly
be
and
you've
proposed
as
a
g-suck
idea.
I
I
think
it's
quite
interesting
to
talk
about
both
of
the
plug-ins
that
you're
working
on
and
maybe
discuss
what
you're
aiming
for
how
you're,
seeing
this
help
evolve.
C
D
And
I
think
if
you've
got
like
a
future,
what
do
you
say
anything
if
you've
got
like
future
road
map
ideas,
sort
of
thing
like
highlighting
what
those
could
be
like
the
scope
of
scope
of
the
plug-ins
in
the
future
could
look
something
like
this,
but
the
g-sub
proposal
is
like
it
might
just
be
a
small
piece
of
it,
but
explain
how
that
fits
into
the
big
picture.
That's
really
useful.
B
So
big
picture
is
basically
interoperability,
just
one
word,
but
yeah
it's
it's
it's
just
it's
just
part
of
all
of
that,
but
it
will
be
nice
to
see
multiple
things
working
together
with
jenkins
way
more
easily
and
in
a
more
standardized
way.
C
Definitely
and
when
the
work,
when
the
plugins
are
you
know,
completed
and
and
moving
forward,
very
well
that
this
is
a
great
story
for
the
cdf
and
for
the
interoperability
seg.
C
So
there
could
be
a
lot
of
a
lot
of
momentum
and
promotion,
then
there,
and
for
now
I
would
say
definitely
bringing
these
ideas
to
the
sigs.
Both
the
cloud
events
say
and
the
inaudibility
say
it's
a
good
place
to
get
wider
feedback
and
maybe
interest
I
mean
you
never
know.
People
could
really
dive
in
like
just
depending
on
who
who
hears
the
message
as
it
were.
C
So
actually
we
have
in
our
chat
here.
This
is
a
good
question.
What
is
dsl
and
then
is
this
dsl
and
we
have
a
link
to
a
jenkins
job
dsl.
C
So
dsl
stands
for
domain
specific
language
and
in
in
my
in
my
understanding
of
how
this
works,
a
lot
of
the
a
lot
of
pipelines
have
their
own
domain.
Specific
language
jenkins
certainly
does,
and
so-
and
am
I
corrected
saying,
tecton
does
as
well
and
then
what
what
is
thinking
is
that
a
student
would
make
sort
of
a
specific
dsl
for
integrating
tecton
tasks
within
jenkins.
Does
that
make.
B
So
it
it's
it's
so
I'll
still
kind
of
I
I
I
don't
know
how
much
I
can
elaborate,
but
it
is
basically
that
you
should
be
able
to
talk
to
find
a
way
to
talk
to
techton
using
the
jenkins
groovy
scripts
so
jenkins
through
the
jenkins
file,
so
that
developing
that
part
of
the
jenkins
file
through
which
we
are
able
to
communicate
to
tecton.
That
is
the.
B
C
Okay,
so
you
I
once
again
have
the
most
action
items
I'll
follow
up
with
vatek
and
see
if
you
would
like
to
present
again
on
the
jenkins
kubernetes
operator
and
help
you
above
in
in
any
way.
I
can
in
moving
forward
your
gsoc
proposals
in
the
next
week
because
they
go
in
next
friday,
so
pretty
exciting.
B
Okay,
that
sounds
good,
so
this
means
that
okay,
I
will
try
to
get
the
proposals
up
to
the
mark,
as
they
should
be,
and.
B
Probably
we
will,
we
should
sing,
we
will
sing
during
the
gsoc
office
meeting
right
office
hours
and
are
we
discussing
all
proposals
at
that
time
by
any
chance
before.
C
What
we're
doing
now
is
just
last
minute
refining,
more
resources
for
students,
any
any
extra
issues
for
them
to
look
at
and
mentors
gathering
mentors,
but
essentially
all
of
them
jenkins,
gsoc
proposals
as
they're
up
now
on
that
on,
the
jenkins
website
will
be
put
forward
as
gsoc
project
proposal,
ideas.