►
From YouTube: Summer of Code student presentations
Description
We will be concluding our Google Summer of Code (https://jenkins.io/projects/gsoc/) projects with student presentations on their projects
A
A
A
A
This
is
the
first
year
when
we
attempt
this
problem
on
this
year.
We
have
about
nine
project
ideas
for
different
areas,
including
Jenkins
of
plugins
super
grant
infrastructure.
Now
we
gently
both
James
and
main
directions,
as
we
may
see,
in
ongoing
conversations
and
opportunities
in
the
community,
we
had
about
15,
vendors
and
three,
or
that
means
students
to
prepare
their
proposals
and
to
go
through
their
projects.
A
A
C
A
The
next
events
like
Jenkins
contributor,
Sally,
petty
gentle
soul,
to
be
able
to
discuss
most
water
to
do
next
is
a
google
Summer
of
Code
and
just
flex
on
setting
statistics.
We
had
five
projects.
One
projects
was
a
delayed
other
weight,
including
his
for
improvements
of
full
project
spirit
awaited
the
plugin
in
a
system
like
external
workspace
manager
and
support
from
plugging
in
fermions.
A
We
also
good
project
surgery,
lubricant
infrastructure,
from
the
communication
partnership
on
the
websites
and
big
data
analysis
for
blogging
insulation
sassette
after
midterm
revelation
we
had
to
Georgians
lift
and
that
they
are
students.
I
will
present
their
their
projects,
redness
relation
to
where
students
like
a
chicken
real,
only
stuff
from
their
presentation
by
Alexandra
sormani,
we'll
talk
about
it
when
a
lot
space
manager
for
pipeline
and
then
some
odd.
I
will
talk
about
Jenkins
Webbie
area
for
months
in
poor
and
also
about
health
editor
plugin,
which
has
been
developed
a
bigger
than
his
foot.
A
A
If
you
watch
the
presentation
to
be
a
people,
even
ask
questions
using
YouTube
or
way
to
you
can
find
it
on
the
top
on
the
left
side,
and
you
can
ask
your
own
questions
so
vote
for
other
questions
and
other
presentations
will
try
to
us
answer
them,
and
also
there
is
a
siege
engines
channel.
We
are
going
to
monitor
it
and
we'll
also
other
questions
I'm
from
this
channel.
That's
all
from
me
or
I:
go
in
there
open
another
presentation
for
someone
actually.
A
On
this
year,
no
actually
we've
had
several
proposals
related
to
stability
improvements,
for
example,
the
work
of
fingerprint
Merlin
engine
and,
of
course,
there
are
other
projects
we
would
like
her
to
consider.
But
in
the
case
of
food
summer
of
hope,
we
finish
such
areas
because
they're
just
conflicts
for
three
months
projects
even
listed
about
the
stability
of
projects
in.
C
A
E
B
E
E
So
one
of
the
problems
that
some
Jenkins
users
are
facing
is
that
it
is
quite
difficult
to
share
and
reuse
the
same
workspace
for
multiple
jobs.
One
use
case,
maybe
when
running
parallel
testing
across
nodes,
an
alternative
is
to
copy
them
from
one
node
to
another,
but
as
we
know,
some
builds
may
have
large
files
and
copying
them
may
prove
to
be
slow.
E
Of
course,
there
are
also
some
other
possible
solutions
like
stashing
and
unspecial
immediate
effects,
but
this
can
be
used
only
in
a
single
pipeline
by
using
the
copy
effects
plugin,
as
I
said
earlier,
this
can
be
slow
or
the
user
can
go
for
some
advanced
job
settings,
but
in
this
case
the
workspace
management
logic
has
to
be
implemented
by
the
user.
So
the
alternative
that
I'm
proposing
to
this
problem
is
the
external
world
space
manager,
plugin.
E
E
First,
one
being
the
run
selector
plugin,
which
is
also
a
new
project
that
I
have
created
and
its
inherited
from
the
copier
track.
Plugin
mainly
what
I
did
was
to
decouple
the
build
selector
extension
point
and
I
have
added
symbol.
Support
with
then
we
have
the
workspace
can
a
plug-in
to
which
I
have
added
pipeline
sport
and
the
job
restrictions
plugin,
to
which
I
have
added
some
minor
improvements.
E
E
Now
we
are
looking
at
Global
fake
for
this
type
for
this
plugin,
so
I'm,
starting
with
this
school
definition,
which
has
this
pool
ID
a
display
name
and
a
description,
then
the
other
three
parameters-
I'll
explain
them
later.
Each
of
them
and
in
this
desk
pool
I
have
to
this
country
is
defined,
each
of
them
having
a
disc
ID
display
name
master,
mount
point:
this
is
the
mounting
point
from
the
Jenkins
master
to
the
disc
and
physical
path
on
disk.
E
This
is
an
optional
parameter,
but
it's
used
for
workspace
path,
computation
on
the
disc
I'll,
explain
it
later
on
and
also
we
can
provide
optionally
some
list
information,
but
again
I'll
I'll
show
you
later
next,
let's
have
a
look
at
the
node
configs
so
on
the
Left
I
have
node
1
config
this.
This
one
is
labeled
linux
and
in
the
external
workspace,
not
property.
E
E
Ok,
now,
let's
have
a
look
at
the
first
example
in
the
pipeline
job.
So
what
I'm
trying
to
achieve
here
is
that
on
one
node,
labeled
Linux,
I'll
I'll
clone
the
project
and
build
it
by
skipping
the
test
and
then
on
the
other
node
a
labeled
test.
I
just
be
from
the
testing
by
reusing
the
same
workspace
as
before.
So,
firstly,
I'm
calling
the
xws
allocate
step
by
providing
the
disk
pool
ID
parameter.
E
This
step
will
allocate
a
disc
from
the
disc
pole
and
on
that
disc,
it
will
allocate
a
workspace
with
the
object
written
by
it.
I
will
pass
it
as
input
to
the
xws
step.
The
xw
step
will
compute
the
complete
workspace
pad,
starting
from
the
node
to
the
to
the
actual
works
based
on
the
disc.
So
by
this
I
have
reused
my
workspace
in
the
same
pipeline
job
next
I'd
like
to
show
you
the
concept
of
reusing
the
workspace
in
two
different
pipeline
jobs.
E
So
the
concept
is
that
in
the
upstream
job
we
can
allocate
the
workspace
build
the
project
and,
lastly,
we
triggered
the
downstream
job.
In
the
downstream.
We
will
make
use
of
the
run
selector
plugin
to
select
the
triggering
build,
allocate
from
the
upstream
and
perform
testing.
Now,
let's
have
a
look
at
the
pipeline
examples
for
this
in
the
upstream
job.
There
are
no
changes
in
the
external
wall
space
commands,
but,
lastly,
I'm
just
triggering
the
downstream
build
by
calling
the
build
step
next
in
the
downstream
job.
E
I
am
using
the
select
one
step
from
the
run,
selector
plug-in
and
that
provided
the
name
of
the
job
name
of
the
upstream
job
and
the
selector
in
this
case,
I'm
using
triggering
selector
which
chooses
the
upstream
build
that
triggered
this
downstream
job.
Of
course,
there
are
also
many
others
selectors
available.
They
are
documented
in
the
wrong
selector
plug-in
documentation
page
next.
What
I
have
to
do
is
to
call
the
xws
allocate
step
by
providing
the
selected
run
parameter.
So
this
step
will
know
to
allocate
the
same.
Workspace
is
used
by
the
upstream
job.
E
So
I
have
here
my
Jenkins
instance
I'll
quickly
go
to
the
global
config
you
here
in
the
global
config
I
have
my
disc
pool
defined
with
to
linux
discs
and
in
the
discs.
I
am
providing
the
mounting
point
from
the
Jenkins
master
to
the
disc,
and
the
physical
patent
is
so.
As
I
said,
this
parameter
is
you
is
used
for
path
computation
on
the
disc,
so
the
path
is
computed
by
default,
starting
with
the
physical
pattern.
This
parameter
followed
by
the
job
name
and
the
build
number,
but
I
will
show
you
later.
E
This
can
be
overridden.
Ok,
so
I'll
save
this,
and
let's
have
a
quick
look
at
the
note
configs
I
have
here,
one
node
labeled
build
a
linux
and
in
the
config
in
the
config,
I'm
defining
the
mounting
point
from
from
this
node
to
the
disk.
Then
I
have
a
second
node.
This
one
is
labeled
linux
and
test
and
again
I
have
similar
external
workspace.
Note
properties,
configs,
ok,
now
I'd
like
to
show
you
the
first
example.
If
we
look
in
the
script
of
this
I'll,
just
zoom.
E
Ok,
so
our
base,
basically
the
Python
script,
is
similar
with
the
one
that
you
have
seen
on
the
slides
and
just
allocating
and
calling
the
xw
a
step
on
different
nodes.
So
I'll
perform
a
cloning
of
the
project
in
one
on
one
node
building
it
and
on
another
note
I'll,
just
test
it
so
I'll
save
this
and
I'll
trigger
the
bill.
Now
triggering
the
build,
and
now
let's
have
a
look
in
the
console
output.
E
So
in
the
console
output
we
get
messages
saying
that
the
selected
disc
ID
in
my
case
is
disc
2
from
the
this
pool,
and
the
workspace
pad
on
the
disc
follows
the
pattern,
starting
starting
with
the
physical
pattern,
disc
2,
which
is
appended
the
current
name
of
the
job
and
the
build
number.
Then,
when
it's
running
on
the
first
node,
we
get
message
saying
running
in
and
it
this
is
the
mounting
point
from
the
node
to
the
disc
2,
which
is
appended
the
workspace
path
on
that
disk
yeah.
E
So
the
build
has
succeeded
next,
it
runs
on
the
second
node
and
again
we
get
similar
messages
run
again
and
the
mounting
point
from
the
node
2
disc
and
the
path.
Ok,
so
the
build
has
succeeded.
What
I
want
to
show
you
next
is
that
on
the
Left
we
have
the
external
workspaces
view,
so
I'll
click
on
it
and
we
can
see
here
they
used
this
pool
the
allocated
disk,
the
path
on
the
disk,
and
here
we
have
the
complete
workspace
path.
E
E
So
the
idea
is
that
for
one
job
that
has
run
here,
I
have
this
one.
By
clicking
on
the
external
workspaces-
and
you
go
to
the
external
or
space
link,
you
can
actually
view
the
workspace
here
in
the
browser
yeah.
But,
as
I
said,
this
is
working.
Progress.
I
still
have
some
technical
difficulties,
but
it
will
be
out
in
the
next
release.
E
E
Let's
have
a
look
in
the
console
output,
so
we
get
similar
messages,
pat
on
the
desk.
This
time
it
uses
the
full
name
of
the
job.
So
in
our
case
the
job
was
located
in
the
upstream
folder,
so
it
uses
the
full
name
then
again
running
in
and
let
the
end
it
should
start
triggering
the
downstream
job
as
soon
as
the
build
finishes.
E
E
E
Ok,
in
the
meantime,
the
bill
has
succeeded.
Okay,
this
was
my
first
demo.
Let's
move
on
I'd
like
to
talk
about
some
advanced
features
that
the
plug-in
has
so
by
using
it.
You
can
also
benefit
from
workspace
clean
up
and,
as
I
said,
you
can
override
the
custom
workspace
pad
that
is
completed
on
the
disk.
You
can
do
this
overriding
either
in
the
Jenkins
global
config
or
in
the
pipeline
script.
E
In
this
example,
I'm,
showing
you
the
pipeline
script
for
the
workspace
clean
up
at
the
end
of
the
script
in
the
finally
block
I'm,
calling
the
ws
cleanup
step
with
clean
one
failure
parameter
set
to
false.
So
in
this
case
the
workspace
will
be
clean
only
if
the
build
succeeds.
If
the
bill
fails,
the
workspace
will
not
be
cleaned
and
next
regarding
the
customer
base
path.
This
is
the
example
in
which
it
overrides
the
base
paths
in
the
pipeline
script.
E
So
I
want
my
workspace
to
be
completed
on
the
disk,
starting
with
the
job
name
followed
by
the
PR
number.
This
is
a
build
parameter
and
to
which
is
appended
the
current
build
number.
Next,
what
I
have
to
do
this
string
I
have
to
pass
it
as
parameter
I
have
to
provide
the
path
parameter
to
the
xws,
allocate
step.
E
E
E
Ok,
so
the
build
has
succeeded
in
running
the
tests
now
and
it's
succeeded
and
we
can
see
message
saying
what
spits
clean
up
deleting
logic
workspace
done.
So
if
we
try
to
browse
this
workspace,
defiled
change,
you
should
directly
to
this
clear
it
CD
will
get
message
saying
no
such
file
or
directory,
so
the
workspace
has
been
deleted
next,
regarding
providing
custom
workspace
pad
on
the
disk.
So,
firstly,
I
said
that
in
the
Jenkins
global
config
you
can,
you
can
provide
here.
E
The
workspace
pad
template
parameter
and
in
the
help
file
you
have
here
are
some
basics.
Some
basic
example
of
how
you
can
use
it
right
now.
I
will
show
you
the
demo
in
which
it
is
over
redone
in
the
pipeline
script.
So,
let's
have
a
look
in
the
pipeline,
so
I
have
here,
PR
number,
which
is
the
build
parameter
and
the
pad
starts
with
the
jab
mein
pyaar
number
and
bill
number
and
I'm
providing
the
path
parameter.
Ok,
so
I'll
save
this
and
trigger
the
build
I'll
provide
20
as
disparate
the
building.
E
E
So
this
was
my
second
demo
and
now
I
like
to
speak
about
even
more
features
that
the
plug-in
has.
Firstly,
you
can
also
apply
some
disc
for
restrictions
if
you'd
like
to
and
it
comes
up
with
flexible
disk
allocation
strategies
so,
for
example,
these
poor
restrictions,
it
has
to
be
defined
in
the
Jenkins
global
config
and
this
this
pool
I'm
restricting
it
to
be
allocated
only
if
in
the
job
in
which
it
is
allocated
only
if
death
job
is
triggered
by
this
user
or
if
the
job
is
located
in
a
specific
folder.
E
So
this
this
is
how
you
can
apply
restrictions
next.
The
the
next
example
is
about
this
calculation
strategy,
so
you
can
define
one
disk
allocation
strategy
as
as
a
default
one
in
the
Jenkins
global
config,
but
this
can
be
overridden
in
the
pipeline
script
by
providing
the
strategy
parameter.
So
what
I'm,
showing
you
here
is
that
I'm
I'm
saying
allocate
the
disk
with
the
highest
weight
speed
also
I
can
provide.
This
parameter
is
optional,
the
estimated
workspace
size,
but
it
has
to
be
set
in
megabytes.
E
So
in
this
case,
I'm
saying
that
my
works
based
on
the
disk
may
have
an
estimated
workspace
size
of
100
megabytes.
So
in
this
case,
if
I
provide
this
parameter,
the
step
will
try
to
allocate
that
disk
only
if
it
has
at
least
100
megabytes
usable
space.
If
it
doesn't
have
that
much
usable
space,
the
job
will
fail
and
now
I'll
show
you
a
demo
of
these
two
examples.
E
So,
regarding
the
job
restrictions,
the
disp
or
restrictions
in
the
global
config
I'm
applying
for
this
disc
pull
a
restriction
that
only
started
by
this
user,
which
is
my
user.
So
I
learn
save
this
and
I'll
have
to
log
in
with
my
user
in
and
if
I
will
try
to
build
this,
it
will
succeed
because
I
am
able
to
allocate
that
from
that
desk
pool.
But
now,
let's
log
out
and
I
will
log
in
with
another
user.
E
So
this
user
is
not
allowed
to
allocate
this
pool.
So
if
I
trigger
this
I'll
get
an
error
message
saying
that
the
disk
poll
identified
by
the
ID
is
not
accessible
to
the
applied
restriction.
Okay.
So
this
was
about
this
poor
restrictions.
I
log
out
next
I'll
revert
the
restriction,
change,
no
restriction.
Okay
and,
as
I
said,
you
can
provide
this
calculation
strategy.
E
The
default
one
can
be
said
here
in
the
Jenkins
global
config,
and
for
this
you
have
to
also
specify,
for
example,
if
you
want
to
choose
the
disk
with
the
highest,
read
speed
or
write
speeds.
Actually,
you
will
need
to
provide
some
custom
disk
information.
We
need
to
specify
which
are
the
read
and
write
speeds
of
the
disks.
E
So
my
first
disc
has
a
higher
read
speed
of
10.
Ok,
so
I'll
save
this
as
it
is,
and
if
I
go
to
the
script
of
this
job
as
a
strategy
I
want
to
provide
the
strategy.
Select
me
the
disk,
with
the
fastest
read
speed.
So
in
my
use
case,
death
disk
should
be
disk
member
1.
So
if
I
save
this
and
I'm
tributing
the
beard
now,
let's
have
a
look
in
the
console
output.
E
So
we
get
the
message
saying
that
the
allocation
strategy
used
is
detected
this
with
highest
rate
speed
and
that
disk
is
disc.
1.
Okay,
regarding
the
estimated
workspace
sighs
if
I
stay
here,
that
my
workspace
size
may
have
100
gigabytes.
So,
as
I
said,
this
parameter
has
to
be
set
in
megabytes,
so
on
saying
it
has
100
gigabytes,
so
the
step
will
try
to
locate
the
disk
only
if
it
has
that
much
usable
space.
So
in
my
setup,
I
don't
have
the
disks
with
that
much
usable
space,
so
the
job
will
fail.
E
Let's
save
this
and
I'll
trip
up
the
job,
and
if
we
look
in
the
console
output
we
get
the
error
message
saying
that
it
couldn't
find
any
disk
with
at
least
that
much
usable
space
okay.
So
this
was
my
third
demo
now
I'd
like
to
talk
about
the
completed
work
summary
that
I
did
during
google
summer
of
code,
but
I'm
reporting
only
for
coding
period,
phase
2
for
phase
one
I
have
reported
in
the
meter
presentation.
So
I
have
grouped
my
work
in
phase
2
epic.
E
What
I
did
was
decouple
the
build
selector
extension
point
from
the
copyright.
A
plugin
I
have
made
workspace
clean
up
plug
into
the
pipeline
compatible
I
have
implemented
customer
space
pod
feature.
I
have
added
this
poor
restrictions,
a
couple
of
extension
points.
I
have
also
written
unit
and
acceptance
test.
My
repository
has
a
Jenkins
file,
so
it
builds
on
see
I,
dr.
Jenkins,
dot,
IO
and
more
details
about
the
work
that
I
did.
You
can
find
on
the
link.
E
It
is
on
this
page
also
I'd
like
to
announce
that
I
have
performed
a
stable
release
of
this
plug-in,
so
it
is
now
available
in
the
in
the
Jenkins
main
update
Center,
and
there
are
some
usage
guidelines
on
the
plug-in
is
read
my
page.
This
is
the
documentation
page,
so
you
can
see
here,
starting
with
some
setup
examples
how
to
setup
the
plug-in
before
actually
using
it.
E
E
Okay
in
the
future,
I
have
grouped
my
my
future
plan
work
in
the
phase
three
epic.
So
the
first
item
is
to
have
the
worst
page
browsing
feature
which
I've
shown
you
earlier
how
it
works.
Then
I'm
planning
to
integrate
fingerprints.
So
by
this,
the
user
will
be
able
to
see
to
see
his
work
space
in
which
other
jobs
was
used
and
on
which
specific
deals
from
that
jobs
was
used.
Then
a
nice
to
have
feature
is
to
integrate
the
plug-in
with
at
least
one
external
dis
providers,
for
example
with
Google
Cloud
storage.
E
E
So
my
presentation
will
take
place
on
the
second
day
on
wednesday,
on
sep
tember
for
thing
and
also
I'll
hold
a
demo
of
this
plugin
at
the
Jenkins
community
booth
and
after
the
demo,
I'll
be
I'll,
be
around
for
questions
and
discussions
so
see
you
there
so
before
starting
the
Q&A
session,
I'd
like
to
mention
that
if
you
have
any
other
questions
after
this
meeting,
you
can
join
the
discussions
on
the
deepest
chet.
So
thank
you
for
your
attention.
I
think
that
we
can
start
the
Q&A
know
alright,.
B
A
E
F
A
E
E
B
E
E
Sure
I
can
do
that
there
is
it
meditation
yeah,
so
you
can
reach
the
documentation
of
going
from
the
second
example
from
pipeline
examples.
From
from
my
plugin,
and
here
we
have
a
warning
message,
saying
that
you
have
to
use
the
run,
selector
plugin
and
it
cool.
We
can
go
to
the
Rigney
page,
and
here
we
have
some,
for
example,
we
can
select
the
upstream
build
based
on
its
status,
so
this
one
selects
the
last
successful
build
or
you
can
select
by
primal
linked
by
their
number,
and
this
one
was
the
triggering
yeah.
G
A
A
E
Well
initially,
this
is
was
the
design
plan
and
because,
if,
if
I
know
correctly,
to
be
able
to
specify
the
workspace,
ID
I
will
need
to
have
my
plug-in
integrated
with
fingerprints
and
currently
I
didn't
do
that.
The
integration
with
fingerprints
and
it's
a
it's
a
working
progress,
but
maybe,
after
that
integration
I
can
also
provide
an
API
for
specifying
the
workspace
by
only
by
the
ID,
but
initially.
This
is
how
how
we
have
designed
this
plugin.
Yes,
but
negatives,.
C
Yeah,
well,
I
just
want
to
point
out
that,
by
by
having
the
downstream
script
call
into
a
plugin
which
then
tries
to
guess
it,
what
the
identity
of
the
workspace
should
be
by
looking
at
build
metadata,
such
as
the
cause
of
the
build
that
you're
sort
of
your
throwing
away
information.
You
actually
had
to
begin
with
in
the
upstream
build.
C
So
if
you,
if
you
pass
the
exact
location
or
some
kind
of
identify
of
the
workspace
as
a
build
parameter
earth-
and
there
is
no,
there
is
no
possibility
of
confusion
between
between
the
two
things
happening.
So,
for
example,
if
you're
using
replay
function
in
pipeline,
you
would
actually
potentially
be
creating
a
different
downstream
build
that
was
not
triggered
by
an
ups
being
billed
at
all,
and
so
the
triggering
selector
wouldn't
work,
whereas
if
you
were
referring
to
the
workspace
explicitly
as
a
parameter
than
that,
something
replay
knows
about
it
and
it
would
copy.
C
So,
basically,
the
the
use
of
build
selectors
makes
sense,
incopy
artifact
for
freestyle
projects,
because
a
freestyle
project
can't
easily
have
any
logic
inside
it.
So
it
has
to
rely
on
logic
in
the
Jenkins
plug-in
to
make
those
decisions
for
you,
whereas
if
you're
using
pipeline,
then
you
can
sort
of
have
everything
you
can
take.
All
of
the
information
that
you
have
in
the
upstream
build
and
you
can
keep
all
of
it
and
not
did
not
have
to
try
to
reconstruct
it
in
the
downstream
build.
E
Yeah,
but
there
was
also
another
use
case
that
I
was
thinking
of,
in
which
the
user,
for
example,
want
to
select
to
select
to
use
the
workspace
only
from
a
specific
build
from
the
upstream,
for
example,
he
wants
to
use
I,
don't
know
he,
he
doesn't
go
for
this
triggering
method
and
just
selects
the
build
a
specific
build
from
from
the
upstream.
So
I
don't
know.
I
have
thought
that
this
may
be
a
flexible,
more
flexible
solution.
B
B
E
Well,
it
was
a
bit
difficult
for
me
in
the
beginning
to
get
used,
firstly
with
the
plug-in
development,
because
I
didn't
know
how
to
develop
a
plugin,
but
yeah
I
have
learned,
I
can
say
pretty
quickly.
Then
I
had
to
get
used
with
the
pipeline
script
syntax,
because
before
now
I
have
used
Jenkins
only
mainly
freestyle
project
or
maven
projects,
or
something
like
this
and
then
after
that
I
think
it
it
won.
It
went
pretty
pretty
okay.
A
H
Would
just
like
to
to
thank
Alex
for
working
on
this
project,
like
you
said
it
to
his
map,
pretty
deep
in
code
more
than
more
than
I
originally
thought,
but
Alex
hurt
he
did
raise
to
the
challenge
and
he
did
dig
deep
into
Jenkins
to
to
make
this
project
successful.
So
he
did
a
great
work.
Thank
you.
Alex
Thank.
A
And
I
can
leave
their
grave
is
marked
the
organization
of
what
project
was
good
and
the
usuals
made
by
Alex
feel
very
consistent
and
I
also
appreciated
his
15
communications
within
the
community,
not
only
with
his
mentor's
but
very
awesome
and
legislations
desires,
our
contributors
etc.
And,
in
my
opinion,
all
these
interpretations
will
be
very
productive.
So
I
know
I'm
also
very
satisfied
by
the
project
results
of
that's
a
walk
to
Alex
for
working
Ibiza.
A
C
A
C
A
Questions
in
the
YouTube,
so,
given
the
wrestle
no
other
questions,
then
we
can
trace
it
to
the
second
presentation
and
if
new
questions
arise,
we
can
just
discussed
at
the
end
of
the
winter,
so
somebody
I
already
yes,
so
let
me
introduce
so
much.
She
was
working
on
the
project
to
do
it
to
get
this
for
multiple
web.
Your
improvements
and
also
some
additional
stuff
like
how
I
did
it
plugin
as
a
multi-sport,
present,
feasible
town.
G
G
So,
let's
start
with
a
general
plan
of
deliverables
which
was
presented
march,
I
will
talk
about
it
in
more
details
later,
but
mostly
it
contained
it
contained
three
parts.
The
first
one
is
the
new
job
creation
page.
The
second
one
is
a
job
configuration
page
and
third,
one
was
optional
with
possible.
You
are
improvements
on
homepage
and
credentials
store
page.
G
G
So
changes
in
court
include
to
open
for
quests
that
are
almost
already
the
first
one
being
the
new
job
creation
pop-up,
and
the
second
is
the
responsible,
invalidation,
so
ninja
operation
pop-up
is
this
is
the
demo
you
can
see
that
a
user
can
create
a
new
job
now
without
need
to
reload
the
page
right
now.
The
state
is
that
most
parts
are
agreed
by
the
community
is
be
ready
to
is
ready
to
be
merged.
However,
there's
some
there's
still
an
issue
that,
hopefully,
sis
and
movers
are
result.
G
However,
the
the
changes
functional
and
implemented
as
intended,
then
the
response
of
germany
invalidation
also
completed
much
today,
the
is
very
now
I
can
have
more
responsive
experience
and
feedback
while
creating
a
job
name.
Lastly,
when
the
job
name
mattress
in
existing
one
and
see
it
right
away
with
that,
showing
this
new
page
and
slowing
him
down,
then
the
second
part
was
the
help
editor
plugin,
on
which
I
worked
during
second
health
of
the
summer.
G
Then
he
can
save
the
help
that
then
will
be
presented
to
all
users
of
this
Jenkins
instance.
So
here
I
reloaded
two
to
show
that
indeed
the
help
was
stored
and
can
then
be
shown.
So
this
will
allow
users
to
have
more
relevant
and
helpful
information
that
so
that
they
can
put
their
custom
specific
information
and
make
basically
this
button
more
useful.
G
G
The
HTML
there
here
like
to
quickly
show
show
the
storage
process
that
the
directory
of
the
help
information
files
is
the
Jenkins
home.
So
basically,
in
this
health
manager,
folder
the
the
files
are
stored
and
then
accessed.
So
here
you
can
see
that
the
file
is
received
by
going
to
the
path
of
the
territory
and
then
accessing
it
by
the
class
name,
which
is
unique
for
each
field,
and
this
is
how
we
missed
in
which
the
relevant
files,
currently
the
health
editor
plugin,
is
released,
but
in
beta,
so
you
can
access
it.
G
G
G
The
second
was
was
also
an
experiment
of
removing
at
description
button
on
the
homepage
and
moving
it
to
the
manage
page
of
the
Jenkins
to
make
to
attempt
to
make
the
UI
more
cleaner.
However,
it
was
decided
that
the
change
itself
is
not
developed
and
ready
enough
to
be
merged,
and
so
also
as
not
accepted.
As
this
point,
and
also
I'd
like
to
mention
that
I
wrote
in
an
PMO
gel
for
remodel
library
that
was
used,
I
mean
pop-up
project.
G
G
So
I
would
like
to
now
compare
the
bland
and
completed
work
that
was
initially
planned
in
March
and
then
what
happened
so
I
would
say
that
more
than
half
of
the
proposed
required
parts
are
completed.
So,
as
I
said,
the
main
ones
are
projects
the
main
projects
on
the
new
job
creation
in
the
the
help
letter
in
our
functional
and
working
and
for
the
most
part,
are
accepted
by
the
community.
However,
not
completely
and
explain
it
later,
then,
optional
parts
are,
unfortunately,
was
not
done,
we're
not
dawn
proud
because
of
time
constraints.
G
So
here's
the
more
detailed
view,
so
I
would
say
that
both
main
parts,
new
job
creation,
were
completed
in
configuration
page.
There
was
initially
also
this
idea
of
styling
the
configuration
page
of
searching
with
other
possible
ways
to
improve
you
I.
However,
that
was
quickly
rejected
as
an
idea,
since
that
was
considered
that
working
it,
maybe
not
the
maybe,
not
be
very
fruitful.
Since
the
UI,
the
global
you
I
of
the
configuration
page,
is
kind
of
reluctant
to
change
in
in
terms
of
student
contributions,
then
optional
changes
as
I
said
in
front
we're
not
done.
G
For
example,
this
homepage
you
I
proposal,
also
included
this
removing
and
editing
this
add
description
button,
but
the
experiment
didn't
work.
And,
finally,
unfortunately,
the
tests
were
not
reading
the
test,
work
that
were
used
for
the
plugin
and
the
new
job
creation
page
were
only
stenner.
So
this
also
a
part
of
the
future
work
that
I
mentioned
later,
so
they
offer
you
of
the
main
issues
that
contributed
to
not
completing
all
the
plant
work
are
I
would
say
that
their
consists
of
two
parts.
G
G
Those
sometimes
hard
to
follow
the
flow
of
the
processes
that
that
were
happening
in
Jenkins
and
I
would
say
that
the
most
part
most
time
I
spend
on
Jenkins
was
due
to
the
this
understanding
and
learning
and
reading
the
code
and
the
peaky
pages,
and
so
that
took
quite
a
lot
of
time.
In
a
second
part,
know.
B
B
So
if
I
understand
you
correctly,
you
said
I
think
you
said
it
has
been
difficult
week
and
they
understand
how
I
things
up
with
the
other
I
guess.
And
then
you
happy
look
at
the
code.
You
have
to
look
at
the
wiki
pages.
You
have
to
scrape
everything
you
can
t
know
if
you
get
you
get
that
understanding
so
that
I'm
in
a
very
valuable
hard-earned
knowledge.
B
G
Yeah
certainly
I
think
that
would
save
time.
I.
Think
I
can
find
some
areas
where
there
is
not
so
much
documentation
like
this.
Yet
I
can
write
something
yes
all
right
and
then
the
second
part
was
understanding
how
Jenkins
should
work,
meaning
that
how
my
projects
should
work
in
Hershey
they
should
be
implemented
so
sometimes
even
after.
I
would
understand
how
the
how
I
should
implement
the
project.
I
would
not
implemented
incorrectly,
and
that
also
take
quite
some
time
to
reiterate.
G
For
example,
this
library
for
the
pop-up
was
initially
agreed,
his
sound
a
good
one
later,
according
to
the
new
feedback
that
should
be
replaced
by
the
by
not
award
and
the
future
work.
Yes,
as
I
said,
this
replacement
of
the
remodel
library
is
a
third-party
library
which
can
be
used
by
one
which,
over
it
is
already
present
in
Jenkins.
Then
there
were
quite
a
few
comments
on
help:
a
better
plug
in
implementation.
G
So
actually
one
of
the
onset
advantages
of
the
hell
better
plugin
is
that
it
does
not
have
changes
in
core,
and
so
it
is
kind
of
more
flexible
to
the
changes.
And,
however,
there
were
some
suggestions,
for
example,
to
have
XML
structure
instead
of
sort,
separate
files
and
final,
of
course,
tests
and
I
think
there
are
important
ones
and
certainly
should
be
added
with
the
better
functionality
and
for
reliability.
A
G
Well,
currently,
these
help
files
are
stored
in
the
Huntington's
in
the
importer,
so
without
web
UI.
You
probably
can't
see
it.
You
can
change
it
directly
as
a
file
and
that
won't
work
go
to
the
fine
but
other
than
that
I.
Think
no,
since
the
the
JavaScript
sends
the
Ajax
requests
and
receives
it
after.
B
That,
let
maybe
I
wasn't
clear
in
the
question,
so
I
assume
that
the
intended
use
case
for
this
feature
does
a
person
who
is
configuring.
This
job
I
can
leave
some.
You
know
some
notes
about
why
I
did-
and
I
said
this
fatty
the
way
it
is
I
think
not
like
things.
For
example,
things
like
not
to
myself
come
back
in
the
two
weeks
after
I
dds
and
then
set
them
back
something.
B
G
A
Then
you
lost
to
clarify
the
question
the
responsibility,
so
this
help
manager
configuration
isn't
being
fun.
I
saw
this
help.
Files
I've
been
configured
on
the
global
level,
so
they've
been
configured
for
particular
class,
etc,
not
particular
to
jump
instance.
I
got
it
and
lift
it.
So
actually
it
could
be
another
useful
feature.
A
Actually
I
wanted
tools,
ask
several
questions,
and
maybe
it's
cuz
future
work.
So
during
the
planning
for
this
favela
to
plugin,
we
were
discussing
integration
with
job
config
history,
and
we
were
also
discussing
support
up
for
markup
for
editors,
which
would
allow
to
use
the
difference
in
yourself
and
limitations.
So
maybe
is
mattingly
clarify
some
of
these
ideas
to
other.
Given
this
means
the
meter.
G
Well,
yeah,
we
were
talking
about
the
add.
The
addition
the
markups
are
initially
is
concerned
is
a
better
way
to
have
the
markdown
formatting
for
the
help.
It's
instead
of
the
usual
HTML,
and
it's
that
that
should
not
be
particularly
difficult
since
and
as
I
understand
Kurt.
If
I
understand
correctly,
there
is
a
plug-in
that
does
just
that
and
so
may
be
unreliable.
G
A
F
G
If
so,
I
also
suggested
during
the
last
week's
that
it
is
better
not
to
load
the
help
files
each
time
when
a
user
clicks
on
this
Help
button
but
blow
boat,
all
the
file,
you
need
to
the
start
into
cash,
and
only
if
the
user
changes
the
help
only
then
to
send
the
matrix
request
and
attach
it
to
the
corresponding
help.
But
otherwise
it's
an
ajax
requests.
Each
time.
The
only
first
time.
A
G
A
So
from
the
atom
expected,
sometimes
I
really
want
to
rewrite
help
for
existing
options,
and
not
only
for
translations,
but
their
else.
A
common
case
when
you
have
to
adjust
recommend
it
for
your
instance
specific
use
cases.
So
maybe,
if
you
could
somehow
modify
existing
help,
it
will
be
rather
useful
addition
to
the
future.
A
A
D
F
G
A
G
G
A
Make
sense
to
discuss
it
together
as
I'm
climbing
90,
and
you
can
actually
release
it
at
any
moment
when
your
feelings,
illusion
of
okay,
maybe
other
people
interested
in
the
plugins
good
people
attend.
This
presentation
would
like
to
provide
the
feedback
we
got
in
the
garden
by
the
mansion
and
if
you
paralyze
a
feedback
somewhat
available
to
respond
to
it
and
may
be
to
make
some.
A
G
Yeah,
so
here's
the
drop
configuration
page
and
we
can
open
the
the
relevant
page.
So
so
here's
this
file
corresponds
to
the
to
the
help
information
for
the
first
?,
and
so,
if
we
change
it
to
automatically
change
here,
also
right,
so
you
can
see
that
has
changed
in
the
file
system
and
then
it
is
stored
for
the
other
users.
However,
if
we
change
some
other
description
and
you'll
see
and.
G
A
G
A
Since
now,
I
don't
see
any
questions
in
a
chance
as
well.
So
if
anybody
wants
to
ask
something
where
you
can
always
follow
up
this
speakers,
so
alex
has
shared
a
link
to
the
Gita
chat
where
we
discuss
the
tropics
is
supposed
to
be
somewhat
also
don't
for
some
communication.
Waste
wood
would
be
the
best
way
so
much
yeah.
G
A
So
I
think
that's
all,
and
if
you
have
for
any
other
feedback
regarding
the
beat
up,
it
is
feel
free
to
comment
in
the
meetup
page
on
meetup.com
and
thanks
a
lot
for
participating
in
this
session
and,
of
course,
fence
about
them
to
sum
up
to
Alex
and
to
their
enters
I.
Think
this
is
the
end
of
four
edges
of
project
on
d.
E
A
So
I
think
I
think
about
the
soul,
see
ya
the
next
sessions
of
changes
on
line
up
the
next
session
will
be
honest,
attempt
06.
We
are
going
to
talk
about
the
jeans,
plugging
development
in
particular
web.
You
guys,
then
you
will
talk
about
plugging,
develop
and
based
on
another
plus
extent
like
step
litter,
gelir
and
uniforms,
and
after
that
ron,
kenoly
will
talk
about
modern,
Janey's
US
based
on
JavaScript,
to
be
somewhat
presented
several
examples
and
there
will
be
much
more
examples
at
the
next.
That's.