►
From YouTube: GSoC/Outreachy 2019: Mid-term project demos, part 2
Description
During this session Google Summer of Code students will present the results they achieved in their projects. This is a midterm evaluation, all projects are in progress.
Agenda:
* Natasha Stopa - Plugin Installation Manager CLI Tool / Library
* Nancy Chauhan - Jenkins Pipelines for OpenRISC (LibreCores CI)
* Aarthi Rajaraman, Gayathri Rajendar - Audit Log Plugin
* Jack Shen - Working Hours Plugin - UI Improvements
Presentation abstracts: https://docs.google.com/document/d/13YwMEMXCjTfFmKGEsB2o8Xpaj9lsirgno1TE0pcMPus/edit?usp=sharing . Please contact us in https://gitter.im/jenkinsci/gsoc-sig if you have any questions or feedback.
B
We're
running
all
right:
we're
live
hello,
everyone,
my
name
is
Martina
dazu
and
I'm.
The
J
I'm
one
of
the
jenkins
google
Summer
of
Code
organization
admins
with
the
Jenkins
organization
this
year
and
today
is
our
part
2
of
the
project
presentations
by
our
students.
We
are
now
at
the
coding
at
the
end
of
coding
phase
2,
so
we
are
in
the
in
the
evaluation
phase
of
our
projects.
So
today
we
have
we're
combining
two
types
of
presentations.
B
We
have
presentations
from
jsoc
students
and
we
have
presentation
from
outreach
e
the
outreach
e
activity
as
well.
So
today
we're
going
to
have
in
order
the
following:
we're
gonna
have
a
presentation
by
Natasha
stopa
on
the
plugin
installation
manager
CLI
to
library.
The
second
presentation
will
be
Jenkins
pipelines
for
open
risk
projects.
This
is
a
liberal
core
CI
project
and
it
will
be
presented
by
Nancy.
B
Chohan
third
presentation
is
an
outreach
e
presentation.
It's
about
the
audit
log
plug-in
presented
by
RT,
agile
to
Herman
and
I
apologize
for
mispronouncing
the
names
and
the
fourth
presentation
is
the
Jenkins
hours
plug-in
UI
improvements
and
our
student
is
Jack
Chang.
So
before
I
before
I
give
the
presentation
to
Natasha
I
would
like
to
say
that
I
would
like
to
thank
all
our
mentors
and
all
our
students
for
their
contribution
so
far
and
we
we
are
having
a
little
bit
of
difficulties
with
the
broadcasting
today
so
in
in
1
hour
from
now.
B
A
Before
we
start,
but
if
you
have
any
questions,
yeah
we'll
have
a
YouTube
broadcast,
but
you
won't
be
answering
questions
in
YouTube.
Instead
of
that,
we
will
be
answering
questions
in
the
Gipper
chat,
so
there
is
Jenkins
a
jae-seok
see
Peter.
If
you're
interested
ask
any
question
just
join
this
chat
and
we
will
pass
the
questions
to
presenters.
B
A
C
So
first
I'm,
just
gonna
give
a
quick
overview
of
the
point
of
this
project
and
the
benefits
the
community.
So
one
of
the
main
benefits
is
better
plug-in,
tooling.
So,
basically
allowing
plugins
to
be
downloaded
before
an
instance
of
Jenkins
starts
being
able
to
see
additional
information
about
those
plugins
and
then
also
having
a
library
that
can
be
reused
across
different
areas
of
Jenkins
and
different
ways
that
you
can
start
Jenkins
and
the
end
of
at
the
end
of
my
project.
C
The
deliver
all
deliverable
will
be
a
CLI
tool
and
a
library
that
can
be
run
independently
or
on.
The
library
can
then
be
incorporated
into
other
areas
of
Jenkins
so
phase,
one
mostly
focused
on
kind
of
like
this
basic
skeleton
of
converting
the
existing
Jenkins
dr.
bash
script
to
install
plug-ins
to
Java.
So
we
created
kind
of
the
basic
functionality
and
released
the
first
alpha.
C
So
I
would
say
most
of
the
work
I
did
in
Phase
two
can
fit
into
a
couple
of
different
buckets,
so
there
was
improving
parsing,
so
just
making
that
a
little
bit
more
robust.
So
instead
of
having
the
most
basic
input
trying
to
filter
out
like
comments
and
blank
lines,
adding
llamó
support
for
plug-in
input
as
well.
The
second
kind
of
area
of
things
I've
been
working
on
is
dr.
compatibility
so
and
the
initial
phase,
a
lot
of
things,
were,
for
example,
like
the
update
centers
were
hard-coded
in
and
then
in
this
coding
phase.
C
We've
added
support
to
try
to
get
those
either
through
the
CLI
or
from
environment
variables,
and
then
also
adding
windows
compatible
defaults
and
then
the
kind
of
like
the
last
big
bucket
is
just
additional
features
that
people
would
actually
want
to
use.
So
this
includes
being
able
to
see
the
plugins
and
their
dependencies
before
you
actually
download
them
being
able
to
see
available,
updates
and
security
warnings
for
your
requested,
plugins,
okay.
So
next
I'll
just
do
a
quick
demo.
C
C
Alright,
so
this
is
basically
just
how
you
can
use
this
with
doctor,
so
getting
closer
to
actually
being
able
to
incorporate
the
library
into
docker.
So
this
is
basically
the
llamó
format
that
that
the
tool
can
accept.
So
basically,
you'll
have
this
root
element.
Plugins
and
you'll
define
information
about
the
plugins,
so
basically
the
plug-in
name
where
you
want
it
where
you,
when
I
download
it
from
so
that
includes
either
the
version
or
the
URL.
C
C
So,
basically,
the
tool
will
go
and
get
the
information
about
the
plugins
that
you
requested
recursively
download
all
the
dependencies
and
then
ultimately
put
that
in
a
directory
that
you
can
specify,
or
you
can
also
use
the
default
one
that
then
can
be
used
for
when
you're,
starting
out
your
talk,
for
instance,
okay.
So
this
is
basically
just
going
ahead
and
downloading
them,
and
so
then
I'll
just
show
quick
example
of.
C
C
Okay,
so
then
kind
of
the
other
thing
that
I
mentioned
that
we've
been
working
on
it
are
these
sort
of
like
new
features.
So,
as
you
saw
when
you
just
downloaded
whatever
plugins
you
specified,
without
maybe
knowing
a
little
bit
more
information
about
them,
that
can
you
know
you
might
end
up
with
plugins
or
out-of-date
or
plugins
that
have
security
warnings
that
you
didn't
know
about.
So
the
second
part
of
my
demo
is
just
showing
basically
some
of
these
new
CLI
options
that
I've
added.
C
Okay,
so
this
time,
just
basically
starting
with
a
plugin
dot,
txt
file,
a
pretty
basic
one
and
then
actually
running
our
basically
the
tool
with
on
this
particular
plug-in
file
and
then
listing
all
the
plugins
and
their
dependencies
that
will
be
installed.
So
there's
a
couple
of
different
things
that
this
option
will
show.
C
So
you
can
see
basically
all
of
your
currently
installed
plugins,
so
plugins
that
are
already
existing
in
your
I
guess,
like
war
file
or
you're,
bundled
plugins
and
then
plugins
that
will
be
downloaded
so
kind
of
basically,
this
set
of
all
the
dependency
and
the
plugins
and
the
dependencies
that
you've
requested
and
then
I
guess
also,
which
ones
will
actually
be
downloaded.
So,
given
that
you
have
some
already
installed,
will
this
actually
kind
of
change
which
ones
will
be
downloaded
that
you've
requested
so,
okay,
so
yeah?
C
So
basically,
these
are
all
the
plugins
and
their
dependencies
that
you'll
go
ahead
and
install.
So
next
is
for
all
those
plugins
that
you've
requested.
Are
there
actually
available
updates
for
those?
So
if
you
have
innocent,
that
includes
also
the
dependencies,
so
you've
requested
some
plugins
and
you
can
now
see
which
ones
have
available
updates,
and
maybe
you
would
want
to
change
which
plugins
you
actually
install
based
off
of
that
information.
C
Yep,
the
security
information.
So
it's
the
same
thing.
You
can
input
your
list
of
plugins,
so
they
can
either
be
through
your
txt
file
or
a
llamó
file,
or
actually
just
through
the
CLI
directly
and
then,
given
those
plugins,
you
can
actually
see
security
warnings
for
that
full
set
of
like
those
plugins
and
the
dependencies
that
would
be
installed
before
you
even
install
them.
C
So
just
kind
of
an
overview
of
what's
next,
so
unfortunately
we're
still
working
through
some
of
the
releases
for
this,
but
basically
we
want
to
finish
cleaning
up
and
testing
all
of
these
changes
and
then
release
like
an
official
version.
So
right
now,
I've
just
been
doing
and
the
pre
release
so
just
like
alphas,
but
we
actually
want
to
release
like
a
full
working
version
of
this
and
then
actually
then
take
that
and
incorporate
that
into
the
docker
image
and
with
the
Yama
file
also
add
compatibility
with
Jenkins
configuration
as
code.
C
So
this
would
be
basically
the
way
that
would
work
is
probably
actually
injecting
the
library
before
an
instance
of
Jenkins
starts,
so
that
you're
not
trying
to
download
plugins
from
within
the
configuration
is
code,
but
you
can
set
all
that
up
in
the
same
Yama
file
and
then
continuing
to
add
additional
features.
So
there
are
a
couple
limitations
right
now
that
we're
working
through.
So
the
first
is
right.
Now
we
don't
support
downloading
plugins
from
maven.
C
There
are
some
issues
where
the
plug-in
versions
have
to
match
exactly
what's
in
the
update
center.
So,
for
example,
if
you
request
1.5,
but
the
plug-in
and
the
version
and
update
center
is
one
point
five
zero,
then
your
plug-in
may
not
download.
So
something
we're
also
aware
of
and
working
on,
fixing
right
now,
if
there's
any
errors,
basically
the
tool
will,
just
you
know,
throw
an
error
and
stop.
This
works,
I
think
pretty
well
for
docker
images
like
that
image
won't
even
be
created
if
there's
an
error,
but
in
case
you're
running
it
locally.
C
That
might
be
a
little
bit
more
problematic,
so
we'd
like
to
add
some
kind
of
support
to
restore
the
original
directory
or
kind
of
deal
with
leaving
that
directory
in
an
inconsistent
state
where
you
might
have
some
of
the
plugins
downloaded,
but
not
all
of
their
dependencies
and
then
the
fourth,
probably
a
large
one
that
we're
working
on
is
or
well
school
soon
to
be
working
on
is
working
on
the
performance
basically
being
able
to
download
those
plugins
in
parallel.
So
it
goes
a
lot
faster.
C
C
C
It
technically
wouldn't
be
a
full
integration,
so
I
think
well,
I,
guess
it
depends
on
how
you
define
it,
but
I
think
some
of
the
previous
problems,
with
installing
plugins
from
Jake
asked,
is
that
you're
trying
to
install
plug-in
from
a
plug-in
before
the
setup
is
even
done.
So
in
some
ways
this
would
be
a
little
bit
separate
from
that,
so,
basically
being
able
to
inject
that,
like
being
able
to
install
plugins
separate
from
Jake
asks
so
that
you
can
kind
of
do
it
before
it's
that
starts
yeah,
so
yeah.
Does
that
clarify
your
question?
C
A
C
D
A
A
C
E
C
B
G
A
G
G
Oh,
how
I
rejection
for
all
working
I
was
plugging.
This
is
the
second
presentation.
After
work,
I
was
plugging
in
this
project
presentation.
We
I
will
show
the
latest
improvements
of
what
we
have
John
on
this
plug
in
theory.
In
the
second
Dakota
face,
my
presentation
will
be
mainly
evaluate
into
three
parts.
G
The
first
would
be
the
improvements,
the
overview,
and
the
second
will
be
the
demo,
and
we
all
we
will
test
some
time
and
until
the
judge,
semantics
excluded
a
judge
in
running
wield
tasks,
and
the
third
part
will
be
some
plans
and
useful
links
and
those
of
the
question
time.
Okay,
the
first
first
part
is
improvements
and
I
mean
what
we
have
done
to
improve
the
improve
the
working
hours.
G
G
G
This
is
the
currently
currently
UI
and
is
powered
by
reactive,
because
reactor
has
and
as
to
has
so
many
UI
components
for
us
to
to
take
advantage
of.
Also
we
add
holiday,
presets
I
mean
we
can
select
some
preset
holidays
and
we
shouldn't
we
couldn't
we
clear
all
media
and
the
operation
of
we
manually
input
at
harder.
G
G
Okay
and
I'm
rawhide
I
had
deployed
this
plugging
into
one
of
my
server,
and
here
is
the
working
hours
can
take
a
page,
and
here
is
the
blue
ocean
UI,
and
this
displays
a
test
tube
task
and
we
had
configure
it
to
enforce,
reschedule
and
you
will
obey
the
into
working
hours
with
general.
We
set
in
this
in
this
plugin,
and
we
can
see
here,
is
in
my
in
my
local
time
is
11:30
if
I
set
it
to
Thursdays
from
10
range
from
8
to
20
and
the
issue.
G
G
Sorry
that
may
be
a
little
bag
will
continue
running
other
tasks.
Alright,
then-
and
we
also
sorry
because
we
owe
because
we
have
added
along
excluded
date
and
it's
excluded
by
D-
it
is
resent.
If
we
need
to
remove
the
dates
you
can
see.
The
task
is
running,
that's
a
mistake,
and
this
task
is
race.
It's
Ronnie
Ronnie,
it's
also
Ronnie
yeah,
also
and
for
excluded
days.
G
There
are
three
types
of
excluded
days
and
for
the
first
one
is
static
date,
and
that
mean
the
date
is
static
like
like,
like
we
test,
divided
25th
yeah
and
it's
automatic
set
automatically
set
you
today.
Every
savanna
close
and
the
new
tasks
run.
That
advice
would
be
would
be
blocked
because,
according
to
the
rule,
justice
dead,
and
if
we
remove
this
rule.
G
G
G
G
G
The
third
part,
the
other
things
like
the
first
one,
is
to
a
deep
place
for
the
codified
stray
and
on
the
working
hours.
Plans
is
to
is
to
write
more
tests
and
more
documents
and
blogs.
Also,
we
want
to
support
more
regional
holidays
because
the
holiday
library
we
use
you
use,
we
are
using
his
job
and
it's
does
it
better.
G
G
Also,
the
other
demo
is
deployed,
had
this
link
and
with
user
name
guest
and
we
can
and
I
can
get
you
to
the
to
the
ring
or
your
login
and
everybody
can
get
log
into
this
plug-in
use,
use,
username,
yeah,
guest
and
the
password
literally
password-
and
you
can
say,
send
into
this
again
and
do
you
work
the
plugins
your
URL
will
be
on
this
one
and
you
can
you
can
try
to
use
this
plug-in
and
yeah
and
we
are.
We
are
looking
forward
to
your
feedback
and
yeah.
G
G
That
you
think
is
is
popular
but
not
including
or
prints
that
we
sell
here,
and
you
can
check
you
can
check
the
presets
and
if
using
their
ass
on
a
hard
day,
is
that
not
pretty
just
should
that
should
somehow
they
should
be
popular
but
not
presents,
and
then
you
can
feel
the
form,
and
there
will
be
really
appreciate.
Viewers
will
be
really
appreciative
if
you
can
send
us
this
form
and
thus
our
only
useful
links
ago
and
just
to
be
two
links
about
okay
and
the
next
question
and
I'm
going
to
answer
some
questions.
I
G
A
G
A
I
J
J
I
You
upload
it
somehow
or
something
like
that,
something
that's
you
know
a
custom,
a
custom
yeah,
so
the
the
library
that
it's
using
that
called
jolly
day
has
I
believe
has
support
for
doing
that
type
of
stuff.
So
it's
probably
something
that
we
could
wire
up,
even
if
it's
not
done
during
Chuseok.
We
could
maybe
do
this
a
fast
follower.
I
I
A
G
G
B
B
D
D
D
So
I'll
just
tell
you
about
4c
Foundation,
it's
a
non-profit
foundation.
Its
mission
is
to
promote
an
assist,
free
and
open
digital
hardware
designs.
It
operates
as
an
open,
inclusive
and
they're
independent
group,
so
lebryk
OCI
is
the
project
which
comes
Foundation
and
Oleg
is
the
core
maintainer
of
it.
It's
just
in
applaud
service
to
provide
CI
to
hardware
projects
so
currently,
I've
been
setting
up
demo
CIO
for
open
risk
project
and
I
hope
so
that
we
target
more
in
future
and
it
is
powered
by
Jenkins.
D
D
So
the
question
arises
that
why
we
are
working
in
with
Jiang
Jenkins,
so
obviously
for
the
reasons
that
it's
free
and
open
source
project,
it's
a
framework,
and
we
can
do
whatever
we
want
like
if
we
can
have
a
self
hosted
set
up,
for
example,
remote,
build
agents
and
the
features
we
needed
for
our
projects
for
multi
branch
pipeline.
We
needed
a
lot
of
two
management
plugins
general
purpose,
plug
plugins,
like
we
have
tap
plug-in
performance
plugin
and
for
the
security
and
shared
shared
access
engines.
D
Yeah
so
I'll
just
review
about
the
elliptic
or
CI
infrastructure.
So,
as
we
can
see
from
the
diagram,
it
is
basically
powered
by
Jenkins,
like
all
the
CI
is
done.
In
Jenkins,
we
have
created
a
set
of
docker
images
which
include
set
of
EDA
tools
or
installation
of
all
the
tool
chains
and
which
we
require
for
the
hardware
projects
like
I
like
to
give
you
a
review
of
a
demo
yep.
D
D
So
coming
back,
so
this
was
a
brief
introduction
about
the
whole
process.
Now
coming
back
to
the
deliverables,
I
just
focused
to
modify
the
more
1kx
Travis
CI,
true
to
use
the
libera
core
CI
docker
image,
because
it
just
speeds
up
the
process.
Then
we
wanted
to
create
a
Jenkins
file
in
open
risk
project
so
that
so
that
we
we
can
have
a
faster
process
with
Jenkins
and
creating
CI
for
your
sis
synthesis.
So
your
system.
This
is
it's
it's
a
tool
which
provides
the
monitoring
resource
usages.
D
It
gives
you
all
the
printing
statistics
of
how
many
wires
we
have
or
CPU
or
the
or
the
resource
usages
we
have
we
want
like.
Then
next
was
creating
CI
for
open
or
City
GDP,
which
is
used
for
debugging.
Then
extending
the
Jenkins
file
in
open
risk
projects
to
make
yo
Sasan,
open
or
City
a
part
of
the
build
pipeline.
D
Then
we
wanted
to
detach
the
reusable
logic
to
our
pipeline
library
of
libera
course.
We
wanted
to
add
support
for
email
notifications.
Then
this
was
the
major
thing
which
we
want
to
achieve.
We
want
to
parse
and
visualize
all
the
test
reports
for
the
open
risk
projects,
and
this
can
be
achieved
using
Jenkins
plugins.
D
D
Then
then
we
yeah.
So
this
is
the
this
is
what
has
been
achieved
in
phase
one.
So
we
were
able
to.
We
were
able
to
create
multiple
pipelines
in
openness
projects,
so,
as
you
can
see
that
we
can
create
pipelines
for
more
1kx
and
or
one
came
or
it's,
you
know,
project
which
are
the
projects
under
open
disk.
So
I'll
just
give
you
a
demo,
so
I
just
wrote
a
Jenkins
file
for
all
the
for
the
more
1kx
project
which
basically
do
which
basically
checks
out
all
the
tests.
And
yes,
so
we
have
developed.
D
D
Now,
after
the
face
after
the
phase
one
we
had
to,
we
had
to
use
your
sis
synthesis.
So
your
sis
is
a
framework
for
very
long
article
synthesis.
It
was
required
for
monitoring
resource
usages.
Now
we
have
a
few
sock
which
few
sock,
which
is
a
tool
packet
manager
and
it
has
icestorm
which
provides
your
synthesis
and
its
back
end.
D
So
we
was,
we
were
able
to
successfully
create
your
sister
log
file,
which
has
all
the
printing
statistics
of
the
project
like,
as
you
can
see,
the
number
of
wires
number
of
cell
processes
memory
bits
now.
The
next
step
was
to
represent
this
data
with
the
help
of
jenkins
plugin.
You
know
you
know
graphical
way,
so
this
is
a
quick
start
or
we
just
need
to
follow
these
commands
so
that
we
can
generate
your
says,
dot
log
file.
D
Now,
after
that,
I
created
a
parcel
file
which
basically
fetches
the
important
data
which
we
require
from
the
log
file
from
the
huge
log
file.
So
I
could
get
this
kind
of
data,
which
is
so
I
can
get
this
kind
of
data.
Now
the
work
is
in
progress
regarding,
so
we
want
to
use
this
theta,
which
we
had
generated
from
your
sister
clock
to.
D
We
want
to
represent
it
in
somewhere
in
this
graphical
method,
as
it
has
Sheen
in
scene
in
this
sample
images.
So
for
this
we
are
working
to
work
into
your
staff
plugin,
so
that
we
can
show
our
test
results
of
the
openness
projects
and
we
want
to
use
performance
plug-in
to
use
to
do
that
can
be
used
for
synthesis
and
PNR
matrices.
So
using
Jenkins
simplified
the
method,
and
we
can
present
it
very
well.
So
this
is
a
work
in
progress
and
I
hope
we
will
develop
this
till
the
end
of
DJ
sock
project.
D
Then
after
this
we
have
like,
we
usually
have
a
conversation
on
Cato.
So
you
can.
If
you
have
any
questions
again,
followers
say
we
remain
quite
updated
on
mailing
list
and
you
can
check
out
my
github
dashboard
for
the
for
the
progress
tan
lines
and
also
why
I
prefer
to
make
blog
post
explaining
whatever
I
have
done
in
this
detail.
So,
yes,.
D
In
the
end,
I
want
to
thanks.
Thank
you
to
my
mentor
Orlick.
He
gave
me
quite
a.
He
gave
me
of
a
huge
support
regarding
Jenkins
slippery
course
CI
and
stop
it
only.
He
is
the
core
maintainer
of
openness,
project,
stiffen
and
definitely
foresee
foundation
for
helping
me
out
and
Jenkins
for
giving
me
an
opportunity
to
present
the
work.
A
Can
probably
ask
a
few
questions
if
you
don't
mind,
they
just
repeat
discussions
behind
before
so
we
originally
are
open
risk
projects,
you're
running
Contreras
and
yeah.
What
is
your
experience
about?
Liberating
definitions
from
Travis
to
Jenkins?
Were
there
any
issues
you
experienced
and
how
was
it
for
you.
D
D
Yeah,
okay,
Thank
You,
Alec,
okay,
so
our
first.
This
is
true.
Like
openness
project
has
its
own
Travis
flow.
So
we
are.
We
wanted
to
migrate
it
to
Jenkins.
So
as
of
now
I
feel
migrating
to
Jenkins
was
a
good
option
because
we
have
so
many
plugins
and
we
wanted
our.
We
wanted
a
lot
of
support
like
like
create
like
visualizing
and
passing
the
reports,
so
that
we
can
have
a
better
view
with
the
plug-in
support
and
we
can
create
our
own
libraries.
D
A
Right
what
I
would
like
to
add
from
the
Jenkins
site,
yeah?
Well
migrating?
We
hit
some
issues.
For
example,
if
you
open
our
jenkees
file
for
open
artists
for
Maalik
project,
you
may
see
that
there
is
a
lot
of
configurations
just
each
just
implementing
a
kind
of
multi
configuration
run
for
matrix.
So
it's
one
of
the
features
which
is
heavily
requested
in
Jenkins
community
to
have
support
of
configurations
in
declarative
pipeline.
Well,
I
guess
it
would
be
something
really
helpful
for
this
project.
A
If
no
questions
yeah
thanks
a
lot
and
ends
here
and
yeah
thanks
a
lot
for
your
work,
hurry
as
I
mentor,
I
can
say
that
it's
a
hard
project
because
we
basically
have
to
make
contributions
in
multiple
hip-hop
organizations
which
have
completely
different
technology
stakes.
So
it's
open
risk,
which
is
more
hardware
design
a
lot
of
HDL
court
in
Bariloche.
Then
there
is
libera
course
which
is
rather
about
the
Jenkins
Jenkins
files
and
Dokic
definitions.
A
A
Okay,
if
my
network
breaks
feel
free
to
just
take
it
over
okay,
so
the
remaining
presentation
is
for
the
outreach
project
a
bit
CA.
We
have
two
students
working
on
outreach
here.
Basically
outreach
is
they
do
the
program
where,
yes,
you
didn't
just
join
projects
under
mentorship
of
organizations
pretty
much
like
jigsaw
just
with
different
focus.
This
is
the
second
time
we
participate
in
this
project.
First
time
was
this
week
we
had
a
good
progress
with
audit
log
plugin
and
this
year
our
switch
students
are
also
thinking
you're
working
on
that.
H
How,
like
we
say,
we
are
working
on
the
audit
log
wagon
approaching
using
apache
log4j
audit.
We
are
developing
this
plugin
for
Jenkins
before
the
demo,
as
this
is
a
just.
You
said
that
I
would
like
to
see
the
context
for
that
call
here.
There
are
a
few
pointers.
I
would
say.
Auditing
is,
is
logging
and
lead
to
audit
their
events
and
audit
log
plugin
I'll
start
with
auditing
RSS
logging
in
a
typical
application.
H
They
will
oppose
other
logging
statements
to
help
diagnose
problems
or
to
document
unexpected
occurrences,
and
these
are
normally
referred
to
as
diagnosed
blocks
generally.
The
diagnostic
locks
aren't
helpful
to
determine
the
particular
changes
made
by
ku
and
when
it
is
made.
On
the
other
hand,
we
have
I'll
tell
about
I'll
tell
about
the
audit
locks,
which
is
focusing
on
their
identifying
when
a
change
was
made
who
needed
and
what
the
data
elements
were
changed
and
also
it
helps
sometimes
in
troubleshooting
the
problems
that,
though
the
dub
standard
shipping
is
not
our
main
purpose.
H
In
recent
times.
It
is
more
common
to
see
audit
logs
return
to
more
simple
data
stores
where
they
came
efficiently.
The
query
I
next
I'll
continue.
This
is
a
difference
between
auditing
and
logging.
Next
I'll
continue
with
lead
to
audit
billions
say,
for
example,
in
Jenkins
enrollment,
where
there
is
item
that
deploys
the
code
to
the
production
and
some
changes
happen.
Often
to
that
and
change
evens
are
audited,
so
that
figuring
the
cause
for
the
impact
becomes
easier
in
the
later
stages
might
be.
H
If
I
put
a
put
up
to
a
general
example,
audit
logs
are
often
used
to
generate
reports
that
are
of
value
to
several
reports
for
the
organization.
For
example,
if
an
auditor
at
a
bank
might
be
interested
in
locating
all
the
accounts
with
more
than
three
failed
login
attempts
than
the
prior
of
the
prior
day
or
all
the
transfers
for
more
than
like
$10,000,
it
helps
you
identify.
H
The
audit
also
find
that
the
those
are
which
he
was
searching
and
now
I
will
come
into
a
audit
Rob
plug-in
audit
log
plugins
helps
us
in
auditing
that
define
events
that
are
happening
in
the
junk
email
prominence.
The
goal
of
our
project
is
to
release
the
plug-in
version
1.0
by
the
made
of
network
next
month.
H
H
Currently
we
have
defined
a
few
humans.
So
basically
we
have
something
happens.
When
something
happens,
they
listen
t1
which
is
have
fun,
and
then
the
plugins
are
logs
either
in
an
illegally
which
are
happening
in
the
environment.
I
would
like
to
share
the
available
events
for
the
happening
in
the
environment.
H
These
are
the
events
which
these
are
the
available
events
in
their
jenkin
enrollments,
and
we
know
that
by
checking
the
fingerprint
that
the
current
sure
trigger
plug-in
creates
also
currently
they
are
working
on
the
task
that
helps
to
add
the
events
through
an
API.
By
the
end
of
it,
we
will
also
be
able
to
add
new
emails
from
the
third
parties
via
API.
H
Now,
as
we
defined
a
lot
of
events
and
are
still
defining
them,
we
also
have
to
concentrate
on
getting
four
odd
events
to
different
destinations
for
now
to
a
rolling
fire
rolling
fire.
Then
the
location
of
the
file
is
configured
other
walls.
It
goes
in
there,
locks
hold
on
in
the
Jenkins
Ohm's
law
and
our
I'd
like
to
show
that
guy
to
also
easily
enable
death
syslog
destination
where
the
logs
are
sent
over
TCP
to
a
different
receivers.
H
H
E
H
H
H
And
actually,
we
are
proud
to
say
that
all
of
the
code
written
so
far
is
unit
tested
and
a
JPM
typing
process
that
was
also
initiated
but
has
to
be
continued
on,
and
the
draft
submission
has
to
take
place.
I
sincerely
thank
my
mentor,
smart,
sitter
and
just
concerned
for
her
happiness
throughout
and
thanks.
Everyone
is
any
query,
sir.
A
A
K
Yeah
cuz
I
thought
you
had
said
my
name
but
yeah.
That
was
a
great
presentation
and
looking
I
was
kind
of
wondering
I
suppose
about
the
no
sequel
database,
as
you
mentioned,
was
there
any
you
had
in
mind
that
might
make
sense
or
as
like
a
kind
of
like
an
initially
supported.
One
like
it
seems
to
be
most
common
for
audit
logging
like
MongoDB
or
CouchDB,
or
elastic,
search
or
Cassandra,
or
something
else
I.