►
From YouTube: 2021 07 13 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
Hi
everybody
and
welcome
for
this
new
jenkins
infrastructure
meeting
today
to
the
agenda.
What
we
have.
We
have
a
small
topic
about
reputation
in
seattle.
We
have
a
topic
about
update
center
issues.
We
faced
last
week,
some
updates
on
the
docker
image,
build
that
damien
is
working
on
at
the
moment
and
a
quick
update
on
the
puppet
puppet
code
that
I'm
currently
updating.
A
A
So
we
still,
we
are
still
affected
by
a
few
issues.
So
as
a
reminder,
we
noticed
that
since
the
24th
of
june
jfrog
did
an
upgrade
of
the
service
and-
and
we
were
affected
in
the
way
we
were-
we
are
using
it.
So
we
were
not
able
to
copy
artifact
from
between
repositories
that
affected
us
when
we
did
the
security
updates
two
weeks
ago
now,
so
we
had
to
put
in
place
a
temporary
maven
repository
as
we
could
not
update
the
the
the
official
release
of
an
repository,
the
production
one.
A
So
we
put
in
place
a
virtual
maven
repository
where
we
would
be
able
to
fetch
packages
either
from
the
security
one
and
from
the
prediction
one.
So
we
are
still
affected
by
that
issue.
So
I
opened
a
support
ticket
on
gfrock
yesterday
I
was
in
contact
with
them
today
and
now
I'm
waiting
for
feedback
from
from
them.
So
that's
still
an
ongoing
issue.
So
until
then,
until
we
have
until
we
better
identify
what's
the
problem
here,
we
still
have
to
to
use
that
foldback
maven
repository,
so
that
has
several
consequences.
A
So
every
tools
that
fetch
jenkins.org
from
the
prediction
maven
repository,
does
not
work
at
the
moment,
and
so
we
have
to
override
with
a
temporary
one.
And
so
I
don't
know
if
I
can
quickly
show
you
yeah.
If
you
have
issues
using
the
prediction,
marvin
repository
feel
free
to
ask
and
I'll
give
you
the
temporary
euro.
So
that's
it
any
question.
A
No
sounds
good,
so
I
can
continue
so
last
week
we
had
an
issue
with
the
update
center
so
because
so
we
we
even
cache
artifacts
and
what
happened
from
time
to
time
is
if
we
try
to
download
a
plugin
and
that
plug-in
return
of
4
for
errors.
We
cache
that
that
errors,
and
so
what
what
happened
last
week
is
we
try
to
fetch
metadata
from
plugins
that
were
officially
there,
but
because
we
had
some
cash
containing
the
four
four
answer.
A
Http
answer
and
the
update
center
job
was
failing
and
because
we
are
using
a
temporary
maven
repository,
so
the
the
fallback
that
I
just
explained,
we
were
modifying
the
wrong
of
the
central
configuration.
So
daniel
came
back.
I
was
available
and
beginning
of
the
week
yesterday
in
fact
quickly
identified
issues.
So
that's
what
was
important
for
us
is.
We
forgot
the
marvin
repository
maven
repository
issues
until
we
have
a
fix
for
that.
We
have
to
keep
in
mind
that
we
are
not
using
the
production.
One.
A
The
next
topic
is
about
building
is
building
the
car
images
for
multiple
architectures,
that's
something
that
damien
is
working
on
at
the
moment.
So
maybe
they
mean
you
want
to
share
more
with
us.
B
B
So
there
are
two
topics
here:
the
first
one
is
a
pull
request
that
has
been
just
switched
by
mark
waite
to
ready
for
review.
That's
a
pull
request
that
tim
started
and
I
work
with
him.
B
The
goal
of
that
request
initially
was
to
to
make
the
build
faster
and
what
it
underlined
is
that
we
were
building
and
testing
all
the
linux
images
on
the
same
machine
and
we
have
the
same
issue
in
windows.
That's
why
most
of
our
builds
are
really
really
slow,
because
only
one
docker
engine,
sometimes
it's
on
a
big
machine
on
a
high
memory.
So
it
works
very
well.
Sometimes
it's
understood
on
a
smaller
one,
so
not
not
only
it's
prone
to
unstability,
but
it's
a
big
constraint.
B
B
So
now
you
respawn
one
machine
for
one
linux
platform,
so
you
have
one
agent
that
build
alpine
linux
and
test
alpine
linux.
Another
agent
in
parallel
that
builds
santos
and
test
centers,
etc.
Windows
is
not
part
of
that.
So
why
mentioning
this
here?
It's
because
a
lot
of
the
pull
requests
on
the
official
docker
image
are
suffering
from
instabilities
during
the
build
most
of
the
time.
B
B
B
The
slower
test
is
now
tester-ness
is
now
taking
two
minutes
and
a
half
instead
of
five
to
thirty
minutes.
So
that's
twice
to
five
times
faster,
which
is
really
good.
Windows
is
the
next
step.
B
Second
topic:
I'm
gonna
start
working
on
this
one.
It
will
be
building
the
multi-arc
images
to
be
able
to
provide
build
and
publication
of
iran
ppc
and
s
ibm,
z,
cp
architectures,
so
I'm
still
reading
what
team
did
on
the
previous
days,
so
I'm
still
ending
over
my
goal
is
to
be
able
to
run
safely.
This
workload
more
is
coming
on
that
we
should
we
will
we
are.
We
have
an
issue
on
the
github
repository
with
the
details.
A
Just
just
one
question:
so:
do
you
mean
that
the
add
multi-arch
build,
which
is
so
that
pr
is
in
draft
mode
at
the
moment?
Is
it
the
one
that
is
almost
ready.
B
We
can
use
kemu
for
building
at
least
that
one
is
quite
easy
and
should
work.
That
means
you
only
require
a
mission
with
intel,
but
we
have
irm
machines
and
we
have
the
issue
of
machines
between
ci
and
trusted.
We
in
that
case
we
have
different
security
issues
related
to
the
sharing
these
machines,
because
these
are
let's
say
we
don't
have
a
lot
we
on
one
or
two
macs,
so
the
pull
request,
multi-publish
multi-arc
from
team
in
draft,
is
about
that
system
being
able
to
build
and
publish.
A
Yes,
thanks
interested
yeah
thanks
for
that
last
topic,
which
is
on
my
side,
so
I'm
currently
doing
some
puppet
updates.
So
I
started
one
pr
containing
many
different
small
updates.
It's
kind
of
I
mean
difficult
because
we
haven't
updated
the
puppet
code
for
a
while,
and
so
it's
like
each
time
you
upgrade
something
it
has
consequences
on
a
third
module.
A
A
So
the
the
initial
reason
why
I
started
working
on
that
was
to
really
play
archive
the
jenkins
that
I
go,
but
it's
like.
I
need
to
update
that
it's
encrypt
module
and
because
I
have
created
its
encrypt
module,
I
I
need
to
upgrade
other
modules
and
so
on.
So
that's
that's
what
I'm
currently
working
on.
I
I
hope
to
have
something
finished
for
the
coming
days,
but
yeah.
The
final
goal
is
still
to
move
and
to
close
the
rackspace
account.
A
B
Had
just
one
I
want
what
we
about
aditya,
we
need
to
think
aditya.
You
want
hi
to
remove
in
production
the
nexus
on
the
release
name,
space
right.
Yes,
so
I'll
switch
the
discussion
on
ioc
or
in
private.
We
do
to
think
when
we
want
to
plan
this,
and
we
will,
I
will
publish
a
mansion
be
in
erc
before
when
we
would
have
selected
the
time
slot.
Okay,
okay,.
C
Oh,
I
actually
wanted
to
ask
one
question,
so
I
I'm
facing
this
error,
so
I
just
wanted
to
know
whether
this
is
due
to
the
artifact
outstanding,
like
the
g
flat
j
profiting.
Is
it
because
of
that.
C
C
A
Authorization
failed
now
that
means
that
you
don't
have
the
right,
username
and
password
to
push
okay,
so.
A
This
one
is
four
four,
three
four
billion,
so
I
can
help
you
so
yeah.
It
just
means
that
you
don't
don't
have
so.
The
github
action
doesn't
have
the
right,
username
and
password
to
push
the
maven
repository.
We
can
debug
that
together,
okay.
C
A
Yes,
I
just
have,
because
I'm
not
sure
that
I
have
permission
on
that
one
to
do
yes,
it
sounds
like
I
do
have
some
permission
so
yep.
I
should
be
able
to
help
maven
token.
Oh,
there
is
a
maven
token
updated
five
minutes
ago
of
an
username,
so
yeah,
it's
definitely
an
issue
with
the
credentials.
So
another
option,
maybe
is
so,
is
it
your
credential.
A
So
when
we
want
to
add
when
we
need
to
grant
access
to
someone
to
push
to
maven
so
repository,
that's
the
name
repository
permission
updater.
So
we
just
have
to
to
be
sure
that
the
username
who
pushed
the
artifact
has
the
right
permission.
So
we
just
have
to
put
to
list
him
in
the
right.
So.
A
Conventional
commits
so
that
was
updated
two
months
ago
and
who
can
push
here?
Okay,
so
okay,
it
sounds
like
I
can
push
to
the
gear
to
the
to
the
maven.
Okay.
We
just
have
to
double
check
who
I
mean
which
credential
was
used
here,
but
you
can
we
can.
We
can
debug
that
together.
A
I
have
one
last
topic
that
I
would
like
to
bring.
Is
I
won't
be
available
next
week,
so
I
would
like
to
just
consult
next
week
infrastructure
meeting.