►
From YouTube: GSoC/Outreachy 2019: Mid-term project demos, part 1
Description
During this session Google Summer of Code students will present the results they achieved in their projects. This is a midterm evaluation, all projects are in progress.
Agenda:
* Parichay Barpanda - Multibranch Pipeline support for GitLab SCM
* Abhyudaya Sharma - Role Strategy performance improvements and a new Folder Authorization Plugin
* Long Nguyen - Remoting over Apache Kafka. Docker/K8s Features
Presentation abstracts: https://docs.google.com/document/d/13YwMEMXCjTfFmKGEsB2o8Xpaj9lsirgno1TE0pcMPus/edit?usp=sharing . Please contact us in https://gitter.im/jenkinsci/gsoc-sig if you have any questions
B
Okay,
welcome
everyone.
My
name
is
Martin
de
su
and
I'm
Jenkins,
google
Summer
of
Code
organ
min
or
for
this
year
and
right
now
we
are
at
coding
phase
two
evaluation
of
the
program,
and
today
we
have
three
presentations.
So
before
we
start,
I
would
like
to
remind
everyone
that
they
can
use
the
guitar
a
jsoc
account
too
for
any
questions
they
have.
B
A
B
Okay,
thanks
for
legging,
so
at
this
point
our
students
have
worked
really
hard
to
prepare
the
code
for
Phase
two
and
they
have
prepared
presentations
to
show
their
progress
on
the
program
and
we
have
three
presentations
today.
The
first
one
is
a
multi
branch
pipeline
support
for
get
lab.
The
second
one
is
the
role
strategy,
plug-in
performance
improvements
and
the
third
one
is
going
to
be
remoting
/,
Apache
Kafka
with
kubernetes
features.
B
C
D
Welcome
to
the
presentation
of
multi
branch
pipeline
support
for
gait
lab
phase
two:
this
is
a
project
which
is
trying
to
improve
the
integration
of
Jenkins
and
gate
lamp
hi.
Everyone
I
am
Parature
from
India
I'm,
an
open
source
contributor
and
their
devotes
enthusiast.
My
mentors
are
Michael
Jackson,
Justin,
hanga
and
Joseph
Peterson.
D
So
in
the
first
phase,
I
was
working
on
a
great
lab
server
configuration
plugin,
so
I'll
just
quickly
recap
through
what
features
that
were
covered
in
this
plugin.
So
it's
a
lightweight
plugin
and
it
supports
Jenkins
configuration
as
code
and
it
has
a
separate
kit,
lab
API,
plug-in
neo
Jenkins
version,
which
provides
some
UI
improvements
and
we,
you
can
also
add
multiple,
get
labs
server
entries
with
same
server
URL,
and
you
can
also
create
get
lab
access
token
inside
Jenkins,
which
is
required
to
authenticate
the
get
lab
API
that
is
used
by
the
plugin.
D
D
D
Okay,
so
the
features
that
include
is
you
can
check
out
over
SSL
or
HTTP
remote
by
giving
your
SSH
private
key
or
your
username
password,
although
it's
not
essentially
required
in
some
cases
where
you
have
private
project,
you
can
provide
these
external
credentials
and
we
have
groups
and
subgroups
support.
You
can
choose
group
projects
from
your
groups
and
subgroups
by
giving
you
the
path
to
that
group.
D
We
have
where
book
support.
This
basically
allows
your
jenkins
to
create
a
web
book
in
your
gait
lab
server
and
jenkins
listens
to
a
specific
URL
and
it
triggers
the
concerned
build
based
on
the
event
that
sent
by
a
third
observer.
So
currently
it's
a
work
in
progress.
The
implementation
required
are
kind
of
done,
but
there
is
a
bug
and
it
fails
to
take
out
the
build
yeah.
D
So
so
the
next
day's
pipeline
status
notifying-
and
this
basically
allows
jenkins
to
notify
the
gait
lab
server
about
the
status
of
your
pipeline
job
and
we
have
new
SCM
trade
api's
that
has
been
implemented.
I'll
just
talk
about
it
in
the
next
slide
and
we
have
worked
on
reducing
the
API
calls.
So
the
indexing
is
faster
and
other
functionality
as
well.
D
Okay,
so
here
is
a
list
of
SCM
trade
api's.
You
can
see
if,
for
example,
skip
notification
that
allows
your
pipeline
status
not
be
notified
to
the
gate,
lab
server
and
similarly
web
book
mode
and
check
out
over
search
AG
discovery.
So
you
can
also
be
it
for
further
extensibility.
We
can
also
add
additional
straight
trades
by
extending
this
get
lab
SCM
source
context,
class,
okay.
So
it's
demo
time
so
I'm
having
a
good
labs,
Jenkins
instance
running
here.
I
will
go
ahead
and
create
a
job
and
I
will
choose
multi
wrench
pipeline.
D
Okay
in
the
branch
saucers
I'll
select
good
lab
project
yep,
so
basically
the
server
configuration
part
that
I
was
talking
the
developed
in
the
phase.
One
was
this:
yeah
I
am
using
Jenkins
configuration
as
code
and
I'm,
ensuring
the
gate
lab
access
token
here
and
the
necessary
fields
that
is
required
to
configure
in
your
jet
get
lab
server
and
your
Jenkins
so
yeah.
So
it's
configured
here
and
I
am
choosing
one
of
the
it
labs
over
and
you
need
to
provide
your
own
it
so
from
based
on
the
owner.
Here.
D
D
So
right
now
Jenkins
will
be
indexing.
The
branches
so
here
the
master
brand
has
been
indexed
and
test
is
not
because
the
merge
request
has
been
fired
from
the
test
lines.
So
in
this
skips
and
directly
goes
to
the
most
requests.
All
the
magic
stuff
is
done
by
SCM
API
plugin
and
we
have
implemented
the
interfacing
in
this
plugin.
Okay,
so
this
so
indexing
has
been
done
and
I'll
go
to
the
status.
So
you
can
see
that
master
branch
the
pipeline
failed
and
hear
the
birds
request
it
passed
and
will
discover
and
see
the
result.
D
We
can
go
ahead
and
see
that
index
index
one
yeah,
so
so,
basically
it
builds
the
pipeline.
It
checks
it
out
and
gives
the
output
so
this
passed,
and
we
can
see
that
our
widget.
This
is
the
project
where
books,
integration
and
initially
there
was
November
and
I'll
just
refresh
the
screed
and
yeah.
So
we
have
a
book
here
that
has
been
created
by
the
plug-in
and
Jenkins
listens
to
this
particular
URL
and
based
on
that,
our,
for
example,
I
wish.
D
D
D
There's
a
form
validation
here,
and
it
says
it
said:
I
let
subdue
and
you
go
ahead
and
save
it
yeah.
So
it
will
basically
index
all
the
projects
did
and
I
have
done
it
already.
Here
you
get
the
list
of
your
projects
and
you
get
the
missiles
from
there
yeah
so
yeah.
These
are
some
of
the
features,
but
not
everything
could
be
covered
in
one
demo,
so
you
can
go
ahead
and
try
it
from
our
plug-in
repository
and
you
can
build
it
from
the
source.
D
We
have
a
documentation
about
it
and
we
have
also
made
a
alpha
release,
and
so
you
can
install
it
from
the
experimental
update
Center
by
using
one
of
the
new
plug-in
management
food
that
is
also
a
part
of
Z
sub
project.
You
can
just
download
this
binary
from
the
repository
and
run
this
particular
command,
and
it
gets
installing
your
Jenkins
instance,
and
we
can
test
it
out
so
after
testing
it
out.
D
So
so
we
have
some
plans
for
the
next
plane,
so
I'll
be
working
on
improving
the
performance
of
the
plugin,
which
would
be
revolving
around
optimizing.
The
data
structures-
and
there
are
also
some
known
bugs
and
old-
would
be
discovered
with
the
testing,
so
I'll
be
working
on
fixing
those,
and
there
is
also
some
room
for
UI
improvement,
so
I'll
be
working
on
that
as
well
and
implement
some
of
the
new
features
like
tag
build
strategies
etcetera.
D
B
D
So
currently,
as
far
as
our
discussion
that
happened,
the
new
ocean
is
building
like
shifted
towards
the
Fred
product,
maybe
some
more
improved
product.
So
presently
the
we
are
planning
to
implement
a
plug-in
for
that.
But
there
was
a
discussion
related
to
that
that
maybe
we
can
directly
work
on
the
new
interface,
which
is
an
alternative
to
blue
ocean.
So
that's
the
most
further
discussion
that
we
had
so
far.
Mm-Hmm.
A
D
A
You
yeah
and
another
question
about
github
organizations
and
multi
branch
pipelines.
So
if
you
use
github,
you
get
a
lot
of
different
options
in
order
to
define
how
a
meals
work,
for
example,
how
to
discover
branches,
how
to
filter
them.
How
to
apply
admissions
and
I
was
wondering
whether
you
have
similar
engine.
Forgive
love.
D
A
E
A
D
A
So
in
github,
by
default,
github
organization,
it
doesn't
allow
you
to
modify
Jamie's
file
unless
you
have
permission
to
the
depository.
So
the
use
case
is
pretty
simple.
If
you
have
a
continuous
delivery
pipeline,
if
somebody
submits
a
pull
request,
you
want
to
make
sure
that
this
somebody
it
doesn't
release
your
product
by
birth
twice
and
go
back,
planned
and
implemented
his
own
one.
A
D
Yeah,
so
I
don't
think
that
we
have
that
particular
support
for
a
trusted
contributor,
but
we
have
sem
create
a
peer
that
is
by
default,
provided
here
we
have
discovered
buzz
request
from
fourths.
So
what
you
can
do
is
you
can
just
go
ahead
and
nobody
you
can
just
select
so
this.
This
is
one
way
to
do
it,
but
if
you
are
talking
about,
we
can
choose
some
trusted
contributors,
then
yeah,
so
that
implementation,
which
is
done
in
github
branches.
We
don't
have
it
in
this
plugin
it
as
of
now,
okay,.
A
E
B
C
Hi,
everyone
and
okay
and
I
have
been
working
to
improve
the
performance
of
their
own
strategy
plugin
as
a
part
of
my
google
Summer
of
Code
program
this
year.
So
what
we
will
discuss
today
is
the
performance
improvements
that
have
been
made
to
the
road
strategy
plugin
and
the
new
folder
authorization
plugin.
C
C
C
Improving
the
performance
in
this
way
is
a
trade-off
between
the
CPU
time
and
the
memory,
because
we
are
storing
all
the
pre
calculated
data
inside
the
memory
at
runtime
now
to
measure
the
performance
improvements.
We
were
using
jamish
benchmarks
and
we
from
this
improvement
we
have
seen
improvements
of
up
to
three
thousand
three
hundred
percent.
C
Now.
The
other
thing
we've
done
is
to
cache
the
implying
permissions.
The
Jenkins
permission
model
follows
a
tree
like
structure
and
a
permission
can
be
implied
by
other
permissions.
So,
for
example,
the
permission
to
read
a
job
is
implicitly
implied
by
the
administrator
permission.
So
every
administrator
has
the
access
to
read
each
and
every
job.
That's
there
in
the
system.
C
So
what
role
strategy
plug-in
did
was
to
calculate
each
of
these
implying
permissions
for
every
permission
check.
Now
we
calculate
the
permissions
when
the
plug-in
is
loaded,
which
means
when
the
Java
class
is
loaded
and
we
store
them
for
quick
access
whenever
we
need
the
calculated
values
now,
a
challenge
we
face,
there
was
handling
dangerous
permissions,
so
in
Jenkins
are
some
permissions
are
considered
dangerous.
For
example,
let's
consider
the
run
scripts
permission.
C
This
permission
allowed
non-administrator
users
to
run
groovy
scripts,
which
could
which
had
the
access
to
Jenkins
internals
and
what
allowed
them
to
configure
anything
that
delight
roll
strategy
plug-in
supports
them
as
an
option
for
backward
compatibility,
and
this
Lord
for
safety
is
disabled
by
default.
Now
this
word
can
be
changed
using
groovy
scripts
at
runtime,
so
we
needed
to
take
care
of
that
and
we
added
a
hook
whenever
the
mood
changes
and
we
invalidate
the
cache
entries
for
these
dangerous
permissions
so
and
the
permissions
are
then
recalculated
again
now
to
measure
a
performance
benchmarks.
C
Like
I
said
before
we
use
the
JH
Bank
max.
We
used
the
micro
benchmarking
framework
that
was
created
inside
Jenkins
test
harness
during
the
previous
phase
of
G
sock.
You
can
see
the
blog
post
on
Jenkins
dot,
IO
to
know
more
about
it
and
you
can
implement
those
benchmarks
in
your
plugins
to
these
benchmark.
Reports
were
generated
during
the
pull
request
builds
and
we
compared
our
results
to
the
previous
ones
using
the
image
visualizer.
These
results
were
also
verified
by
running
a
compute
heavy
configuration
on
my
machine
and
running
profiling
using
visual
VM.
C
Now
the
improvements
that
we
have
observed
after
these
changes
up
to
ten
thousand
percent
in
the
overall
performance
of
the
plugin,
so
these
are
the
best-case
scenarios,
but
it
has
been
verified
that
these
performance
improvements
have
actually
been
made.
Now
I
would
like
to
introduce
the
new
folder
authorization
plugin.
This
was
a
plugin
that
was
created
during
this
phase
to
avoid
the
performance
issues
which
thorough
strategy
plugin
had,
since
this
is
a
black
brand-new
plugin,
it
saves
us
from
having
backward
compatibility
from
the
road
strategy.
C
C
C
Now,
let's
discuss
some
features
of
this
plugin
global
roles,
just
like
what
emotionality,
plugin
and
applicable
everywhere
inside
Jenkins,
the
folder
rules
work
on
folders
from
cloudBees
folders
plugin
and
they
can
be
assigned
to
multiple
users
and
multiple
folders.
At
the
same
time,
the
features
of
folder
rules,
the
major
feature
folders,
is
that
the
permissions
granted
through
a
folder
well
I
inherited
to
all
the
children.
So
agent
roles,
on
the
other
hand,
allow
configuring
permissions
for
multiple
agents
and
what's
connected
to
Jenkins,
and
they
work
on
the
full
names
of
the
agents.
C
C
C
This
is
what
the
UI
looks
like
right
now,
so
we
have
a
global
rolls.
We
have
a
folder
rolls
and
we
have
a
agent
rolls
now.
Let
me
just
show
you
what's
going
on
here:
we
have
an
admin
role
which
has
permissions
for
everything.
Next,
we
have
a
read
role,
which
applies
to
all
the
authenticated
users.
This
authenticated
user
group
is
provided
to
us
from
Jenkins
code
there's
another
one
just
like
this,
that
is
the
anonymous
s
ID
and
that
is
applicable
to
all
users,
whether
they
logged
in
or
not.
C
The
first
thing
we
have
is:
we
have
three
folders
the
root,
1
root,
2
and
root
3,
and
we
give
the
read
permission
to
use
a
1
using
this
role
and
we
have
another
child
folder
inside
it,
and
we
give
you
user
permissions
for
configuring.
The
job
I'll
add
another
role
here:
I'll
call
it
root
to
read,
and
this
would
apply
to
root,
2
and
we'll
give
the
permissions
to
read
the
job
and
to
delete
it,
and
we
just
click
Add
role
and
the
role
was
added.
C
As
you
can
see,
the
role
was
added.
Also,
let's
note
that
user
1
has
the
permission
to
delete
an
agent,
that's
connected
to
the
master,
that's
test
one,
but
not
the
other
two.
So
now,
just
let
now,
let's
login
as
user
1
and
the
only
folder
he
has
permission
into
is
route
1
and
the
folders
can
be
added
to
the
bottom.
To
increase
the
permissions.
C
Let's
say
he
has
the
permission
to
configure
the
project
and
the
folder
here,
but
he
does
not
have
the
permissions
to
configure
job
1
in
the
same
way.
Let's
just
go
to
the
home
page
and
see
them
see
the
two
nodes
which
are
connected
and,
as
you
can
see,
the
user
has
the
permission
to
delete
the
agents
and
but
he
does
not
have
the
permissions
to
delete.
I
am
test
2.
C
C
Now
these
are
some
screenshots
from
the
plug-in
and,
let's
just
compare
it
to
the
latest
release
of
Royal
start
lets
us
compare
the
performance
of
this
plug-in
with
that
of
the
Rho
strategy,
plug-in
with
all
the
performance
improvements.
So
let's
first
talk
about
global
roads,
and
so
what
people
observed
over
500
global
rules
is
that
the
global
rules
in
the
new
plug-in
are
up
to
nine
hundred
and
thirty
four
times
faster.
Then
the
global
rozilla
strategy
plug-in
this
is
for
data
set
of
500
global
rules
and
folded
rules.
C
The
in
these,
the
new
folder
rules
are
almost
15
times
faster,
not
an
equivalent
regular
x
in
regular
expression,
implement
stationed
in
the
role
strategy.
Plugin,
you
can
see
the
spoil
request
for
the
bench
back
results
now.
Some
challenges
that
I
face
that
I
faced
during
this
phase,
the
first
one
was
to
have
official
permission
checks,
and
we
had
a
lot
of
discussion
with
the
mentors
when
I'm
enters
to
produce
an
efficient,
efficient
solution
for
having
permission
tricks
now
as
a
benefit.
C
C
Next
thing
was
configuration
discord,
so
configuration
is
code,
uses
data
band
configurator
for
data
bound
constructors,
which
did
not
support
which
neither
supported
import
or
export
of
sense.
So
I
had
created
to
pull
request
to
the
configuration
discord,
plugins
and
the
boots
has
been
released
in
configuration
is
called
1.24
now.
The
next
steps
would
be
more
performance,
improvements
in
their
own
strategy,
plugin
and
improving
the
UI
of
the
foil
or
authorization
plugin,
and
so
and
writing
user
and
developer
documentation
for
it
and
finally,
I
want
auto
release
for
the
folder
authorization
problem.
C
Last,
but
not
the
least
I
would
like
to
thank
my
great
mentors.
Whole
net
runs
a
and
sukoon,
and
thank
you
everyone
thank
you
to
the
entire
Jenkins
community.
Please
do
share
your
feedback
through
either
the
role
strategy
plug-in,
get
a
chart
and
or
through
the
Jenkins
developer
mailing
list.
Thank
you.
These
are
some
useful
links.
A
B
A
F
A
Why
I
thought
about
this
use
keys
because
sometimes
it's
really
useful
for
micropenis
Asians,
because
yeah
on
the
folder
level,
you
can
define
pipeline
libraries,
you
can
people
find
many
other
folder
properties
and
sometimes,
as
I'd
mean
you
didn't,
want
your
users
to
modify
these
properties.
So
you
want
to
give
people
a
sandbox
with
everything
pre-configured,
so
they
can
create
jobs
and
do
whatever
they
want
with
these
jobs
in
this
setting
box.
D
C
The
main
difference
is
row
strategy
plug-in
works
on
regular
expressions
which,
when
they
repeatedly
called
it,
has
a
lot
of
performance
penalty.
Because
of
that
and
these
permissions
X
are
very
frequent,
so
we
in
the
foyer
authorization
plugin
we
just
straight-up-
do
not
support
regular
expression
that
all.
C
A
Would
just
want
to
say
a
few
words,
but
we
have
basically
a
little
bit
what
Marcus
said
about
parochet
the
question:
the
project
is
going
really
well,
basically,
we
completed
the
entire
jae-seok
project,
except
a
few
bits
like
releases
but
yeah
at
all
strategy,
already
both
big
performance
improvements.
We
contributed
a
generic
once
tasted
framework,
which
is
available
for
putting
developers
in
the
jenkees
community,
and
there
are
some
ongoing
adoptions
already,
which
is
great
and
moreover,
they
will
purchase
two
other
projects
like
Jing
his
configuration
s
code.
A
If
you
take
a
look
at
the
last
release
of
Jake
asked,
you
may
discover
that
the
most
of
patches
have
been
actually
done
by
a
Buddha,
but
these
patches
are
useful
not
only
for
all
the
growth
plug-in,
but
also
for
the
entire
community,
because
they,
the
bound
configurator,
is
just
the
core
of
liberationist
code
plug-in
and
used
almost
everywhere
and
I
believe
that
other
projects
we
are
presenting
today
also
use
this
configurator
for
setting
up
the
instance.
So
yeah
thanks
a
lot
of
you.
There
I
think
that
yeah
the
project
goes
well.
A
It
was
really
nice
to
see
this
matrix
where
we
have
1,000%
ten
thousand
percent
improvements.
Yes,
sometimes
an
artificial
use
cases,
but
even
for
user-provided
cases,
we
have
performance
improvements,
something
like
ten
times
anymore,
which
is
really
great,
so
I
think
the
goal
of
the
project
is
fully
completed
and
we
go
forward
by
providing
different
channel
EQ.
So
yeah
I
mean
this
is
great
and
thanks
a
lot
for
all
your
work.
C
Thank
you
thanks.
A
lot
for
mentoring
me
I,
believe
there
is
a
question
in
the
Gaeta
chart.
I
would
love
to
move
some
of
the
stuff
Thanks,
especially
the
global
road
stuff
that
we've
made
for
folders,
but
the
thing
is:
if
we
move
the
stuff
from
folder
authorization
to
row
strategy,
that
would
mean
breaking
a
lot
of
backward
compatibility.
So
I
think
that
meant
to
live
together
right.
A
Basically,
we
had
some
discussions
about
making
our
all
strategy
plug-in
pluggable
so
having
additional
selection
strategies,
not
on
delegates
but,
for
example,
folder,
selective
and
something
else.
As
an
extension
point,
it
might
be
one
of
our
natural
involvements
for
the
project.
You
just
can
just
combine
these
plugins
potentially,
but
here
right
now,
it's
not
available.
B
Are
we
ready
to
move
on
to
presentation?
Well,
thank
you
very
much.
This
is
great,
so
I
think
we're
ready
to
move
on
the
presentation.
Number
three
and
presentation:
number
three
is
remoting
over
Apache
Kafka
with
kubernetes
features
and
our
student
is
long
and
lead
mentor
is
Andrea
Falco,
but
today,
on
the
call
we
have
butuan,
who
is
mint,
who
is
helping
with
mentoring
this
year
route?
1
is
a
former
JSOC
student
who's
now
mentoring
this
year.
F
F
So
the
current
version
of
promoting
to
have
care
requires
users
to
manually
configure
the
entire
system,
which
had
many
moving
parts,
a
zookeeper
and
Kafka,
and
he
also
does
support
dynamic
agent
provisioning.
So
it's
hot
it's
hard.
Okay,
it
has
to
skill
and
for
this
project
we
aim
to
solve
two
problems.
F
The
first
one
is
an
out-of-the-box
solution
to
provision
a
budget
Afghan
cluster,
and
this
is
what
I
have
done
in
the
first
one,
and
the
second
thing
is
dynamic
agent
provisioning
in
kubernetes,
and
this
is
what
I
have
been
doing
in
Phase,
two:
okay,
let's
move
on.
So,
let's
take
a
look
at
the
last
phase
work
so
for
first
one
I
have
implemented
a
community
factory
adapter
class,
so
this
class
can
be
used
to
connect
to
kubernetes
cluster.
F
So
user
can
put
in
the
kubernetes
cluster
connection
information
here
and
then
just
click,
the
stuff,
Kafka
and
kubernetes
button
and
wait
a
few
moment
and
everything
will
be
set
and
done.
They
don't
have
to
figure
out
how
to
configure
Kafka
and
okay.
Let
me
move
on
to
phase
two.
So
what
I
have
done
in
phase
two
is
I
have
implemented
a
cloud
API
for
automatic
agent
of
ending
in
kubernetes
and
also
support.
Jenkins
configuration
s
code
and
I
have
implement
an
integrate.
F
F
Like
junkies
is,
there
is
no
note
with
the
corresponding
label
is
presented
contains.
We
asked
the
cloud
to
provision
a
new
node
and
this
Kafka
community
cloud
with
provision.
A
new
new
node,
which
is
early,
have
clouds
left
and
Kafka
Crosley
will
launch
chaff
computer
launcher
with
an
instance
of
a
Kafka
cloud.
F
Okay,
okay,
chunking
is
if
up
and
I
will
look
in
into
Jenkins
in
the
ham.
Short
value
of
I
saw
the
value
face
like
a
parameter
of
configuration
file
for
the
Hampshire
and
in
this
I
define
as
a
CSV
a
config.
So
basically,
this
tray
CSV
will
will
conflict.
The
remoting
have
kept
looking
and
also
conflict
a
job
to
test
test.
The
asian.
F
F
Okay,
success
jenkins
new
oil,
so
this
is
the
basically
the
asian
information
description,
working
directory
and
label.
So
the
label
I
said
here
is
cloud,
and
this
is
a
demo
job.
The
job
is
a
simple
one.
So
with
your
one
on
the
Lee
Clow
label,
so
label
cloud
is
served
by
no
node
and
one
cloud.
So
this
it
means
I
didn't
mean
when
only
the
job
which
caused
a
left
cloud
cloud
API
and
it's
a
simple
public,
echo
hello
world.
F
F
F
So
when
we
run
a
job,
so
we
ran
a
job
for
the
first
time
on
a
new
agent.
It
will
take
a
while
because
argentine
master
need
to
transfer
all
the
Java
files
and
the
classics
to
the
Asian.
Ok,
it
won
a
bash
squid.
We
should
echo
hello
war
and
it
also
take
a
while
to
finalize
the
job,
but
this
is
just
for
the
first
one
after
the
first
one.
It
will
be
fast
because
all
the
job
and
the
crusties
are
presented
on
the
asian
machine.
F
F
Southern,
so
the
second
one
only
take
3
second
and
waste
plow
API
we
can,
we
can
scale,
we
can
scale
the
job
like
whenever
you
don't
have
been
up,
not
as
cloudy
I
will
create
an
agent
and
then
create
important
communities,
and
then
we
can
still
as
much
as
a
community
cluster
can
handle,
and
this
is
a
nice
hinge
in
your
technology,
in
clarity
and
and
after
enslave
it
created.
It
will
stay
here
forever
and
you
don't
have
either
manually.
F
B
C
F
A
Yeah
we
we
can
actually
solve
it.
It's
not
a
big
deal
to
solve
it
for
plugin
poem.
The
problem
is
for
your
plugin,
because
you
need
the
recent
Genki
sweet
aversion
to
pick
up
other
cheeks,
so
we
have
reduced
you
patch
in
Jenkins
code
in
the
latest
victor.
So
basically,
if
you
wanted
to
include
this
patch
for
the
mountain
Kafka,
you
would
have
had
to
bump
up
the
dependency.
A
F
That's
awesome,
Cory
solution,
okay,
so
that's
a
big'un.
We
may
try
to
do
in
phase
3
and
the
next
phase.
A
phase
3
plan
is
okay.
So
now
we
have
to
point
to
the
2.0
beta
version
and
most
features
are
implemented
and
we
just
need
some
more
unit
tests
to
officially
released
2.0
version,
and
the
second
thing
here
we
test
the
retention
strategy.
F
It's
something
I
said
earlier
that
the
patient
we
stay
forever
after
created
and
retention
strategy
is
that
user
can
choose
so
that
Asian
can
terminate
immediately
after
running
a
job
or
it
may
wait
for
a
timeout
before
terminating
so
like
like
the
Asian.
The
number
of
Asian
can
scale
up
and
scale
down
automatically,
and
that
is
something
I'd
like
to
do
and.
F
So
for
now
there
are
many
new
things
and
there
isn't
any
documentation
and
I
wanted
to
arrive
more
documentation
and
Quick
Start
Guide,
so
that
new
user
can
get
used
to
outlook
in
and
the
next
thing
is
integration
test,
a
cache
can
kubernetes.
So
the
blue
key
now
have
many
moving
parts
and-
and
it
would
be
nice
to
have
an
intervention
integration
test
with
author
or
the
modulite
traffic
and
kubernetes,
and
the
links
and
friendly
Q&A.
F
F
F
Okay,
so
the
hem
chart
for
remoting
kafka
agent
is
a
very
simple
one.
It's
mostly
mostly
juice
the
the
power
of
the
Jenkins
Hampshire
and
Kafka
hand
shot
just
reconfigure,
some
small
value
and
that
look
at
the
junkies
hand
shot.
So
this
is
the
official
Jenkins
time
chart
and
it
has
already
have
all
the
RBI
CS
service
account
for
Argentine
master
roll
and
roll
binding.
So
the
roll
solo
for
the
RBI
zero
for
the
champion
shot
is
only
involved.
The
pot
yeah
listen
create,
so
that's
it.
F
The
answer
is,
are
BAC
is
interpreted
in
the
interdependencies
and
sure.
Thank
you
for
not.
Oh
and
now.
The
second
question
from
monkey
is
Mike.
I
noticed
you're
caught
in
defining
a
note
part
in
a
note
URL.
It
is
configurable
with
an
infrared
controller.
Okay.
So
this
we
can
also
contribute
this
by
overriding
web
overriding
Jenkins
ham,
shark
configuration.
So
look
at
the
default
value
again.
So.
F
F
Your
operation,
that's
it
and
question
from
Justin.
Are
you
incorporating
your
changes
into
the
mention
kiss
him
short
or
was
it
me
a
separate
hand?
Short?
Okay,
so
I
think
there
will
be
a
separate
hand
short.
So
this
is
just
a
use
case
of
the
official
our
chart
so
I,
mostly
juice,
gym,
kids,
I'm,
trying
to
kafka
headshot
and
over
while
that's
some
small,
otherwise
you
can
see
is
pretty
long,
but
because
they
say
for
demo,
purpose
is
a
actual
hand
shot.
We
are
only.
F
B
F
Can
you
okay,
so
this
is
the
physical
health.
Our
values
and
have
value
is
another
word
for
heme
short
configuration
and
basically,
in
one
hand,
shot.
Okay
here
is
a
official
Henshaw
and
it
defined
many
configuration
yeah
and
now
I
am
a
user
of
this
hand.
Short
and
I
can
override
any
configuration
here
and
this
first
project
teams,
the
is
for
the
dependencies,
and
this
is
the
configuration
I
over
Y,
so
I
hope
I.
The
the
version
contains
version
I
over
why
the
blocking
install
the
case
est
justice.
So
this
is
a
choker.
B
F
B
F
A
F
G
Okay,
so
attend
you,
no
longer
a
good
job.
For
the
second
phase,
we
managed
to
deliver.
I
want
a
great
feature
on
town
with
his
faith
and
so
I
did.
We
did
to
release
and
find
it.
The
second
phase
there
are
so
long,
but
I
fixed
some
bucks.
It's
a
box
sitting
plugin,
so
I
appreciate
that
so
yeah.
We
looking
forward
to
working
with
long
for
the
test
phase
full
of
equipment
and
hope
that
we
can
release.
B
Okay,
this
is
this
is
great,
so
I
would
like
to
congratulate
all
the
students
for
the
work
that
you
have
done
so
far
and
wishing
you
the
best
for
coding,
phase
three
and
I
want
to
thank
all
the
mentors
for
supporting
our
students.
So
thank
you
very
much
and
I
believe
this
concludes
our
presentations
today.
A
Just
some
beats
tomorrow
we
have
a
second
part
of
presentations
for
presentations
by
five
students.
So
tomorrow,
would
you
not
on
digital
history
stock?
We
will
have
people
from
outreach
union,
so
we
have
another
project
going
on
right
now
and
yeah.
They
will
be
also
one
student
journey
from
another
agency
or
organization
to
present
to
work
about
Jenkins,
so
we
have
at
the
same
time
for
presentations.
A
D
Okay,
so
you
asked
me
about
the
blue
ocean
plug-in
okay,
so
the
present
plan
for
Jenkins
is
like
they
want
to.
There
is
no
concrete
plan
as
of
now,
but
there
is
a
plan
to
modernize
Jenkins,
so
blue
ocean
would
be
improvised,
and
so
my
plan
was
to
implement
the
gait
lab
plug-in
in
blue
ocean,
so
that
I
learn
about
the
architecture
of
blue
ocean
and
and
I
can
contribute
to
the
modernization
of
I
mean
the
blue
ocean
plugin.
So
so
that
was
my
plan
right
now.
D
A
So
I
believe
for
this
topic
will
be
heavily
discussed.
The
DevOps
voltage
angles
fault,
so
they
will
be
considerable
summit
on
August
12
and
most
like
the
web,
UIs
and
web.
The
organization
will
be
on
the
agenda
for
these
discussions.
So
what's
the
tune
to
see
what
would
be
the
final
outcome
of
these
discussions
and
yet
thanks
a
lot
for
your
interest
in
this
area.