►
From YouTube: 2022 09 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
Hello:
everyone
welcome
to
the
Jenkins
infrastructure
public
weekly
meeting.
We
are
the
13th
of
September
2022.
Today
we
have
myself
the
memory
portal,
Bruno,
Martin's,
Stefan
mail,
Mark
Waits
and
her
velomer
I
forgot.
I
forgot,
no
one!
Okay,
you
can
find
the
collaborative
note
on
the
current
Zoom
chat
and
that
will
be
published
in
community.
So,
first
of
all,
I'm
sorry
I
was
on
holidays.
So
we
are
late
on
the
publication
of
the
recording
of
previous
meetings,
but
not
on
videos
Mark.
A
B
A
Problem
so
I
will
take
care
of
them
and
thanks
survey
for
sharing
the
one
that
you
managed.
Sorry,
because
the
first
day
of
my
early
days
looks
like
that.
Mark
was
also
off
and
I
forgot
to
chair
the
credentials
so
I
promise
that
won't
happen
again
next
time,
I
will
share
the
account
with
you
folks,
bye
bet,
thanks
for
taking
care
of
that.
A
Let's
get
started
with
announcements,
so,
as
usual,
the
weekly
so
I
saw
someone
was
faster
than
me.
So
the
version
the
2.368
version
of
Jenkins
has
been
successfully
released.
At
least
the
war
file.
The
docker
image
and
the
packages
are
currently
being
built
or
already
published
and
I
assume
the
rest
of
the
checklist
for
the
release
has
to
be
run,
but
almost
there,
no
abusero.
A
B
A
Stefan
is
our
new
designated
volunteer
to
update
the
docker
image
of
Jenkins
score.
A
B
When
we
have
28
days
from
September
7th,
so
October
4
or
something
I
can
look
it
up.
Damien.
A
Okay
cool,
so
that
mean
after
the
devops
fault,
so
no
worries
right
now
correct
your
mission
in
Fatima
is
we
should
check
that
after
that
meeting
we
all
add
if
it's
not
the
case,
either
the
public
John
Kim's
calendar
with
that
information
or
a
new
event
on
our
team
calendar
for
the
next
LTS.
That's
a
cool
responsibility.
A
Next
security
release
sure
they
have
one
published
yet
many
dates.
So,
yes,
there
might
be
one
in
the
upcoming
months
as
usual
as
soon
as
it's
public.
We
can
talk
about
that
next
major
event,
so.
A
B
C
A
Next
major
events
except
the
devops
world
in
two
weeks
where
part
of
the
team
here
will
be
traveling,
so
we'll
shift
we
will
have
to
discuss
during
the
Jenkins
where
we
will
have
a
contributor
submit
I.
Don't
remember
the
special
date
time,
but
I
propose
that
we
canceled
the
Jenkins
infra
weekly
meeting,
because
with
the
all
the
things
that
will
happen
at
the
web,
develop
soul,
I
feel
bad
for
letting
Stefan
running
the
meeting
alone.
B
You're
so
nice,
thank
you.
That's
that's!
Actually,
the
day
of
the
contributor
Summit,
so
it's
it's!
It
would
be
unworkable
for
four
of
the
five
of
us
in
this
meeting
right
now
to
attend
right.
We
will
exactly
collide
with
contributor
Summit.
So
so
yes,
cancel,
makes
sense
to
me.
Yeah
and
I.
Don't
have
the
the
CDs
account
for
the
for
the
registration
for
the
recording.
B
A
World
in
two
weeks,
Jenkins
in
fra,
meeting
canceled
I,
don't
remember
the
exact
calendar
27
right.
B
A
Okay:
let's
proceed
with
the
tasks;
many
thanks
again
everybody
for
the
automating
system
that
allows
us
to
extract
these
tasks
in
a
nice
way
and
so
usable
way.
A
I'm
taking
the
task
in
the
order
of
the
meeting
notes
that
should
be
the
same,
but
yeah
with
GitHub
I'm,
never
sure
that
we
have
all
the
same
view
and
so
I'm
taking
them.
On
the
left
of
my
screen.
A
On
these
virtual
machines,
there
were
some
python
packages
installed
and
when
it's
installed
on
virtual
machine,
the
content
of
the
package
is
not
exactly
the
same
as
when
you
install
it
on
a
container,
and
this
is
because
of
the
way
python
default
user
for
pip
walks,
and
sometimes
it
does
not
download
all
the
transitive
dependencies
and
we
were
missing
two
transitive
dependencies
in
the
process.
A
So
now
this
transitive
dependencies
for
the
Azure
CLI
have
been
added
explicitly.
So
we
are
sure
that
the
team
started
on
Old
platform
on
all
platforms,
and
that
won't
happen
again.
I
haven't
tracked
the
exhaustive
list
of
transitive
dependency
of
the
Azure
CLI
I
talked
about
it.
I
listed
them
and
I
decided
to
just
fix
the
issue
because
adding
more
than
200
transitive
dependency
was
a
bit
too
much.
I
expect
people
to
do
that.
For
me
so
yeah
a
note.
A
A
No
question
next:
one
approve
Jenkins
domain
on
the
GitHub
organization,
so
that
was
one
fix
for
Jenkins.
Thanks
survey
for
taking
care
of
this
one
because
we
were
missing
the
Jenkins,
cert
or
GitHub
organization,
which
is
a
separate
organization
survey,
did
all
the
lifting
with
the
SEC
team,
and
now
they
have
that
nice
badge
on
their
organization.
So
many
thanks
that
was
a
nice
job.
A
Remove
Jesse,
as
default
assignee
for
pipeline
groovy,
plugin
I,
think
that
Timor
is
it
team
or
UAV
will
remove
the
or
even
mock
thanks
Mark.
So
Jesse
is
not
going
away,
but
it
was
a
former
plugin
that
has
been
moved
somewhere
else.
Another
topic
so
that
made
sense.
B
A
C
But
is.
B
A
Have
access
to
Sun
City
Data?
Not
that
we
don't
trust
you,
but
less
people
have
access
to
this
better.
It
is
because,
once
you
have
access,
you
can
extract
all
the
vulnerability
list
of
Jenkins
right,
which
is
we
prefer
keeping
the
model.
It's
just
that
we
need
someone
from
the
infibel
to
access
the
war,
film,
okay,.
A
C
I'm,
adding
preparing
a
pro
request
to
add
a
command
to
IRC
board,
to
Archive
repository
and
change
the
description
of
them.
Oh.
A
Nice
is
there
an
issue
to
track
it
or
should
I
write
it
on
the
work
in
progress.
A
A
Many
thanks
for
that
weekly
release.
Build
does
not
resume
thanks.
Everyone
involved
in
that
one
the
issue
was,
if
accidentally,
someone
from
the
team,
in
particular
Damian
reporter
merge,
pull
request
on
the
release,
CIA
controller
and
it's
redeployed.
A
A
But
first
most
of
the
issues
were
planned
on
the
parent,
build
that
wasn't
doing
that
wasn't
even
requiring
any
agents,
so
we
removed
this
spot
allocation
for
the
release
and
it
worked
today
without
any
flow,
so
proved
that
it
wasn't
required.
The
goal
of
that
parent
bill
is
to
trigger
the
sub,
build
release
and
then
trigger
the
package.
A
Also,
we
have
added
the
system
or
retry
system
that
Jesse
worked
on
that.
If
there
is
an
issue
with
the
agent
or
control
of
both
during
the
packaging
Port,
it
automatically
retried.
So
it's
a
okay.
It
failed
and
it
will
try
your
second
time
and
it.
So
we
can
use
spot
instance,
for
instance,
if
the
agent
is
killed
abruptly,
then
it
will
restart.
A
Jenkins
has
the
knowledge
of
the
reason
of
the
failure
we
did
not,
and
it's
really
important
that
why
I'm
giving
these
details
thanks
to
Jesse,
he
pointed
out
that
this
retry
system
must
only
be
enabled
on
Pipeline
that
are
ident,
which
means
you
can
run
the
same
pipeline
two
three
four
at
least
one
time.
You
will
have
the
same
results
and
Publishing
a
release
is
not
either
important
because
you
cannot
override
a
release,
at
least
on
the
maven
repository
it's
you
should
not,
and
it
has
been
blocked
on
our
systems.
A
So
once
you
are
released,
if
you
run
the
initial
release,
build
that
bill,
Jenkins
run
the
test,
create
a
new
tag
and
then
deploy
the
tag
to
the
repository.
If
you
run
it
a
second
time
that
means
you
will
create
a
new
tag,
so
it's
not
hidden
important,
so
you
don't
want
an
automatic
retry
in
case
of
failure
on
such
a
build.
A
So
the
last
case
we
have
to
track
now
is
maybe
we
can
run
on
some
cases
where,
during
that,
build
that
bill
Jenkins
and
tests.
Sometimes
the
controller
could
still
restart
if
the
men
continue
merging,
pull
request.
All
the
time-
and
it
should
continue
working
because
that's
what
the
pipeline
is
expected
to
do
in
normal
case.
A
However,
if
we
see
issues
on
that
so
I'm
asking
Mark,
because
you
are
the
author
of
that
issue-
if
but
it's
for
everyone,
if
you
see
again
non-resumability
so
not
a
retry
But
continuing
the
work
after
the
controller
restart,
then
in
that
case
we
might
have
a
real
bug
and
Jesse
asked
for
more
details.
If
we
can
reproduce
this
one
or
if
you
see
new
occurrences.
A
We
can
artificially
try
it
since
we
can
trigger
a
weekly
release
when
we
want
no
I
want,
especially
with
the
security
release
next
week.
Otherwise,
I
will
have
people
visiting
me
physically.
B
A
Okay,
next
topic,
I
had
was
archive
extra
executable
War,
so
repository
not
used
anymore.
That
has
been
archived,
so
thanks
team
again
for
doing
that
and
everybody
by
the
way,
if
there
are
ISC
Bots
involved,
an
issue
see
a
note
edge
on
the
CIA
case,
kubernetes
cluster.
It's
that
issue
was
dated
two
weeks
ago,
the
last
day
when
I
was
walking,
there
has
been
a
deployment
of
the
AWS
so
to
scalar.
A
It
was
fixed
before
my
holidays,
but
I
forgot
to
put
all
the
fixes
and
we
have
updated
the
components
and
fixed
the
issues.
There
was
a
bug
in
the
M
chart,
so
we
had
to
wait
for
the
new
version
of
them
chart
fixing
the
back.
That
kind
of
thing
happened
sometime,
so
we
lost
two
builds,
two
plugin
builds
that
were
restarted
manually
and
that
was
an
outage
of
15
minutes
on
cic
the
jenkins.io.
So
the
issue
has
been
closed.
A
With
details
on
the
bus
pack,
no
more
action
expected
there
upgrade
CI
to
the
latest
LTS
we
had
LTS
release.
We
had
to
use
it.
So
thanks
thanks
a
lot
on
all
the
Stefan
on
preparing
and
merging
the
docker
images,
because
I
had
a
clean
state
with
only
the
changes
related
to
the
LTS.
That
was
easy.
So
in
less
than
two
hours,
everything
was
deployed
and
running
flawlessly,
full
GDK
event
for
everyone
and
last
fully
completed
task,
delete
an
account
to
be
deleted
in
Jenkins
IO.
A
So
thanks
survey,
I
think
that
you
are
the
one
who
took
care
of
that.
So
a
reminder
in
order
to
prove
identity.
When
someone
has
such
a
request
deleting
an
account,
so
something
related
to
the
account
in
the
ldap
being
able
to
comment.
Jericho
is
one
way
to
prove
that
the
person
is
able
to
access
the
account,
because
if
you
ask
them
to
send
you
an
email,
it's
not
good
enough
to
prove
they
are
the
person
they.
They
pretend
to
be.
A
B
Well,
and
and
I
wonder,
is
there
a
place
where
we
should
be
putting
these
kind
of
challenge
techniques,
because
I
I,
like
knowing
those
techniques,
the
technique
that
everybody
used
is
really
helpful?
Is?
Oh,
yes,
of
course,
if
you
still
have
your
jenkins.io
account
password,
you
can
update
a
bug
report
and
that
will
prove
it
and
and.
C
B
I
I
like
that
well
and
and
I
use
a
similar
Challenge
on
GitHub
side
to
prove
that
they
own
a
GitHub
account
asking
them.
Please
Fork
the
get
client
plugin
repository
into
your
account
and
that's
when
I
see
that
the
fork
is
visible.
I
know
that
they
they
did
it
so
so
those
kinds
of
challenges,
I,
think,
are
a
good.
A
good
thing
for
us
to
describe
and
I
have
never
put
that
fork
thing
in
the
in
the
runbook
either
so
I
think.
Maybe
we
want
action
items
to
say,
update
the
challenge.
A
Nice
one,
so
that
means
we
have
two
update.
The
existing
run
book
for
that
part
was
volunteering
for
that
yeah.
A
A
More
questions:
okay,
I'm
proceeding
for
the
work
in
progress
subjects
latest
link
for
some
plugins
on
archives
during
King
Sayo
are
outdated.
So
it's
a
second
topic.
We
already
had
an
issue
with
the
latest
on
the
get
Jenkins
xiaomi
raw
system,
and
now
we
also
have
that
on
archives,
Jenkins
I
haven't
diagnosed
yet
both
are
different
systems.
A
A
We
haven't
worked
on
that
yet
just
commented
and
acknowledged
to
the
end
user
because
they
ask
if
it
was
the
right
place
to
ask
and
if
they
did
something
wrong,
they
didn't
that's
an
issue
on
our
side:
okay,
publish
acceptance,
test,
Earnest,
Docker
image
and
release.
So
now
the
image
is
built
and
pushed
as
the
latest
image.
A
The
next
challenge
that,
on
the
line,
a
big
trouble
with
the
CD
process
of
the
Jenkins
plugins,
is
that
Jenkins
on
our
on
our
instance.
We
have
a
policy
that
say,
don't
build
a
tag
which
is
older
than
three
days.
The
goal
is
that
if
you
accidentally
scan
a
repository
that
ReDiscover
all
the
tags
since
the
beginning,
you
don't
want
Jenkins
to
start
rebuilding,
not
only
because
it
consume
resource
for
nothing,
but
also
publishing
at
the
risk
of
overriding
existing
Docker
images
in
that
case.
A
So
that's
why
we
put
that.
The
problem
we
have
is
that
the
tags
created
when
the
CD
process
used
for
plugins,
it's
a
GitHub
release,
object
and
it's
generated
by
release
drafter
as
a
draft.
So
it's
not
visible
publicly.
That
draft
is
created
once
you
merge
your
pull
request
after
release,
it
starts
creating
the
new
release
nodes
and
it
creates
a
temporary
tag.
A
That
tag
has
a
unique
identifier.
Then,
the
day
you
publish
the
release,
it
will
create
a
tag
Associated
to
the
release,
pointing
to
the
moment
in
time
where
you
want
to
release
the
kind
of
git
tag
created
by
the
GitHub
release,
which
are
two
systems
is
known
as
LightWave,
which
means
the
tag
is
only
a
label
pointing
to
a
shf.
That's
all
it
does
not
have
a
timestamp.
The
timestamp
is
the
timestamp
of
the
commits,
which
means
the
tag
was
seen
with
a
more
than
three
days
or
even
if
team
just
created
it.
A
A
few
minutes
before
so
Jenkins
was
not
picking
it
up,
and
that
will
be
this.
That
will
be
the
same
with
Trevi
Circle,
CI
gitlab,
even
GitHub
actions.
It's
just
that
by
default.
The
the
tags
created
by
your
GitHub
release
are
lightweight
so
the
solution,
because
we
already
met
that
problem
with
the
Jenkins
and
Docker
images
that
are
not
using
CD
but
still
same
pattern
released
after
and
everything
we
create
a
special
kind
of
tag,
name
annotated.
A
So
it's
a
tag
with
a
sign
body
Associated
to
the
Tiger,
where
you
can
put
change
log
message
like
with
the
commit
and
when
you
create
another
tag,
the
timestamp
become
the
time
when
the
tag
have
with
The
annotation
was
created
and
pushed
for
us.
It
was
easy
we
did
that
five
months
ago
we
add
the
flag-a
when
creating
the
tag
here.
So,
instead
of
git
tag,
you
git
tag
Dash
a
name
of
the
tag.
You
push
it
and
that's
all
here.
A
It's
trickier
because
we
had
to
open
the
contribution
to
the
CD
process
and
now
I'm
in
the
process
of
testing
it
on
the
Jenkins
plugin
infra
test
to
see
if
it
work
as
expected.
Right
now,
my
contribution
is
not
working,
but
we
need
that.
So
I
will
continue
working
on
that
this
week.
If
I
can
make
it
end
of
week,
if
I
haven't
find
a
variable
solution,
then
I
will
follow
GSE
tip.
A
A
The
thing
is
that
if
you
can
create
a
release,
you
can
override
a
tag.
There
is
no
blocking
it's
not
like
overriding
code,
it's
different,
but
there
are
two
downside:
I,
don't
know
the
behavior.
If
you
have
a
release
pointing
to
the
tag
that
you
override
I'm,
not
sure,
how
is
the
link
working?
Is
the
release,
unpublished
or
found,
or
just
updated,
to
use
the
new
tag?
A
So
that
one
was
pretty
tricky,
the
good
thing
is
that
now
afrasia
is
able
to
build
and
publish
images
on
the
Jenkins
CIA
organization.
So
we
can
provide
that
service
to
more
projects
on
the
community,
not
only
the
Jenkins
in
fights
the
the
idea
here.
It's
a
kind
of
City
they
can
still
have
CI,
build
and
test
with
the
same
method,
same
tooling
same
adult
constraint
publicly,
and
we
only
do
the
deployments.
So
that
means
we
could
ideally
start
pushing
the
official
agent
images,
for
instance
from
infrastia
I.
Don't
say
we
should.
A
Next
one
thanks
a
lot
everybody
for
hosting
pluginil
scoring
application.
So
there
that's
a
new
gsoc
project
led
by
Adriana
chapati
with
one
or
two
gsocket
on
these
I.
Don't
remember
how
much
so
we
will
have
to
ask
that
as
infrastructure
in
a
way
that
they
make
them
as
autonomous
as
possible
for
the
scope
of
the
gsoc,
and
then
we
will
see
how
to
productize
this
one.
That
means
providing
them
CI,
which
we
already
did
a
few
weeks
ago,
and
now
it
was
the
cd
part.
If
I
understand
correctly
foreign.
C
C
How
cool
this
is
document
I
proposed
him
to
make
it
that
he
wanted
to
take
a
look
so.
C
A
A
Information
about
database
I,
don't
remember
that
Stefan
walked
a
few
months
ago
on
manage
postgresql
database
on
Azure,
which
has
been
terraformed.
So
you
should
be
able
to
take
the
walk
from
him.
So
don't
say
to
ask
him
for
to
pair
that
will
be
interesting
to
work
together
on
that
if
they
need
be.
C
A
Sorry
I
was
muted,
I
might
have
muted
sorry.
So
thanks
a
lot,
that's
a
lot
of
Works.
Many
thanks,
don't
hesitate
to
help
continue
helping
Adrian
like
you,
do
that's
really
important
that
they
are.
They
don't
wait
too
much
on
us
and
there
is
autonomous
as
possible.
A
A
A
Just
because
I
forgot
to
talk
about
that
on
the
announcement.
So
we
had
a
meeting
with
g
frog.
We
will
need
to
start
a
discussion
that
should
mainly
take
place
during
the
contributors
submit
in
two
weeks
about
the
future
and
how
we
use
g
frog,
artifactory
system
we
have
a
constraint
is
that
we
need
to
decrease
our
bandwidth
usage
on
the
system.
A
The
order
of
magnitude
is
five
to
six
times.
Less
bandwidth
should
be
consumed.
We
consume
a
lot.
We
have
learned
a
lot.
Daniel
started
knowledge
sharing
with
me
about
the
Legacy,
even
if
Mark
already
has
some.
So
the
goal
is
continue.
Working
on
that
area,
there
are
multiple
Solutions
that
all
solution
will
involve
an
infort
on
our
area.
A
First
point
I
have
been
granted
by
Daniel
yesterday,
access
admin,
access
to
the
Repository,
so
I
should
not
require
that
access.
It's
a
separated
account,
but
I
will
publish
a
run
book
with
the
rules.
The
main
rule
is
don't
delete.
Anything
and
the
second
rule
is
don't
zap.
The
cache
absolutely
I
will
open
an
issue
that
Daniel
shared
with
me.
A
C
Yeah
so
I'm
still
rinsing
around
some
error.
Permission
error,
I,
fixed
the
apps
probe,
I
needed
for
the
container
in
kubernetes
and
I'm
working
on
the
digital
proxy
providers.
C
I
have
to
I,
am
I
had
last
week
and
I'm
now
deploying
an
external
load
balancer,
so
I
can
refer
to
its
VP
address
more
easily.
That's
called
so.
This
is
in
progress,
I
think
as
soon
as
as
soon
as
I
fixed
the
else
and
permission
error,
I
will
be
able
to
put
C
Azure
proxy
or
in
tests
or
start,
and
then
we
will
be
able
to
write
the
user
provider
as
soon
as
they
are
ready.
A
Nice
job
that
wasn't
an
easy
one
honestly,
because
it's
really
uneduced
gates
for
a
kubernetes
there,
demo
of
pattern,
digital
signing
coming
so
next
step
test.
It
is
that
is
that
a
good
summary.
C
Yes-
and
we
have
the
drinking
surface
plugin
for
basic
testing
and
I
I
like
to
know
I,
will
ask
what
is
a
plugin
with
the
most
dependency,
so
a
big
one
to
build.
C
B
B
A
That
will
be
a
nice
October
for
this
topic.
Thanks
a
lot
to
Irving,
that's
a
topic
of
the
most
important,
so
we
have
to
continue
the
effort
there.
That's
a
way
to
communicate
also
to
g-frog
that
we
are
working
actively
on
reducing
the
bandwidth
conception,
we'll
get
back
publicly
with
more
information.
Once
we
will
start
the
topic,
we
might
need
to
run
some
experiment
on
the
infrastructure
by
enabling
authentication
for
our
agents.
A
A
However,
there
might
be
some
because
that's
the
second
thing
we
we
will
have
a
migration
of
g-frog.
They
told
us
that
they
still
have
to
communicate
the
date
time,
but
they
will
migrate
from
the
current
machine
hidden
somewhere
that
they
are
using
to
their
new
platform.
So
then
we
should
be
able
to
get
back
on
the
system
that
mean
almost
one
hour
outage
on
ripogenic
in
ci.org.
They
will
communicate
with
us
the
date
and
time
and
we
will
have
to
update
statues
at
that
moment.
A
A
Datadog
metrics
for
one
archives,
cluster,
it's
weird
and
I-
don't
understand,
but
there
are
missing
metrics
only
for
pod
public
Gates
cluster
I
can't
really
understand
why?
Because
temp
private
works
and
it's
in
Azure
also
it's
the
same
version
eks
and
the
uks
are
perfectly
fine.
We
have
all
the
metrics
already
and
everything
it
works
fine.
A
A
Twitter
Jenkins
release
accounts.
I
didn't
took
the
required
time,
thanks
Verve
for
backing
me
up
on
that.
During
my
early
days
we
have
access
to
the
Twitter
account
wherever
you
made
a
proposal
for
maybe
just
revoking
the
token
used
by
the
lvr
and
adding
a
new
Automation
and
implementation.
A
So
the
goal
of
that
account
is
to
create
tweets
that
come
from
the
RSS
publication
of
the
plugins
and
project
on
Jenkins,
so
yeah
I
still
need
to
answer
to
dlver
support
the
ticket.
You
open
their
way.
C
A
C
A
B
And
and
we'll
see
him
at
devops
World.
Actually
so
it's
oh
yes,
perfectly!
Okay,
we'll
be
we'll
we'll
be
held
to
Elbow
with
him
at
devops
world
and
it's
a
great
opportunity.
If
we
haven't
resolved
it
by
then
to
just
say:
hey:
let's
do
it
together
and
I'm
sure
I
would
have
a
computer
up.
You
know
as
far
as
I
know
he
he
very
frequently
does
yes.
A
Nice,
thanks
for
the
reminder,
I
forgot
that
he
was
attending
so
okay,
so
Alvin
and
I
will
be.
That
will
be
our
mission
during
the
devops
world,
so
I
propose
that
we
put
that
one
on
all
the
for
the
any
tweaks
looks
good
for
you.
A
B
There
I
will
say
exactly
the
same
thing
than
last
week.
Almost
there
I
I
think
that
for
that
it's
it's
just
going
to
production,
but
I
need
to
make
sure
with
you.
How
I
would
do
that?
But,
okay,
this
one
I'm
I
did
Azure
I
did
ec2
Amazon,
and
it's
it's
now
working
since
yesterday,
or
even
this
morning,.
A
A
Many
thanks
for
that
work.
Next,
one
still
you
Stefan,
so
we
have
the
the
high
level
topic
is
providing
Java
17
Windows
agents.
We
have
the
all-in-one
container.
Oh.
B
A
B
So
so
I
think
that
this
one
is
closed
for
for
resolved
too,
as
I'm
right
now
trying
it
on
the
on
the
plugin.
The
test,
plugin
infra,
test,
plugin
and
I
I
saw
that
it
it's
crashed
on
the
17,
but
I'm
not
quite
sure
of
why
but
I'm
okay,
good
direction.
B
A
So
first
we
send
an
email
with
the
timeline,
but
that's
my
proposal.
We
sent
an
email
when
we
are
sure
that
it
work
on
bus
with
your
testing.
We
send
an
email
saying
here
is
the
issue.
Here
is
the
timeline
and
the
day
of
the
timeline.
You
have
preparable
requests
that
remove
your
testing
templates
and
change
the
existing
one.
A
They
keep
the
same
name
and
labels,
but
to
send
the
rest
of
the
setup
and
we
try
if
it
doesn't
work,
we'll
revert
it
back
to
the
old
images
and
then
we
we
keep
watching
for
for
the
bills
and
the
feedbacks,
but
the
most
important
part
is
to
let
developers
know
at
least
one
day
before
so
if
they
have
a
build,
failing
or
release
failing,
they
know
that
it's
not
because
of
them,
but
because
of
us-
and
they
can,
let
us
know
it's
not
working,
so
we
can
quickly
revert
and
unblock
them
if
needed.
That's.
A
No
because
there
will
be
no
way,
as
you
discovered
on
the
pipeline
Library
code,
there
is
no
way
for
the
developer
to
say:
I
want
to
use
the
fallback
and
it's
better
to
have
only
simplified
configuration.
So
we
have
less
things
to
test
at
the
given
time
and
if
it
doesn't
work,
we'll
roll
back
and
start
again
with
the
test.
A
Understood
looks
good
yes,
so
almost
there
Next
Step
still
on
that
topic,
I've
almost
successfully
built
a
Windows
container
with
the
same
provisioning
script
as
the
virtual
machine
I'm
in
the
process
of
what
is
missing
on
the
Windows
Server
core
container
that
the
all
the
cloud
machines
have
on
the
template
for
Windows
server.
A
I,
add
issues
with
the
Pod
SSH
some
packages,
but
almost
there
I
have
two
tools
on
the
24
tools
that
we
installed:
two
that
are
missing
so
almost
there,
which
means
once
Windows
container
are
okay.
Then
we
can
start
adding
the
windows
17
agent
with
the
all-in-one
pattern
that
will
be
easy,
Windows
container,
I'm
I'm
failing
only
the
provisioning,
but
right
now
in
my
request
in
Frasier,
is
already
able
to
spawn
a
Windows
machine
and
build
container,
which
means
the
EV
lifting
has
already
been
done.
A
A
word
on
separated
pipeline
for
update
CLI
Airway
started
to
split
in
two
pipelines
for
kubernetes
management
as
the
first
POC.
For
that
concept,
the
idea
is
to
have
separated
Pipeline
and
separating
jobs
in
infrasti
that
take
care
of
running,
update,
CLI
div
and
apply
so
then
we
would
have
less
complex
pipeline
because
split
into
Allah
GitHub
workflow.
A
Right
now
we
are
using
a
static
definition
with
job
DSL
of
multi-branch
pipeline
for
this
one
to
validate
that
checks
and
everything
works
in
the
usual
workflow
of
our
pull
requests
and
it's
blocked
by
your
missing
feature
on
our
M
chart
that
Define
the
jobs
for
Jenkins
controller
in
Cuba.
We
we
want
to
use
a
GitHub
organization
and
it's
not
implemented.
Yet
it's
only
a
matter
of
you
writing
the
template.
The
goal
is,
we
would
have
a
GitHub
organization
scanning.
A
A
So
then
the
convention
will
be
at
that
Pipeline
and
that
will
work.
We
can
improve
and
iterate.
We
could
use
a
file
a
token
per
repository.
There
are
multiple
solution,
but
we
are
there.
The
goal
is
to
simplify
your
pipeline,
so
they
are
faster
and
we
won't
wait
for
updates
here,
like
we
parallelize
as
much
as
possible,
did
I
miss
something
early.
A
Nope,
okay,
chart
POC
on
kubernetes
management.
Thanks
for
that
walkerby
publish
pipeline
step
dog
generator
on
backend
extension
indexer
that
will
be
for
next
week.
The
goal
is
to
stop
having
cigub
publishing
files
that
are
used
to
build
Jenkins
IU
website,
not
only
it's
unsafe,
but
also
it's
slowing
down
security
processes.
A
So
the
goal
is
to
have
a
job
on
infrastiae,
which
is
mainly
a
report
job
that
would
upload
the
result
of
these
Builds
on
a
bucket
which
is
publicly
available,
because
that
the
goal
is
that
having
that
data,
but
that
data
will
be
generated
on
infra
CI.
So
we
can
stop
see
agent,
King,
Sayo
and
rebuild
the
website
in
kinsayo
still
successfully,
even
with
CI
Jenkins
ayodon
I
haven't
worked
on
that.
Yet
anyone
interested
can
start
working
on
that.
It's
building
jobs,
otherwise
I
will
use
it.
I
will
take
it
as
fallback.
A
I
haven't
started
working
on
Mirror
by
cleanup
that
involved
the
maybe
breaking
all
the
public,
the
publication
of
all
plugins,
so
I'm,
still
careful
on
that
one
I
needed
to
go
back
to
work
and
be
having
some
brain
time.
It's
blocking
the
migration
to
Oracle
for
the
updates
changed.
A
So
next
step
for
me,
I've
taken
care
of
incoming
work
by
your
way
and
I
think
that's
already
a
lot
of
work
from
the
world
team.
There
are
Advanced
Event,
thanks
for
taking
care
of
this
huge
issue
that
you
are
both
working
on.
That
might
not
looks
like
you
are
working
on
a
lot
of
issue
at
the
same
time,
but
this
issue
a
huge
really
huge
thanks
for
that.
A
Okay,
I,
don't
have
something
else
to
add,
so
I
will
close
the
meeting,
publish
this
meeting
and
the
previous
recording
and
create
a
new
milestone.