►
From YouTube: INFRA Weekly Meeting 2020-08-04
Description
Jenkins Infrastructure Project Meeting - 2020-06-16
Notes - http://bit.ly/2T0oZ9v
A
Hi
hi
everybody
welcome
for
this
new
jenkins
infrastructure
meeting
we
don't
have.
I
mean
we
have
a
few
things
to
the
agenda,
but
I'm
not
sure
if
we
already
covered
them
in
the
previous
meeting,
so
I
just
want
to
review
the
different
point
to
be
sure
that
and
they
are
covered.
I
saw
that.
The
first
point
is
jenkins.
As
a
service,
I
don't
know
who
put
that
nose
there,
but
I
don't
have
any
information
regarding
that
jenkins
into
the
service.
A
Okay,
let's
just
put
this
here
regarding
the
git
app
on
seattle
jenkins
as
see
either
jenkins
yo.
I
saw
that
you
did
a
bunch
of
water.
Do
we
have
anything
missing
there?
I
think
a
lake
did
pretty
much
ever
I
did
everything
or
so
for
the
github
github
app
on
cigars.
B
A
A
Team
yeah,
no,
it's
working,
so
I
was
just
saying
so.
I
installed
the
github
api
check,
but
we
have
to
restart
searching
the
layout.
So
I
guess.
A
Okay,
okay,
but
then
then
yeah,
because
I
already
installed
the
plugin
so
pick
me
when,
when
it's
available-
and
so
I
update
the
version-
then
restart
the
instance
because
right
now,
it's
not
enabled
because
it
has
dependencies
on
other
plug-in
versions
that
needs
in
order
to
take
them
into
account.
We
have
to
restart
the
idle
junk
in
the
layout,
so
yeah,
but
anyway,
I
see
that
there
is
a
lot
of
testing
at
the
moment
on
the
energy
keys.
So
it's
definitely
probably
not
the
best
time
to
restart
it.
B
C
Yeah
felix
ran
them
all
and
you
reported
a
bunch
of
issues
and
it's
picked
up
one
bug
and
core
nipple
request
and
one
bug
in
the
promotion
plug-in
the
rest
of
them
just
been
annoying
css,
selectors
and
and
fixes
that
are
tested
and
broken
for
ages.
Some
plugins
have
been
broken
for.
Like
last
sorry,
some
testing
broken
like
the
last
15
16
versions
from
the
css
framework.
B
And
then
olivier
in
terms
of
the
load
on
sia
jenkins,
that
I
oh
yeah,
it's
got
over
100
in
the
queue
right
now.
So
it's
it's
triggering
our
our
warning
on
and
ath
is
the
big
one.
Can
we
afford
given,
given
the
funding
that
aws
has
provided?
Could
we
afford
to
increase
the
number
of
maximum
high
memory
that
we
could
run
from
three
to
say
a
four
or
five.
A
C
B
B
B
A
A
I
remember
that
I
put
the
lts
release
in
the
weekly
release
so
far.
We
don't
have
anything
new
there.
I
merged
the
pr
this
morning
regarding
adding
information
for
the
gpg
for
debian
and
red
hat.
It's
working
for
that,
but
it's
not
for
debian.
It
sounds
like
there
is.
We
are
trying
to
read.
It
sounds
like
there
is
a
something
wrong
with
the
path
where
we'll
read
the
gp
tpg
key,
I
mean
it
should
be
easily
fixed,
but
yeah.
A
We
just
have
to
look
at
the
scripts
at
the
moment,
but
it
does
not
affect
future
release
so
yeah
we
still
have
green
green
builder.
A
Regarding
the
automated
release,
we
still
have
to
work
that
need
to
happen
in
order
to
close
the
epic.
That's
what
I
was
looking
for.
A
So
one
minor
thing
is
to
align
so
right
now
when
we
do
an
lts
release
or
security
release.
We
freeze
the
codes
on
the
jenkins
ci,
slash,
release
repository,
but
on
the
jnk
in
ci
slash
packaging.
We
are
still
using
the
branch
infra-910,
something
like
that,
and
we
should
merge
that
branch
on
the
master
branch
and
then
start
to
freeze
again
the
branch
when
we
do
another
test
release,
so
we
should
add
to
the
process
to
create
a
branch
each
time
we
need.
We
need
to
create
an
lts
release.
A
So
it's
it's
minor
thing,
but
I
think
we
should
just
fetch.
I
mean
ensure
that
we
can
merge
we
safely.
We
can
safely
merge
the
branch
900
and
then
to
the
master
branch
on
jk
packaging.
So
it's
basically
the
ticket,
infra-2660
and
infrared
1363.
So
I'll
put
the
link
in
the
dock.
B
A
So
there
is
a
variable
on
released
on
jenkins
and
first
release,
where
we
specifically
says:
do
you
check
out
that
git
repository
on
that
branch?
Right
now?
It's
I
mean
just
in
the
parameters
and
we
just
now,
instead
of
using
that
we
have
to
use
a
master
branch,
but
before
doing
that,
we
have
to
be
sure
that
the
master
branch
is
a
line
on
on
and
from
900.
A
B
A
I
will
I
would
just
wait
because
I
don't
have
a
lot
of
time
here
and
I
cannot
promise
on
my
time
for
the
moments
and
the
thing
is.
While
I
do
not
expect
anything
that
I
mean,
I'm
not
expecting
anything
broken
there.
I
just
don't
want
to
take
the
risk
to
you
know
to
have
whatever
happened,
so
I
will
not.
A
I
will
not
close
it
here
for
not
now,
I'm
not
planning
to
work
on
it,
but
I
will
just
update
it
to
be
sure
that
we
are
aware
of
what
we
need
to
do
there
and
the
second
thing
so
infrared
2660
is
about
free,
yeah,
freezing,
updating
the
master
branch
on
jenkins,
yes,
packaging.
A
A
A
And
this
one
is
about
and
the
same
I
would
not
so
I
have
open
prs.
I
will
not
merge
my
peers
because
I
don't
want
to
take
the
risk
to
break
the
current
release
process,
but
the
second
ticket
is
about
promoting
red,
hat's
use
and
debian
packages,
so
the
idea
is
to
put
them
in
a
staging
directory
and
only
deploy
them
on
the
mirror
horse
at
the
end
of
the
process.
So
right
now
we
have
staging
promotion
from
promotion
from
staging
to
their
to
production
for
the
package
in
their
website.
A
We
don't
have
promotion
mechanism
from
your
house,
so
we
publish
the
packages
and
then
we
stage
the
website
and
then
we
promote
the
website,
and
so
this
means
that,
yes,
it
was
a
little
bit
challenging
for
the
red
hat,
because
red
dots
generate
the
websites
on
on
the
machine
on
the
fire
on
the
production
machine
and
we
need
we
need
sorry.
We
need
to
read
the
package
to
the
list
of
packages
from
the
prediction,
so
we
don't
have
this.
I
mean
we.
A
We
have
to
specify
one
directory
where
all
the
packages
are
located
and
so
having
to
fetch
the
list
of
packages
from
two
locations.
The
staging
and
the
prediction.
Environments
I
mean
was
a
little
bit
more
complicated,
and
so
it
applies
a
little
bit
more
cleaning.
It
sounds
so
that's
mainly
because
of
reductions
used
packages
that
I
haven't
been
able
to
match
my
peers,
but
yeah
it
should
be.
It
should
be
ready
now.
A
And
yep,
I
think
it's
tim,
who
puts
a
link
to
the
jenkins,
slash
docker,
so
yeah,
I'm
just
moving
to
the
next
point.
Tim
have
you.
How
are
you
the
person
who
put
jenkins
here,
slash
checker,
link.
C
Next
meeting
intentionally-
but
yes,
I
didn't
want
to
mention
it,
I
don't
remember
adding
it
there,
maybe
it's
from
the
last
one
but
yeah.
Is
there
anything
blocking
the
plugin
installation
manager
tool
getting
added
to
the
docker
just
now,.
A
C
No,
it's
yeah,
it's
preview,
it's
not
a
prototype,
it's
production
ready
and
better
than
the
install
plugins.
Really
I
really
wanted
to
put
it
in
as
preview
for
a
little
bit.
Originally,
I
had
it
in
there
as
the
preferred
way
and
left
install
plugins
is
the
backup
way.
C
A
A
Okay,
perfect
and
so
there's
just
one
last
thing,
because
in
there
are
the
two
in
the
table
at
the
top
of
the
document
we
have.
We
have
one
prioritize.
The
big
jenkins
influence
merge
policy.
I
don't
remember
anything
like
about
that,
but
it
was
probably
me,
but
I
don't
know
if
you
have
any
concern
context
about
that.
I
think
you
can
just
delete
this
button.
A
In
the
prioritized
topics,
so
we
still
have
the
infra
910.
The
second
point
is
changing.
The
first
touches
slash,
charts,
merge
policy,
I
guess
yeah
we
can.
We
can
close
this
one
and
to
to
discuss
topic.
We
had
the
agent
leveling
and
seattle
jenkins.
I
think
it's
done
as
well,
so
I
think
we
can
close
it
mark.
Do
you.
A
Perfect,
so
I
think
we
are
good
for
today.
So
do
you
have
any
topic
that
you
want
to
bring
here.
A
B
Yeah,
that
would
be
great
okay,
so,
okay,
if
I
share
my
screen
or
best,
if
I
don't,
what
do
you
have
a
preference,
olivier
yeah,
you
can
share
your
screen.
That's
that's
great!
Okay,
let's
see
if
I
can
find
that
okay,
so
here's
this,
and
the
idea
is
that
our
jira
instance
is
running
jira.
B
7.13.12.,
hang
on
and
I'll
share
this
screen,
which
will
be
officially
off
support
at
on
november
28th
2020..
So
we
need
to
get
off
that
version
onto
a
newer
version
of
jira,
and
one
of
the
benefits
of
being
part
of
the
continuous
delivery
foundation
is
that
we
get
some
free
services
from
the
linux
foundation.
That
is
the
host
of
of
cdf
and
one
of
the
things
that
they
do.
B
Is
they
support
jira
instances
for
open
source
projects,
so
this
draft
plan
is
trying
to
identify
crucial
objectives
and
proposals
for
what
we
should
do
in
order
to
make
this
transition
by
november
28th.
Now
olivier
is
going
to.
Let
me
lead
this
one,
so
I
would
be
happy
to
give
request
to
others
as
reviewers
for
the
proposed
plan
right
now.
The
crucial
players
are
andrew,
grimberg,
brian
warner
and
steve
era
of
the
linux
foundation.
B
A
To
add,
thanks
mark,
we
just
add
a
little
bit
here.
The
idea
is
we
try
to
to
prepare
that
migration
in
advance,
so
the
best
scenario
linux
foundation
can
upgrade
the
version
for
us
and
they
do
all
the
work
here,
the
worst
scenario:
we
have
to
upgrade
the
jira
version
by
yourself
before
november,
and
that's
why
we
start
working
on
this
now,
so
we
are
still
at
the
x1
in
exploratory
mode.
A
A
So
so
so
it's
it's
kind
of
related,
but
not
I
mean
it's
kind
of
related.
The
the
question
right
now
is:
are
they
okay
to
use
our
system
management
because
we
still
have
this
still
something
that
we
have
to
discuss
in
the
community
in
the
community
about
what
we
do
with
the
jenkins
identity
management?
But
I
have
the
feeling
that
it's
going
to
be
a
little
bit
more
complicated,
not
in
terms
of
complicity
about
the
migration
or
whatever,
but
more
in
terms
of
what
we
do
about
the
data
here
and
yeah.
A
A
I
don't
want
to
work
on
nikki
cloak
right
now,
because
it's
not
it's
not
yet
clear
if
it
makes
sense
or
not,
but
yeah
the
the
discussion
will
probably
happened
while
we
discuss
about
jira,
because
we
have
to
see
how
I
mean
if
it's
possible.
C
B
Well
well
and
tim,
I
would
think
we
will
want
a
similar
plan
that
does
a
identity
management
next
steps
plan
right,
whether
that's
a
transition
to
click,
key
cloak
or
transition
to
linux,
foundation,
identity
management
or
something
else
agreed.
I
was,
I
was
just
focusing
on
jira
for
this
exercise.
A
B
But
yeah
so
tim,
tim
and
alex,
are
you
interested
in
being
reviewers
on
this
document?
If
so,
I'm
happy
to
share
it
with
you.
Yeah
okay
will
do
sure.
A
Careful
careful
and
while
we
are
talking
about
jira,
I'm
just
wondering
if
you
both
alex
and
tim,
you
would
be
interested
to
have
ssh
access
to
the
machines
to
the
puppet
infrastructure,
because
if
you
do,
you
just
have
to
provide
your
ssh
key
and
then
we
can
plan
some
knowledge
transfer
about
how
to
to
fix
issues
on
those
machines
or
how
to
improve
whatever.