►
From YouTube: INFRA Weekly Meeting 2020 03 24
Description
Jenkins Infrastructure Project Meeting - 2020-03-24
Notes - http://bit.ly/2T0oZ9v
A
I
tried
to
do
a
better
job
this
time,
different,
so
hi.
Everybody
welcome
for
this
new
change
in
cell
for
a
meeting.
The
purpose
of
this
meeting
I
mean
the
number
of
the
P
that
we
want
to
discuss
is
pretty
low.
So
basically,
the
main
the
main
thing
that
I've
been
working
on
and
with
other
people
on
the
infra
said,
was
to
me
grades,
Jenkins
agents
that
are
running
on
Azure
to
Amazon,
and
we
are
facing
few
limits.
Few
limitation,
few
I
mean
different
behaviors
and
so
I
would
just
try
to
mention
all
of
them.
A
A
So
basically
the
window
machine
seems
to
be
working
kind
of
well,
which
is
definitely
not
the
case
for
the
Windows
machine
for
the
just
to
come
back
to
the
urban
tools.
I
know,
how's
that
we
are
getting
right
now.
A
data
that
is
not
really
clear
is
that,
after,
while
the
connection
timeouts
and
the
nodes
is
disconnected
empirical
to
consider
as
disconnected
even
if
the
node
is
working
well,
no
displace
issues.
A
The
connection
is
fine,
no
yeah
everything
seems
to
be
working
fine
and
if
we
go
back
to
trinkets
and
just
click
who
learns
the
agent
in
it's
working
again
for
a
few
upwards
and
stick
and
disconnected
so
that's
one
of
the
thing
that
you
are
investigating.
There
is
a
tree
right.
Shoes
related
to
this,
so
I
will
just
add
it
to
the
to
the
nodes.
So,
if
you're
interested
to
follow
what's
up
in
there,
Olivier,
yes,.
B
A
I
was
I
was
getting
there,
but
we
kill
okay,
okay,
yes,
we
can
get
there
No
so
long
as
we
get
our
that's
great,
oh
yeah,
yeah,
but
you're
right.
We
can
just
bring
the
context
of
what's
happening
on
Seattle
Jenkins
that
I
own,
so
I'm,
just
everything
is
kind
of
related
to
the
work
at
working
with
Amazon.
So
because
we
are
we
provision
instances
for
Amazon.
We
also
reduce
the
number
of
machine
that
provision
on
a
sure.
A
A
So
that's
that's
one
of
the
issue.
The
second
issue
is
something
that
we
investigate
with
mark
this
afternoon.
I
mean
this
morning
for
him,
but
basically
what
happened
is
for
some
reason
now
when
we
try
to
deploy
a
new
machine
on
the
other
account
it
also
provision
of
BJP.
It
also
create
an
attached
and
public
IP
and
the
limit
of
those
public
eye
pieces
very
low.
A
It's
okay,
please
across
the
region,
including
cri-kee
that
I
yesterday
I
and
all
the
other
machine,
and
so
for
some
reason
we
did
not
have
enough
people
cabbies,
so
we
were
not
able
to
provision
new
Windows
machine
boot
machine,
and
so
it
was
kind
of
also
related
to
the
to
the
outage
that
we
had
over
the
weekends.
So,
basically
what
we
did
to
fix
it.
A
We
first
asked
her
to
increase
their
needs,
even
if
I
do
not
understand
why
we
were
affected
today
and
we
were
not
affected
in
the
past,
because
we've
been
using
Azure
forum
for
years
now
and
whenever
we
never
had
these
issues
in
the
past.
So
I
don't
know
what
changed.
So,
maybe
it's
related
to
the
fact
we
change
to
a
sure,
icon
type,
but
yeah
right
now,
I'm,
not
sure.
A
So,
basically,
what
we
did
with
the
two
things
we
ask
Allah
to
increase
the
limits
of
the
VIPs
that
we
could
use
and
at
the
same
time
we
updated
the
configuration
to
not
use
the
APIs
but
just
use
pray
IPS.
But
for
that
we
had
to
provision
agents
in
a
specific
spiritual
network
with
specific
security
groups
and
so
on.
So
right
now,
Windows
agents
are
working,
so
at
least
is
working
for
now,
but
the
final
goal
is
still
to
use
Amazon
infrastructure
instead
of
azure.
So
what
right?
Now
we
just
have
a
fallback
in
case.
A
Joke
when,
when
configuration
change
at
a
time
and
so
now
to
switch
back
to
Amazon,
we
have
we
have
issues
with
into
Amazon
and
Windows
machines.
So,
as
I
was
saying
for
that
for
the
Ubuntu
machines
Mir
automated
so
they're
my
opportunity,
a
Spiker,
though
Spectre
image
producing
my
are
pitched
3.
So
we
can
provision
machine
we
can
use.
Those
machine
is
just
a
tough
afterward
to
stick
and
it
is
Canadian,
for
some
reason
does
not
reconnect
back
to
the
master,
and
so
either
we
delete
the
machine.
A
Who
is
all
thing
that
we
need
that
Java
and
Sun
there
what's
happening
is
for
some
reason
take
in
start
to
used
a
password
to
authenticate
on
the
machine
and
that
authentication
does
not
work,
and
so
we
are
still
investigating
with
that
X
and
to
see
what's
the
root
cause
there,
but
normally
we
create
a
security
group.
We
so
mu
is
a
right
port
open.
B
And
it
looks
like
I
just
checked
and
it
looks
like
there's
a
minor
configuration
issue
on
the
windows
images.
The
tests
are
passing
now
that
we're
failing
over
the
weekend,
so
I'm
delighted
at
that.
That's
really
great,
it
looks
like
there's
a
minor
configuration
issue
that
get
LFS
is
not
installed,
but
command
line.
Get
is
I'll
work
with
Alec
Cyril
on
that
one.
These
are
the
as
your
images,
so
I
probably
will
also
adapt
the
tests
that
depend
on
get
out
LFS
to
not
depend
on
Goodell
affairs.
So.
A
If
you're,
if
you
are
spending
some
time
with
that,
it
would
be
nice,
maybe
to
open
a
Giro
a
ticket,
so
we
can
track
this
work.
The
second
thing
is,
it
should
be
pretty
straightforward
to
fix.
If
it's
for
the
azure
images
there
are
some.
There
is
a
neat
script
that
you
can
update
here.
So
it's
probably
just
install
git
LFS.
There
I
just
put
the
link
of
the
file
in
the
chat.
B
A
A
Windows,
it's
probably
the
script
that
need
to
be
updates.
There
is
just
one
thing
that
I
forgot
to
mention.
Last
week
we
discussed
about
having
a
harm,
65
architecture
on
the
Amazon,
and
so
I
also
created
an
invite
for
its.
So
if
we
use
a
nibble
harm
64,
we
can
start
testing
whatever
we
need
to
test
on
that
specific
architecture.
A
I
still
have
to
write
a
blog
post,
or
at
least
some
in
the
middle,
with
no
information
with
the
different
issues
and
how
we
solve
them.
It's
hard
to
stay
focused
when
the
currents
up
period
with
the
contact,
infinity,
I,
wouldn't
mention
something
else:
horn,
64
now
any
Aeneid
up,
question
and
unshielded
into
the
Rio,
so
yeah
there's
something
that
I
want
to
say.
The
reason
why
were
first
was
producing
an
agent
you're,
not
planning
to
move.
The
master
is
because
we
don't
have
any
repository
with
some
problem
to
configure
them
as
an
account.
A
So
this
means
that
all
modification
right
now
happens
manually.
So
this
is
me
doing
that
thing
like
MSM
accounts
and
so
I
did.
I
would
like
to
take
some
time
to
boost
throughout
a
project
similar
to
taking
saber
slash
measure
where
we
can
automate
the
configuration
of
the
Amazon
accounts,
and
so
right
now
we
don't
have.
A
lot
of
configuration
is
mainly
I
created
the
credential
for
provisioning
Institue
instances.
A
A
The
last,
the
last
part
that
I
wanted
to
mention
is
that
I'm
planning
to
take
some
weeks
off
during
the
next
summer.
So
if
you
have
any
work
pending
work
depending
on
me,
that's
probably
the
right
time
to
plan
it
to
see
how
we
can
do
some
knowledge
transfer
or
whatever
you
know,
I
shouldn't
have
even
if
I'll
be
available,
I'm,
not
planning
to
stay
out
of
my
computer
during
the
next
summer.
So
it.
A
A
If
you
want
to
help
with
a
specific
item
in
let's
say
that
you
need
specific
credentials
or
whatever
we'll
have
to
because
I
mean
we
have
to
decide
if
we
trust
you
enough
food
to
give
you
the
right
permission
or
if
there
is
enough
people
working
on
this
I
mean
it's
difficult
to
say,
but
while
we
try
to
be
as
transparent
as
possible,
wickets
I
cannot
give
you
access
to
the
machine
to
the
first
person
who
asked
ya.
So
that's
perfectly
fine.
So
the
idea
is
really
if
you
already
work
on
a
specific
area
whatever.
A
Maybe
that's
where
I
all
right
time
to
move
to
the
next
step.
Yeah.
C
For
me,
the
question
Bay:
is
there
a
way
we
have
known
contributors
at
the
moment?
So,
for
example,
for
me
it's
less
of
a
problem,
whether
I'm
interested
or
not
in
a
particular
area.
It's
a
rather
problem
what
to
do
if
something
goes
from
there
and
for
me,
raishin
code
to
you
would
be
a
last
resort
and
before
that,
if
we
have
a
list
of
these
graphs
or
whatever,
probably
we
could
spend
some
time
towards
the
summer
to
reduce
the
number
of
them.
So
we
didn't
disturb
you.
Okay,.
A
B
So
I
was
having
a
conversation
with
somebody
not
long
ago
about
the
data
dog
monitoring
that
we're
doing
and
just
saw
an
email
yesterday
that
highlighted
that
it
had
the
data
dog
had
in
fact
detected
the
outage
that
we
had
over
the
weekend.
I
just
didn't,
look
at
it
and
didn't
see
it.
So
I
was
delighted.
It
has
a
monitor
already
for
some
of
the
things
we
were
having
failures
on
over
the
weekend.
Thus
reminding
me
I've
got
lots
still
to
learn
about
infra,
so.
A
So
so,
to
be
clear,
the
yours
that
was
reported
by
that
today
is
the
size
of
the
you,
the
big
queue,
the
job
queue.
This
was
a
check
that
I
put
in
place
like
something
in
September
or
something
that
that
is
just
a
way
to
know.
If
something
is
wrong,
so
I
think
like.
If
we
have
more
than
100
item
in
the
job,
it
means
that
something
is
wrong
somewhere.
The
junk.
A
So,
for
example,
we
had
an
issues
over
the
weekend
about
Kira,
so
basically
JIRA
run
out
of
disk
space,
and
so
we
just
had
to
assess
it
from
the
machine,
but
because
that
machine
does
not
have
a
lot
of
disk
space
there,
always
sometimes
your
friends.
So,
for
example,
last
Friday
I
clean
up
some
old
logs
that
were
not
useful.
This
Monday
I
just
deleted
all
the
car
images
and
stuff
like
that.
So
it's
more
like
there
are
the
objects.
C
I'm
not
talking
about
documenting
how
to
fix
that
I
rather
documenting,
where
the
gaps
in
terms
of
ownership
on
axis,
because
the
commutation
or
unbox
is
definitely
important,
but
the
first
step
would
be
to
understand
way
these
people
and
after
that
we
can
probably
see
what
we
could
not.
For
example,
me
and
Mark
could
dedicate
some
time
to
study
this
area.
Maybe
to
some
knowledge,
transfers
physically
cannot
create
run
books,
but
yeah
first
item
first
would
be
to
understand
what
are
these
centers
okay.
B
A
Sorry
personally,
I
really
like
I,
really
like
the
idea
that
the
way
you
said
ownership
yep,
the
idea
is
really
to
identify
what
other
thing
that
I'm,
the
only
one.
So
a
small
example
is
as
an
icon
that
you
are
running
at
the
moment
for
for
for
some
reason
we
can
only
have
20
employees.
Do
you
think
that
you
have
to
fix
something?
A
This
is
my
that
need
to
be
transferred
to
the
community,
but
for
now
the
gap
is,
if
you
not
have
been
employee,
don't
have
access
to
the
log,
so
this
is
definitely
a
place
where,
for
example,
March
and
unlike
good
health
work,
for
example,
silicon
that
I
own
does
not
mean
this
daily.
Anything
CLE
junkies
at
I/o,
for
example,
and
we
could
have
more
people.
Other
account
is
the
same.
We
could
have
more
people
so
typically
for
the
case
of
the
doctor.
A
A
C
In
my
case,
I
was
specifically
about
drinking
CI,
github
organization
you
and
about
our
use
cases
cough
changed:
okay
generation,
because
the
current
situation,
and
that,
if
you
open
our
Jenkins
Jenkins
means
you
can
see
that
it
half
actions
account
which
cut
at
the
release
and
I
would
like
to
fix
back
I
already
prototype
a
fix
which
basically
replaces
big
it
hop
up
by
another
off
up.
I
can
do
that.
C
C
A
C
B
A
A
So
I
will
just
implement
that,
and
so
there
is
a
there
is
one.
There
is
another
point
that
you
eat,
that
you
asked
there
isn't
so
yeah
I'm
the
odd
started.
Fine,
the
only
they
are
see,
also
asked
if
it
was
possible
to
enable
ETF
issues
for
Jaden
Sarah,
it's
33,
so
the
pipette
repository
and
yeah,
not
just
something
I
mean
I.
A
Don't
have
strong
opinions
about
you
think
it's
a
bit
issues
each
other
I,
don't
want
to
have
to
I
mean
I,
just
not
like
ready
to
have
beautiful
tools
to
switch,
because
each
I
mean
it
makes
it
more
difficult
to
generate
reports.
It
makes
it
one
if
you
got
to
find
the
right
information
and
it's
not
young
Phineas
I
have
there
is
that
discussion
about
using
directed
getting
rid
of
clear
or
whatever
or
fixing
grr?
But
this
is
something
that
we
still
have
to
work
on
right.
C
So
if
we
don't
want
us
to
traitors,
so
the
main
problem
is
issue
migration,
it's
possible
to
mediate
issues
to
get
hurt,
but
sometimes
it's
just
normal
head
and
practically
would
have
seen
in
other
repositories.
Once
you
enable
github
finishes,
the
traffic
to
drink
is
jittery
basically
vanishes,
so
it
would
be
an
archive
for
historical
issues,
but
I
wouldn't
expect
too
many
activities
there
with
you.
So
I'm
not
really
concerned
about
duplication,
especially
if
you
say
that
okay,
now
it
hop,
which
is
a
source
of
truth
for
new
issues.
No.
A
Yeah
but
my
point,
but
duplication
was
more.
For
example:
okay,
you
have,
you
have
cleared
up
issues
for
the
pipette
repository,
but
for
the
VPN
for
the
docker
image
and
stuff
like
this
and
on
the
in
front
we
have
a
lot
of
free
mysteries.
So
my
point
was
more
either
we
enable
for,
although
in
from
work
or
we
don't
because
I
don't
want
to
have
when
I
start
working
on
when
I
start
with
Eddie
said,
I
want
to
have
to
open
to.
A
C
B
But
I,
like
the
the
statement
that
you
said,
do
not
care,
because
that
means
we
could
switch
on
JIRA
issues
for
all
of
Jenkins
infra,
as
suggested
by
Olivia,
and
not
not
violate
the
constraint
you
gable
like
and
I.
I
am
all
for.
Turning
on
github
issues,
the
experience
with
Jenkins
that
I
owe
for
github
issues
has
been
positive.
I
think
it's
been
very
good
and
I
think
we
will
benefit
by
turning
on
by
enabling
github
issues
yeah.
A
But
yeah
my
I,
don't
I,
don't
think
we
need
AB,
no
I
mean
I,
don't
require,
but
meeting
all
the
issues
from
JIRA
to
to
deter,
because
if
it's
really
an
issues
that
that
come
backs,
then
we
can
just
reopen
the
issues
and
just
put
a
link
to
the
to
the
one
from
zero
and
that's
final
and
anyway
at
least
we
have
a
lot.
We
have
a
lot
of
old
issues
that
are
not
relevant
anymore
because
in
for
evolve
and
the
project
evolved
and
sound
so
just
in
different
ways
to
to
start
from
zero.
A
A
B
A
That
I
don't
want
to
force
a
move
in
either
ways
because,
for
example,
let's
say
that
I
know
that
Daniel
rely
a
lot
on
JIRA
and
because
it
created
is
it
for
the
same
reason
that
me
create
a
dashboard,
and
so,
if
we
decide
to
switch
everything
to
get
officials,
we
just
to
implement
some
work,
a
treat
it's
for
the
projects.
So,
for
example,
in
the
case
of
Keira,
yes,
I
have
dashboard
to
say
who's
working
on
what
what
are
the
most
critical
components
that
we
that
we
have
inside
that.
A
So
it's
a
way
for
me
to
say:
okay,
I
spend
a
lot
of
time
on
Sierra
Jenkins
OTO,
instead
of
whatever
things,
and
so
if
they
decide
to
switch
everything
to
get
ambitious
and
yeah.
I
have
to
also
change
this,
which
is
not
too
big
deal.
But
yeah
minutes
awesome
work
changing
my
process
so
so
yeah.
For
me,
it's
it
on
open,
but
I
mean
I
would
like
to
have
that
discussion
because
we
need
we
need.
We
have
to
find
a
solution
before
September,
October
or
November
I.
A
Don't
I
don't
remember,
but
there
is
a
deadline
for
Kiera,
because
the
current
state
is
Kiera
need
to
be
upgraded.
We
need
to
work
on
the
database
and
so
yeah
just
reminder.
The
current
states
JIRA
is
using
a
duplicate,
it's
my
SQL
version,
and
so
the
new
word.
The
new
GUI
version
do
not
support
the
database
a
trap,
so
we
have
to
upgrade
the
database.
We
have
to
get
the
creation
on
the
database,
so
there
is
some
work
with
the
theorem.
A
C
A
C
C
A
A
C
A
Wishes
because,
typically,
typically
enabling
github
issues
just
for
this,
that's
what
I
mean
by
some
issues
will
be
reported
in
India
and
others,
nuts,
and
that's
why
I'm
not
really
in
favor
of
two
of
enabling
it
but
yeah?
If,
if,
if
other
people
think
that
I'm
wrong
I
mean
I'm
clarifying
to
it
to
enable
it
just
that
this
is
my
concern
this.
This
project
is
not
only
used
for
planning
up
for
wiki,
redirect
rules
yeah,
that's
right!
So.
C
A
B
Yeah
yeah
yeah
I.
Don't
think
that
I
don't
think
the
concern
actually
is
about
account
access.
It's
rather
that
at
least
for
me.
Github
issues
are
attractive
because
they're
much
closer
to
and
very
precise
to
the
component
that
I'm
I'm
doing
work
on,
but
that
that,
admittedly,
does
sacrifice
many
of
the
benefits
we
get
from
JIRA.
So
I,
don't
think
only
do
proposing
a
global
switch,
rather
one
repository
at
a
time,
and
only
when
that
repository
makes
sense
and
its
contributors
agree
that
it
makes
sense
exactly.
B
A
B
The
specific,
when
you
were
I
wonder,
do
we
need
a
process
by
which
we
say
who
are
the
contributors
to
this
repository
and
how
do
we
get
them
to
unify
that
we're?
Okay?
Switching
this
one
I
I
took
the
pre-emptive
choice:
to
switch
Jenkins
dot
IO
to
use
github
issues,
I
enabled
it
because
I
happen
to
be
an
administrator
and
I
I
didn't
consult
anybody.
I
just
did
it.
The
danger,
of
course,
is
that
now
we
could
get
bug
reports
in
both
places.
I
accepted
that
danger
is
very
much
worth
it.
C
B
Which
I'm,
actually
not
I,
don't
I
will
I
will
happily
work
to
close
out
the
issues
on
JIRA
that
are
there
and
accept
new
issues
as
the
transition
I,
don't
feel
any
need
to
have
a
single
repository
for
that
particular
project.
Now
there
are
others
I'm
unwilling
to
enable
github
issues
on
the
get
plugin,
because
there
are
500
issues
in
JIRA
that
I
can
I
will
not
move.
So
so
it's
it's
just
different
it.
For
me,
it's
per
repository.
It
was
where
the
decision.