►
From YouTube: 2021 12 07 Jenkins Infra Meeting
Description
Jenkins infrastructure meeting with discussions of new improvements, recent outages, and future agenda topics for build and test acceleration
A
A
A
A
B
It
has
congratulations
to
damian
for
being
elected
with
uncontested
as
the
jenkins
infrastructure
officer-
that's
great,
and
and
yes,
there
have
been
some
other
others
as
well.
So
I've
accepted
the
position
as
documentation
officer
and
I'm
a
member
of
the
board
and
thanks
to
oleg
for
continuing
to
serve
as
a
member
of
the
board
as
well.
A
A
A
B
I
I
I
don't
I'd
have
to
do
some
I'll
have
to
do
some
research,
so
the
it's.
I
think
it's
a
good
good
point
to
realize.
Oh
we've
got
a
service
there
that
I
thought
it
was
something
about
underst,
surveying
and
understanding
what's
what's
distributed,
but
how
it's
different
than
stats.jenkins.io-
I
don't
know
so
we're
just
gonna-
have
to
do
the
research.
A
So
let's
ask
olivier
for
help
on
that
part.
If
it's
okay
for
everyone,
unless
team
has
an
idea,
I
will
start
by
asking
on
irc-
and
I
I
assume
team
and
olivier-
should
be
able
to
answer,
but
the
machine
is
up
to
date
at
least,
and
there
is
an
apache
server
that
answers
http
not
authorized
that
asks
for
a
password.
So
it's
a
private
service
or
there
is.
There
might
be
some
specific
endpoint
that
I'm
not
aware
of.
I
haven't
checked
the
access
log.
A
A
Is
there
any
question
about
that
part
yep
next,
one,
so
pulpit
cleanup
thanks,
rv
and
team
for
helping
me
so
the
puppet
cleanup
is
we
started
by
removing
the
some
part
of
the
prepaid
code
that
is
not
used
since
a
few
weeks
month
or
years
for
some
we
started
by
kubernetes.
So
we've
put
all
the
pull
requests
on
the
nuts
that
we
have
done
until
now.
That
was
focused
on
the
roles.
A
Now
we
will
start
starting
next
week,
also
removing
machines
that
doesn't
exist
anymore
from
the
inventory
we
had
to
do
that
on
the
I
think
that
was
the
last
that
there
has
been
one
pull
request
that
rem,
where
removing
the
roll
was
not
sufficient.
We
also
had
to
remove
the
machine
in
order
to
be
sure
that
it
was
breaking
but
or
at
least
not
the
test.
A
So
let's
continue.
Why
do
we
want
to
remove
that
code?
Because
then
we
will
have
to
work
on
upgrading
puppet
dependencies
and
test
rns,
because
right
now
it's
using
it's
not
using
the
same
dependency
tree
for
production
and
the
testing
environment.
We
cannot
upgrade
without
breaking
the
test
environment
and
the
two
kinds
of
tests.
Unit
tests
and
operational
tests
are
based
on
bricks
and
foundations
that
are
to
hold,
and
that
should
be
changed.
A
So
the
main
goal
will
be
switching
all
the
testing
harness
either
you
need,
or
or
end-to-end
to
the
puppet
development
kit
aka
pdk,
which
is
a
tool
set
that
works
on
multi-platform
that
allows
testing
and
managing
all
the
lifecycle
of
the
test
for
puppet
roles.
Profiles
and
also
simulate
machines.
As
docker
container.
A
Once
we
will
have
switched
all
the
test
harness
the
existing
tests
that
can
be
reused
as
much
as
possible.
Then
we
should
be
able
to
have
one
line
of
dependency
and
we
can
start
improving
things
such
as
running
end-to-end,
test
on
the
master
branch
or
like
this,
and
we
should
we
might
be
able,
in
the
future,
to
go
back
to
a
staging
environment.
A
A
A
B
A
A
A
A
The
postmortem
has
been
pushed
a
few.
A
few
days
ago.
We
showed
the
freeze
and
publish
it
next
week.
So
any
comments
is
welcome.
Thanks
harvey
for
the
initial
review
we
had,
I
hired
to.
I
have
to
publish
the
outage
two
weeks
ago
from
jenkins.you
mark.
Did
you
have
time
to
go
over
that
one?
I
did
I
I
made.
B
B
Were
yeah
there
were
one
or
two
places
where
I
added
a
question.
I
the
the
description,
seemed
reasonable.
I
think
I
understood
it.
I
liked
the
your
plan
for
the
things
we
should
do.
There
were
one
or
two
things
about
okay.
Should
we
also
consider
this?
There
was
in
the
long
term.
I
added
a
question
and
I
think
it's
you've
already
mentioned
it.
We
may
consider
in
the
future
long
term
having
a
way
to
do
prototype,
setups,
yep.
B
A
B
A
B
At
devops,
world
2021
gradle
enterprise
did
a
30-minute
presentation
on
their
build
and
test
acceleration
product
and
and
they
I
happened
to
talk
with
them
afterwards,
and
they
said
oh,
yes,
we
love
to
have
open
source
projects,
use
gradle
enterprise.
We
let
them
do
it
for
free.
We
grant
them
a
license
and
we
run
a
series
of
experiments
to
identify
which
things
we
should
work
on
and
then
work
on
those
things
and
watch
the
results
and
then
based
on
the
results,
decide
what
to
work
on
next
it.
B
B
The
some
of
their
technology
has
the
ability
to
decide
that
a
dependency
has
not
been
changed
and
skip
tests
as
a
result,
and
we've
got
a
major
cost
in
our
a
major
portion
of
our
execution.
Time
in
on
ci.jenkins.io
is
in
fact
running
tests,
and
I
know
in
the
code
that
I
maintain
many
times
the
the
test
that's
being
executed
is
absolutely
unaffected
by
the
code
change
that
was
just
submitted.
B
B
Theirs
is
using
some
machine
learning
to
decide
to
to
make
heuristic
guesses,
which
tests
should
be
run
and
which
should
not,
and
jesse
thought
that
that
was
probably
more
likely
to
help
us,
because
it's
not
as
strictly
dependent
on
whether
or
not
a
dependency
changed,
and
so
my
thought
was.
We
also
invite
someone
from
launchable
to
present
to
the
to
the
infra
team.
B
After
conversations
in
the
in
the
mailing
list
my
goal,
there
is
really
accelerate
accelerate
jobs
by
reducing
the
number
of
tests
we
run
so
that
we
only
we
run
tests
that
are
important
or
useful,
not
every
test.
Every
time
would
would
it
be
okay
with
the
three
of
you
if
we
invited
gradle
to
attend
this
meeting
next
week
for
a
for
a
an
up
to
15
or
20
minute
presentation
and
question
and
answer
yes.
A
Yes,
yes,
please,
that
will
make
sense.
Do
you
do
you
think
that
we
might
want
to
to
do
a
specialized
meeting
with
some
people
from
development
teams
such
as
jesse
or
james
or
oleg,
because
here
the
thing
is
that
as
infrastructure
people
we
might
not
be
at
use
of?
How
could
we
consume
gradle?
So
I
I
fear
that
we
will
have
a
well
shaped
discourse
that
will
be.
A
Oh,
our
tools
is
solving
this
and
this,
but
we
might
not
be
able
to
do
the
correlation
with
what
is
being
done
on
the
I
don't
know
the
bomb
or
all
these
costly
jobs.
We
don't
really
know
what's
under
the
hood
for
us,
so
we
might
need
the
expertise,
at
least
for
the
usage
or
the
weight
work
from
jc
on
the
other,
because
in
fact,
for
us
it
will
be
more
okay.
A
If
we
have
to
use
this
as
infrastructure
team,
how
can
we,
what
are
the
requirements
for
us
to
install
what
would
be
the
impact?
So
if
we
do
only
during
the
jenkins
infrastructure
meeting,
that
will
be
only
okay?
What
are
the
steps
to
install?
What
are
the
constraints
and
are
we?
Okay,
but
then
we
cannot
decide
anymore
because
yeah
we
don't
manage
that
that
software
stack
them.
B
B
I
think
if
we
then
say:
okay,
we
think
the
infra
impact
would
be
acceptable.
We
we
may
want,
then,
to
consider
a
separate
session
after
infra
assessment,
a
separate
session
that
says:
okay,
how
do
we,
what
will
our
objectives
be
and
what
are
the?
What
will
our
measures
be
and
how
will
we
decide
if
we
were
successful
or
not
and
and
that
would
feel
like
a
great
place-
to
involve
a
skilled
developers
who
understand
more
about
the
details
of
bills
of
material
and
dependencies.
A
Be
careful
to
tell
maybe
both
companies
that
they
will
need
to
do
two
meetings
with
two
different
interlocutors,
so
they
can
come
with
this
course
that
will
be
adapted
to
the
internet,
culture
they
met
and
they
won't
lose
their
time,
and
in
our
case
we
won't
have
to
try
to
understand
the
under
the
hood
that
gradle
does.
While
we
are
interested
on
the
infrastructure
impact.
B
No,
no
actually
there,
they
said
that
their
biggest
acceleration
is
by
letting
gradle
enterprise
help
maven
build,
so
so
the
for
me
that
was
very
and
and
I'm
less
interested
while
while
builds
may
help
I'm
much
more
interested
in
the
test
avoidance
attribute
than
I
am
in
the
build
acceleration
build.
Acceleration
will
will
certainly
help
us
a
little,
but
avoiding
tests
could
help
us
an
awful
lot,
and
so
that
was
the
intent
of
the
conversation
with
them.
B
And-
and
I
that's
why-
I
think-
a
presentation
next
week
on
on
what
their
techniques
are
for
the
first
10
minutes
that
they
present
should
give
us
a
at
least
a
high
level
overview
of
why
they're
able
to
accelerate
maven
and
what
their
techniques
are
and
you'll
ask
questions
about?
Okay,
what
would
that
mean
on
our
dns
infrastructure
on
our
service
or
service
infrastructure?
B
C
B
C
Sorry
there
are
two
different
things:
firstly
written
in
the
same
format;
secondly,
changing
the
engine
under
the
hood,
because,
let's
assume
there
is
supply
chain
vulnerability
on
the
gravel
side,
due
to
whatever
reason,
it
means
that
humeva
cracks
gradle.
They
can
instrument
it
and
basically
modify
jenkins
deliverables
without
us.
Knowing
about
it.
B
B
It
will
and-
and
it's
it's
a
good
point
that
we
should
probably
invite
well
do
we
want
a
separate
session
with
the
gradle
enterprise
team
to
specifically
address
security
topics.
I'm
I'm
not.
I
think
it
would
be
more
than
we've
got
capacity
for
to
fit
that
into
a
15-minute
segment
during
the
infra
team
meeting.
But
I
think
security
concerns
are
a
valid
place
as
well,
not
just
developer.
C
C
To
be
honest,
I
in
the
currency
is
that
I
don't
particularly
see
point
in
infrared
discussion,
so
I
guess
intent
from
the
infrastructure
team
site
is
clear.
I
reduce
the
cost
for
the
bills
and
probably
shorten
them,
but
here
I
think
that
the
vast
majority
of
input
should
come
actually
from
developers
here.
A
You
so
do
we
still
keep
them
to
present
at
least
the
infrastructure
and
technical
requirement
at
first.
That
will
be
a
first
opener.
I
don't
see
any
hormones
keep
doing
what
you
propose
to
10
15
minutes.
Next
week
I
mean
worst
case
we
lose
a
15
minute
of
our
life
and
that
will
start
triggering
discussion,
at
least
on
the
security
and
infra
part
and
requirements.
A
C
A
A
A
A
A
Yeah
good
yeah
private
message:
okay,
thanks
mark
we'll
see
if
we
can
reach
kk
no
emergency
but
yeah.
That
could
be
good.
If
we
can
do
that,
if
he's
busy,
we
can
totally
take
over
again
that's
the
message
he
proposed
this
help,
which
is
really
nice.
It's
just
that
we
want
to
be
sure
that
he's
not
rushing
this
thing,
oracle
cloud,
yes
mark.
If
you
can
unsure,
I
I
used
to
have
an
account,
but
I
cannot
get
back
my
password.
A
The
password
I
have
is
mentioned
as
not
working,
so
I
assume
that
either
I
don't
have
saved
the
correct
password
or
my
account
has
been
disabled.
I
can
tell
with
the
error
message
so
if
you
can
just
check
that
team
rv
hi
and
we
have
the
access
and
in
order
to
confirm
that
it
work,
my
goal
will
be
to
create
an
account
for
stefan
soon,
so
that
will
confirm
that
we
are
multiple
person
that
can
manage
the
account.
A
Yes
or
wherever
it
good
good
point,
I
forgot
to
send
an
email
to
tyler
so
still
to
do.
I
owe
about
the
io
domain
renewal,
so
I
still
haven't
emailed
you.
If
you
have
question
on
that
topic,
please
read
the
news
from
last
week:
there
is
an
email
to
get
information
and
legacy
knowledge
from
taylor
about
the.
A
A
C
A
A
A
Where
is
it
because
if
it's
on
azure,
for
instance,
it's
already
available
for
the
linux
foundation-
and
there
is
nothing
to
do
for
us
because
they
already
have
access
the
world
as
your
infrastructure,
dns
zones
are
managed
on
azure.
So
my
guess
is
that
I'm
sure
we
have
also
the
azure
as
registrar,
but
we
have
to
check
that.