►
From YouTube: Jenkins 2019 Summer Project Demos. Part 2
Description
This summer Jenkins projects participated in Google Summer of Code, Outreachy and Community Bridge. During this Online Meetup sessions our students will present the results they achieved in their projects.
There will be 3 presentations in this video:
* Parichay Barpanda - Multi-branch Pipeline support for Gitlab
* Nancy Chauhan - Jenkins Pipelines for OpenRISC projects (LibreCores CI)
* Sladyn Nunes - Jenkins Configuration-as-Code Plugin Developer tools
You can find the presentation abstracts here: https://docs.google.com/document/d/1Ey-VXbMa1JT3tFDLDoW9yIRkzH324hP7OB1j7B80lX0/edit#heading=h.qqca5oaw5rxp
Gitter chat for Q&A: https://gitter.im/jenkinsci/gsoc-sig . You can also find more information about the Outreach programs in Jenkins here: https://jenkins.io/sigs/advocacy-and-outreach/outreach-programs/
A
We
are
now
recording
hello,
everybody
and
thank
you
for
joining
the
2019
google
Summer
of
Code
project
demos.
This
is
part
two.
The
date
is
August
26th
I
am
one
of
the
org
admins
Marky
Jackson.
We
have
a
full
set
of
demos
today.
I
am
very,
very
happy
and
very
very
proud
for
those
that
don't
know
when
you're
joining
just
so.
A
You
are
aware
that
google
Summer
of
Code
it's
a
global
program
for
the
open
source,
community
organizations,
mentors
and
students
there's
but
15
years
of
Google
Summer
of
Code
over
14,000
students
covering
a
hundred
nine
countries,
651
open
source
organizations
and
over
35
million
lines
of
codes
committed.
You
can
find
out
more
about
this
at
Summer
of
Code
with
google.com.
A
As
most
of
you
are
aware,
we're
the
Jenkins
organization
within
the
google
Summer
of
Code.
This
is
our
third
year
participating
in
the
google
Summer
of
Code.
When
this
started
for
this
year
we
started
with
seven
projects
we're
now
down
to
five.
If
you'd
like
to
look
at
our
projects
page,
you
can
do
so
at
Jenkins
dot,
io
forward,
slash
projects
forward,
slash
GSoC.
A
We
have
our
blogs
at
Jenkins,
dot,
IO,
forward,
slash
nodes
forward,
slash
tags
for
such
Google
Summer
of
Code,
and
finally,
if
you'd
like
to
reach
out
to
us,
you
can
do
so
via
the
google
Summer
of
Code
get
our
channel
the
link.
Is
there
I'm
not
going
to
reiterate
that,
for
everybody?
I
would
like
to
extend
a
huge
thank
you
to
our
2019
students.
As
most
are
aware,
this
is
a
very
competitive
program.
A
A
Just
an
amazing
effort,
I
think
all
of
you,
students
for
everything
you've
done.
Your
efforts
have
been
noted.
They
have
been
praised
and
we're
just
so
thankful
for
everything
you
do.
Students
Prachi
a
Natasha
Gwen
have
a
day
Jack
Prussia
Tech,
you
see
if
I
butchered
any
of
the
names
I
deeply
apologize.
It
was
nothing
personal
and
then
I'd
like
to
thank
the
google
Summer
of
Code
team
things
that
really
might
not
be
known
is
we're
always
looking
for
ideas.
A
We
we
love
to
help
and
mentor
we're
looking
for
students,
we're
looking
for
mentors
technical
advisors,
google,
Summer
of
Code
admins.
All
of
these
great
things.
If
you
have
any
questions,
please
do
not
hesitate
to
reach
out
to
one
of
the
org
admins
one
of
the
Mentors.
If
you
feel
that
you,
you
know,
you
don't
want
to
reach
out
in
the
public
Channel,
please
feel
free
to
direct
Li
message.
One
of
us
on
getter
you've,
also
I'm
sure
you've
seen
our
emails
in
the
Jenkins
dev,
as
well
as
the
Jenkins
Summer
of
Code
Google
Groups.
A
So
please
don't
don't
hesitate
to
reach
out
if
you
don't
want
to
do
so.
In
a
wider
forum,
you
can
also
contact
us.
You
can
look
for
information
that
Jenkins
got
IO,
for
it
says
projects
/g
SOC,
so
we're
gonna
jump
right
into
the
day's
presentations.
Today
we
have
up
broch
a
he
will
be
doing
the
get
lab
branch
source
or
multi
branch
pipeline
support.
We
have
Nancy
who
will
be
in
the
Jeep,
will
be
showing
us
the
Jenkins
pipeline
for
the
open
risk
project.
A
That's
the
Lib
course
CI,
and
then
we
have
Slayton's
who
will
be
doing
jenkins.
Configuration
is
code,
plug-in
developers
tools.
I
would
like
to
make
a
note.
There
has
been
the
outreach
e
presentations
that
have
been
postponed
for
this
session
to
we
do
have
an
open
doodle
for
a
session
3
which
we
will
be
presenting
out
to
the
community
very
shortly,
probably
when
the
next
day,
so
with
that
I
am
going
to
turn
it
over
to
parot
Jay
brought
Jay.
Take
it
away.
B
Okay,
hi
everybody
welcome
to
the
presentation
of
a
great
lap
dancers
plugin,
so
this
plugin
was
developed
as
a
part
of
google
Summer
of
Code
under
Jenkins
project.
So
officially
this
is
the
team.
So
this
is
me
Parature
and
this
Markey
Justin
and
Joseph
so
together.
Actually
we
did
a
lot
of
work
collaboratively
and
was
a
nice
experience.
So
this
is
the
efficient
team
but
anti
Jenkins
community
Oleg
Marty
and
Jesse
Gavin.
Everybody
put
efforts
to
this
plugin,
so
I
just
want
to
thank
everybody
for
their
thoughts,
so
yeah.
B
So
we
have
after
three
months
we
have
the
final
release
of
argot
lab
dancers,
plugin.
So
a
brief
introduction
about
it.
So
this
is
a
lightweight
plugin
which
lets
you
easily
configure
your
gait
lab
server
on
Jenkins
and
we
have
support
for
configuration
as
code
which
is
Jake
asked,
and
you
can
do
that
by
using
wireman
and
the
main
part,
which
is
multi
branch
pipeline
and
for
that
organizations
that
that
has
been
also
implemented
and
with
that
generally,
before
what
you
had
to
do
is
using
for,
in
your
gate,
lab
server.
B
You
have
multiple
projects
and
in
the
other
thing
you
have
multiple
branches,
thanks
magic
words
etc.
So
for
that
you
have
to
create
additional
jobs.
So
right
now,
I
just
don't
have
to
create
row
what
you
just
have
to
create
one
job
and
that
manages
everything
from
triggering
the
build,
builds
on
update
events
or
you
can
just
trigger
it
from
yogurt
lamp,
server
and
etc,
and
you
can
also
create
the
jobs
using
job
DSL,
which
is
a
GUI
script.
B
B
Okay.
So
this
is
what
we
did
in
the
one
I'll
just
quickly.
Recap
would
be
there
in
all
the
phases.
So
in
the
phase
one,
the
gate
lab,
API
plugin
was
developed
and
there
was
it
lab
server
configuration
part
of
the
plug-in,
which
also
allows
you
to
create
gait
lab
personal
access.
Token
inside
Jenkins
also,
you
Jake,
as
the
foot
was
added
repository,
was
implemented
by
and
Java
incompatibility
with
scheme
api's,
and
there
were
three
enhancement
and
fixed
releases
in
this
part.
B
We
have
also
worked
on
reducing
the
API
calls,
which
increases
the
performance
of
the
plug-in,
and
we
had
to
alpha
releases
in
this
part,
and
you
have
said
phase
3,
which
is
the
space
then
discovered
completed,
and
in
this
way
it
was
more
about
fixing
the
bugs
and
adding
some
of
the
missing
features
based
on
users
feedback.
So
webhook
support
was
broken,
so
they
fixed
it
and
basically
that
should
trigger
the
job
on
get
lab.
Events
and
system
of
support
is
also
part
of
MIT
lab
support,
which
will
let
you
create
different
jobs.
B
The
different
repository
in
your
get
lab
server
and
Jenkinson
detected
here,
the
bamboo
pond
that
and
basically
add
it
to
your
job.
If
it's
configured
that
way,
so
this
one
so
and
then
trusted
permission
strategy,
it
is
a
security
feature
that
was
recommended
by
all
day.
So
what
it
lets
you
do
is
sometimes
the
fork
fork.
B
Merge
request
can
be
from
untrusted
users,
so
you
not
what
your
CI
to
be
broken
or
some
details
to
be
shown
up
publicly
or
anything
with
damaging
your
security
so
touched
information
strategy
when
only
and
sure
that
they
uses
having
access
level
of
develop
the
maintainer
or
owner
access
level
will
be
allowed
to
trigger
the
pain
and
some
other
trades
like
you
can
trigger
the
bird
with
comment
on
your,
mr.
Sometimes
the
externally
server
fails
to
build.
So
this
is
also
user
requested,
feature
and
log
bill
status.
B
S
comment
this
one
also
added,
because
in
some
times
the
gate
latch
server
has
not
no
feature
for
them:
status:
notification,
for
example,
for
modular
request.
So
this
health-
and
we
have
also
added
the
Jake,
ask
and
your
BSL
documentation
with
the
repository
and
that
will
help
users
to
configure
the
plugin,
and
on
this
we
had
three
beta
releases
and
based
on
the
testing
of
our
testers
and
our
using
this.
B
B
B
B
A
B
So
we
have
this,
so
you
can
just
go
to
the
repository
you
can.
We
have
the
instruction
there
and
you
can
just
build
it
yourself
and
test
it
out.
There
is
more
to
it
in
the
documentation
that
is
all
the
description,
how
to
configure
etc,
and
we
have
all
the
the
GE
relations
also
here
you
can
just
test
it
out.
B
So
some
of
the
statistics.
In
the
three
months
we
had
two
contributors
we
had
489
permits.
There
were
a
hundred
eleven
issues
out
of
its
95,
that
fix
thirty-five
pull
requests
were
made
2.5
k,
installs
with
lab
API
plugin
120
file,
installs
of
hitler,
Brancheau
plugin
so
far,
and
there
were
12
locked
first
out
learning
all
the
week's
work
and
yeah.
So
you
can
just
if
you
want
to
talk
to
us
about
any
issue
or
any
feature
requests.
You
can
just
drop
your
meal
in
a
developer.
B
Mailing
list,
I'll
be
keeping
a
track
of
that
and
you
can
report
issues
to
the
Jenkins
zero
with
get
LaBranche
plugin
component,
and
you
can
also
join
our
Gator
channel.
So
you
can
just
tag
me
there
or
anybody
okay,
so
the
this
is
what
I
planned
for
the
future
I'll
be
actively
maintaining
the
repair
branch
plugin.
So
I
am
also
planning
to
add
gait
lab
support
in
blue
ocean
and
then
so
I
will
be
exploring
ways
house
and
can
see.
B
I
can
be
modernized
modernize
in
the
sense
that
I
think
the
front
end
can
be
improved
as
well
as
Jenkins
can
support
additional
tech
stocks
that
is
being
in
avoid
these
days.
A
lot
of
them,
so
III
will
explore
ways
by
taking
feedback
from
the
Jenkins
users,
because
I
am
NOT
a
particular
develop
user,
so
might
be.
Some
user
feedback
would
be
more
helpful,
and
so
my
exploration
will
be
on
site
okay.
So
this
is
all
about
my
new
sub
project.
So
to
ask
any
questions:
if
you
have.
A
Thank
you
very
much.
Prachi
I'd
like
to
thank
you
for
your
fairly
massive
effort
that
you
put
forth
in
this.
You
were
as
one
of
the
the
mentors
for
this
project.
I
will
have
to
say
it
very
self
managed
itself.
You
didn't
just
a
phenomenal
job
and
just
very
good
person
to
deal
with
and
I
love
your
demeanor
and
your
positivity.
So
thank
you
very
much
for
all
of
your
effort.
Does
anybody
have
any
questions
either
here
on
the
recording
or
via
the
getter
channel?
I
am
looking
and
I.
C
B
It's
about
the
plug
in
job
functionality
like
this,
some
of
the
traits
that
has
been
developed
like
scape
notification.
This
is
a
Purdham
job
like
it
notifies
you.
It
makes
additional
configuration
to
your
job
like
you,
do
not
notify
your
gait
lab,
so
that
can
be
a
different
plug
in
so
that
way,
extensibility.
B
D
B
So
far,
I
think
all
the
features
that
is
there
in
github
dancers
plugin.
It
has
been
covered
in
gait,
lab
branchless
plugin,
and
we
have
some
additional
features
as
well
and
they
some
of
the
features
that
you
might
find
missing
here.
It's
because
maybe
a
gate,
LAN
server
does
not
support
it
by
default.
So,
but
in
my
knowledge,
I
think
all
the
pieces
are
completely.
B
B
B
B
B
D
So,
just
to
share
some
context
on
that.
I
was
basically
hurting
something
quite
a
bit
for
it
half
last
week,
because
here
we
have,
we
should
be
staging
miss
rebuild
so
there
and
the
idea
was
to
partially
replicate
replicate
interface
front
row,
because
here
probably
is
one
of
engines
for
kubernetes,
which
also
comment
ups,
and
basically
this
is
the
only
mode
it
supports.
So
I
have
any
just
similar
interface
for
Jenkins.
For
me,
it
was
jinkies
rebuild
bus,
but
it
was
mentioned
in
the
beginning.
D
E
Is
it
I
think
with
github
plug-in
I'm,
not
sure
if
this
is
still
a
case,
but
I
know
I
had
to
install
the
core
request?
Comment
build
plugin
in
order
to
get
this
functionality
for
github.
So
it's
nice
that
it's
a
treat
that's
just
kind
of
like
available
for
you.
Don't
have
people
to
search
for
it,
but
yep
pulling
that
down.
Though
I
can
I
see
an
API.
What
would
be
cool?
Oh
yeah,.
D
A
B
F
Hi
everyone-
this
is
Nancy,
so
so
my
project
is
a
continuous
integration
for
hardware
projects
on
typical
CI.
So
this
error,
I
did
my
G
sock
with
quasi
foundation
and
so
I
had
this
I
like
this
is
a
very
great
idea
to
have
a
CI
for
Hartree
projects.
So
so
we
have
our
automation
server
as
Jenkins
and
I
walked
down
the
on
link
and
Stafford.
F
So,
okay,
so
I
will
be
just
presenting
it
yeah.
So
for
C
foundation,
just
a
brief
interview,
just
a
brief
introduction
about
4c
Foundation,
it's
a
non-profit
foundation
and
it
promotes
an
assess
the
free
and
open
source
digital
hardware
designs.
So
you
can
go
through
the
link
and
you
can
see
other
other
hardware
projects.
So
we
have
an
idea
regarding
libera
core
CI,
so
I
walked
under
elliptical
CI.
It's
an
approach
service
to
provide
continuous
integration
to
hardware
projects
and
total
powered
by
Jenkins.
F
So,
as
we
can
see
from
the
diagram,
so
we
have
a
like,
we
can
maintain
all
the
we
can
maintain
all
the
hardware
projects,
the
CIA
regarding
hardware
projects.
So
this
summer,
I
worked
with
open
risk
open
risk.
Community
I
worked
on
I
worked
on
integrate,
I
worked
on
CI
for
open
risk,
which
is
a
family
of
free
and
open
source
processor
implementation
on
your
desk
architecture.
F
So
we
can
see.
This
is
the
whole
diagram
which
can
which,
which
win
which
can
briefed
about
elliptic
or
CI.
So
it's
powered
by
Jenkins
and
we
have
a
predefined
docker
images
which
can
be
used
for
tiberias
for
the
various
configuration
of
various
hardware
projects
so
projects
they
connect
their
infrastructure
to
elliptic
or
CI
and
there's
a
quick
set
up
of
nodes
by
project
maintainers.
For
example,
I
developed
some
docker
images
for
Optimus
projects
specific
to
open
this
project.
F
So
just
to
recap
of
first
phase.
So
first
phase
was
all
about
all
about
enhancing
these
CI
pipelines
because
it
previously
worked
on
Travis
CI,
so
I
just
moved
it
to
Jenkins
and
for
that
I
created
a
docker
docker
container
for
that
so
which
has
the
environment
for
all
the
for
it
to
run.
So
now
the
open
risk
CI
runs
in
Jenkins
then
about
the
second
phase
yeah.
So
the
second
phase
about
was
about
working
on
your
synthesis.
So
your
synthesis
is
for
all
the
hardware
projects.
F
Nic
is
for
hardware
world
for
the
RTL
synthesis,
so
so
I
work
the
nozzle
synthesis
and
there
was
a
good.
There
were
changes
in
code
description
file
of
the
more
one
kicks
which
is
one
of
the
project
of
open
risk.
So
what
do
we
mean
by
code
description
file,
so
we
walked
on
few
socks.
So
few
sock
is
a
packet
is
a
packet
tool
manager
which
is
a
which
is
a
very
great
tool.
F
So
it
provides
everything
for
FPGA
and
hardware
tools,
so
there's
a
code
description
file
in
which
we
have
to
define
everything
what
we
want
and
your
sis.
So
we
have
a
back
end
of
your
sis
and
pure
sock,
so
we
basically
have
to
define
in
the
core
description
file
that
we
want
to
use
your
synthesis.
So
the
back
end
is
idealized.
Now
during
this,
when
I
wanted
to
integrate
your
synthesis
and
openness
project
we
had
to
do
we
had
to
face
many
arm.
F
We
had
to
face
many
issues
which
led
to
developments
so
that
so
the
issue
was
that
we
wanted.
Initially
we
wanted
to
try
only
for
monitoring
resource
usages.
We
don't
want
to
go
to
hardware,
so
we
wanted
to
make
it
flexible
so
that
we
can
use
only
for
monitoring
the
resource
usages
and
also
for
the
hardware
projects.
If
we
have
hardware
connected
XP,
she's
so
kind
so
we
made
it
flexible.
So
there
were
developments
and
Eid
lies
which
made
it
flexible,
and
now
we
can.
We
can
monitor
the
resource
usages
for
any
hard
paper
check.
F
F
Due
to
this
there's
a
new
release,
version
of
libera,
cosy,
I
pasted,
docker
image,
which
is
a
standard
docker
image
for
elliptic
or
CI.
And
so
this
version
has
the
new
feature,
which
is
your
sis
matrix
parser,
and
it
can
be
used
by
any
hardware
project.
It
can
be
used
there.
Any
hardware
project
who
wants
to
wants
to
have
this
feature
of
yourself.
Isis
wants
to
see
the
monitoring
wants
to
have
the
monitoring
resource
usages
other
than
that.
We
use
that
plugin
of
check
in
stuff
clucking.
F
So
my
work
was
to
convert
the
test,
results
into
tap
format
and
then
publish
the
results
on
tap
plugin
yeah
so
other
than
that
I
wanted
to
make
it
generalize
for
any
hardware
project
so
that
not
only
for
openness,
it
can
be
used
for
any
hardware
project.
So
first
part
was
our
inside.
Even
even
open
risk
is
a
huge
family,
so
I
created,
like
I,
worked
on
creating
a
Python
library
so
that
it
is
generic
for
all
the
projects
which
can't
which
comes
under
open
list
other
than
that.
F
So
these
are
the
results
which
I
want
to
show
like
right
now.
Put
any
hardware
project
begins,
visualize
the
project
we
can
visualize
the
result.
In
this
way
we
can
have
a
cell
count.
We
can
so
yeah.
This
is
by
using
plot
plug
in
this
is
by
using
that
plug
in
so
I
just
want
to
describe
brief
about
the
pipeline
library.
I
worked
on,
so
this
was
open,
RIS
pipeline,
which
is
which
is
generalized
for
any
open
risk
project.
So
I
created
this
pipeline,
you
just
have
to
define
the
job.
F
We
just
have
to
define
certain
parameters.
Then
we
have
few
socks,
so
I
worked
on
creating
I
worked
on
channel
or
generalizing
the
few
soft
invocation
so
that
it
can
be
used
by
various
projects.
It
just
chooses
a
base
docker
image
with
few
sock,
which
we
can
define
in
our
lipra
course.
It
adds
the
library
it
runs
the
fuse
of
steps.
F
Then
then
we
have
your
say,
synthesis
report,
so
your
say
synthesis
report,
so
I
added
this
in
our
lab
request
pipeline
liability.
This
is
quite
generalized.
We
just
need
to
define
the
core
of
any
hard
to
project
the
target,
the
log
path,
and
we
just
need
to
have
a
tick,
a
simple
decorative
call
and
we
can
have
the
whole
your
synthesis
process
going
on
with
the
with
the
results
which
will
be
published
on
Jenkins.
So
this
was
this
was
about
the
project
yeah.
So
what
did
I
learn
in
chuseok
I
learned
about
various
technologies.
F
F
Here
we
have
all
the
links
and
I've
described
my
most
of
the
work
in
blog
post,
so
yeah
in
the
end.
I
want
to.
Thank
you.
My
mental
Oleg
kind
of
supported
me
a
lot
with
all
the
queries
Stafford.
He
is
the
core
maintainer
of
open
risk
for
sea
foundation,
of
in
open
risk
and
jenkins
organization,
definitely
to
provide
me
an
opportunity
to
present
my
work.
A
F
Okay,
I
just
shoulder
yeah
I'll,
just
show
the
the
pipeline,
so
this
is
how
I
create
it.
So
basically,
this
is
for
more
one.
Kids
and
I
did
a
configuration,
so
we
can
see
that
so
it's
a
simple
configuration.
We
just
need
to
call
this
step
like
the
your
sis
report
and
we
just
need
to
set
the
parameters
just
save
it
and
when
we
build
it.
So
I've
already
done
this
because
it
takes
a
lot
of
it
takes
a
bit
of
time.
So
I've
already
done
it
for
the
presentation.
F
So
we
can
see
that
we
have
plot
graphs
for
cell
count.
We
can
see
different
parameters,
for
example,
SPL
UT's
SP
carries
which
were
part
of
this
hard
to
project,
so
we
can
visualize
all
that
thing.
We
can
compare
the
results
according
to
the
dates
if
we
have
any
yeah
and
also
for
resource
usage
like
public
wire
bits,
wire
cells,
memory,
bits,
yeah,.
A
F
So
I
think
this
can
be
so,
as
you
can
see,
okay,
I'll
just
show
so
I
can
extend
my
pipeline
library,
or
so
you
can
see
that
this
is
right
now.
This
is
only
for
monitoring
the
resource
usages
later.
If
somebody
wants
to
see
the
bit
stream
like
going
to
hack
the
bit
strip
paths
or
any
other
parameters
when
FPGA
is
are
connected,
so
we
can
extend
this
pipeline
right
ready
to
have
that
feature.
F
D
All
people
think
maybe
I
could
adhere
a
few
words
about
the
project,
yeah,
so
yeah.
Basically
it's
when
you
work
with
hardware.
It
means
that
you
work
on
not
only
with
hardware,
but
these
dozens
of
different
technology
chains,
including
software,
various
continuous
integration,
DSL
etc,
and
the
analysis
project
is
an
example
of
that.
So
she
was
working
for
github
organizations
with
different
roles
with
different
practices,
and
this
completely
different
technology
sticks.
So
what
CD
languages
for
hardware
projects?
D
It's
a
lot
of
scripting
in
Python
in
the
correct,
but
it's
a
docker
plus
it's
groovy
pipeline
and
also
some
Java,
because
to
be
able
to
dive
into
Jamie's
code
in
some
cases
so
yeah
there
was
a
lot
of
collaboration
across
multiple
organizations
and
the
it
was
probably
the
most
challenging
part
of
the
project,
because
here
we
were
working
in
so
many
different
areas,
but
in
a
nature
the
world.
So
basically
all
the
main
goals
of
the
projects
are
delivered
and
we've
got
some
improvements
for
the
Brecker.
C
is
a
generic
framework.
D
There
is
still
a
lot
of
work
to
be
done
there,
but
it's
going
back
in
the
right
direction.
So
yeah
thanks
a
lot
thanks
if
all
your
contributions,
yeah
and
actually
it
was
sudden
that
we
started
working
on
this
project,
not
in
me
but
in
December.
It
gets
so
Nancy
reached
out
to
liberal
arts
organizations
earlier,
and
we
had
a
lot
of
contributions
which
are
not
listed
in
the
current
presentation
because
yeah
they
be
done
before
the
J
sub
time
thing.
G
A
G
A
G
Okay,
so
yeah
so
I'll
be
presenting
the
Jake
ask
dev
tools,
project.
This
project
comes
under
the
community
bridge,
which
was
a
Linux
Foundation
initiative
that
was
just
started.
So,
as
we
all
know,
Jake
asked
has
a
lot
of
support:
writing
Vimal
files
directly
without
without
any,
without
any,
without
touching
the
Jenkins
UI,
so
the
Jake
as
project.
Actually
one
second
is,
let
me
move
the
things
I'll
be
presenting
here
will
be
just
an
introduction
about
what
I
do.
G
What
am
I
studying
and
stuff
the
problem
statement,
but
what
things
are
missing
in
Jake
asked
whether
I
have
AB
dealing
with
a
broken
scheme,
the
developer
tools
and
I'm,
going
to
implement,
etc
the
community
bridge
or
what
is
it
all
about?
What
are
the
goals
for
the
phases
since
we
have
just
two
phases,
because
the
second
phase
is
to
be
honest,
it's
quite
huge
and
the
status
so
I'll
be
demoing.
Some,
whatever
work
have
been
that,
whatever
whatever
I've
been
doing
and
the
future
plans
of
course.
Okay.
So
let
me
just
go
yeah.
G
So,
although
amatory
our
undergrad
from
Mumbai
University,
I've
interned
at
quite
a
few
companies
in
the
past,
most
notably
the
open
mainframe
project,
that's
currently
going
on
actually
that's
another
initiative
by
the
next
Foundation
and
that
deals
with
all
of
s,
390x
systems
and
stuff.
So
a
lot
of
C,
C++,
programming
and
I've
worked
for
cloudy
was
that
so
Australian
start
up
quite
a
lot
of
Java
there
as
well.
So
as
you
know
that,
since
Java
is
quite
a
strong
background,
Jenkins
I
was
naturally
attracted
to
Jenkins
as
a
project.
G
You
can
find
me
on
github,
Kato
and,
of
course,
my
personal
website
if
anyone
is
interested.
So
let's
move
on
to
the
community
bridge.
Okay,
so
I
came
across
the
community
bridge
project
I
think
in
the
outreach
channel
which
on
which
overlooked
quite
frequently,
post
update,
so
the
I
reached
out
to
him,
stating
that
is
there
a
availability
for
the
community
bridge
project,
and
he
told
me
that
there
was.
He
gave
me
a
range
of
projects
and
said
that
Jake
asked
is
one
that
they
have
all
of
the
foundations
to
undertake.
G
So
the
community
bridge
project
is
one
that
is
hosted
by
it's
a
new
initiative,
that
is
by
the
Linux
Foundation,
and
it
has
a
host
of
projects
under
it
so
under
which
Jenkins
obviously
comes
it
so
yeah
good
okay.
So
the
goal
for
the
community
bridge
project
basically
is
two
phases.
First,
is
the
json
schema
validation?
So,
as
we
all
know,
we
write
a
host
of
IML
files
and
we
have
no
way
of
validating
whether
what
we're
writing
is
correct.
G
So
maybe
you
write
some
Vimal
file
and
you
realize
as
a
typo
somewhere,
so
Jenkins
neither
does
vs
code,
not
IntelliJ.
Warn
you
that
the
yml
file
that
you've
written
is
wrong
and
unless
you
load
it
up
into
Jenkins
and
then
Jenkins
says
that
it's
it's
invalid,
while
trying
to
load
it
up
so
part.
One
of
the
project
deals
with
the
json
schema
validation,
so,
basically
fixing
the
json
schema.
That
was
there
was
that
is
currently
generated
by
jenkins
and
validating
it.
G
G
Basically,
we
are
so
used
to
auto-completion
vs
code
in
IntelliJ
and
various
such
IDs,
so
it
would
be
you
GPA,
ID,
ID
auto-completion
forge
a
cast,
maybe
just
maybe
type
in
system
and
system
message
and
stuff
and
Jenkins
just
sort
of
completes
it
for
us
how
cool
that
would
be
so
for
assisting
me
on
this
project.
I
have
three
wonderful
mentors,
Tim,
Joseph
and
Oleg,
who
will
be
guiding
me
throughout
this
project
and
since
it's
just
I
think
20
days
since
the
project
started.
G
F
G
Time
I
will
so
yeah,
so
a
little
bit
about
Jake
asked
for
those
who
don't
know
I
think
everyone
does,
but
still
so
Jake
asked
allows
you
to
write.
Oh
yeah
Vimal
files
right
out
of
the
box,
no
need
to
there's
no
need
of
clicking
on
different
UI
buttons
and
writing
system
messages.
Maybe
writing
maybe
configuration
of
different
types
of
plugins.
We
have
so
many
plugins
and
Jenkins
going
in
and
configuring
each
one
writing
their
messages
or
how
they
behave.
G
Instead
of
doing
all
of
this,
you
could
just
do
this
so
right,
Jenkins
system,
message,
number
of
executors
and
all
of
your
plugins
suppose.
If
you
have
maybe
the
credentials
plug-in
or
maybe
something
else,
you
could
just
open
up
a
yml
file
load
it
up
and
load
up
the
Jake,
ass,
plugin
and
just
hit
load,
and
this
would
configure
the
UI
without
you
using
any
without
you
using
your
mouse,
basically
so
moving
on.
Okay,
so
phase
one.
G
So
it's
been
many
days
since
phase
one
started
and
we
have
been
working
on
the
generation
of
the
schema.
Basically,
so
the
currents
kheema
that
is
generated
has
been
written
in
jelly
files.
So
basically
XML
executable
XML,
so
the
jelly
the
files
are
currently
being
generated
are
actually
not
up
to
the
draft
standards,
whatever
files
that
have
been
written,
they
don't
validate
at
all,
so
my
first
task
was
to
actually
fix
that.
So
what
I've
done
is
we
have?
G
We
decided
that,
instead
of
following
the
entire
jelly
approach,
we
would
rewrite
it
in
Java,
so
rewriting
in
Java
has
its
own
advantages.
It
becomes
easily
testable
right
out
of
the
box.
It's
easy
to
debug,
going
line
by
line.
If
you
find
anything
wrong
with
the
schema,
you
could
easily
just
fix
it,
make
up
a
pull
request
and
submit
it.
Okay,
some
of
the
other
things
that
the
jelly
files
do
is
they
make
it
very
hard
to
debug
figures.
G
There
are
different
jelly
files
being
called
in
each
of
these
in
each
of
the
execution
steps
by
the
DSL
plugin.
So
it's
quite
is
quite
it's
very,
very
difficult
to
maintain,
so
we
decided
for
a
rewrite
in
Java,
so
the
work
done
so
far.
So
since
we
decided
that
we
would
require
a
rewrite,
we
decided
to
start
right
from
scratch
so
basically
to
generate
a
schema,
we
need
the
plugins
and
for
each
plug-in,
has
its
own
configurators,
it's
descriptors
and
so
on.
So
we
decided.
G
The
approach
that
we
were
going
to
follow
is
take
all
of
these
plugins
take
all
of
their
configurators
and
basically,
whatever
sub
configurator
or
sub
attributes
they
have.
We
would
just
kind
of
pick
generate
a
JSON
object
and
then
generate
the
schema
accordingly,
so
that
was
these
are
step
1
and
step
2,
that
is,
to
generate
the
schema,
configurator
wise
and
basically
make
sure
that
we
follow
the
gelly
approach.
G
So
we
just
didn't
want
to
reinvent
the
wheel
eeeh
we
just
followed
what
the
jelly
files
did
and
basically
just
wrote
it
in
Java,
and
it's
not
easy
as
it
sounds,
because
the
jelly
files
do
a
host
of
things
and
to
replicate
that
in
Java
is
kind
of
it's
kind
of
kind
of
very
difficult,
because
because
it's
it's
not
easy
to
understand
a
JSON
schema.
Okay.
So
now
a
bowtie.
Let
me
just
just
okay,
so
this
is
the
original
ski
freaking
see
my
screen
yeah.
G
So
this
was
the
schema
that
we
that
the
currant
jelly
files
generate.
So,
as
you
can
see,
it
doesn't
validate
very
well.
You
can
see
a
host
of
errors
here,
so
this
is
an
online
tool
that
I'm
using
to
verify
that
the
json
schema
is
correct,
so
you
can
see
that
it
should
be
an
array
and
the
rest
should
the
mismatch
in
schemas
and
one-offs.
G
So
you
cannot
actually
write
anything
you
so
that
it
kind
of
it
kind
it's
kind
of
no
use
actually
to
be
honest,
so
what
we
did
was
we
generated
a
schema
in
Java
and
we
it's
just
six
version.
Six,
as
you
can
see,
we
decided
to
go
with
the
latest
revision.
I
think
version.
Seven
or
it
is
six,
doesn't
yeah,
you
decided
to
go
with
version
7.
So,
as
you
can
see,
the
Jen,
the
schema
generated
right
of
the
box
is
valid
according
to
draft
seven.
So
we
are
making
progress
in
that
aspect.
G
Apart
from
that,
since
this
schema,
you
cannot
validate
anything
against
it.
No
matter
what
you
write,
it
doesn't
fit.
Just
the
schema
is
invalid,
so
doesn't
matter,
but
here,
as
you
can
see,
since
the
schemas
valid
you
are
allowed
to
make
change,
you
can
actually
verify
that
the
JSON
that
you're
passing
is
correct.
So
now
you'll
be
wondering.
Why
am
I
passing
a
JSON?
So
what
we
do
is
we
take
a
vial
file
that
Jenkins
has
and
we
convert
it
a
JSON
and
then
validate
against
the
json
schema.
G
G
Yeah,
so
a
number
of
executors
yeah
boom,
so
the
document
validates
against
the
schema.
So
this
is
a
valid
schema.
The
moment
you
decide
that
your
number
of
executors
should
be
how
the
world
should
be
an
integer,
so
yeah.
So
basically,
this
is
what
we
have
done
so
far,
we've
managed
to
make
sure
that.
F
G
Nesting,
simple
nesting
is
valid.
The
moment
you
shift
on
to
more
levels
of
nesting.
It
becomes
quite
difficult
to
violate
the
schema
because,
as
you
can
see,
we've
we
followed
the
gelly
format
so
that
didn't
handle
nesting
very
well.
So
that
is
one
of
my
future
goals
that
I'll
keep
talking
about
in
my
presentation.
G
If
I
could
just
go
on
yeah
future
plan,
because
I
am
done
with
kind
of
presenting
some
of
my
work,
the
future
plan
would
be
first
of
all,
to
fix
the
nesting,
so
support
nesting
of
Vimal
configuration
file.
So,
as
you
go
deeper
and
deeper
into
mavin,
generation's
and
J,
decays
and
stuff,
we
need
we
need
our.
We
need
our
validator
to
kind
of
validate,
all
of
that,
so
that
is
actually
phase.
One
I've
put
it
in
C
or
it's
not
priority
wise.
But
still
this
is
priority.
G
Number
one
try
D
number
two
is
to
figure
invoke
validation
before
application.
So,
basically
now
there
is
no
validator
I.
Think,
as
Joseph
told
me,
so
we
need
to
maybe
validate
it
before
applying
the
schema
so
that
it's
much
easier
for
the
developer
to
figure
out
what
he
is
doing
and
the
third
one
is
addition
of
custom
configurators,
so
developers
can
add
their
own
configurators
according
the
plugin.
G
So
basically,
we
were
thinking
of
developing
some
sort
of
an
conflict,
an
epi
where
the
developer
just
puts
in
his
plugin,
and
we
just
pick
the
descriptive,
the
attributes
and
stuff
in
this
bang.
We
generate
the
schema
according
to
our
requirements,
so
phase
one
means,
in
approximately
two
weeks
holy
told
me
to
be
a
bit
careful
with
the
future
plan.
F
D
Community
yeah
thanks
what
for
slide
in
for
working
on
this
project,
because
it's
a
new
experiment
for
us.
It's
also
really
available
to
the
community,
because
the
identification
is
code
isn't
new,
but
we've
got
the
modern
effects
on
all
the
installations.
Since
it
was
announced
and
yeah,
it's
just
skyrocketing,
so
they're
released
every
week,
some
releases
I
break
the
configurations
and
its
really
essential
for
users
to
have
access
to
schema
so
that
they
can
really
date
their
configurations
before
applying
them
and
same
for
development
tools.
D
So,
basically,
my
vision
is
not
on
the
IDE
auto-completion,
but
also
validation
and
into
the
deployment
in
an
ad.
So,
for
example,
as
a
user
I
can
take,
one
idea
see
visuals
to
the
airport
or
IntelliJ
IDEA
and
I
can
manage
my
instance
from
there
was
all
kinds
of
development
tools
for
configuration.
Management
I
mean
you
have
to
mind
if
configuration
management,
so
it
would
be
the
end
goal
and
the
project
just
starts.
So
there
is
a
lot
of
things
to
complete,
but
there
was
already
some
progress
and
this
is
Beit
thanks
yeah.
H
A
H
G
G
Yeah,
so
we
are
Martin,
we
actually
we
actually
pick
up
the
configurators,
basically
from
every
from
each
and
every
plugin,
and
so
the
type.
Obviously,
since
we
need
them
to
be
since
the
basic
on
base
configurators
our
object
and
all
of
the
nesting
comes
under
it,
so
we're
basically
picking
up
most
of
the
configurators
and
having
that
types
already
hard-coded
and
as
we
go
into
nesting.
That
is
the
problem.
G
Actually,
as
we
go
into
nesting,
so
we
need
to
define
their
properties
properly,
because
if
we,
if
we
get
any
of
the
properties
wrong,
the
nesting
doesn't
work
and
your
schema
isn't
isn't
of
any
use.
Although
it
will
be
valid,
it
won't
be
of
any
use.
So
this
is
what
we
are
trying
to
work
on
that
when
we
go
into
levels
of
nesting,
that
is
once
we
put
in
the
properties
that
the
further
the
further
kind
of
integrations
that
are
done
for
the
schema
are
actually
valid
and
the
nesting
is
probably
done
properly.
G
A
A
Well,
I'd
like
to
thank
all
of
the
reason
the
presenters
today,
it
was
very
awesome.
I
know
everybody
has
put
in
a
lot
of
hard
work
to
this,
so
I
am
very,
very
happy
and
I'm
very
thankful
for
everybody,
so
definitely
take
a
moment.
Take
a
bow
for
yourself
and
be
thankful
for
what
you've
put
forth.
This
concludes
our
presentations
for
today.
Does
anybody
have
any
questions
in
general
about
anything
that
they've
seen
if
they
would
like
to
talk
about.
A
Taken
how
to
join
yes,
thank
you.
Well,
since
you
asked,
I
will
go
ahead
and
let
everybody
know
so.
We
have
a
google
Summer
of
Code
ghetto
channel.
We.
That
is
one
way
you
can
join
another
way,
as
you
can
send
an
email
to
our.
We
have
a
Google
Group,
which
is
a
google
Summer
of
Code
jinkins.
All
you,
you
know,
if
you
don't
want
to,
you
know,
ask
out
right
you're
more
than
welcome
to
approach
any
of
the
the
mentors
I'm
sure
the
students
would
love
to
talk
to
you.
A
The
org
admins
will
talk
to
you
all
day
long,
so
be
careful.
If
your
ask
there
I
joke
when
I
say
that
please
feel
free
to
ask
any
any
of
us
what
we
can
do,
there's
so
many
projects
that
we
have
there's
so
many
ideas
out
there.
So
what
I
really
would
like
to
say
is,
as
a
lot
of
you
understand,
that
the
Jenkins
project
is
an
open-source
project.
We
try
to
be
very
diverse.
We
try
to
be
a
very
inviting
community
and
very
helpful.
A
So
if
you
feel
that
you
know
I,
don't
want
to
ask
in
public
talk
to
one
of
us
for
any
of
the
people
that
were
at
Jenkins
world
you'll
know
just
the
org
admins
I
can
speak,
for
we
are
super
super
approachable
and
by
and
large,
this
community
is
very
approachable.
A
lot
of
our
SIG's
need
help.
We
need
more
people.
A
We
cannot
do
this
project
as
a
whole
without
everybody
chipping
in
even
if
it's
something
as
little
as
working
on
a
dock
or
just
asking
hey
I
only
have
an
hour
a
month
that
I
can
dedicate
what
can
I
do?
We
will
help
you
get
involved
in
the
open-source
community,
but
more
sort
mo
more
so
towards
the
jenkins
for
the
jenkins
google
Summer
of
Code
project.
A
A
You
can
reach
out
to
any
of
the
org
admins
I
want
to
thank
the
Oregon
mins.
This
is
a
very
dedicated
thing.
We
spend
a
lot
of
time
making
sure
this
is
good.
I
want
to
thank
all
of
the
mentors
they
give
this
is
we
don't
get
paid
to
do
this?
Everybody
dedicates
their
time
to
make
this,
but,
more
importantly,
and
by
and
large,
none
of
the
google
Summer
of
Code
is
possible
without
the
students.
A
What
you
all
do
is
nothing
shy
of
amazing,
because
you
put
forth
you
take
sometimes
the
criticisms
and
that,
but
the
guided,
of
course
it
is
so
awesome
with
that.
We're
now
coming
to
the
end
the
thing
to
started
what
seems
like
an
eternity
ago,
so
thank
you
all
very,
very
much
and
I
would
like
to
just
just
give
you
a
round
of
applause,
and
thank
you
very
much.
Would
anybody
else
like
to
add
anything.
D
Well,
I
will
later
that
we
will
make
sure
to
post
all
links
in
the
meter
page
and
if
you
want
to
contribute
a
when
it
goes
out
do
so,
there
is
a
number
of
opportunities
and,
for
example,
in
one
month
they
will
be
Oktoberfest
and
we
will
make
sure
to
participate.
So
if
you
have
some
ideas
for
smaller
projects
for
especially
for
newcomers
and
those
experience
contributors,
so
let
us
know
because
we
can
use
them
as
a
source
for
Oktoberfest
and
other
hackathons.
We
want
organized
over
the
year.
D
A
Welp
that
concludes
this
presentation
also
note
that
there
will
be
a
third
presentation
for
the
outreach
e
things
that
I
mentioned
at
the
beginning.
There
is
a
doodle
currently
going
around
to
firm
up
the
times,
for
that.
So
do
look
out
for
that.
If
nobody
has
any
other
questions.
That
concludes
this
meeting.
I.
Think
you
all
for
taking
the
time
out
of
your
busy
schedules
to
sort
of
celebrate
our
students.
B
B
I
learned
them,
I
learned
about
them
personally,
so
it
was
really
nice
and
so
just
a
personal
experience
that
I
also
got
a
job
because
of
Jenkins
ji-sung
is
itself
a
really
nice
addition
to
your
profile,
but
in
addition
to
that
being
a
part
of
Jenkins
which
is
really
popular
in
the
organizations
that
use
it,
and
so
it
really
is
a
nice
organization
and
very
helpful.
So
I
like
to
request,
if
you
ever
want
to
participate
in
T.
B
D
D
And,
of
course,
we
should
say
thanks
to
mobile
as
well,
because
he
isn't
free,
even
if
mentors
and
doing
get
paid
organizations
and
get
some
stipend.
For
example,
I
mean
usually
steep
enter
this
year
to
sponsor
trips
of
our
students
to
join
his
work
and
other
conferences,
so
here
step
until
those
two
sponsoring
student
projects,
but
he
also
our
students
it's
different
and
yeah.
Basically,
it's
still
ten
thousands
of
dollars,
invest
by
Google,
just
in
Jenkins
project
and
also
I,
think
is
just
one
project.