►
From YouTube: End User Panel (full session)
Description
Jenkins Contributor Summit June 25, 2021 End User Panel (full)
End user panel presentations from Andrey Babushkin, Ioannis Moutsatsos, Ivan Fernandez, and Victor Martinez
B
Yeah
hi,
my
name
is
andre
babushkin
and
currently
I
work
for
intel
in
intel
open.
We
know
to
kid
projects
and
we
use
jenkins.
We
use
drinking
since
the
inception
of
our
project
it.
As
far
as
I
remember
it's
2018
and
the
oldest
jenkins
version.
I
was
able
to
find
this
2.1
or
so
so
we
have
seen
many
updates
we've
seen
how
jkusk
was
created,
we've
seen
ui
improvements.
B
We
I
think
we
have
upgrade
issues
only
once,
and
I
can't
remember
when
it
was
last
time.
So
this
part
of
jenkins
is
very,
very
great
and
most
of
us
experience
issues
I
think,
is
connected
with
the
fact
that
oprah
mina
is
not
a
java
project
right.
So
we
don't
have
any
java
experience,
and
you
know
when
something
goes
wrong
with
jenkins
or
in
jenkins
pipeline
they're
huge
stack,
traces,
mentioning
some
strange
concepts.
Some.
B
We
sometimes
we
want
to
specify
that
this
build
is
dependent
on
from
this
build,
and
this
build-
and
currently
we
cannot
do
this
in
our
multi-drop
pipeline
right.
So,
basically,
that's
all
that
I
was
thinking
of
a
few
day
for
a
few
days
after
end
user,
if
you
ux
panel
announcement,
so
I
think
that's
all.
A
A
Yeah
so
yeah,
why
I'm
asking
because
it
actually
supports
speaking
reports
by
various
factors
and
tags
and
programming
languages
if
you
want
so
if
the
user
experience
today
is
what
you
would
like
to
see,
maybe
it
could
be
a
good
referral
for
indonesia.
I
believe
that
the
unit
plugin
currently
uses
github
issues
and
team,
who
is
on
the
call
he's
currently
one
of
the
maintainers
of
the
g
unit,
plugin.
B
Yeah,
but
like
test
reports
is
just
one
example
of
why
we
need
to
split
our
jobs
out
by
playing
to
a
few
jobs
right.
Other
thing
is
amount
of
logs.
We
need
to
see
and,
like
we've
tried
to
put
this
into
one
big
pipeline,
but,
like
just
imagine,
you
have
parallel
steps
with
ubuntu,
centos,
debian
and
windows
and
mac
os
and
inside
each
parallel
stage.
B
C
I'm
not
talking
about
the
stage
overview
or
anything
like
I'm
purely
talking
about
the
test
result
reports
as
in.
If
you
go
to
the
build
slash
test
report,
you
will
get
kind
of
I'm
just
trying
to
pull
up
an
example
on
my
instance,
so
I
can
tell
you
exactly
rather
than
just
going.
I
think
it
works
like
this
based
on
my
memory.
A
B
A
A
Personally,
I
think
that
zhinki's
pipeline
engine
supports
it
in
principle,
but
it
requires
a
significant
rework
of
how
our
desales
implemented
so
right
now
there
is
no
way
to
actually
implement
them
jenkins.
You
can
just
have
parallel
jobs,
which
well
basically
start
from
very
beginning.
Then
you
could
probably
use
a
join
or
milestones
plugin
to
actually
do
some
dependencies,
but
it
would
be
quite
complicated.
B
We
actually
have
tried
to
use,
I
don't
know
the
name
of
the
plugin,
but
it
has
added
stage
like
awaits
or
something
like
that,
but
it
seems
there
was
some
bug
in
this
plugin
and
we
have
received
some
deadlocks
in
our
pipelines,
so
we
stopped
using
that,
but
actually
we
use
jenkins
not
only
for
continuous
integration
purposes.
We
run
many
many
tests
in
our
nightly
and
weekly
validation
cycles
and
our
weekly
cycle
is
about
3
000
jenkins
bills,
and
it's
quite
a
lot.
C
A
A
So
thanks,
andre
and
yeah,
I
think
that
we
could
try
a
deeper
dive
later
so,
for
example,
if
your
team
will
want
to
join
together
so
that
we
deep
dive
into
your
topics,
actually
I
had
an
honor
to
go
to
new
zealand
and
present
there
at
one
of
meetups
and
yeah.
I
know
that
there
is
a
lot
of
jenkins
users
there,
so
we
could
organize
something
specifically
to
the
different
use
case.
For
example,
if
you're
interested
in
jcask
and
pipeline,
you
can
invite.
B
A
A
A
C
D
D
But
back
in
2013,
I
discovered
jenkins
myself,
I'm
a
I'm
a
trained
phd
molecular
biologist,
but
I
went
back
to
school.
I
got
a
master's
in
software
engineering
and
I
was
for
a
long
time
interested
in
in
software
development
and
I'm
in
a
in
an
interesting
intersection
of
medicine
and
data
science.
Now,
which
makes
a
lot
of
these
things
really
really
interesting.
D
Jesse
importantly,
my
colleague,
who
is
now
in
a
new
zealand
bruno
kinoshita,
who
developed
some
of
the
key
plugins
for
these
and
participants
in
the
gsoc
2020
last
year,
where
we
developed
a
machine
learning
plugin
for
for
jenkins.
So
why
use
jenkins
for
life
science
applications?
Really?
There
are
a
lot
of
standardized
things
that
jenkins
offers
that
are
key
enablers,
such
as
the
accessibility
of
the
jobs
via
web
portal,
the
freestyle
parameterized
jobs,
easy
deployment.
You
know
the
super
rich
plug-in
ecosystem.
D
I'm
not
going
to
read
this
this
whole
list,
but
these
are
what
I
call
sort
of
the
standard
enablers
of
jenkins
that
have
made
these
possible
and
the
benefits
that
this
offers
is
that
life
and
data
science
pipelining
really
requires
integration.
A
lot
of
different
utilities,
applications,
custom
script
tools
and
jenkins
able
to
do
all
of
that.
Finally,
we
have
developed
this
concept
of
one
page
web
apps
on
a
shoe
string.
D
People
can
go
to
a
jenkins
job
interface
and
be
able
to
execute
an
entire
data
analysis
or
data
ingestion
and
processing
and
parsing
in
a
very
reproducible
way.
That
leaves
a
really
good
what
we
call
data
provenance
path,
where
we
can
always
determine
where
the
data
came
from
and
finally,
through
this
similar
web
portal,
we're
able
to
to
share
this
data
with
others
and
and
and
collaborate.
D
Nonetheless,
you
know
there
is
a
kind
of
any
impedance
mismatch
between
develop
and
operations
and
science
and
just
always
as
a
kind
of
funny
point.
I
bring
this.
This
word
artifact
that
we're
using
in
gen
games
and,
of
course,
artifact
is
used
with
the
idea
of
something
that
jenkins
creates,
but
for
science
this
is
really
a
serious
observation
and
a
bad
thing,
something
that
you
do
not
want.
So
you
know
just
that.
D
D
The
builds
are
almost
always
deleted
and
the
artifacts
are
automatically
tested
on
the
scientific
side,
though
there's
nothing
such
as
the
concept
of
an
scm
for
for
data
and
instruments.
The
files
are
all
over
the
place,
whether
it's
on
on
a
particular
instrument
on
a
local
network
drive
the
pipelines
are
really
discontinuous.
It
consists
of
an
ad
hoc
mix
of
the
jenkins
jobs.
D
Different
tasks
are
encapsulated
in
separate
jobs
that
need
to
provide
input
and
output
to
each
other.
The
builds
are
almost
never
deleted,
because
this
is
really
primary
data
that
you're
generating
it's
not
a
kind
of
a
you're,
not
superseding
all
the
data
or
old
jars
or
old,
builds,
and
the
artifacts
are
really
inspected,
annotated
and
curated
by
the
scientists,
rather
than
in
an
automatic
way.
D
So
what
we're
missing
and
still
is
sort
of
this
configuration
exploration,
dependency,
management,
understanding
where
these
things
is
what
you
see
on
the
right-hand
side
is
a
kind
of
my
attempt
to
roll
my
own.
This
is
actually
the
parameters
in
a
in
a
particular
job
and
they
depend
on
each
other
and
so
and
they
depend
on
groovy
scripts
and
strip
flips
that
are
executed
as
part
of
the
job.
D
So
this
is
sort
of
you
know
our
own
version
of
trying
to
understand
the
configuration
better,
but
it
would
be
great
if
we
had
a
kind
of
a
better
supported
tool.
Search
and
metadata
are
still
issues.
I
think
in
the
standard
version
of
jenkins,
searching
for
artifacts
across
different
builds
is
still
very
difficult,
build
level
metadata
is
not
searchable
and
it's
not
generated
very
easily
and
the
same
thing
across
builds.
D
I
call
it
relational
builds
where
you
know
a
downstream
build
will
depend
from
two
or
three
upstream
builds,
and
it's
very
difficult
to
sort
of
document
that,
and
it's
even
more
difficult
to
do
a
cascade,
which
we
would
like
to
do.
If
you,
if
you
delete
a
primary
artifact
on
which
a
bunch
of
analysis
are
dependent
on
stream,
you
would
like
to
have
the
opportunity
to
at
least
identify
those
validate
them
and
delete
them.
D
Here
is
a
concept
that
is
critical
for
what
we're
doing
and
is
solely
missing
from
jenkins.
What
we
call
this
is
the
interactive
pre-builds,
a
lot
of
activity
going
on
before
you
even
start
the
build-
and
this
has
to
do
with
the
fact
that
starting
a
complicated
analysis
in
r
python
image
processing
whatever
requires
the
selection
of
a
bunch
of
parameters
that
they
may
be
appropriate
or
not
for
the
analysis
and
going
through
a
full
build
cycle.
D
Something
that
may
not
go
well
with
a
lot
of
people
is:
please
don't
let
security
function.
You
know
groovy
script,
execution,
inline,
javascript
html
are
keys
for
the
kind
of
things
that
we're
doing
and
we
have
been
struggling
and
struggling
to
maintain
their
functionality
in
the
present
scheme
of
security
improvements.
D
Finally,
I
would
like
to
say
that
you
know
we're
talking
about
a
lot
of
big
companies
are
using
jenkins
and
about
a
lot
of
you
know:
big
installations
junkies,
but
for
the
life
sciences
and
data
sciences,
we
cannot
forget
how
jenkins
would
fit
into
sort
of
the
environment
of
an
academic
lab
where
you
know
there
is
academic
lab
doing
some
research.
They
need
to
deal
with
their
data
in
their
laboratory
instruments
and
they
do
have
one
developer
there.
D
A
A
We
discussed
them
a
lot
of
the
previous
summits
and
I
think
that
it's
a
really
valid
points
from
an
user
standpoint
who
actually
want
to
keep
junkies
as
a
framework
for
use
cases
like
your
informatics
or
whatever
way
you
still
don't
get
like
games
out
of
the
box.
But
you
want
to
use
a
power
assistant,
automation,
engine.
B
Yeah
I'm
gonna.
I
just
want
to
add
something
about
security.
I
need
to
make
a
confession,
because,
since
the
beginning
of
our
project,
we
use
permissive
script,
security
plugin
and
we
use
it
just
because
we
are
not
creating
new
plugins.
Instead,
we
put
all
our
custom
functions.
Functions.
Github
api
integrations,
gitlab
api
integrations
something
like
that
into
our
jenkins
shark
library
and.
B
A
A
Yeah
so
yeah,
basically,
we
have
10
minutes
more.
So
would
you
like
to
continue
feedback
from
iranians
for
now,
or
rather
take
it
offline
because
yeah,
there
is
a
lot
of
feedback
to
discuss.
I
think
it
would
be
rather
feasible
to
have
something
like
one
hour
session
or
maybe
on
half
a
session
together
with
whomever
is
interested
and
talk.
E
E
Yeah,
I
I
want
to
make
a
point
about
the
the
they
use
the
try
to
to
avoid
the
the
security
script
like
to
in
the
yankees.
Sorry
library,
and
we
have
a
really
big
solid
and
we
don't
need
to
to
approve
any
any
script
or
or
use
that
plugin
for
anything
we
can.
We
will
manage
to
to
do
everything
that
we
want
without
have
to
worry
around
the
script
security
plug
with
scrapes
with
binaries
with
other
things.
So
I
I
think
that
this
is
not
required
to
to
use
the
plugin.
A
A
B
B
F
B
D
In
our
case,
a
lot
of
the
scripts
are
part
of
the
parameters
in
the
ui,
we're
using
the
active
choices,
plugin
that
creates
sort
of
interactive
cascading
parameters
and
creates
for
us
these
html
and
javascript
elements
that
were
interested
for
more
interaction
in
introducing
graphics,
libraries,
scientific
libraries,
imaging
and
so
on
and
yeah
all
of
those
for
us.
We
need
to
go
and
approve
those
scripts.
E
A
current
task
that
is
used
in
all
the
pipelines
and
we
have
some
regression
or
wherever
we
move
that
stuff.
That
is
the
current
to
the
previous
one,
and
we
fix
the
the
issue
in
the
time
we
release
the
the
library
ten
times
five
times
and
between
five
and
ten
times
a
week,
and
we
managed
to
have
the
the
library
in
version,
without
any
issues
in
the
three
years
that
we
are
using
the
library
more
or
less.
G
So
this
one
on
the
top
is
like
you
were
saying
about
this
ability,
so
I
want
to
be
the
voice
as
well
from
some
of
the
users
that
we
have
at
the
elastic,
like
some
of
them
find
really
hard
when
you
run
so
many
things
in
parallel
on
a
pipeline
to
debug.
What's
going
on
right,
so
that's
one
of
the
issues
we
hear
about
quite
often
how
to
make
this
easier
to
debug
from
the
console
our
potential
one,
because
sometimes
he
doesn't
even
reload
correctly,
then
the
locks
in
the
ui.
G
G
And
also
about
the
usability,
I
think
that's
also
a
good
point,
the
one
regarding
to
make
the
life
easier
from
the
end
user,
how
to
restart
a
particular
stage
when
the
bill,
or
that
particular
pipeline
failed,
not
working
in
all
the
cases,
and
that's
probably
one
of
the
key
areas
as
well.
How
we
can
make
people
way
of
working
with
the
jenkins
pipelines
easier
that
they
don't
really
need
to
wait
for,
as
I
already
hear,
like
some
bills,
take
hours
and.