►
From YouTube: 2022 01 18 Jenkins Infra Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Can
you
see
my
screen
and
can
you
read
it?
Yes,
okay,
let's
get
started
so
welcome
everyone
to
the
jenkins
infrastructure,
weekly
team
meeting.
We
are
the
18th
of
january
2022.,
so
mark
stefan
rv
and
I
are
present
today.
A
Last
week
the
security
release
that
happened
last
week
during
the
wednesday
so
the
day
after
previous
team
meeting,
everything
went
very
well
on
the
open
source,
so
we
are.
For
the
rest,
I
don't
know
we
were
able
to
release
in
the
in
the
timestamp
lts
1lts,
one
weekly
and
more
than
20
plugins.
So
thanks,
everyone
involved
on
that
process
directly
indirectly.
A
Thanks
for
the
support
that
was
quite
a
success,
even
though
just
for
later,
a
reminder
is
that
we
we
had
a
weekly
that
was
triggered
the
day
before
accidentally,
because
we
all
we
all-
have
been
bitten
by
the
fact
that
weekly
are
triggered
automatically
each
week
and
if
we
disable
a
job
on
the
ui,
the
automatic
system
might
override
that
part.
We
need
to
find
the
solution.
A
There
is
an
issue
on
the
jenkins
san
francis
process
for
that
so
next
time
we
should
have
a
solution.
So
anyone
with
ideas
and
ready
to
implement-
let's
go
for
that.
We
can
speak
about
that
later.
But
that's
a
reminder.
Next
time
we
have
to
be
careful
on
that
part.
It's
not
enough
to
disable
the
job.
A
A
We
do
there
is
a
weekly
that
will
happen
today.
I
haven't
checked
the
status,
yet
it
might
break
because
we've
I've
merged
with
the
help
of
team.
Yesterday,
some
fundamental
changes
on
the
pipeline
that
run
this
release
and
packaging
and
there
might
be,
let's
say,
punctual
weekly
between
today
and
next
week
they
might
have
some
weekly,
because
if
we
see
too
much
rate
or
too
much
changes,
we
want
to
trigger
intermediate
weekly
to
validate
the
new
process,
changes
that
might
have
been
introduced
in
the
meantime.
A
Okay
before
we
go,
I
need
someone
to
drive
the
meeting
next
week
because
I
should
be
a
day
off,
so
I
won't
be
able
to
run
and
prepare
the
meeting
who's
gonna
volunteer.
For
that
we
can
share
the
you
can
share
the
burden
between
multiple
persons.
A
A
A
Okay,
let's
proceed
first,
a
few
minor
subjects
that
we
delayed
during
the
past
week
because
of
all
the
activity,
repo
cijenkins.org
have
a
certificate
that
was
expected
to
be
to
be
valid
until
march
this
year.
A
Thanks
a
lot
kosuke
for
dealing
with
g-frog,
he
took
time
to
generate
the
required
elements
and
send
a
new
certificate
with
its
key
encrypted
to
gfrog.
They
updated
successfully
immediately,
so
everything
went
well,
no,
no
service
outage,
and
now
the
new
certificate
is
in
place
on
repo
seitan
kinsa
talk,
so
thanks.
Kosuke
we've
had
it
on
the
team
calendar,
which
is
run
brand
new
less
than
one
year
old.
A
Integration
and
partnership
started
with
netlify,
we
have
an
open
source
account
and
we
are
able
to
provide
website
preview
for
jenkins
dot,
io
plugins
in
scio,
and
I
think,
a
third
one
any
of
our
static
websites.
So
we
use
netlify
before
for
status.
We
still
need
to
migrate
status
to
this
new,
but
that
allows
us
to
provide
on
each
pull
request
automatically
netlify
generate
the
website
and
add
a
link
directly
into
the
pull
request.
So
the
author
or.
C
A
A
A
Ok,
just
a
note:
gavin
did
the
hard
work
on
providing
safe
mechanism
to
ensure
that
this
deployment
preview
happens
and
everything
is
run
from
infra
ci,
so
he
took
care
of
using
the
native
github
deployment
object,
which
provides
advanced
check
that
maps
to
deployments
that
allows
to
say
that
commit
is
deployed
at
that
place.
If
we,
you
add,
commit
on
the
request,
your
new
deployment,
etc,
and
also
the
website
is
not
built
by
netlify.
A
We
have
a
lot
of
free,
but
given
the
high
activity
on
these
websites
in
term
of
contribution,
we
will
completely
burn
these
free
credits.
So
instead,
if
I
understand
correctly
given
implemented
something
that
we
build
on
our
own
machine
that
we
pay
for-
and
we
use
the
netify
preview
that
provide
unlimited
preview
for
free.
A
He
worked
hard
on
the
safety
of
that
system,
meaning,
for
instance,
on
jenkins
dot.
Io.
An
external
contributor
will
see
a
ci
bill
that
will
take
care
of
building
the
website
on
cr
jenkins
io.
So
you
have
a
feedback
as
contributor
that
is
available
publicly
and
in
parallel
trigger
a
build
only
for
the
deployment
part,
so
it
build
a
copy
of
the
site
on
its
own
and
deploy
it
and
then
commit
back.
Add
the
command
to
the
request.
C
So
so
damien
just
to
be
sure
I've
understood.
So
there
is
now
an
infra.ci
component
for
the
www.jenkins.io
site
that
really
wasn't
their
pre
or
or
it's
a
new
component.
That
was
not
there
before.
Specifically
in
doing
these
deployments
so
they're,
not
we
don't
have
the
credentials
for
netlify
deployments
in
ci
jenkins.
He
successfully.
B
C
A
A
Okay,
quick
one
rating
jenkins
io,
so
it
was
reported
a
few
weeks
ago
that
there
were
some
apache
tokens
appearing
on
the
page
on
different
services,
including
writing,
jenkins,
io,
so
irve
started
the
work
and
then
finished
it
with
the
holy
days.
So
now
we
can
say
that
rating
jenkins
is
not
publishing.
A
Now
we
took
the
opportunity
to
add
automating
update,
clip
or
request
for
production
deployment.
So
each
time
you
have
a
new
version
of
the
image
for
rating
now,
in
the
next
day,
you
will
have
a
pull
request.
Open
that
say:
hey
there
is
a
new
version
of
the
container
blah
blah
blah.
Would
you
want
to
debug
it
that
one
was
missing
good
job.
A
A
The
idea
will
be
to
migrate
that
service
on
kubernetes,
because
it's
running
on
a
standalone
virtual
machine
right
now
which
make
low
value,
so
that
could
be
a
nice
topic
for
rv
or
stefan
in
the
coming
months.
It's
just
there
is
no
priority
on
that,
but
that's
something
to
have
in
mind.
A
Next
topic,
digital,
are,
they
mic?
Is
yours.
B
We
intend
to
run
this
as
an
experiment
for
three
months
to
see
the
easy
associated
cost
and
the
old
other
alternative.
The
part
2
could
be
would
be
to
you
to
add
a
new
agent
as
a
digital
ascent,
vm
vm,
it's
not
started
yet
we
could
do
it.
Let's
do
these
two
parts
simultaneously
or
one
after
the
other.
It's
not
decided
yet.
A
A
They
will
be
on
private
and
isolated
kernels.
They
will
allow
us
to
not
fear
running
docker
on
these
agents
compared
to
pods.
We
have
a
bunch
of
virtual
machine
provider
everywhere.
It's
just
that.
We
need
one
plugin
for
each
cloud
provider
on
jenkins
compared
to
kubernetes.
That's
one
single
plugin.
C
A
Yes,
so
that's
a
balance,
I
don't
have
absolute
answer,
but
gavin
pocked
us
for
good
reason.
That
I
think,
is
right.
Even
if
it
frustrated
me
on
the
because
we
were
working
on
kubernetes
since
sometimes
the
reality
is.
We
have
to
question
that
or
or
improve
the
jenkins
kubernetes
plug-in
as
a
community,
because
there
are
a
lot
of
users
that
stop
complaining
about
these
weaknesses.
A
A
So
that's
really
something
to
push
to
the
let's
say
cloud
native
relative
subject,
maybe
to
other
parts
of
the
community,
I'm
not
sure
where,
where
will
be
the
good
start
on
that
part,
because
I
think
there
some
help
is
needed
to
improve
that
plugin.
A
Thanks
sergey,
as
a
reminder,
that's
part
of
the
partnership
with
digitalocean.
We
have
limited
credits
on
that
area
and
we
will
have
to
write
down
a
blog
post
once
we
will
have
started
after
one
month
of
operation.
That
should
be
a
good
good
start.
We
can
quote
all
the
things,
but
they
asked
us
to
do
this.
We
might
want
to
put
some
logo
somewhere,
but
don't
worry
gavin
will
buck
us
when
needed.
A
A
A
C
C
A
A
A
A
So
stefan
did
all
the
ev
lifting
behind
next
step
will
be
deploying
these
images
and
we
can
start
using
it
and
we
have
delayed
the
work
for
the
windows
containers
because
multiple
issues
and
the
goal
was
to
deliver
as
quick
as
possible
already
the
linux,
because
it
has
value
and
then
we
can
delay
on
windows.
C
A
C
A
A
A
A
We
are
downloading
15
gigabytes
of
docker
image
on
the
windows,
server,
docker
container
system,
that's
half
of
the
time
spent
on
a
release
which
both
the
security
people
and
usual
release.
People
are
not
really
happy
about
this.
That
means
we
should
be
able
to
have
to
decrease
twice
the
time
for
a
release
if
we
can
solve
that
issue,
because
for
sure
we
don't
need
the
world
15
gigabytes,
so
we
have
to
work
on
that
part,
the
different
path
installing
or
need
required
tools,
etc.
But
there
is
some
work
to
be
done
here
for
sure.
A
A
That
logic
is
not
on
jenkins,
suffer,
which
means
the
jenkins
and
farrelly's,
and
the
docker
images
we
are
building
on.
Infra
are
only
to
reproduce
that
process,
but
that
process
should
be
tested
already
on
ci
junk
inside
before
so
basil
did
a
really
huge
work,
and
I
think
it's
not
finished
yet,
but
there
are
much
steps,
but
the
goal
is
that
we
should
have
at
least
once
per
day
a
full
build
of
a
war
that
should
validate
that
we
can
run,
and
I
wonder
that's
a
personal
proposal.
A
If
we
shouldn't
move
all
the
dependency
logic
that
say
you
need
the
tools
to
build
rpm,
you
need
the
tool
to
build
debian
package.
You
need
a
week's
tool
set
to
build
msi.
All
this
logic
should
be
available
to
developer
on
that
repository
and
our
work
on
a
release
and
docker
packaging
should
be
only
specific
to
our
release
process,
meaning
gpg
agent,
inbound
agent,
but
only
tools
specific
to
the
infra.
A
A
A
Sorry,
good
that
change
would
have
impact
on
the
release
process
and
the
security
procedures
on
the
way
we
build
and
release
jenkins.
So
that's
why
discussion
is
needed
before
acting,
because
there
might
be
some
consequences
that
we
haven't
foreseen.
So
that's
why
I
prefer
asking
the
question
before
discussing
and
see,
but
the
value
of
that
will
be
we
we
wouldn't
have
to
transplant
and
cherry
pick
each
change
to
hold
stable
and
we
will
only
have
one
process
that
we
can
run
regularly
and
be
confident.
C
So
so
the
the
safety
check,
I
think
we
need
there
is.
We
need
to
understand
one
of
one
of
the
security
team's
strong
requests
that
we
do
not
have
is
the
ability
to,
I
believe,
it's
stage
or
package
a
a
release
in
a
staged
fashion.
So
we
can't,
we
can't
generate
a
deb
file
or
an
rpm
or
an
msi
that
isn't
published
immediately
invisible.
Do
I
do
I
understand
that
correctly.
A
C
Release
date
got
it
right,
and
so
we
today
we,
the
the
tooling,
does
know
how
to
stage
the
jenkins
war
file
before
release,
but
it
can't
do
the
packaging
and
that
creates
this
critical
path.
Long
long
lead
time
thing
of
building
the
docker
images
takes
a
long
time,
building
the
msi
building,
etc.
Okay,
thanks
damian.
A
Okay,
one
last
important
topic
is
that
it's
been
so
the
13th
of
january
yesterday,
and
today
we
saw
g
frog,
repo
dot,
jenkins,
ci,
org
downloads,
loudness.
A
There
is
an
issue
that
has
been
opened
on
our
new
lds
by
end
user.
The
consequence
for
end
user
is
that
every
builds
of
a
jenkins
plugin
that
requires
a
notifier
from
ripo
jenkins.
Ci
is
terribly
slow
like
less
than
five
kilobytes
per
seconds
in
download.
When
you
are
lucky,
let
me
find
the
issue
we
have.
B
A
I
have
it
okay
thanks,
so
we
have
ask
g
frog
support
for
feedbacks
to
them.
Sometimes
they
ask
us
for
more
details,
because
I
think
they
are
running
blind
with
our
initial
requests.
So
rev-
and
I
worked
on
an
answer
earlier
today,
so
we
gave
them
proof,
we
gave
them
reproducibility
and
we
gave
them
the
metric,
because
not
only
the
download
that's
slow
on
ci
gen
kinsio,
it
fails
the
builds
because
we
reached
a
one
hour
timeout
for
bills
that
should
take
5
or
10
minutes.
A
A
A
I
think
that's
jc
glick
that
asked
the
question
to
let's
say
leverage
the
impact
of
this
at
least
on
the
sea
agent
inside
your
area
will
be
to
think
again
about
a
service
that
will
be
a
artifact
caching
system
on
our
build
system
that
could
be
used.
So
that
will
be
let's
say
it
was.
If
I
understand
correctly,
it
was
kind
of
nginx
proxy.
We
have
to
configure
our
builds
to
use
it,
and
if
you
use
it,
then
that
system
act
as
a
man
in
the
middle.
A
C
A
Okay,
if.
A
Do
this,
the
two
of
us
unless
someone
is
interested.