►
From YouTube: 2021 07 06 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
Well,
hi
everybody
welcome
for
this
new
jenkins
infrastructure
meeting.
We
are
the
first
week
of
july,
which
is
quite
interesting
summer.
Vacation
way.
A
So
today
to
the
agenda,
we
don't
have
major
announcement
to
share,
so
we
have
a
few
topics
that
we
want
to
cover.
So
first
one
is.
We
had
an
issue
with
repo
jenkins
here.org.
Over
the
last
week
we
had
a
few
stabilization
done.
Untrusted.Ci.
We
have
one
issue
with
updates
cli.
We
also
have
a
topic
on
the
docker
image
that
we
build
in
ship
for
the
jenkins
organization.
A
We
currently
have
someone
going
work
with
puppets
and
few
other
things.
So
the
first
one
is:
let's
go
back
to
the
g
frog
incident.
So
what
happened
last
week,
while
we
were
doing
the
security
release,
we
noticed
that
we
could
not
published
maven
artifacts
under
the
release
repository
and
at
the
same
time
we
discovered
that
gfrog
was
doing
some
maintenance
on
the
service.
So
the
service
was
available.
We
could
download
artifact,
we
could
publish
some
plugins,
but
some
repositories
were
lucky.
A
The
problem
is
because
jenkins,
the
problem
is
because
jenkins
is
looking
at
the
maven
repository
to
know.
If
a
new
version
is
available
and
nobody
would
receive
notification
that
a
new
version
was
published
and
also
because
the
way
we
build
docker
images,
we'll
fetch
the
latest
version
from
the
maven
repository,
and
so
we
could
not
build
and
publish
docker
image
in
time.
So
we
were
able
to
publish
every
other
artifacts
like
the
given
package,
redat
and
so
on.
A
So
those
were
available,
but
the
problem
was
for
people
with
an
existing
jenkins
instance
and
for
to
build
the
car
image.
So
what
we
did
is
because
the
security
release
is
built
in
advance
and
store
on
a
private
maven
repository.
We
just
created
a
virtual
maven
repository
in
front
of
the
release,
one
and
that's
a
secret
one,
the
the
one
used
by
the
security
release,
so
that
was
a
workaround.
A
We
I
think
I
looked
yesterday
and
now
we
were
able
to
to
publish
the
repository.
It
appears
that
the
service
was
degraded
since
the
24th
of
june,
so
yeah
it
took
us
a
while.
So
we
had
discussion
with
people
from
gfrog.
One
of
the
thing
is,
I
still
have
to
update
the
runebook
we
now
have.
We
can
say
we
should
send.
We
should
have
sent
an
email
to
support
gfront.org
to
create
an
issue
on
their
site.
A
So
that's
something,
but
obviously
because
it's
a
free
service,
we
don't
really
have
a
cd
whatever.
So
what
I
would
like
to
be
sure
in
advance
is
that
we
are
notified
for
such
maintenance.
I
mean
it's
not
a
big
deal
to
delay
the
security
release.
I
mean
this
is
something
that
we
like.
We
would
like
to
to
identify
in
the
future,
because
yeah
security
release
involves
a
lot
of
different
people.
Danielle
does
a
great
job
to
do
that,
coordination
in
advance
and
yeah.
This
one
was
not
something
that
we
expected.
A
This
is
the
first
time
that
this
issue
happened
during
the
process,
so
yeah.
We
just
want
to
be
sure
that
it
does
not
happen
anymore.
Any
question.
B
A
So
that
that's
okay,
that's
a
question
that
I
asked
and
I
got
no
answer
to
that.
So
the
problem
is
so:
we've
been
moved
to
the
g4
cloud
recently
several
weeks
ago,
but
before
because
we
are
kind
of
I
mean
because
it's
a
sponsored
instance,
we
don't
have
a
gpro
account,
so
we
don't
receive
gmail.
I'm
sorry
for
the
duck.
C
B
Questions
no
problem:
what
do
you
think
about
starting
by
sending
an
email
to
support
giffrop.com,
to
acknowledge
that
we
use
that
address
to
contact
them
since
they
asked
and
use
that
initial
email
to
ask
for
how
do
we
know
for
the
upcoming?
So
that
will
be
the
an
excellent
support
for
the
question
and
it
will
show
them
a
good
example
that
we
acknowledge
their
their
request.
A
Yeah,
that's
a
very
good
point.
We
should
definitely
send
an
email
to
support
actuallyfrog.org
to
identify
ways
to
to
identify
ways
to
be
notified.
At
the
same
time,
I
know
that
there
are
discussion
with
our
vp
of
engineering
or
something
like
that
to
to
see
how
how
they
could
work
with
us
because
yeah,
that's
that's
a
pretty
big
instance
for
them,
and
it's
a
very
critical
instance
for
the
jenkins
project
as
well
so
yeah.
A
Definitely
any
other
topic
regarding
gene
frog
sounds
good,
so
the
next
topic
is
about
trusted
ci
and
ci
stabilization.
So
this
is
one
more.
Oh
sorry
mark
damian.
You
put
the
topic
to
the
to
the
agenda.
B
B
A
Yeah,
that's
that
was
very
nice,
so
nothing
major
to
report.
Last
week
I
mean
most
of
my
attention
was
with
the
chief
work
with
the
secretary
release,
but
I
accepted
that
yeah
that
was
pretty
pretty
smooth.
B
A
The
next
topic,
which
is
update
cli,
so
we
identify
an
issue
with
the
tli
since
last
friday,
so
something
changed
on
github
site,
so
I'm
not
able
to
authenticate
with
the
github.
I
mean
the
way,
the
the
way
I
wrote
up
the
cli.
I
cannot
authenticate
with
the
github
api
anymore
for
the
ghcr,
so
we
generate
issues,
and
so
right
now
builds
that
need
to
fetch
docker
image
from
the
ghgr
docker
registry
are
failing.
I
have
a
fix
coming,
which
should
be
released
today
or
tomorrow.
A
So
that's
very
brief,
but
yeah
until
until
there,
just
just
that,
you
know
that
that
affects
the
way
we
deploy
hem
charts,
because
once
a
day
we
also
when
we
when
we
deploy
and
we
manage
activities
cluster
we
use
and
file
and
part
of
the
process,
is
also
to
run
update,
cli
to
fetchlet
newer
to
fetch
latest
dependencies,
and
so
because
of
the
series
it's
failing
at
the
moment,
yeah
that
affect
one
of
the
job,
but
most
of
them
in
for
the
rest
of
the
day,
because
we
don't
try
to
update
the
rest
of
the
day.
A
The
next
topic
is
about
docker
images,
so
the
jenkins
here
at
the
jenkins
locker
image.
So
in
this
time
tim
jacobs
started
working
on
how
we
built
and
published
jenkins
docker
images,
so
jenkins
jenkins.
So
this
time
it's
not
really
directly
related
to
the
jenkins
infrastructure.
A
But
what's
what
team
started
here
was
to
use
a
new
feature
provided
by
docker,
which
is
docker
bdx,
to
improve
the
way
we
build
and
published
docker
images.
So
there
is
a
pr
that
demon
put
here,
which
is
the
docker
issues
1139.
So
I
really
encourage
you
to
look
at
it.
It
really
improved
the
visualization
of
the
number
of
combinations
that
we
want
to
do,
and
it
will
also
simplify
how
we
build
docker
image
for
multiple
architecture.
A
So
the
really
nice
thing
is:
is
pr
prepare
the
world
for
a
lot
of
things
coming,
so
we
have
a
lot
of
exciting
features
that
will
come,
so
one
of
them
will
be
to
build
to
use
docker
pdx
to
build
docker
images
for
ppc
64.
s
396x,
but
yeah.
I
really
encourage
you
to
look
at
that
pr
provide
feedback,
because
that
will
have
an
impact.
The
way
we
build
one
of
the
biggest
advantage
that
we
have
right
now
is
it
drastically
reduce
the
big
time.
A
That
means
that,
because
we
built
darker
images
in
paradile,
we
can
also
add
more.
We
can
also
have
more
yeah
docker
images.
So
it's
that's.
That's
really
a
nice
improvement,
anything
to
add
damien.
B
No,
we
are
also
wonky
on
accelerating
the
tests,
but
right
now
we
cleaned
up
updated,
did
some,
let's
take
our
tasks,
so
don't
today
to
look
at
the
issue
tracker.
Just
one
thing:
it's
not
the
pull
request
link
you
have
there
it's
an
issue
where
team,
the
effort
of
listing
everything,
all
the
steps,
each
element
of
the
tool
list
might
be
related
to
a
sub
second
pull
request.
B
The
advantage
is
that
we
have
a
bunch
of
tiny
pull
requests
that
can
be
deployed
to
master
really
soon,
so
we
can
see
the
effect
right
now
and
it
for
to
split
the
work.
So
anyone
interested
don't
state
to
discuss
and
comment
on
the
scope
of
that
issue.
There
is
a
lot
of
detail,
so
that's
interesting
the
impact
for
the
infrastructure.
B
There
is
still
a
link,
it's
about
the
machines
we
propose
for
these
architectures
and
the
security
associated
to
that,
in
particular
using
different
patterns.
So
I
let
you
read,
but
the
impact
is
related
to
how
do
we
use
this
virtual
machine
and
sure
they
are
not
full
in
term
of
our
drive
that
they
are
up
to
date?
And
how
do
we
manage
safely
to
credentials.
A
The
next
topic
is
about
some
work
that
we
are
currently
doing
with
puppets
so
just
to
bring
the
context
about
what
we
are,
why
we
are
spending
a
little
bit
more
time
with
puppets.
As
I
mentioned
last
week,
we,
the
rackspace
sponsoring
and
that's,
and
we
now
have
to
move
to
machine
archive
dodging
kizario
to
another
location
and
we've
been
investigating
either
migrating
that
machine
to
scale
way
or
to
oracle
clouds.
A
The
reason
why
we
want
to
bring
a
new
cloud
provider
is
because
we
have
some
credit
there
that
we
could
use
and,
more
importantly,
we
currently
have
so
the
content
that
we
have
on
archive.
That
jenkins.io
is
already
replicated
on
amazon.
So
we
were
thinking
to
move
that
to
azure
or
to
another
location.
A
We
decided
to
go
with
oracle
cloud
right
now,
because
we
did
some
experimentation
with
the
new
harm
infrastructure,
and
I
mean
that's
working
great,
that's
not
expensive,
because
we,
we
are
still
in
the
free
tier
and
we
have
one
gigabyte
of
traffic,
which
is
enough
for
a
fallback
service.
So
the
idea
now
is
to
deploy
that
that
machine
on
oracle
cloud,
but
we
have
two
constraints
here.
The
first
one
is
in
order
to
use
the
harm
machine.
A
A
We
need
to
be
sure
that
opposite
code
can
work
with
ubuntu
204,
which
imply
bumping
some
puppet
modules,
and
the
second
thing
is:
we
also
need
to
be
sure
that
the
base
configuration
also
work
on
our
architecture,
so
it
does
an
interesting
work,
but
that
forced
us
to
go
back
to
the
puppet
codes
and
update
the
the
dependencies
and
so
on,
while
I'm
testing
and
running
the
tests.
I
I
really
realize
how
much
time
we
haven't
updated
that
that
git
repository,
so
we
have
quite
a
lot
of
updated
dependencies
and
yeah.
A
It's
like
updating
the
let's
encrypt
module
implied
that
you
want
that
you
need
to
upgrade.
I
mean
we
need
to
upgrade
the
firewall,
let's
encrypt
module.
We
need
to
upgrade
a
lot
of
different
private
modules,
and
so
we
have,
I
mean
we
have
some
work
to
do
here.
So
that's
what
I'm
doing
right
now.
So
most
of
my
work
is
under
testing
at
the
moment.
I
know
that
damien
has
been
working
as
well
under
the
testing
environment
for
the
puppet
code.
A
So
what
the
men
try
to
do
is
to
replace
the
background
with
a
virtual
machine
to
replace
that
by
docker
images.
So
it's
faster
to
run
the
test
and
it's
easier
to
replicate.
It.
B
Just
the
point
of
that,
the
goal
is
about
the
request
I
did
along
with
steve
on
the
mailing
list
about.
Do
we
need
the
staging
branch
or
not,
because
on
one
way
the
staging
branch
is
slowing
us
down
and
the
other
way
we
need
some
tests
to
be
sure
that
we
don't
break
the
puppet.
The
issue
is
that
the
master
branch
of
that
triple
repository
doesn't
have
a
deploy
step
as
soon
as
the
code
is
on
the
production
branch,
puppets
pull
it
without
the
ci
finishing
or
the
test
passing.
B
A
No,
no,
so,
no
so
the
reason,
so
the
reason
why
historically
we
had
the
staging
environment
is
because
tyler
at
the
time
was
merging
pr
on
staging
I'm
testing
on
the
staging
branch
and
usually
on
friday,
it
was
merging
the
staging
branch
to
the
master
branch.
A
That's
just
for
that.
So
the
idea
was
just
to
have
to
have
a
buffer,
but
I
don't
think
that
the
staging
branch
still
makes
sense
today.
What
we
did
at
some
point
was
to
automate,
so
we
were
automatically
create
pr
from
from
staging
to
master
branch,
but
yeah.
I
think
we
should
just
get
rid
of
staging.
B
B
A
Next
topic
is
about
terraform
1.0.
I
see
that
you
bring
the
so
yeah.
I
think
that's
demian
who
added
that
topic,
so
the
idea
would
be
to
upgrade
tutorial
from
1.0.
I
mean
that
totally
makes
sense.
I
think
we
need
to
go
one
each
repository
at
a
time,
because
we
have
terraform
code
for
azure
for
amazon
for
datadog,
so
I
don't
know
if
you
want
to
start
working
with
one
in
particular
daemon,
probably
because
that's
the
one,
you
are
the
most
familiar
with.
B
Yep
and
because
this
is
the
amazon
and
that
address,
we
have
a
ci
running,
even
if
the
ci
fails
once
per
week,
but
still
it's
running
automatically.
So
we
need
to
start
with
this.
One
datadog
works
without
any
issue.
I've
tested
it
already
and
I
have
to
some
work
to
do
on
the
aws
might
have
one
or
two
pull.
A
Requests
we
just
if
you
start
working
with
that
terraform.
We
should
be
sure
that
we
have
some
automation
in
place
to
update
on
on
a
regular
basis
when
a
new
version
is
available,
because
what
I
noticed
with
azure
is
that
we
bump
the
version,
and
then
we
just
leave
the
key
repository
there
and
we
don't
don't
retest
and.
B
B
Okay,
yeah,
it's
right!
Now
you
there
is
automated
update
of
the
latest
patch
version
of
terraform,
so
we
are
using
o
dot,
13
dot,
something
and
it's
kept
updated
by
update
cli.
A
B
It's
just
there
is
a
lock
on
the
minor
version,
so
the
lock
will
be
on
1.0
dot,
something
but
yeah.
That
could
be
an
improvement
to
have
something
to
notify
us.
But
the
idea
is
that
1.0
will
freeze
the
syntax
change.
That's
the
premise
of
terraform
one,
not
oh,
for
all
the
branch,
one,
that's
something!
That's
something
that
the
first
production
already
and
there
is
lts
and
that
they're
discussing
about,
but
so.
D
A
A
D
If
there's
anything
actually
to
present,
so
what
we've
got
is
a
report
that
metadata
signature
checks
are
failing
if,
when
referencing
the
allure
plug-in
its
tool
installer,
so
it's
the
tool,
installer
check,
that's
failing,
but
as
far
as
I
can
see
from
inside
the
json
data,
it
looks
like
there
is
no
sha-256,
so
there's
no
checksum
at
all
and
I've
got
to
do
more
investigation.
I
don't
know
if
there's
anything
for
this
meeting,
I
was
worried.
D
A
Okay,
thanks
for
sharing
that
information,
there
is
one
last.
So
I
have
one
topic
that
I
would
like
to
add
to
the
agenda.
I
don't
know
if
you
saw
so
gavin
started
the
discussion
on
this
course
about,
should
we
replace
google
analytics
for
by
another
tool.
Last
week
or
two
weeks
ago,
we
did
some
very
quick
experimentation
with
plausible,
but
yeah.
I
quickly
run
out
of
budgets
on
my
accounts
and
now
giving
starting
I'm
hosting
matamo
to
on
on
his
own
infrastructure.
A
A
We
just
have
to
would
be
nice
to
just
spend
a
little
bit
more
time
to
evaluate
other
options
like
sponsoring
for
long
term,
because
my
what
I
fear
with
that
kind
of
service
is
that
you
have
some
state,
I
mean
you,
have
you
generate
some
data
and
that's
interesting
to
have
those
that
are
on
long
term.
A
I
know
that,
for
example,
in
the
case
of
google
analytics
from
time
to
time,
I
just
try
to
identify
what's
the
trend,
for
example,
who's
coming
I
mean
the
visitors
sometimes
are
coming
from
asia,
sometimes
they're
coming
from
america
and
europe
and
so
on,
and
so
it
helped
me
to
identify
where
to
deploy
service,
and
so,
if
the
idea
is
free
to
replace
by
something
else
than
google
analytics,
then
we
should
be
sure
that
we
we
can
collect
that
down
after
on
long
term.
A
So
that's
what
I
want
to
say,
so
I
really
encourage
you
to
look
at
the
discourse
it's
under
the
infrastructure,
so
it's
under
contributing
infrastructure,
topic
and
yeah.
That's
all.
I
want
to
say
any
other
topic
that
you
want
to
bring.
D
A
A
So
that's
that
that's
the
thing.
B
A
The
the
the
reason
yeah
the
reason
why
I
was
saying
that
postgresql
database,
you
have
manage
service
and
they
are
really
stable.
So
I
mean
you
deploy
that
and
just
use
them
and
that's
really
easy
to
use
an
example
is
a
rating
application
it
to
support
sql
database
since
say
seven
years.
Eight
years
I
mean
I
have
I
don't
know,
I
don't
remember
when
when
that
service
was
put
in
place,
but
as
long
as
we
don't
have
to
maintain
the
database,
I'm
fine
with
that.
A
Otherwise
we
we
still
have
the
opportunity
to
start
discussion
on
this
course.
As
I
mentioned
under
the
contributing
infrastructure
topic
category
sorry-
and
we
still
have
the
infrastructure
mailing
list
if
we
want
to
discuss-
and
we
are
still
on
rc.
So
if
we
don't
have
additional
topic,
I
propose
to
stop
the
call
here
thanks
everybody
for
your
time
and
goodbye.