►
From YouTube: GSoC: Phase 1 demos by students
Description
Jenkins Google Summer of Code students will present the current statuses of the projects and show demos. We will have 3 projects presented: Code Coverage API Plugin, Remoting over Kafka, and Simple Pull-Request Job Plugin.
More info about projects: https://jenkins.io/projects/gsoc/
A
A
If,
if
you
have
never
participated
in
JSOC
before
it's
one
of
them,
most
popular
open
source
initiatives
and
one
of
the
biggest
ones,
it
has
more
than
30,000
students
all
over
13
years,
and
there
are
hundreds
of
open
source
organizations
which
participated
in
this
project.
Generally,
students
work
with
open
source
organizations
in
order
to
work
on
open
source
projects
a
it's
considered
as
a
kind
of
summer
internship,
it's
a
full-time
program,
so
students
code,
almost
full-time
or
by
the
way,
do
I
show
you
the
screen.
A
A
Okay,
so
good
start
yeah.
So
what
I
was
going
to
say
that
a
JSOC
is
the
most
popular
projects?
Students
work
almost
full-time,
and
this
is
the
second
year
when
Jenkins
participates
in
google
Summer
of
Code.
So
we
have
three
students
this
year.
If
you
interested
to
know
more
about
google
Summer
of
Code,
you
can
visit
resources
on
jenkins
website.
A
So
we
have
a
separate
project
page
where
you
can
find
on
automation
above
G,
so
we
have
multiple
blog
posts
so
on
JSA
or
for
this
face
they
will
also
blog
post
by
students,
and
we
also
have
neither
channel
where
you
can
discuss
everything
about
diesel,
so
miss
Kay.
As
I
said,
we
have
three
projects.
She
knew
Jane.
It
was
working
on
code
coverage,
API
plug
in
Bhutan
works
on
the
motor
cover
kafka,
which
includes
plug-in
and
client,
so
that
agents
can
communicate
over
remoting
and
Abhishek.
A
Gautama
is
working
on
a
simple
pull
request,
job
plug-in
and
we
had
other
projects
announced,
but
unfortunately,
the
students
who
were
unable
to
participate
so
yeah.
Basically,
we
have
three
projects
and
yeah,
even
if
it's
just
the
first
coding
phase
demo.
Actually,
there
was
a
long
discussion
before
so
and
long
process
before
so
the
restart
that
discussions
about
G.
So
in
December
in
night
February
the
projects
were
announced.
A
So
if
you
have
any
questions
during
the
presentations,
please
use
jenkins
RC
channel
on
freenode
or
our
guitar
channel.
I
will
be
monitoring
all
these
resources
and
if
you
have
any
questions,
I
will
pass
them
to
students,
but
yeah,
and
the
main
agenda
for
today
is
of
course,
presentations
by
student.
So
we
will
start
from
G.
You
will
present
code
coverage
API,
then
I
will
have
remote
ink
and
then
we
have
a
simple
request
job.
So
that's
it
from
me
to
you.
Are
you
ready.
C
Yeah,
so
so
so
my
project,
my
project,
is
called
College.
Api
I
have
participated
in
this
year's
G
stock
and
am
a
project
is
taking
the
core
ecology,
API
plug-in
and
my
mentors
Stephen
crypto
super
Jeff
and
Eric
and
take
you
me
so
much
have
helped
in
this
project,
and
I
am
very
appreciative.
So
about
me
my
name
is
the
same
vision,
and
this
is
my
github
account.
C
I
am
master
D,
a
student
in
computer
science
and
the
technology
at
Hanoi,
University
from
China
I,
like
programming
and
reading,
especially
reading
some
book
about
historic
history
and
Fusaro,
first
Rafi,
so
why
we
needed
this
project
project?
Why
we
needed
this
plug-in
I
think
Isaiah
several
reasons.
First,
there
are
a
lot
of
proteins.
We
should
current
Lee
implementer
code
coverage.
For
example,
we
have
commercial
protein,
we
have
jacoco
plugin,
we
have
a
crawler,
probably
and
so
on.
So
this
we
have
was
so
much
so
many
talking
about
her
could
hardly
know
if
whoa
yeah.
C
Well,
how
do
we
have
more
code
code
coverage
cause?
Maybe
we
need
more
code
coverage
plug-in,
so
it
is
part
of
our
more
generic
prog
into
integration.
Team
also,
the
second
most
code
coverage.
How,
with
the
same
structure,
you
need
to
say
or
college
reports
can
be
represented
by
true
structure.
She
can
she
can
be
passed
to
true
true,
you
know
each
metric
can
have
our
child
knows
each
and
the
parent
knows
so.
The
structure
of
a
cold
cow
little
pot
is
the
same.
So
is
most
college.
C
It
was
how
would
a
similar
content,
it
is
say,
for
example,
for
example,
we
all
have
similar
felt
like
a
mister
like
car,
with
the
land
branch,
mr.
branch
cada,
so
be
how
so
for
socially
product
take
how
similar
content.
So
there
is
so.
This
is
why
we
need,
which
is
probably
we
can
have
a
plug-in
to
do
the
most
repeat
things
for
them
so
that
they
can
to
only
cop
hat
and
it's
a
most
of
you.
C
Peter
walk
like
past
past
reporter
and
like
founder
reporter,
we
can,
or
we
can
can
be,
can
all
be
done
by
our
party.
So
we
add
we.
As
we
have
said
before
me,
we
can
have
a
plug
into
the
most
early
Peter
walk.
So
what
is
the
most
of
you?
Peter
work
for
most
courage
to
plug
in
they
usually
do
many
do
three
things:
they
finally
pause.
C
They
pass
reports
and
if
they
show
the
reports
so
be
so
co2
the
same
thing
as
so,
but
so
we
can
so
we
can
so
you
can
have
a.
We
can
have
a
courage,
program
issue
to
all
the
things
same
and
so
that
the
other
college
programs
only
needed
to
Lansing
come
when
to
be
pause.
So
how
commendable
pass
and
what
what
is
common
to
pose
in
code,
ecology,
API
protein,
the
basic
we
have
four
basic
process.
C
First,
we
found
color
to
the
post
according
to
you,
just
configure,
then
use
other
paths
to
commend
reports
into
or
a
standard
format
the
past
and
formal
reports
and
agree
to
them
finally
surpassed
the
results
in
a
chat.
So
we
have
found
reports
for
all
core
ecology
fork
for
all
code
calls.
It
was
and
we
have
passed
those
reports
we
have
shows
us
reports,
other
proteins
or
only
need
one
see.
You
add
a
path
to
true.
Only
neutralizing
come
when
the
report
into
our
standard
format.
So
this
is
our
protein
structure.
C
C
C
Please
life:
we
have
those
tasks:
prototype
based
on
commercial
provision,
data
model,
integrate,
add
the
Java
code
coverage
at
all
and
all
the
tech
support,
how's
the
product
and
so
on.
I
will
show
each
own
labor
demo,
so
you
can
have
live
a
demo
with
per
minute.
I
will
okay,
so
in
code,
ecology
plug-in
you
can
configure
by
a
two
way
by
two
ways.
Why
do
you
disturb
her
configure?
C
We
have
a
detector
knocking
them
which
can
found
out
report
automatically
and
go
for
team
into
is
correspondent
and
a
pad
so
that
we,
we
are
not
needed
to
figure
out
what
it's
a
leap,
renamed
or
ecology
tourjournal.
It
is,
and
also
we
can
specify
you
to
manually
like
that,
we
can
specify
later
to
jacoco
XML
file
and,
like
that
also
we
have
work.
C
Also,
we
have
a
global,
slash,
folder,
which
you
can
specify
to
/ho,
specify
issue
/
folder
with
health
structure
and
stable
/
like
that,
and
we
can
have
and
build
a
group
of
options
which
can
fail
the
build
so
far
if
child
unhealthy
/
so
also
we
have
a
/
holder
for
each
a
d-pad
it
can
make
it
toast
seems
more
flexible
and,
for
example,
we
can
specify
such
holder
for
files
for
18,
because
verse
5.
We
can
specify
how
/
holder
to
18400
for
parametric
padded.
We
can
set
her
jacoco
to
19,
like
that.
C
C
It
is
before
it
is
a
random
gender
chat,
but
we
or
we
have
used
the
same
or
before
so
you
see
the
it
is
no
change
so
also
we
can
hide
up.
You
should
hide
each
matrix
under
show
it
like
that.
We
have
and
we
have
a
file
say:
oh
okay,
Farrell
95,
so
this
is
the
trader
truck.
Also
we
can
have
a
summary
chart.
This
is
a
much
harder
for
current
calendar
magic.
C
C
C
C
So
we
can,
we
can
configure
it
up
by
para.
This
one
is
a
pepper
support.
Oh
I,
hosted
pepper,
I
am
okay,
wait.
A
minute.
I
will
show
my
another
window.
Oh
sorry,
I
will
show
my
yeah,
so
this
is
all
Pamela
we
have
I
behaved.
Should
we
have
set
it
to
publish
ecology
and
the
center
of
you
take
a
pass
set.
It
the
other
paths
and
like
that
we
also
have
you
the
we
also
use
well
push
you
to
do
this
build
this
project.
This
project
is
a
commercial
protein.
C
So
we
have
configured
configured
up
configured
reporter
trainer
with
email
and
sale.
Okay,
so
we
have
configured
co-co-co
generate.
You
have
a
configure
commercial
generated
generation.
So
this
what
this
well
generator
culture
pot
than
me,
which
the
packaging
phase
okay.
So
we
should
look
to
add
other
path.
C
C
C
C
C
D
C
C
A
C
If
you
press
that
was
in
phase
1,
prime,
we
have
in
phase
1,
probably
have
all
those
tasks
and,
as
you
can
see
in
my
my
screen,
sharing
before
how
tell
them
I
have
done,
I
hope
turned
him
off.
First
I
have
using
commercial
are
probably
in
the
model
to
build
the
prototype
and
integrator
and
integrator
jacoco
coverage
at
all,
and
also
how
awfully
taxed
border.
Also,
how
health
report
supporter
and
the
paper,
a
supporter
and
the
threshold
support,
also
modernize
reporting
and
how
some
more
unit
tests.
So
this
is
the
current
status
phase.
C
C
We
are
men
in
2000,
first
integrated
kabbalah
problem
with
the
core
ecology
API.
It
is
me
cabal
poking
us
also.
We
have
integrated
Kabat
rajbhog
in
a
path
between
how
back
for
the
capacity
if
we
have
if
we
use
the
capacity
of
Hawaii
before
we
cannot
comment
on
the
report,
her
to
or
colander
colander
report,
so
I
will
plan
to
integrate
the
capacity
of
Hawaii
and
Akita
back
for
back,
can
passage
and
so
user
can
move
from
kebab
can
plug
into
our
plug-in
without
it
with
any
any
history
called
history.
C
College
report
and
the
second
is
the
provider
Java
API
and
the
RESTful
API
for
get
for
getting
college
information.
It
means
that
others
can
through
Java.
If
you
are
a
RESTful
API
to
get
a
college.
Information
like
her
like
so
Dante
can
take
I
use
those
information
in
their
own
dashboard
and
eat
her
mix
util
makes
the
area
makes
the
others
Malita
to
to
integrate
other
integrator
money
before
entire
dashboard
and
exam
we
panda
to
implementing
abstract
layer
for
other
report
format.
Thank
you,
Jason.
C
Now
the
only
support
a
supporter
XML
fail,
so
the
next
phase
I
plan
to
implement
her
jason
report
format.
Second
result:
we
plan
to
support
a
comment
for
no
Java
language.
For
now,
we
only
support
a
Java
language,
Java
Java
called
the
college
Attalla
culture,
cocoa
and
capella.
Next
is
I
plan
to
support
other
language,
and
also
we
plan
to
score
the
compact
combining
the
post
building
a
Buda.
It
means
we
can
call
a
publisher
college
market
ham
in
in
one
pewter
and
we
can
integrate
them
together.
C
C
A
A
C
C
A
A
E
A
B
So,
just
kind
of
like
a
a
quick
overview
of
the
whole
thing:
I
guess,
yeah
I
guess
share
pretty
much
covered,
I
guess
everything
that
was
kind
of
needed
for
it.
We
finished
I,
guess
his
slides
kind
of
showed
like
we
completed
a
lot
of
the
initial
tasks
and
we
have
a
lot
more
kind
of
heading.
The
way
for
the
next
phase
as
well,
including
trying
to
integrate
with
the
new,
are
trying
to
integrate
with
the
the
current
cobertura
plugin
to
make
this
available
even
for.
B
A
So
my
point
of
view
should
use,
definitely
read
the
schedule,
so
one
of
the
things
that
we
had
chose
the
demo
of
the
plugin,
if
I
recall
correctly
on
the
second
day
of
coding
phase.
So
even
at
that
point
we
already
did
some
progress
and
yeah.
It
was
a
nice
to
see
how
the
project
improves
over
this
phase
and
I
would
say
that
the
Cheniere
was
working
mostly
independently,
so
we
were
doing
a
lot
of
sync
ups,
etc,
but
he
was
the
one
who
was
defining
the
plan
and
priorities.
A
F
You
can
see
my
screen:
yes,
yeah.
Okay,
so
you
know
everybody.
So
this
is
my
presentation
for
google
Summer
of
Code
for
the
first
evaluation,
so
my
project
is
xanthines
remoting
over
menses,
mousse
and
Q,
and
some
quick
introduction
so
I'm
a
final
year,
computer
science
student
from
Singapore-
and
this
is
my
first
time
participating-
who
go
somewhere
code
and
contribute
to
an
open
source
of
annotation
and
working
together
with
me.
I
have
two
mentors
all
and
subpool,
as
jisub
mentor
and
also
I
have
to
support
from
Jeff
and
David.
They
are
developed.
F
Those
of
the
remove
team
project,
so
I
will
give
some
overview
about
the
project.
So
currently
we
have
Jen,
please
use
TCP
as
a
communication
protocol
for
the
master
and
asian
master
Asian
communication
and
which
TCP
we
have
some
problems
for
this.
If
the
connection
other
asian
fills
the
view
files
and
we
have
to
restart-
is
over
again
another
issue
we
may
encounter
is
we
have
the
traffic
prioritize,
prioritization
and
managing
communication?
This
impacted
Jenkins,
scalability
and
stability.
F
Layer
in
Jenkins,
so
why
we
use
Kappa
so
at
first
we
we
tell
you
about.
We
decide
about
the
using
the
vegetation,
gnome
ssq,
such
as
rabbitmq
or
80
mm
view,
then
after
some
discussion
we
decide
to
use
after
because
is,
this
might
have
some
suitable
features
which
made
suitable
for
same
things
remotely.
So.
The
first
reason
is
Kafka
is
not
a
cube.
It's
not
a
traditional
view.
It's
a
distributed
and
replicated
commit
lock.
East
have
to
remove
the
message
deliver,
which
might
have
to
remove
the
message.
F
F
So
yes,
I
plan,
because
the
project
is
self-contained
consists
of
many
components.
So
we
want
to
deliver
the
project
as
a
set
of
computers
now
compose
components.
We
have
a
Kafka
cluster,
then
in
master
with
a
plug-in
inside
and
a
custom
Asian
wish
to
connect
with
master
using
using
Daphna,
and
in
the
first
side
we
want
to
create
a
POC
with
a
new
conventions
for
implementation.
To
support
Kafka,
so
it
involves
a
basic
things
such
as
command,
command,
invocation,
remote
method,
invocation,
class
opening
and
data
shipping.
F
So,
in
order
to
do
this,
we
have
we
need
to
implement
a
new
convention
zone
and
we
need
to
also
need
to
do
change
in
reporting
and
core
to
make
them
accessible
and
in
the
end
of
the
first
day,
we
want
to
decide
whether
we
should
you
can
craft
or
not
in
our
final
period,
implementation
and
an
optional
one
is
we
want
to
release
and
unfasten
of
the
plugin
by
the
end
of
the
first
day,
so
the
proposal
is
soloed.
So
first
we
have
a.
F
F
The
producer
and
consumer
program
inside
the
next
part
is
I,
have
a
removed
ink
after
plucking,
so
the
we
should
do
is
provide
a
configuration
for
master
to
connect
the
master,
to
connect
to
a
fan,
NGO
connection,
to
a
gene,
and
so
will
be
a
custom
agent
which
use
custom
conventions
for
to
connect
to
master
and
all
these
things
like
a
packaging,
a
package
using
docker
compose
so
to
give
an
overview
of
the
DSi.
So
we
have
them
in
semester
and
we
have
the
remote
ink.
F
After
plugging
in
side,
we
have
the
calf
that
global
configuration
where
we
we
can
specify
the
connection
to
the
CAFTA
truster
and
also
there's
a
Kaffir
computer
launcher
with
extender
a
system.
Computer
launcher.
We
use
the
command
the
the
new
commands,
also
to
connect
to
Kafka
to
do
the
command
to
do
the
communication
and
similarly,
from
the
Asian
side,
we
also
use
the
new
convention
squad
with
engine
with
a
custom
engine
to
do
the
connection
as
well
as
we
banned
all
the
removed
in
Asia
in
the
region.
F
F
F
F
F
F
F
A
A
F
Okay,
so
I
there's
a
class
named
classic
conventions.
What
including
promoting
one.
So
what
I
have
done
is
explained,
extended
synchronous
conventions
for
me,
so
what
I
have
done
is
I
had
and
the
similarity.
So
this
classic
convention
sought
extend
the
synchronous,
operation
and
Easton
is
send
a
comment
as
a
it
least.
I
realized
a
comment
as
a
rivalry
and
say
no
vodka.
F
F
A
A
F
C
A
F
I
should
either
Asian
lunch
then
okay,
I
can
maybe
I
can
show
the
code.
So
so
we
have.
We
have
this
and
jingle
Java
I,
just
called
me
over
and
modify
before.
I
mean
it's
not
completed
yet,
but
I
just
copy
it
for
a
few.
So
we
have
engine
dot,
Java
engine
keys
or
removing.
If
I'm
not
wrong,
then
I
just
copy
over
and
do
the
channel
set
up
with
new
convention
spot.
F
Yeah
so
from
the
Africa
yeah
from
the
you
know,
we
override
the
lunchmeat
on
and
we
call
the
saginomiya.
So
this
search
and
no
we
have
to
yeah.
So
this
is
a
patch
in
jenkins.
Car
we
use
a
custom,
I
mean
is
the
yeah.
We
use
a
custom,
a
new,
such
animators,
we
check
and
the
arguments.
It
consists
of
Genovia
conventions
for
and
easy
to
set
up
the
channel.
A
A
A
F
F
F
So
because
we
you
have
some
issue
some
small
issue
with
it
in
contention
and
also,
we
need
to
wait
for
the
call
and
the
remove
thing
to
be
released
so
goodly.
We
can
not
release
by
the
end
of
this
race
yeah.
So
for
the
next
I
plan,
there
are
some
some
plan
inside
so
firstly,
we
need
to
support
the
security
for
the
master
and
agent
communication,
because
yeah,
currently
we
don't
have
any
security
mechanism
model.
F
Next
thing
is,
as
I
said,
we
want
to
improve
the
GAF
Kapoor
user
consumer
model
to
ensure
the
reliability,
and
we
need
to
do
bug
fix
things
and
yeah.
We
decide
to
move
to
release
the
anti
project
in
the
second
phase.
There
are
my
bees
and
other
features
which
might
be
helpful,
so
the
first
one
is.
We
want
to
use
Casa
to
store
the
log
file
chance
to
over
avoid
the
overloading
of
channel
and
real
king
of
system
comment.
F
Yeah
and
another
thing
is
going
to
stop,
bundling
remove
being
in
the
claim,
as
well
as
we
can
charge
some
message:
encryption
between
captor
but
yeah.
This
is
other
features
which
might
be
good,
so
this
is
some
useful
in
so
we
have
YouTube
repository
the
gto
channel,
the
density
in
I/o
project
bed
and
the
blog
post,
which
I
took
of
the
issue
by
their
anniversary
so
yeah.
This
is
the
end
of
my
presentation.
So
if
some
time
for
Q&A.
E
A
A
F
A
A
A
Task
force
a
different
community
bonding
and
mutual
coding
phase,
but
it's
great
that
you
have
a
prototype
working
at
the
end
of
the
first
phase,
it's
something
which
was
a
kind
of
top
expectations'
for
the
first
phase
and
we'll
try
and
achieved
that.
Obviously
there
are
many
topics
to
consider
like
security
also
and
I/o
and
performance.
So
but
it's
just
a
just
phase
and
we're
a
still
have
eight
weeks
of
coding,
ahead,
yeah
from
my
completed
what
we
stated
and
the
loss
of
plate
recording
sessions.
A
A
G
Yeah
yeah,
as
you
mentioned,
I,
think
it's
a
big,
complex
project
because
you
need
to
study
the
low-level
distributed
code
base
so
but
as
of
now,
we
have
the
working
prototype.
So
that's
a
great
achievement
and
he
did
a
good
background
study
during
community
funding
period,
which
messaging
protocol
is
suitable,
so
and
yeah
I.
Think.
A
Okay,
yeah
and
I
would
explicitly
mention
that
it
was
me
and
soup-bone
have
experience
with
rabbitmq,
so
our
kind
recommendation
was
totally
consider
RabbitMQ
but
yeah,
but
on
complete
solutions.
Then
I
said
that
Kafka
would
be
preferable
for
this
case.
He
justified
that
and
yeah.
That's
why
we
have
taken
Kafka
and
it
proves
to
be
a
successful
choice.
So
yeah
I
think
it's
also
a
good
thing
to
highlight.
D
Yeah,
so
I
am
I,
am
ambition
Gotham.
This
is
my
first
time
participating
in
Lua
Summer
of
Code
and
I
am
working
on
simple
request.
Job
blogging
project,
so
I
am
a
third-year
compression
student
from
India.
My
college
is
when
Chris
place
for
the
National
Institute
of
Technology
and
I
have
done
some
intense
two
internships
in
game
game
program
as
a
gaming
programmer
and
I
am
also
part
of
a
sim
chapter
and
Google
student
develop.
D
D
So
there
is
some
time
prior
work
related
to
I
am
Ellen
Jenkins.
First,
when
it's
Travis
Vimal
plug-in
what
it
does.
It
takes
Travis
for
a
mill
and
tries
to
run
it
as
a
pipe
ends
of
a
Jenkins,
and
it
does
not
support
external
pull,
requests
and
also
Travis
environment
is
very
different
from
Jenkins,
so
it
doesn't
make
sense.
We
use
that
and
also
it
fits
laughs.
It
has
a
last
tomato
14,
November
2016
and
next
one
is
coal
ship
plugin.
D
D
So
it
has
been
decided
that
this
plug-in
will
be
built
on
the
top
of
multi
branch
pipe
and
plug-in
because
it
provides
a
nice
interface
to
show
branches
and
pull
requests
separately,
and
it
also
detects
trusted
religions
in
the
repository
so
that
wrong
wrong.
The
revision
should
not
will
build.
Also,
it
publishes
status
reports
to
the
platform's,
github,
bitbucket
or
bitmap,
so
many
functionalities
will
be
inherited
from
deck.
Only
then
we
have
decided
to
convert
the.
D
Also,
environment
users
will
be
able
to
specify
scripts
without
the
extension
of
the
script
like
on
UNIX
systems.
We
need
a
dot,
SH
script
to
run,
but
on
Windows
system
we
need
a
dot
bad-bad
script
to
run,
so
you
just
will
only
specify
the
path
of
the
script
without
extension
of
the
script,
and
this
plug-in
will
give
that
which
machine
it
is
running
on.
If
it
is
UNIX
machine,
then
it
will
append
dot
SH
at
the
end
of
the
path
will
turn
this
trip,
as
it
will
appended
back.
D
So
the
things
available
now
our
users
are
able
to
build
the
pull
requests
using
Jenkins
file,
dot
yml
there.
It's
a
good
step
implementation,
which
users
will
not
be
using
explicitly,
but
it
will
be
used
by,
but
this
tab
will
be
called
by
the
plug-in
itself
in
case
the
we'll
build
is
successful
and
all
test
cases
are
passing
and
you
just
just
able
to
specify
that
they
want
the
pull
request,
changes
to
be
pushed
to
the
target
repository
or
not
in
case
the
build
is
successful,
use
we
can
call
user
strips
for
we
care
agent.
D
Confirmation
is
fully
supported.
We
we
can
specify
any
type
of
agent.
We
can
label,
we
can
use
the
Aqua
file,
we
can
use
docker
as
well.
If
this
we
can
harvest
the
results
and
reports,
it
supports
genuine
fireworks
and
artifact
artery
artifact
steps
and
a
basic
interface
to
parse.
The
Vimal
and
converted
to
the
declared
a
pipeline
has
been
implemented.
D
Yeah
then
there
is
a
build
configuration
then
we
can
do
we
can
select
by
Jenkins.
Why
am
L
here
and
in
grant
sources?
We
need
to
specify
the
github
right
now.
I
have
lit
up
only,
but
you
can
specify
bitbucket
and
you'd
love.
Also,
the
the
plugin
has
not
been
tested
for
them
till
now,
but
it
will
be
done
in
next
40
days,
so
you
can
specify
get
credentials
here.
The
owner
of
the
repository
can.
D
D
D
D
D
D
And
the
Bimal
file
I'm
using
is
this
one
in
this.
This
part
is
not
being
used
for
now
for
the
follow
demo.
It
has
the
agent
specifications,
it
has
test
results,
it
has
find
bug
vehicle
configure
and
these
are
the
stages
the
these
are.
This
is
the
name
of
the
stage.
This
is
the
script
which
will
call
in
this
stage
and
likewise
following
and
we
have
artifact
say
archive
I,
protect
property
in
which
we
can
give
the
path
to
dark
artifacts,
which
we
want
to
say
so
the
plumbing
has
generated
this
declarative
pipeline
from
here.
D
You
can
see
the
docker
specification
here.
This
is
the
image.
This
is
the
arts
we
have
specified
in
the
environment,
you
can
see
the
wire
here
and
these
are
the
stages.
This
is
the
script.
If
the
instance
will
be
UNIX,
$10
schedule,
Collins
dot
bite
will
be
called
after
the
build
we
have.
We
are
archiving
the
artifacts
here
and
in
the
after
test
stage
in
success,
we
are
leaving
j-unit
step
to
publish
the
test
results
and
in
and
the
find
bugs
step
is
used
here.
D
So
if
you
scroll
down,
you
can
see
that
the
cool
pull
request
has
been
fetched
and
it
has
been
merged
to
the
target
branch.
Here
you
can
see
that
office,
specifically
docker
special
specifications
has
been
applied
and
the
bail
will
be
will
be
run
in
the
rocker
container.
Here
is
the
bill.
The
bill
has
been
started
and
yeah
Esther
and
Ronnie.
For
now,.
H
A
A
D
So
that
Biggs
and
I
chose
declare
the
type
of
end
is
that
it
will
be
easier
to
write
the
code
to
generate
the
declarative
pipeline,
and
maybe
it
will
be,
it
will
be
easier
for
other
than
of
us
to
read
it,
and
if
they
are
some,
it
has
been
pointed
out
that
there
are
some
I
think,
but
they
can
be
overcome
using
the
scripts
yeah.
They.
G
A
A
D
D
D
A
D
After
the
demo
for
the
coding
phase
ii,
we
have,
I
need
to
formalize
our
viable
format
to
jenkins
filed
or
vironment,
and
to
use
the
steps
in
the
vironment
Genting
step
in
the
wire
well
be.
I
am
working
on
a
step.
Configurator,
it's
not
completed
yet
after
it
has
been,
it
will
be
completed.
You
just
will
be
able
to
use
all
the
steps
the
come
in
the
in
the
viable.
Finally,
then,
there
is
supply,
I
have
rotor
class
snippet
generator
in
which
I
am
generating
tabs
manually.
I
need
to
get
rid
of
that
so
yeah.
D
A
A
E
A
D
So
I
have
this
function.
This
function
push
I,
am
using
git
client
plug-in
in
order
to
push
the
thing
push
the
team
this
and
yeah.
This
is
the
step
and
I
am
calling
that
function.
The
push
function
from
the
cute
operations,
class
and
I
will
get
the
IDP
ID
of
the.
What
is
it
credentials?
Yeah
and
the
URL
of
the
repository
and
I
will
call
that
function
and
it
will
push
it.
So
do
you
thing
like
it
can
be
moved
another
plugin.
A
D
A
F
D
E
So
I
reached
first
reached
out
to
us
pretty
early
in
the
program
again,
I
have
to
admit
at
the
beginning
the
mentors,
the
other
with
student.
We
had
some
a
lot
of
back
and
forth
between
us
regarding
the
definition
of
this
plugin,
so
we
we
had
to
do
a
lot
of
work
with
regard
to
defining
what
we
wanted,
something
that
has.
D
E
H
Yeah
I'm,
assuming
you
guys,
let
me
know
if
there's
too
much
background
noise
and
you
can't
hear
me
well
but,
as
Martin
said,
it
was
a
little
bit
late
that
the
mentors
joined
in
on
the
project
so
I
think
it
was
after
we
actually.
Third
this
into
the
Chuseok
projects
that
we
decided
to
join
em.
And
so
then
it
took
us
a
bit
of
those
first
weeks
to
try
to
come
up
with
a
clear
definition
of
what
our
project
was.
H
So
we
lost
some
time
there,
but
I
think
we
ever
check
was
able
to
do
a
good
job
of
getting
in
the
proof
of
concept
up
and
running
and
implementing
some
of
the
key
features
that
are
needed
and
for
our
next
coding
phases.
We
have
some
clear
definitions
of
areas
to
improve
that
we
mention
ours
and
I.
Think
as
we
keep
going,
we'll
continue
to
find
some
good
improvements,
learn
how
to
make
this
plugin
fit
well
with
the
community.
So,
as
a
first
phase
went
I
think
we're
all
pretty
pretty
comfortable
with
its
grants.
E
A
Okay
and
I
guess
so
that's
all
these
presentations
thanks
a
lot
to
all
students
for
their
demos
and
thanks
a
lot
for
to
everybody
who
participated
in
the
discussion,
especially
thanks
to
Jesse.
Next
time
we
see
ya.
It
is
just
join
the
meetings
and
yeah
if
everybody
is
watching
the
presentation.
Thank
you
as
well.
We
are
going
to
publish
all
material
soon,
as
Abhishek
said,
he's
working
on
the
blog
post,
but
it's
also
possible
to
find
all
materials
on
jenkins
JSOC
site.
So
if
you
go
to.