►
From YouTube: Jenkins GSoC 2020 - GitHub Checks API project discussion
Description
Project idea pge: https://jenkins.io/projects/gsoc/2020/project-ideas/github-checks/ . Notes: https://docs.google.com/document/d/1CZgvSLdWe4i65i_WspmCSniaH0ZgOcHfE6nq5LnWmds/edit?usp=sharing
A
A
Because
this
way
we
could
get
a
lot
of
benefits
for
from
check
Sapien
jenkins,
and
we
already
got
a
few
proposals
from
students
for
this
project
which
we
are
reviewing
so
today
we
just
have
an
opportunity
to
do
a
connie
and
maybe
to
do
some
sinker
for
these
figures
of
what
needs
to
be
done,
especially
if
there
are
multiple
students
interested
to
work.
So
we
could
just
use
this
time
to
see
whether
we
could
paralyze
that
or
how
we
could
adjust
this
code.
B
So
I'm
slated
I've
been
working
with
Jenkins
for
the
past,
I
mean
by
five
months.
I
guess
so.
With
the
community
bridge
project
I
was
I
was
involved
with
Tim
and
Joseph
in
building
a
json
schema
generator
for
the
Jake.
Ask
so
I
have
a
bit
of
knowledge
about
the
Jenkins.
The
ecosystem
I've
been
contributing
in
various
areas
like
document
migration,
a
bit
of
plug-in
warnings
plug-in,
maybe
github,
API
and
stuff,
so
yeah.
B
D
D
There
would
be
more
but
yeah
what's
on
this,
video
watch
is
online,
so
my
name
is
Olli
I'm,
the
author
of
the
Warnock's
plugin
and
yeah
I.
Think
some
of
the
requirements
are
coming
from
my
plugin.
That's
the
reason
we
want
to
have
this
project,
so
I
talked
with
a
lot
of
users
of
my
plugins
and
what
they
wish
is
to
have
some
information
from
github
from
from
the
Jenkins
job.
In
get
happen,
that's
the
reason
we
started
this
project.
A
E
My
name
is
Jeff
I'm,
a
contributor
to
open
source.
This
is
my
third
year
in
involvement
in
JSOC
I
maintain
a
couple
of
plugins
and
I'm.
Also
the
author
of
a
plug-in
that
provides
build
information
via
the
github
status,
commit
status
API,
which
is
deprecated
and
and
also
to
various
other
dashboards.
So
it's
kind
of
in
this
area,
so
I'm
interested
in
just
just
monitoring
in
general
and
and
doing
what
I
can
to
help
move
it
forward.
F
I'm,
just
showing
a
kamikaze
I
came
from
China
and
I'm
interested
in
this
project.
I
will
try
to
wrote
a
project
of
concept
and
I
posted
in
our
killer,
channel
and
I
have
contributed
to
the
warnings
next
generation
plug-in
before,
and
also
the
github
API
for
Java
and
I
want
to
participate
in
this
project
for
this
summer.
Thank
you,
mm-hmm.
H
A
Thank
you,
I
mean
I'm,
one
of
four
G's
Orkut
means
I
started,
participating
in
just
Oakland
2016
when
we
Jenkins
and
I'm
really
proud
of
this
program
and
I'm
happy
to
create
contribute.
However,
I
can
and
I'm
a
very
big
fan
of
github
check
CPI.
So
if
you
get
its
hot
food
in
Jenkins,
it
would
be
awesome
and
I
will
do
my
best
to
contribute
and
to
shake
expertise
when
I
can.
A
D
D
Okay,
no
sharing;
no!
No!
Yes,
it
is
okay,
so
I
think
the
the
proposal
is
best
described
if
you
have
a
look
at
a
typical
pre
request
of
Jenkins
or
at
one
of
the
plugins.
This
is
one
of
champions
plugins,
and
this
is
a
typical
pull
request
where
we
have
a
lot
of
commits
here
and
a
lot
of
checks,
and
what
we
have
here
is
some
boxes
in
this
pull
request,
which
are
from
other
tools.
This
box
here,
for
instance,
is
from
courtesy.
D
Here
we
have
here
are
the
tops
which
are
running
after
the
pull
request
has
been
committed,
and
the
last
line
of
this
line
here
is
showing
that
Jenkins
is
building
there.
We
request-
and
this
is
the
only
message
what
Jenkins
is
showing
currently
so
in
order
to
see
why
this
committee
cannot
be
built.
I
need
to
click
on
the
details
and
then
Jenkins
is
opening
its
user
interface.
D
The
idea
from
my
plugin
users
is
it
would
be
much
better
if
we
run
the
Jenkins
build
and
then
push
these
notifications
in
this
style
here
in
form
of
a
pull
request,
so
everybody
sees
which
line
has
a
new
warning,
etc.
So
this
is
I
think
the
main
idea
behind
the
proposal.
From
the
user
perspective,
it
would
be
nice
to
have
warnings
for
each.
D
We
request
shown
directly
in
the
pull
request,
and
it
not
only
in
Jenkins
user
interface,
and
if
we
extend
this
approach
a
little
bit
more
I
think
it
makes
sense
to
also
show
you
test
failures,
a
code
coverage
increase
or
decrease,
and
things
like
that.
Everything
what
is
actually
monitored
in
Jenkins
would
make
sense
to
be
presented
in
the
pure
request
here.
D
So
nobody
needs
to
open
the
web
interface
of
Jenkins
and
if
we
think
it
a
little
bit
more,
maybe
in
a
couple
of
years
Jenkins
has
no
user
interface
at
all
and
it
makes
sense
to
just
get
the
data
from
Jenkins
and
presented
somewhere
else,
and
one
thing
would
be
to
show
it
here
in
the
github
pull
request.
Yeah.
A
D
This
is
I,
think
the
view
of
the
proposal
from
my
requirements
whew.
So
what
needs
to
be
done
on
the
technical
side
to
implement
this
actually
I,
don't
know
how
to
do
it.
So
I
know
there
is
the
API
in
github,
but
I
think
the
students
are
already
much
deeper
in
that
part,
as
I
am
so
I
can't
say
much
to
the
API
itself
in
github
and
what
needs
to
be
done
on
the
tank
inside
here
so
I
think.
For
me
it
is
okay.
If
it
has
somebody
some
questions
regarding
the
requirements
here,
I.
F
D
E
E
B
Provide
some
insights
on
that.
Actually,
if
you,
if
you
kind
of
write
an
application
and
from
me
register
it
to
the
github
applications,
we
go
to
the
developer
settings
and
actually
create
an
app
github,
actually
lets
you
post
certain
certain
events
to
the
github
page.
So
as
soon
as
you
run
that
check-
or
you
run,
that
application
github
automatically
kind
of
its
events
from
your
app
and
post
them
on
your.
So
there
are
different
kinds
of
events
like
on
create
uncomplete
in
progress
and
stuff.
B
So
as
soon
as
you
create,
and
as
soon
as
you
know,
the
pull
request
will
cease.
Its
first
event
github
sends
out
the
create
web
book
to
all
of
the
apps
that
are
subscribed
to
the
repository.
So
if
you
create
an
avenue
subscribe
it
to
the
repository
github
sends
out
the
create
web
book
and
your
application
can
actually
catch
that
webbook
and
run
a
status
check.
So
that's
what
most
of
the
actions
or
apps
they
captured
the
create.
B
F
G
G
So,
there's
a
default
message
in
the
github
notification
context,
which
is
where
it
decides
what
it's
going
to
send,
depending
on
the
build
result
so
inside
the
messages
file.
There's
like
ten
different
texts
that
will
see
it
based
on
how
it
was
based
on
the
result,
and
you
see
a
different
different
plugins
can
implement
their
strategy
and
I.
Think
there's
also
other
plugins,
which
just
do
it
themselves
as
well
to
see
an
ad
hoc
notification
messages.
Yeah.
A
G
A
Exactly
the
state
of
the
art
also
several
libraries
for
github
API
and
Jenkins
users,
github
API,
slash
github
API,
it's
a
project
which
was
originally
created
by
course,
I
care
and
now,
thanks
to
team
which
supports
github
of
solidification
and
other
components,
I
forgot
to
introduce
team
in
the
beginning.
Sorry,
so
yeah.
If
you
would
like
to
introduce
yourself
it
in
big
feet,
sure.
G
Hi
I'm
Tim
at
least
see
me
introduced
me:
I
use,
github
a
lot
I'm,
a
maintainer
of
a
few
plugins
and
Jenkins
slack
jerky
vault
configuration
is
code.
Imaging
is
core
maintainer
as
well.
You
have
fairly
large
Jenkins
instance
and
my
company
that
we
use,
but
also
quite
a
lot
of,
is
your
dev
ops
as
well.
So
I
see
quite
a
few
things
there.
G
I've
looked
implementing
this
before,
but
it
was
basically
blocked
for
a
very
long
time,
because
github
API
project
wasn't
released
for
almost
a
year.
It
got
stuck
in
transition
between
kohsuke
and
others
and
then
finally,
finally,
liam
is
now
taking
over
there.
So
it's
moving
at
a
much
higher,
much
faster
pace
and
because
of
that,
I
was
able
to
get
the
application
working
for
the
github
ranch
sauce
plug-in.
G
A
A
A
B
Actually,
I
wanted
to
ask
one
question:
I
had
a
question
regarding
the
code
coverage
API
plan,
so
the
code
coverage
appear
to
again.
So
how
do
we
want
the
code
coverage
to
be
displayed
because
there
are
a
few
ways
that
currently
I
think
work
up
displays
reports,
but
code
I
think
there
is
a
plug-in
existing
that
just
displays
the
coverage
possibility.
So
how
do
we
want
to
proceed
with
that?
Do
we
want
because
I
don't
think
the
checks?
Api
supports
reporting
coverage
reports,
but
the
github
pull
request
review
comments
does
allow
you
to
post
reports.
B
A
So
we
get
in
Co
warnings
in
our
change
requests
about
code
coverage
issues,
particularly
about
the
parts
of
the
new
code,
which
is
not
covered
by
a
test,
and
if
it
was
displayed
by
checks
API,
you
could
just
put
information
to
the
lines
and
say
that
hey
this
block
is
not
covered.
Do
something
about
that.
It
would
be
the
first
obvious
kiss
kiss
for
me.
Okay,.
B
D
D
This
is
a
another
pre
request
of
my
plugin
and
here
what
I'm
using
is
code
coverage
or
a
code
cuff
this
tool,
I,
don't
know,
I
want
to
call
it,
and
this
tool
is
computing.
The
code
coverage
from
the
change
and
yeah.
This
is
but
really
interesting,
because
this
is
just
a
dependency
that
changed,
but
normally
they
here
you
see
which
kind
of
coverage
you
have
changed
in
the
positive
or
in
the
negative
way.
E
G
D
E
It's
interesting,
it
almost
feels
like
it
would
be
creative.
This
solution
was
extendable
so
that
it
could
maybe
publish
information
from
different
places,
because
you
know
some
people
probably
would
want
to
use
that
code
cuff
service
and
some
people
might
not
so
maybe
there'd
be
some
different
options.
Different
ways
to
extended
yeah.
H
B
A
E
Not
sure
you
know
what
other
companies
do,
but
but
in
practice
what
I've
seen
is
that
almost
all
of
the
coverage
that
we
gather
gets
converted
to
the
cobertura
because,
like
I've
done
a
lot
a
lot
in
in
node
nodejs
and
we're
doing
golang
right
now
and
all
of
those
and
even
Python,
there's
ways
to
convert
it
to
cobertura
and
then
publish
that.
So
it
tends
to
be
kind
of
a
common
format.
A
To
be
used
such
approach
a
lot
and
there's
a
lot
of
converters
until
the
very
recent
time
it
wasn't
possible
to
publish,
for
example,
coverage
for
C++
code
named
Jenkins
without
conversion
through
compared
to
the
format.
There
is
a
project
called
G
cover
video
publishing,
hardwired
code
coverage
using
cover
split
apart
again,
it's
still
partial
miss
keys,
because
cobertura
format
is
far
from
being
video,
though
we
provides
basic
information.
E
B
Okay,
so
what
yeah?
So
probably
the
code
coverage
API
plugin
could
I?
Does
it
I
believe
it
does
have
some
more
extension
points,
so
they
do
publish
some
of
the
reports,
so
maybe
the
gate
objects
API
plugin
could
make
use
of
those
reports.
I
mean
pass
those
reports
and
probably
generate
some
sort
of
reporter
are
much
more
useful
to
be
displayed
in
github
pull
requests
so
I
get
up
wasted
posted
a
link
on
the
on
the
document.
B
D
Okay,
I
think
one
plug-in
which
should
also
report
something
is
the
j-unit
plug-in.
So
if
someone
in
a
pull
request
fails
a
test,
it
would
be
very
helpful
if
the
test
failure
would
also
shown
in
the
pre
request.
So
currently
Jenkins
says
yeah.
It
failed
and
then
I
need
to
go
to
Chang
kids
to
see
where
it
failed,
and
it
would
be
much
better
if
they
also
have
the
chair
unit
plug-in
report,
at
least
the
failures
in
the
pull
request.
E
I
I
think
that
would
be
useful
in
our
experience,
because
a
lot
of
people
that
I
work
with
one
of
the
things
they
don't
like
about
Jenkins
is
having
to
to
click
through
the
link
and
go
figure
out
what
failed
and
so
the
more
information
that
we
could
have
on
the
pull
request
page.
The
happier
people
would
be
mm-hmm.
H
A
A
A
We
offer
wide
open
project
ideas
so
that
students
could
research
to
them,
explore
to
the
area
and
come
up
with
their
proposals
and
they
get
a
lot
of
freedom
or
what
they
can
propose.
We
start
from
there.
So
will
you
please
correct
me
if
I'm
wrong,
but
I
think
that
all
items
here
are
just
examples
of
what
would
be
done.
These.
D
Are
actually
examples,
I
think
it.
It
is
a
good
project
which
can
be
done
very
incremental,
so
we
can
start
with
a
simple
check
that
prints
some
hello
world
from
Jenkins
and
then
maybe
a
warning
and
then
I
think
it's
up
to
the
student
in
which
direction
we
are
going,
and
it's
also
really
hard
to
decide
now,
which
are
the
milestones.
F
A
So
what
you
do
now,
you
do
a
project
proposal
and
we
totally
understand
that
we
cannot
commit
to
the
scope
right
now,
because
the
proposal
may
change
the
environment,
may
change
and
there
may
be
obstacles
they
discovered.
So
it's
pretty
much
like
an
any
other
software
project
and
right
now,
yeah
you
work
on
the
proposal.
We
want
it
to
be
feasible,
but
still
there
may
be
a
lot
of
changes
during
the
project
itself.
A
For
example,
during
community
bonding,
we
usually
ask
project
teams
to
work
on
I
mean
design
based
on
my
original
proposal,
so
that
you
review
your
proposal
together
with
mentors
see
what
could
be
done
in
a
different
way.
It
needs
to
be
done
would
be
excluded.
What
would
be
the
order?
So
you
would
work
the
project
together
and
the
basically
start
working
after
bed
and
a
final
project
plan
may
differ
from
the
original
proposal,
so
we
don't
consider
students
to
be
committed
to
fully
committed
to
what
is
listed
in
the
deliverables.
A
Of
course,
we
want
it
to
be
somehow
aligned.
So
don't
expect
a
situation
when
you
come
get
accepted
and
then
people
say
you
that
you
do
complete
different
project.
Oh
it's
not
going
to
happen.
It
will
be
a
discussion
between
teams
and
we
want
to
have
proposal
along
these
lines,
but
they,
if
something
changes
it
happens
and
basically
our
approach
is
as
long
as
mentors
are
happy
with
the
result.
There
is
a
recognization.
A
There
sometimes
that
are
really
interesting,
good
results
and
deviations.
So,
for
example,
when
we
working
with
shinu,
together
with
Jeff
southern
taken,
I,
believe
the
original
scope
of
the
project
was
completed
in
mid-june,
or
something
like
that,
and
when
we
were
exploring
slightly
different
areas,
the
overall
it
was
a
really
successful
project,
but
yeah
such
things
happen.
A
Please
don't
be
afraid
about
that,
but
still
think
what
you
would
like
to
work
on
and
what
would
be
so
if
you
are
concerned
about
this
item,
if
you
didn't
really
want
to
work
on
that,
you
can
find
something
else
or
you
could
just
put
it
to
the
identity
of
area
for
the
future
discussion.
I'm,
not
sure.
E
You
know
I'm
always
a
fan
of
having
api's
that
can
be
used
by
other
plugins.
Well,
I
think
that
maybe
the
mentors
or
the
community
could
help
flesh
out
it.
At
least
what
the
interface
would
look
like.
That's
the
that's
general,
and
maybe
we
only
implement
it
for
github,
but
but
the
interface
is
defined,
so
somebody
can
add
the
others
later.
A
B
B
Yeah
so
I
just
took
a
basic
warning
report:
that's
a
static
fawning
report
and
on
the
basis
of
that
report,
since
obviously
there
is
no
dynamism
in
war
I'm,
not
making
any
call
to
the
Jenkins
reporters
country,
warnings
plugin.
So
what
I
did
was
this
was
the
kind
of
report
that
was
generated,
so
it
can
show
you
the
line
number,
the
file
name,
the
line
start
line
end
and
stuff
and
I
wrote
the
Springwood
application
that
can
that
is
basically
registered
as
a
get
about
currently.
B
So
this
gate
of
application
does
what
it
parses
the
warning
report
and
for
whatever
pull
requests
that
you
would
generate
whatever
public
was
that
I
generate.
It
shows
a
kind
of
it
shows
you
what
kind
of
warnings
have
been
generated.
So,
if
I
take
a
look
at
some
of
the
warnings
that
have
been
generated
here
so
I'll
show
you
an
example.
So
if
you
look
at
the
warnings
report,
yeah,
it's
just
a
static
warnings
reports.
B
It
doesn't
make
sense,
though
it
can
show
you
the
message
so
the
it
may
fail
to
clean
up
Java
input
stream
or
return
value
of
report.
Yet
okay.
So
you
get
the
gist
of
it,
so
these
are
the
kind
of
one
is
that
have
been
generated.
So
currently
there
are
only
three
warnings
generated,
so
what
I
did
was
I
wrote
up
the
app
and
registered
it
as
github,
so
get
up
runs
it
so
if
I
can
show
you
a
demo,
so
this
is
the.
B
This
is
just
a
test
file
that
I've
written
it's
just
copy
pasted
from
from
one
of
the
free
event
freely
available
repository,
so
doesn't
ignore,
what's
written
in
it,
but
what
is
important
here
is
so
I've
registered
the
app
on
a
particular
repository.
So
if
you
have
a
look
another
sandbox
repository,
so
this
is
just
a
blank
repository
and
what
I
will
do
is
I
will
push
up,
pull
request
to
this
so
I'm
going
to
push
this
to
buy
from
this
whole.
Second,
so
I'm
gonna
push
it.
B
B
This
is
the
probably
allow
me
to
yeah
open
a
pull
request,
so
this
is
probably
whether
the
so
my
app
is
running.
So
what
happens?
Is
it
receives
a
commit?
And
if
you
have
a
look
here,
it
actually
send
in
the
two
checks
from
yeah
yeah.
So
if
you
have
a
look
at
the
text
plug-in
that
kind
of
displays
this
morning,
so
if
I
have
a
look
at
some
of
the
pull
requests,
it
actually
successfully
displays
some
of
it.
B
The
check
see
why
so
the
check
see.
Why
is
this
way?
So
if
whatever
whatever
warnings
we've
opened
up
here,
they
show
up
like
this,
so
we
could
either
take
that
approach
or
we
could
either
take
this
approach,
that
it
just
displays
the
warnings
on
the
checks
plug-in
or
it
goes
ahead
and
displays
the
warnings
on
to
the
conversation
now.
The
conversation
could
become
very
cluttered
because
of
this
because
I,
though
there
might
be
20,
30,
40,
50
warning
gate
objects,
API
limits
it
to
currently
50
for
a
time
but
yeah.
B
So
this
could
probably
be
one
way
of
displaying
the
pull
request
warning
show
up.
This
was
the
demo
that
I
wrote.
This
was
a
proof
of
of
the
road,
so
this
could
be
I.
Think
Tim
has
worked
on
the
authentication
of
it,
so
that
could
probably
be
reused
and
since
I've
already
used,
the
github
are
not
made
use
of
the
github
API
and
I've
written
some
of
the
functions
on
my
own
yeah.
B
That
certainly
could
be
reusable,
but
yeah
I
just
wanted
to
kind
of
display
the
proof
of
concept,
since
we
plan
to
display
warnings
on
the
pull
request.
So
this
kind
of
makes
use
of
the
warnings
report
that
are
generated,
so
the
warnings
the
plug-in
could
develop
could
be
extended,
could
have
an
extension
point,
and
this
could
be
connected
to
that.
So
currently
it's
just
a
static
warning,
but
yeah
this
was,
this
would
probably
be
I,
think
step
one
or
just
a
basic
proof
of
concept.
Yeah,
that's
about
it.
A
A
So
one
way
basically
kind
of
computation,
whatever
possible
proposal
means,
but
it's
not
the
only
way,
because
it's
an
open
source
project
I
mean
deliberately
try
to
give
as
much
information
as
possible
in
a
public.
We
encourage
students
to
collaborate
with
each
other
and,
for
example,
if
you're
interested
to
work
together
and
see
whether
it
could
be
somehow
they
can
fix
it,
so
that
we
could
have
two
proposals
which
which
operate
in
the
same
area
but
can
be
delivered
separately.
A
B
Yeah
would
be
up,
for
collaboration
sounds
like
a
really
cool
idea.
Yeah
I
have
no
issues
in
yeah
in
setting
up,
maybe
in
collaboration
we
could
work
in
parallel
for
the
project.
Maybe
we
could
focus
on.
Maybe,
though,
some
other
set
of
plugins
like
code
coverage
or
something
other
than
one
could
focus
on
the
warnings
and
stuff
sounds
like
a
cool
idea.
I.
Would
it.
A
A
A
D
E
It
seems
like
it's
it's
both
right.
It's
a
it's!
The
the
mentors
agreeing
that
there's
there's
enough
work
for
two
people
to
work
on
it
and
and
I
guess
also
that
the
students
convincing
us
that
there's
enough
work
to
have
two
projects
right,
because
it's
like,
like
one
one
to
GOC
project,
it's
three
months
of
coding.
So
if,
if
we
could
collaborate
and
get
six
months
of
coding
in
three
months,
then
it's
possible.
A
You
know
it's
some
additional
requirements
to
projects,
but
technically
it's
possible,
and
there
are
cases
when
there
was
successful
collaboration.
We
didn't
have
such
example.
You
know
organization.
So
far,
though
we
had
students
close
to
collaborating
with
each
other,
but
other
because,
for
example,
you
know
areas
like
Jake
asked
where
there
was
all
the
love
but
yeah.
You
have
cases
for
a
single
project
idea
person,
but
other
organizations
did
have
them
and
they
say
that
it
actually
works
pretty
well.
A
We
received
two
project
proposals
now,
but
number
four
students
in
the
end
will
be
31st
of
March,
so
we
have
a
pretty
ish
arm
on
the
call
we
have
some.
It
may
be:
Sunita
watch
the
big
passion
and
they
said
hey
now,
I
want
to
work
on
checks,
APA,
who
knows,
and
maybe
other
students
will
submit.
Let's
see
so
we
do
not
know
the
number
and
yeah
they
mouth.
A
Should
be
submitted
individually
and
ultra
four
adults
should
be
deliverable
separately
and
they
should
be
measured
separately.
Why?
It's
and
because
yeah
life
happens,
and
especially
this
year
is
all
dissension,
and
nobody
knows
what's
going
to
happen
tomorrow,
not
speaking
about
the
J
sub
campaign.
So
that's
why
there
is
a
strong
requirement
from
Google
that
projects
could
be
delivered
separately.
Obviously
there
might
be
some
conditional,
etcetera,
but
technically
it's
a
it
might
be
possible,
but
the
each
proposal
should
be
submitted
separately
and
it
should
be
related
separate
here.
A
A
F
F
Thank
you,
I
have
implemented
most
workers
in
the
listeners
and
after
the
collapse
has
sent
a
request
for
our
chicks
for
chicks
realm,
and
my
subscribe
subscriber
will
subscribe
the
event,
and
it
has
contains
message
decree
so
later
when
listener
was
triggered
I
liked
by
Jenkins
problem
I'm
triggered
by
uninitialized.
As
you
can
see
on
the
on
the
graph,
it
will
request
the
chicks
to
event
from
the
message
decree
in
the
event
subscriber
and
you
will
then
I
have
implemented.
F
There's
some
extension
points
and
other
plugins
can
extend
this
these
extension
points
and
to
provide
informations
like
summaries
conclusions
and
I.
Oh
I
gather
those
deformations
just
like
searching
in
the
extension
east
and
get
all
these
the
plugins,
informations
and
Denison
and
then
create
the
check
rounds
and,
as
you
can
see
in
later,
I
I
will
do
almost
the
same
thing
on
start
or
uncomplete
and
I.
Just
I
just
have
a
problem
with
my
implementation
for
now,
because
event
is
independent
from
the
Jenkins
Brown.
F
F
F
B
E
F
G
A
F
F
G
B
Yeah,
actually,
that
chaccaron
is
probably
the
the
cheque
suit
that
the
pull
request
parcels
could
be
is
very,
very
useful
in
actually
posting
back,
because
that
the
cheque
suited
event
basically
sets
up
your
entire
pipeline.
So
that's
the
first
event
you
receive
as
soon
as
you
open
a
pull
request
so
moment
with
the
pull
request.
Bang
you
get
a
check
suit
and
you
can
actually,
on
the
basis
of
that
checks,
would
start
your
entire
pipeline
and
so
I
guess.
Tim
has
made
that
part.
I.
Think
thanking
the
data.
B
So
yeah,
if
that's
possible,
because
if
Jenkins
is
a
github
app
is
possible,
then
it
makes
this
part
very,
very
simple,
because
then
the
warnings
plugin
and
the
code
coverage
API
plug-in
just
need
extension,
because
the
app
will
in
generate
a
token
for
every
organization.
I
will
be
there
for
defense,
any
building
so
yeah.
It
makes
much
much
easier
if
drinking
lose
an
app
gets
delivered
quite
easily.
I,
don't
know!
If
that's
a
prerequisite
for
this
project
but
yeah.
If
that's
there,
then
it
makes
the
project
will
not
easier.