►
From YouTube: 2022 08 16 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
A
A
B
A
Me:
okay:
let's
go
the
new
weekly
size
so
that
the
war
has
been
published
successfully.
I,
don't
know
for
the
rest
of
the
checklists.
To
be
quite
honest,
so
we
might
have
to
wait
a
bit
before
updating
the
docker
image
that
should
be
updated
automatically
in
the
next
few
hours.
I
think
it's
the.
A
A
A
And
an
a
next
security
really
is
not
far
as
We
Know.
Next
major
event,
devops
world
end
of
September
I'm
just
kidding,
we
will
array,
Bruno
and
I
will
be
there,
so
anyone
interested
in
infrastructure
can
can
come
there,
let's
get
started.
What
did
we
do
since
last
week?
Not
so
much
because
Elvis
just
went
back
from
PTO
today,
I
was
alone.
A
I
finished
the
3D
API
plugin
fixes,
which
involved
having
to
specify
the
Java
binary
path
used
to
spawn
the
Jenkins
agent
process
on
all
of
our
templates.
That
created
a
lot
of
chaos.
I'm.
Sorry,
for
that,
that's
the
value
of
having
a
team,
because
when
there
is
a
team
they
restrain
myself.
The
restaurant
me
from
breaking
things.
The
idea
is
that
for
gdka,
8
and
gdka
17
agents
we
had
to
to
add
the
gdka
11..
A
The
goal
is
we
want
to
run
Jenkins
engine
process
with
the
same
GDK
as
the
controller,
while
the
default
GDK
is
the
one
expected
by
developer
as
a
developer.
When
you
use
hdka
8
label,
you
expect
Java
Dash
versions
to
Sage
Java
1.8.something,
while
the
Jenkins
agent
process
should
run
with
gdka
11
same
as
our
controller,
as
for
today
one
exception:
the
ec2
windows
machines.
A
They
are
using
GDK
11
because
it's
the
default.
So
it's
not
blocking
that
issue
specifically.
However,
when
it
will
come
with
the
gdka
17,
we
will
absolutely
need
to
change
the
default
GDK
for
agent
and
right
now
there
is
a
feature
request
that
I've
opened
on
the
ec2
plugin.
A
team
commented
that
it
should
be
quite
easy
to
add
and
should
be
easier
than
hacking
around
I
agree
with
him,
so
next
step
contributing
to
a
plugin.
Anyone
interested
is
welcome
to
help
us,
of
course,.
B
Yeah
I'm
probably
try
it
I
looked
at
the
modification
and
take
a
quick
look
at
the
CQ
again
I
think
I've
looked
at
the
path
being
changed
for
the
night
clinics
and
Windows
Launcher.
A
That's
cool
in
those
template.
Thanks
survey,
not
blocking
the
issue.
Another
consequence:
I've
opened
a
bug
and
I've
contributed
to
the
kubernetes
plugin.
It's
in
review,
States
I,
don't
know
since
when,
but
the
Pod
agents
on
Jenkins
were
missing.
When
connected
the
item
system
information,
you
were
only
able
to
check
the
Pod
logs
and
events,
but
not
the
system,
information
which
is
the
gvm
retrieving
information
about
the
operating
system,
the
gvm
parameters,
environment
and
elements.
A
All
the
other
agents
have
this,
and
it's
quite
useful
on
the
UI
for
for
admins,
specifically
when
you
want
to
check
which
GD
card
and
which
version
and
what
what
pass
is
used
to
spawn
the
agent
process,
which
was
the
core
of
this
one.
That
is
plugin
contribution,
and
so,
let's
see
if
we
can
improve
that
situation
with
the
upcoming
gdka
17.
A
A
Is
there
any
other
question
things
good
job?
Next,
one
repeat
the
great
campaign,
so
our
puppet
infrastructure
is
up
to
date
to
the
latest
six
dot.
Something
Mainline
Origins
are
using
open
source
puppets,
but
the
I
rediscovered,
because
I
should
have
unknown.
But
I
did
not
thanks
Olivier
for
reminders,
but
the
Puppet
Master
is
using
Enterprise
puppet
Edition
with
the
free
license
for
10
nodes.
A
That
means,
if
we
want
to
add
more
pet,
manage
node.
We
are
close
to
the
limits.
The
Proposal
is
to
switch
to
open
source
Puppet
Master
for
the
upgrade
to
the
7.
something
version,
and
we
keep
the
pipette
Enterprises
for
today,
because
it's
not
blocking
us
right
now
at
First
Sight.
The
only
added
value
of
the
Enterprise
in
our
use
case
is
the
installer
that
should
be
replaced
by
a
few
command
line
for
the
upgrade,
but
outside
this
I'm
not
sure
there
are
other
operational
changes
and
we
don't
need
support.
A
So,
let's
see
next
time,
but
at
least
we
are
up
to
date,
let
me,
but
it
has
been
updated.
A
A
What
else
the
both
of
these
issues
created
a
lot
of
chaos
and
cig
and
Kim's
IO
I
apologize
for
that,
but
now
that
should
be
clear
and
we
have
a
road
to
the
next
puppet
configuration.
Are
you
between
help.
A
So
Maven
11
goes
by
tree
lead
fixed
sorry
for
that.
That
was
a
side
effect
of
the
walking
around
the
treated
part
same
for
the
maven
windows
and
other
flights.
I
was
working
on
changes,
yeah,
I,
messed
up
things.
A
Thanks
the
he
checked
during
24
hours,
the
state
of
the
updates
on
third
generation
and
fix
the
odd
link,
so
that
was
not
an
easy
task,
so
yeah
that
was
a
Sim
link
or
link
issue,
at
least
so
that's
okay,
user
I've
confirmed
that
it
was
fixed
within
the
hours.
So
nothing
else
to
do
nothing
expected
from
the
infra
team.
There.
We
detected
the
issue
at
the
same
time
as
the
user,
and
then
we
asked
for
help.
A
Granting
create
permission
to
Jenkins
start
app
done
by
teams
thanks
team
and
finally,
as
we
said,
we
had
the
LTS
release.
So
the
update
to
that
version
for
the
four
controllers
trusted
CI
search
and
release
have
been
done
in
the
few
hours
after
the
release.
So
thanks
Alex
for
leading
that
release
and
we
are
up
to
date
any
question
nope.
B
B
Yes,
I'm
currently
retrieving
the
drinking
CIA
foreign.
B
A
B
I'm
looking
to
know
how
to
create
such
organization.
A
Cool
so
I
understand
that
we
have
to
wait
from
either
term
for
one
and
npm
people
for
the
other.
Yes,
hence
the
move
it
to
next
Milestone.
Then
thanks
a
lot.
Harvey
I
didn't
have
time
to
pass
on
this
one.
Okay,
next
one
introduce
an
artifact
caching
proxy
for
CI
General.
Why?
Because
we
absolutely
need
to
decrease
the
bandwidth
usage
to
repogen
ci.org,
that's
a
long-running
subjects
in
siors
and
right
now
we
are
crossing
some
limits.
A
The
idea
is
to
start
with
the
docker
image
and
install
one
to
three
instances
and
then
see
how
we
can
configure
CI,
jinkinsio
and
eventually
other
others
to
use
this
caching
proxy.
The
idea
is
it's
an
nginx
server
that
receives
requests
for
from
mvn
downloads
and
if
it
has
the
file,
it
serve
it
from
its
local
file
system.
Otherwise,
it's
request.
Repo
Jenkins,
Ai
and
cache
locally.
The
Cache
can
be
cleaned
either
by
deleting
files
restarting
the
instance
or
reaching
the
the
maximum
timestamp.
A
Why,
for
instance,
is
because
one
in
Azure,
because
we
have
virtual
machines
and
agent
running
in
Azure,
the
goal
is
to
have
the
same
region
to
avoid
bandwidth,
cross-region
costs.
So
we
need
one
in
AWS
for
container
Regent
on
eks
and
same
on
digital
ocean.
But
let's
get
started
with
one
at
first
and
see
with
behave.
A
So
everybody
I
asked
you
alone
this
morning.
Do
you
confirm
you're
interested
on
working
on
that?
Yes,
okay,
move
it
to
next
duration,
so
we
have
to
work
just
one
time,
both
of
us
to
start
a
local
instance.
I
need
to
share
knowledge
with
you.
So
once
you're
able
to
run
a
maven
build
with
local
caching
on
a
local
Docker
image,
then
you
should
be
able
to
proceed
to
the
install
and
eventually
use
the
old
code
of
that,
because
they
were
a
service
that
we
removed
two
years
ago.
A
So
the
way
we
distribute
the
settings
XML
file,
depending
on
which
Cloud
a
Mark,
told
us
that
the
first
settings
XML
could
be
managed
by
a
Jenkins,
plugin
name,
config
file
provider.
I.
Think
that's
a
plugin
that
allows
to
pass
reusable
configuration
file
for
the
tools.
So
Maven
is
a
known
tools
by
Jenkins.
So
the
goal
is
for
each
agent
or
each
build.
It
adds
the
settings
XML
with
whatever
credential
in
it.
A
That
plugin
should
be
able
to
select
different
settings
XML
based
on
the
label
of
the
agents.
So
potentially
we
could
use
labels
with
the
correct
region
or
Cloud
to
specify
the
correct
settings.
Example,
we
might
have
the
iterations
let's
see,
but
let's
start
with
one
instance
looks
good.
B
A
My
dog
disagree,
but
it
doesn't
have
a
power
in
the
in
the
mix.
So
let's
get
started
with
this
one
I've
put
the
Finish
cleanup
of
mirror
brain.
It's
blocking
the
migration
of
update
Jenkins
IO
to
Oracle
it
poop
at
work.
I
got
some
templates
clean
up
on
the
packaging
machine.
A
A
Okay
next
item
one
containerized,
Java,
17,
Windows
agents,
so
Airway
the
idea
was
to
switch
all
the
agent
images
to
backer.
You
did
that
successfully,
at
least
on
the
billboard,
for
the
Linux
container.
So
in
order
to
finish
that
issue,
we
need
first
to
start
using
Linux
container
built
from
Packer
on
sea
agencio
or
at
least
on
test
environment
before
deploying
on.
Secondly,
start
building
windows
container.
A
Does
it
look
good
for
for
you,
should
we
speed
the
burden
there
or
do
you
want
to
proceed?
It's.
B
A
good
I
wouldn't
mind
doing
some
pairing
with
you.
If
you
have
some
time,
yep.
A
So
I'm,
adding
both
of
us
and
moving
to
next
iteration,
we
could
go
faster
by
adding
a
custom
made
windows
image,
but
the
build
time
are
absolutely
terrible.
So
if
we
have
to
spend
some
time
better
to
spend
it
on,
one
definition
rule
them
all.
A
No
question
sure:
no
okay,
next
one
opened
by
team,
we
have
some
part
of
Jenkins
Sayo
that
are
built
on
CI
Jenkins.
Are
you
and
deployed
from
CIT
and
kinsayu?
That
should
not
so
the
idea
is
to
work
on
moving
the
generation
to
either
trusted
or
better
in
fresier.
A
A
Publish
acceptance,
Docker
image
and
release,
so
there
is
to
have
infrasti
being
able
to
build
the
docker
image
for
the
acceptance
test
on
S
on
the
organization.
Jenkins,
everything
is
set
up,
a
team
described
the
need
that
one
should
be
quick
at
First
Step.
So
unless
there
is
something
unforcing
I
propose,
we
keep
it
on
next
Milestone
I
need
to
add
a
job
job
DSL
configuration
that's
a
few
line
three
or
four,
and
then
that
should
be
okay.
A
A
So
updates
removed
because
blocked
by
finish,
cleanup
replace
so
the
cpuc
machine
I
will
remove
it
from
Milestone
mark
share
with
me
shared
with
me,
the
SSH
key
to
that
machine,
so
SSH
key
shared
with
me.
A
There
is
no
action
there,
except
I
want
to
try
an
experimental,
ruby,
gem
installation
of
pet
agent,
because
there
is
no
package
for
that
CPU
architecture.
A
Okay
alert
fatigue,
data,
dog
and
Page
your
duty,
so
thanks,
Stefan
and
RV.
You
did
very
well
on
this
one
by
disabling
the
issues.
So
first
manual
silent
alerts
done
two
weeks
ago:
I
think
if
I'm
not
mistaken
or
three
weeks
ago
and
Stefan.
A
Did
appear
to
disable
page
your
duty,
so
the
monitoring
data
dog
is
still
alerting
us,
but
since
that
monitor
sometimes
work,
but
most
of
the
time
does
generate
false
positive.
Now,
it's
silent,
Next
Step
require
more
steps,
so
I
propose
to
postpone
as
well.
B
A
A
Weekly
release
bill
does
not
resume.
I
need
to
spend
some
time
on
this
one,
but
I
thought
it
was
a
quick
one,
but
some
questions
need
to
be
asked
so
I'm,
adding
in
the
next
milestone,
for
the
analysis,
part
just
to
be
sure
that
we
want
builds
to
be
retried.
A
A
team
asked
for
valid
certificate
for
trusted
CI
that
requires
configuring,
lexan
Crypts
certificate
renewal
from
HTTP
to
DNS,
in
puppets
no
emergencies
for
this
one.
So,
let's
postpone
as
well.
There
has
been
the
same
request
for
third
CI
but
same
statues.
Both
services
are
private,
so
we
cannot
use
the
default.
Let's
uncrypt
HTTP
challenge,
so
we
need
to
create
a
restricted
technical
account
on
Azure
that
are
restricted
to
one
or
two
DNS
records
and
we
need
to
add
these
credentials.
A
A
That's
the
goal
for
next
week:
I
missed
time
to
do
that:
Pastor,
Milestone
and
then
the
next
step
after
that
will
be
to
configure
controller,
to
pass
the
data
dog
API
token
and
start
the
docker
agent
service
when
starting
agents,
but
that
one
is
will
be
in
two
weeks.
A
Finally,
last
item
opened
by
Daniel,
it
looks
like
there
is
a
Twitter
Jenkins
Dash
underscore
release
account
which
feed
on
RSS
the
RSS
is
a
flu
flow
is
absolutely
okay,
the
correct
that
time,
correct,
plugin
releases
and
that
Twitter
account
should
publish
tweets
based
on
the
plugin
releases.
But
it's
not
working
as
expected.
A
We're
not
truly
sure
Thanksgiving.
Gavin
pointed
us
different
elements.
It
seems
like
neither
Mark
I
Olivier
Daniel
gave
in
our
team,
have
access
to
the
account
itself
only
Tyler,
but
that
account
might
be
running
on
where
we
run
but
I
think
it's
the
puppet
master.
So
we
have
to
diagnose
that
part.
I
don't
allocate
anyone
on
this
one.
A
A
So
here
on
the
bottom
of
my
screen,
you
see
the
issues
I've
postponed
migrating
pipelines
here
and
it's
blocked
by
the
publish
pipeline
steps.
Docs
generator
use
case
and
repository
for
GitHub
command.
Ups
I
saw
you
had
it
content.
B
It's
like
some
more
yeah.
It
was
an
open
issue
for
Community
to
express
themselves
that
they
don't
see
a
lot
of
commands.
So
I
don't
know.
A
Okay,
was
there
a
community
thread
on
that
topic.
A
B
Yeah
and
yeah
maybe
convince
Team
to
write
a
request.
A
The
rest
enabled
developments
latest
search
using
gdka
17.
All
of
these
have
been
postponed
some
another
day.
Okay,
I,
don't
see
new
issues.
Do
you
have
a
new
ones
on
your
own.
A
B
B
A
So
I
will
do
that
afterwards,
yeah,
okay,
I'll,
take
care
of
that
I.
Don't
have
anything
else.