►
From YouTube: 2021 04 06 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
So
next
topic-
I
guess
that's
well.
I
could
put
that
what's
the
current
status
with
amazon
sponsorship.
Basically,
we
are
back
to
the
previous
situation
where
cloud
is
paying
the
accounts,
so
the
amazon
budget
we
got
is
totally
spent
by
now
and.
B
A
Last
time
I
was
in
contact
with
them
that
was
yeah.
We
it's
difficult
to
know
for
sure
if
they
won't
sponsor
us
anymore,
but
at
least
yeah.
C
A
C
Well-
and
I
assume
the
release
is
already
built
that
yes,
daniel
has
already
certainly
built
it
and
has
it
ready
and
staged
privately
so
that
it's
not
not
that
we're
dependent
on
the
release
infrastructure
tomorrow,
we're
dependent
on
delivery
infrastructure
tomorrow
and
and
the
mirrors
etc.
So
so.
A
C
B
B
Yes,
so
I'm
still
a
bit
concerned
about
table
studies
impact
because,
with
the
tomorrow's
release,
we
might
be
pushing
the
user
stop
date.
We
know
about
the
number
of
plugins
which
are
still
not
compatible.
B
A
Basically,
the
once
once
you
have
the
codes
on
the
on
the
branch
on
jenkins
ci,
slash
jenkins.
Once
your
branch
is
ready,
the
release
environment,
it
takes
approximately
two
hours
to
build.
It
is
the
wi-fi.
A
The
lts
require
a
little
bit
more
work,
but
it's
like
maybe
10
minutes,
10
15
minutes
just
the
time
to
to
update
the
file
with
the
correct
configuration
and
someone
to
review
that
configuration
so
yeah
it
approximately
approximatively,
take
one
hour
32
hours
to
build
the
jenkins
score
and
then
15
minutes
to
package
and
publish
that
those
new
packages.
C
B
B
A
Then
I
propose
to
finish
the
meeting
here
thanks
for
your
time
and
see
you
on
rc
have
a
good
day.
Bye-Bye
thanks.
Everybody
welcome
for
this
new
jenkins
infrastructure
meeting,
so
be
so
few
announcements
before
we
continue
the
first
one
is.
We
are
going
to
upgrade
the
communities
cluster
used
by
the
jenkins
project
next
week.
A
We
are
planning
to
do
that
on
thursday
on
tuesday.
Sorry,
sorry,
next
tuesday
I'll
do
that
with
carrots
and
damian.
So
normally
everything
I
mean
we
should
have
interruption
but
yeah
better.
Do
I
prepare
put
on
that
in
advance
anyway?
The
second
topic
that
I
briefly
want
to
mention
is:
I
created
the
keytap
adobe
group,
and
so
the
rule
is
as
a
contributor
once
you
have
privileged
access.
A
If
you
know
that
you
won't
be
able
to
contribute
in
a
short
and
short
term,
it's
just
better
to
to
ask
to
be
to
have
your
permission
reduced,
so
we
don't
take
the
risk
of
getting
compromise
for
whatever
the
reason.
So
that
was
the
second
thing
that
I
want
to
mention.
A
So
if
we
go
back
to
the
ongoing
work
this
morning,
we
did
specific
releases
using
release.ci
and
we
faced
a
bunch
of
issues
for
some
reason.
So,
basically,
we
got
timeout
issues
between
the
jenkins
agent
and
jenkins
controller,
so
we
were
affected
by
the
same
behavior
on
infrared
ci.
Last
week,
damien
made
the
suggestions
to
switch
the
connection
using
websockets,
which
seems
to
be
solving
the
connection
issues.
I
still
don't
understand
why
we
were
affected
now.
A
Why
why
we
are
affected
now
by
not
using
the
websockets
but
yeah
switching
to
the
website
and
made
it
made
it
working?
Maybe
I,
like
you,
have
some
ideas
there.
A
B
So
current
state
of
web
circuits
that
it's
officially
still
in
preview,
okay,
because
web
circuits
works
perfectly
fine
on
java
8
for
java
11
and
hence
for
our
instances.
There
are
some
unknown
issues
with
a
certificate
which
haven't
been
troubleshooted
yet
so
we
reviewed
it
with
jc,
greek
and
jc
said
that
most
likely
it's
a
specific
environment
issue,
but
we
have
never
already
tested
that.
B
B
B
A
At
least
in
the
jenkins
project
to
release
the
ti
in
front
of
ci
and
see
if
jenkins
are
running
on
java,
11.
trusted
ti
and
third.ci
are
running
in
java,
8.
D
B
Yeah,
but
it
was
noting
that
our
instances
are
relatively
simple
when
you
take
the
number
of
installed
plugins.
A
Autumn,
thanks
any
other
suggestion
regarding
the
issue
we
had
this
morning,
so
basically
we
have.
We
have
prs
to
change
the
configuration
of
info.ci.
We
just
did
the
manual
change
this
morning,
so
we
could
move
far
faster,
but
once
the
release
is
over,
we'll
we'll
apply
the
configuration
change.
A
So
that's
that
thing,
that's
anything
so
until
tomorrow
we
put
an
older
job
and
infra
the
ti
that
managed
taking
this
cluster.
So
no
change
right
now.
To
that.
A
The
next
topic,
so
if
you
have
some
topic
that
you
want
to
bring
that's
a
break
freak
time
as
we
don't
have
a
lot
of
things,
so
something
that
I
want
to
share
is
some
experimentation
that
I
did
with
keep
look
last
week.
So
kick
lock
offered
the
possibility
to
delete
to
allow
users
to
delete
their
accounts.
I
just
faced
two
main.
I
mean
once
minor
issue,
keep
clock
change
the
theme,
so
we
want.
A
If
you
want
to
keep
using
the
jenkins
theme,
we
have
to
do
some
minor
modification
which
is
not
a
big
deal.
But
yes,
but,
more
importantly,
deleting
users
only
delete
the
users
from
key
cloak,
not
from
ldap,
which
means
that
if
you
really
want
to
use
that
feature,
we
really
have
to
switch
using
key
cloak
instead
of
ldap
for
issues
touching
that
ideo,
that's
one
thing
and
the
second
limitation
is
deleting
user
to
not
delete
the
group
inside.