►
From YouTube: 2022 07 26 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
B
A
Nice
second
announcement
just
a
reminder
that
for
the
northern
hemisphere
this
is
summer,
which
means
a
lot
of
people
are
going
in
holidays.
I
will
be
off
starting
tomorrow,
included
for
eight
eight
days
next
week.
Rv
is
going
for
two
weeks
in
the
holidays,
and
I
assume
that
stefan,
you
are
going
in
holidays
in
three
weeks,
which
means
during
the
months
of
august,
some
of
us
are
going
to
be
there
or
not.
There
depends
on
the
weeks
mark,
I
assume
you
might
have
some
holidays
as
well.
B
A
A
We
could
choose
another
location,
but
for
this
month
you
have
the
information
for
members
of
the
team
and
for
anyone
else.
That
means
we
will
have
limited
availability.
Our
bandwidth
will
be
decreased
because
we
won't
be
full
team
available.
So
we'll
try
our
best
to
fulfill
requests
but
expect
some
delays.
A
A
Jenkins
lts
release
candidate
schedule
tomorrow.
That's
the
next
announcement
mark.
B
Correct
so
alex
brandis
has
volunteered
to
be
released
off.
Release
lead
for
the
that
release.
Kevin
martins
is
assembling
the
changelog
lts
back
ports
relatively
few,
and
alex
has
confirmed
that
the
windows
installer
change
that
would
that
intentionally
forbids
java.
8
will
not
be
used
for
jenkins
2.346.3.
A
Okay,
I've
added
it
in
that
part.
Next
week
we
should
have
the
a
weekly.
Is
that
correct,
correct
that
one
will
be
for
stefan
just
because
of
the
calendar,
because
their
boss,
serviendai
won't
be
there
nothing
expected
as
usual,
that
should
work
at
least
the
10
past
work
without
any
issue.
If
there
are
any
issues
as
usual,
you
have
to
read
the
logs
or
ask
mark
for
and
team
for
help.
B
B
A
Which
mean
tomorrow,
try
to
avoid
merging
things
on
kubernetes
and
puppets,
so
the
controller
won't
restart
and
people
will
be
able
to
do
the
lts
release.
Candidates
sounds
good
for
everyone.
B
D
B
A
So
there's
been
the
installation
of
the
github
command
ops.
I
understand
that
work
by
team
and
rv.
At
least
it
appeared
that
there
have
been
some
rush
on
installing
that,
as
I
understood
so
it
has
been
disabled
except
for
at
least
one
or
two
repository
test
repositories
on
the
jenkins
ci
organization
is
my
understanding,
correct.
D
A
Enabling
or
disabling
is
what
problem
do
we
want
to
solve
for
which
repository
and
then
security
assessment,
because,
for
instance,
I
don't
want
anyone
to
use
it
for
puppet,
but
I
can
understand
it's
needed
for
jenkins
io.
So
we
need
an
exhaustive
list
of
the
repository
where
it
should
be
installed.
A
A
D
A
Don't
get
me
wrong.
I
think
that
truly,
a
really
useful
tool
is
just
that
for
some
repositories
it's
useful
and
for
some
it's
dangerous,
and
since
we
have
both
part
of
the
equation,
we
need
just
to
list
where
it
will
be
useful
without
any
risk.
That's
the
only
thing
I
ask,
but
I
don't
mind
having
it
on
the
on
the
system.
A
A
I'm
taking
the
issue
in
the
order
of
the
notes.
There
has
been
a
someone
that
wasn't
able
to
connect
to
repo.g,
so
it
was
due
to
an
invalid
email
on
account,
chinkin
sayo.
So
thanks
everyone
for
solving
that,
not
a
lot
to
say
about
this
one.
A
A
A
So
thanks
for
that
work,
I
don't
know
if
there
are
any
questions,
something
to
note
next
one
then
disable
all
anti-spam
protection
on
cell.ci,
so
with
the
work
that
rv
did
recently
on
the
puppet
templating
to
allow
search
ci
to
have
some
exception
to
to
diverge
from
the
ci
jenkins,
iu
usual
config.
A
C
I
think
between
the
set
of
plugins
and
this
particular
apache
raw
stuff,
I
think
those
were
the
big
ones.
Thank
you
for
cleaning
those
up,
no
problem.
A
A
A
D
Yes,
it's
the
same
as
art
factory.
This
test
is
now
trying
to
log
in.
C
A
A
A
C
So,
for
what
it's
worth,
artifactory
is
acting
up
today,
okay,
while
we
were
trying,
so
this
is
something
I
first
discovered
like
two
security
advisories
ago
or
something
I
can
create
a
new
private
staging
repo
for
security
fixes
and
artifactory,
and
for
several
hours
afterwards.
Our
defectory
isn't
quite
sure
whether
that
repository
exists
or
not,
which
is
a
problem,
especially
if
stuff
is
already
stationed.
We
expect
it
to
remain
staged
and
then
the
artifactory
claims
it
has
no
knowledge
of
anything
related
to
the
staged
content.
C
C
C
Just
do
it
ourselves,
so,
ideally
adriana
is
reaching
out
to
me
when
he's
doing
that.
The
problem
we
have
in
artifactory
is
that
I
think
we
have
logs
for
two
minutes
or
something
they
have
insanely
aggressive
log
rotation,
and
so,
if
you
tell
me
20
minutes
after
the
fact
that
something
went
wrong,
I
know
nothing
about
it.
D
A
A
Yeah,
I
will
go
for
during
the
briefing
once
I
will
request,
because
yeah
that's
a
good
point.
I
need
to
be
briefed
on
what
to
do
and
not
to
do.
A
A
I've
redirected
him
to
the
mailing
list,
because
that
will
involve
giving
him
some
kind
of
privilege.
Permissions
on
see,
I
don't
know
given
joseph,
is
helping
the
infra
team
that
will
make
sense
from
a
pure
infrastructure
point
of
view.
That's
why
I
said,
as
in
professor,
I
don't
see
any
issue
on
that.
However,
that
could
have
some
side
effect
that
I
haven't
talked
about.
C
D
C
Has
been
quite
clear
to
me
because
the
infra
library
be
such
that
the
all
pipelines
would
be
trivial.
No,
I
mean,
even
even
if
he's
updating
the
jenkins
file,
except
how
much
can
possibly
go
wrong.
There.
C
Well,
it's
running
in
the
sandbox,
so
it's
not
like
it
sounds
yeah
yeah
right,
but
the
point
is
usually
the
jenkins
files
are
maintained
by
the
plug-in
maintainers
and
for
jenkins
file
changes
to
be
effective.
C
D
C
Just
right
users
with
admin
all
right
permission,
this
one
exactly
right,
so
the
use
case
isn't
clear
to
me.
So,
even
if
he
wants
to
propose
pull
requests
that
get
pipeline
changes.
C
So
it's
not
clear
what
the
use
case
is
and
is,
if
he's
a
contributor
to
a
specific
component
like
the
bomb,
then
he
can
just
commit
his
changes
to
an
origin
branch
rather
than
a
branch
of
a
fork,
for
example.
A
For
me,
I
understand
it's
that
you
want
to
test
the
jenkins
file,
pull
request,
changes
and
in
that
case
either
you
are
admin
rights
under
repository.
But
if
you
are
admin
of
the
jenkins
controller,
you
can
trigger
builds
that
will
be.
You
will
be
seen
as
trusted.
That's
the
only
exception
of
the
trust
model.
There.
C
No
he's
specifically
asking
for
the
rebuild
permission
of
of
pipelines.
He
doesn't
even
need
admin
permissions,
and
so
he
can
still
file
the
pull
request.
It's
just
that
the
pull
request
would
ignore
the
jenkins
file
changes
and
use
the
jenkins
file
of
the
main
branch.
But
when
the
maintainer
merges
the
changes
to
the
jenkins
file,
then
the
ci
build
of
the
default
branch
would
pick
up
those
changes.
A
Because
the
the
the
thing
is
that
you
could
break
the
the
builds
for
if
the
approver
read
the
jenkins
file,
but
don't
understand
fully
the
consequence
of
the
change
and
merge
it,
because
the
green
will
be
built
with
the
jenkins
file
with
the
old
version
and
not
the
new
one
of
the
pull
request
once
merged.
It
could
break
everything
and
you
will
need
to
do
subsequent
pull
requests,
meaning
the.
C
That's
that's
what
I
meant
in
the
bit
at
the
beginning.
I
would
expect
the
pipeline
library
to
be
is
easy
enough
to
use
that
you
don't
really
need
ci
for
changes
to
the
pipeline,
because
there
shouldn't
be
any
options
that
are
required
that
need
ci
other
than
perhaps
can
does
this
plug
and
build
on
windows
or
not.
I
strongly.
A
D
The
pull
request
triggering
this
issue
is
on
the
variant
plugin,
where
the
jenkins
version
was
in
the
jenkins
file
and
it's
so
part
of
the
technicality
you
wanted
to
to
replace
to
change
for
the
bomb
so
variant
plug-in.
So
I
prepared
him
by
replaying
is
built
with
the
zinc
inside
change
in
it
directly.
Okay,.
A
I
feel
like
that.
We
don't
have
an
answer
right
now
that
should
be
discussed
on
the
mailing
list,
not
that
I
don't
want
to
have
that
discussion
right
now.
That's
really
instructive,
but
yeah.
It's
not
clear
the
real
needs
there.
I
agree
with
daniel,
but
I
don't
see
an
easy
solution
for
me.
It's
it's
the
block,
a
blocker
point
of
the
trust
model.
The
trust
model
is
required
and
we
need
it,
but
we
don't
have
an
easy
solution
for
that.
A
C
And
even
if
that
he's
a
maintainer
of
at
least
one
jenkins
plugin,
which
means
he
can
push
whichever
branches
of
the
subject
plug-in
to
his
report
at
any
other
branch
ref
and
then
just
do
his
changes
and
validate
them
there.
He
doesn't
need
commit
access
to
the
specific
plugin
repo
to
test
changes
to
the
pipeline.
C
Understand
so
git
as
a
distributed
version
control
system,
you
can
push
branches
of
one
repo
to
another
repo,
yes
right,
yep,
so
he's
the
maintainer
of
at
least
one
jenkins
plugin.
Let's
call
it
the
chatterson.
Oh,
oh,
that's
tricky!
So
so
he
can
push
the
master
branch
of
varian
plugin
to
the
not
master
branch
of
jetterson
plugin
and
see
what
happens
to
to
the
ci
build
there
and
since.
B
C
A
C
A
Do
you
mind
communicating
that
to
him
either
on
that?
I
think
the
issue
should
be
okay,
if
we
close
it
afterwards
or
do
you
feel
keeping
that
private.
C
I
can
I
can
write
something
up
and
maybe
I
misunderstood
the
use
case
anyway.
So
that's
also
another
possibility.
B
I
object
if
we
ever
use
that
I
think
I'm
delighted
that
a
security
person
joined
us
and
shared
something
that
is
really
a
novel
technique.
Copying
repository
a
into
repository
b
sounds
like
a
horrible
thing
to
do
to
that
git
repository,
but
yes,
it
is
allowed.
I
I
I
I
mean
thoroughly
impressed.
That's
a
brilliant
technique.
A
For
me,
it's
also
an
indicator
that
if
jenkins
pipeline
would
be
portable,
then
we
wouldn't
have
that
issue,
because
anyone
will
be
able
to
spin
up
quickly
at
jenkins
instance,
run
it
to
test
the
change
and
then
move
it.
That's
not
the
reality
of
jenkins
pipelines,
because
you
need
so
much
plugins
and
configuration
and
stuff
that
it's
not
not
possible.
A
Okay,
that
was
the
sorry
the
issue
opened
by
no.
Let's
move
on
next
topic:
one
container
raised
java,
17
windows
agent,
I've
added
that
to
the
release,
so
airway
is
currently
working
on
using
packer
to
not
only
build
the
virtual
machine
template
for
the
agent
to
use
on
cigo
another
controller,
but
now
we
want
to
start
using
the
same
image
and
same
content
also
for
container.
A
So
whether
you
are
running
on
a
kubernetes
agent
or
a
virtual
machine
on
ec2,
you
would
have
the
same
tools
with
the
same
version
on
the
same
location
with
the
same
behavior,
so
that
one
being
able
to
provide
gdec,
17
windows
agent
is
part
of
that
area.
The
reason
is
because,
on
the
virtual
machine
we
already
have
the
free
gdk
installed
and
maintained
for
virtual
machines.
A
So,
instead
of
having
to
deal
with
the
world
dog
jenkins,
ci
docker
windows
agent,
is
it
car
or
nano
server
or
whatever
or
2019,
or
that's
a
nightmare?
So,
let's
focus
on
the
infra
only
so
we
have
our
own
dependency
and
with
the
that
work
we
should
be
able
to
have
one
location
to
to
change
the
free
version,
and
then
it
work
for
windows
and
linux
the
same
way.
A
A
A
D
A
We
to
cover
that
one.
If
you
don't
have
time,
I
will
take
over
gavin
will
want
to
publish
npm
package
sounds
like
we
need
to
contact
tom
finley,
at
least
for
one
of
the
npm
name
spaces
for
jenkins.
A
I
have
no
idea
of
all
of
this
work,
but
we
need
to
take
over
at
least
one
because
none
of
them
are
managed
by
us.
As
far
as
I
understand,
and
I
assume
that
gavin
checked
with
the
board,
there
has
been
someone
who
is
using
jenkins
the
string
jenkins,
namespace
reference
on
gavin
issue.
I'm
not
sure.
If
it's
do,
you
think
mark
we
could
contact
npm
and
say
hey
hello.
We
are
the
jenkins
infrared
and
we
can
prove
prove
it
by.
A
I
I'm
just
asking
questions
because
I
don't
know:
oh
any
of
this
work.
A
So,
okay,
is
it
okay,
if
you
synchronize
with
gavin
on
that
area,
and
I
will
and
stefan-
and
I
will
take
over
next
week-
if
you
didn't
have
any
answer,
but
the
goal
will
be
to
contact
npm
repo
for
for
ticking
this.
I
don't
think
there
should
be
an
issue
with
tom.
We
just
have
to
get
his
current
email,
but
by
linkedin
or
twitter.
That
should
be
easy.
If
we
don't
already
have
it
on
the
mailing
list.
A
A
A
way
to
follow
up
next
one
infras
are
mentioning
expired,
datadog
api
key,
so
the
goal
is
to
have
the
private
controller,
to
send
metrics
to
collect
metrics
to
datadog,
which
is
a
private
system.
By
default.
A
A
Okay,
so
it's
only
for
infrasi.
We
haven't
fixed
that
behavior.
On
the
other
controllers,
there
will
be
the
next,
but
let's
fix
this
one.
The
subtlety
here
is
that
infrastr
is
running
on
another
kubernetes
cluster
then
release
ca,
which
means
we
add
to
first
install
datadog,
so
we
have
to
control
the
data.
Dog
is
working
for
the
wall
cluster
before
being
able
to
be
sure
that
it's
an
issue
with
controller
overview,
so
whip
to
be
diagnosed.
A
Next
issue:
unless
there
is
a
question
about
that,
the
metric
for
infrasi
pupet
upgrade
campaign
to
latest
six
dot
x,
so
I've
covered
I'm
ready
to
update
to
the
latest
version.
The
puppet
master
agents
are
all
fine.
We
are
able
to
test
it
with
backgrounds.
We
have
removed
most
of
the
security
alert
on
the
github
public
repo.
Everything
should
be
fine.
I
haven't
seen
any
blocker
so
now,
I'm
holding
on
that
one.
A
I
will
finish
it
after
my
my
holidays,
but
that
should
be
only
a
few
minor
version
jumps
it's
just
that
puppet
is
a
mess.
The
version
doesn't
map
at
all,
it's
clearly
worse
than
the
jenkins
docker
images
in
term
of
version
scheme,
and
that's
not
a
compliment
to
ourselves
from
me,
but
everything
is
for
many
thanks
stefano
nerve
for
helping
me
on
all
these
areas
and
testing
that
we
are
improving
our
property
knowledge
there.
A
Just
a
note,
I've
opened
an
issue
which
is
not
there,
which
is
upgrading
puppets
to
seven
dot.
Whatever
the
upgrade
to
puppet
7
is
a
blocker
for
us
before
being
able
to
upgrade
the
virtual
machine
to
ubuntu
222,
because
pooped
6
is
not
supported,
same
thing
for
using
pupet
on
ppc
or
cpu
z
or
whatever
exotic
cpu
puppet
6
has
world
behavior
it's
okay
for
intel
and
irem.
But
it's
word
for
the
rest.
We
we
need
to
move
to
puppet
seven.
A
On
hold
for
early
days,
download
slash
latest
directory
out
of
dates,
I'm
so
happy
to
have
you
there
daniel,
because
I
I
will
need
help
in
the
upcoming
weeks
on
this
one.
A
The
latest
directory
is
a
sim
link
on
most
of
the
original
virtual
machine
on
updates
ci
an
update,
chankin
sayo.
The
machine
with
the
package
is
on
the
update
center.
A
A
So
then,
get
jenkins
io
as
that
as
your
bucket
file,
where
all
the
files
are
put
it
check
it.
It
gets
the
signature
and
then
it's
able
to
determine
which
mirror
is
providing
that
file
and
the
process
of
synchronizing
uses
something
named
bluebig
cipher,
which
is
a
command
line
by
azure
to
it's
a
kind
of
air
sync,
but
for
the
azure
file
storage,
and
it
sounds
like
that.
A
I'm
not
sure
if
anyone
has
the
knowledge
or
if
we
should
try
that
require
updating
the
synchronization
script,
which
is
quite
the
amount
of
work,
because
we
need
to
add
a
step
that
will
cover
all
the
latest
sim
links
and
unsure
and
resolve
them
and
force
upload
them
right
now
the
synchronization
says:
don't
overwrite
something
that
you
already
sent.
I
will
delete
them
first,.
A
B
Yeah,
I'm
I'm
hesitant
to
change
that.
I'd
rather
accept
that
this
latest
director
is
out
of
date
than
than
risk
deletion,
so
but
damian,
if
it's
okay,
let's
take
it
up
later,
I
think
dropping
it
from
this
this
the
work,
the
planned
work
is
fine
with
me,
because
it's
just
not
that
crucial.
An
issue.
C
So
especially
so
what
we
did
a
while
back
is,
I
remember
the
download
page
on
jenkins
io
used
to
refer
to
the
latest
link.
C
The
problem
with
that
is
that
the
page,
as
rendered
explicitly
stated
what
the
last
version
was,
and
so
if
the
site
hadn't
been
regenerated,
but
the
latest
link
was
updated
to
a
new
release
that
just
came
out.
There
was
a
discrepancy
between
what
jenkins
I
o
slash
download,
said
and
what
you
were
actually
downloading.
C
So
what
we
did
was
the
url.
This
links
to
is
now
a
specific
version,
as
you
can
see
on
the
bottom
there,
and
this
was
especially
important
once
we
added
the
shard
check
sum,
because
otherwise
people
in
that
case
wouldn't
just
get
a
newer
version
than
they
were
expecting,
but
checksum
also
obviously
wouldn't
match.
C
A
Absolutely
I've
tried
an
experimental
process,
it's
with
only
checking
the
latest
and
uploading
with
override
only
the
latest
directories,
but
it
takes
some
times
so
it's
additional
times
before,
having
everything
in
sync.
That's
why
I
really
love
the
idea
of
do
we
really
need
the
latest.
A
A
C
A
Yep,
fair,
that
that's
absolutely
fair
point
and
we
could
absolutely
blacklist
the
latest
link
from
get
jenkins
sayo
once
it
doesn't
stop
having
the
directory
latest
for
each.
Then
it
should
not
serve
to
mirrors
which
mean
what
you
just
said.
People
are
really
wrong
if
they
are
using
a
direct
link
to
a
specific
mirror.
A
Cool,
so
let's
all
down
on
this
one
for
sometimes
thanks
for
the
details.
Next
one
enable
development
integration
in
jira
postponing
to
september.
A
That's
too
much,
I
don't
have
access
to
the
jenkins
cia,
so
that
mean
back
and
forth
with
people
with
this
permissions
that
require
old
token,
that
it's
a
world
permission
issue.
We
doesn't
support
github
app,
so
I
propose
that
we
do
it
once
we
have
everyone
on
board,
I'm
a
bit
worried
by
this
one.
Maybe
it
could
be
just
jenkins
ci,
but
that
requires
clearly
more
discussion.
A
The
request
is
clearly
legit
and
will
help
a
lot.
The
developers
and
contributors
james
clearly
understated
that
and
that
that
makes
sense.
But
right
now
I
don't
see
any
proactive
action
that
we
could
do,
because
that
requires
administration
right
on
both
jira
and
jenkins
cia
guitar
organization.
Unless
I
missed
something,
so
you
assume
that
tim
and
daniel
have
these
rights,
maybe
mark
I
don't
have.
C
B
Yeah,
that's
that's
a
so
daniel.
I
think
you're
you're,
assuming
exp
assuming
knowledge
from
others
that
they
may
not
have.
That
is
that
jira
has
announced
the
end
of
hosted
jira
instances
that
everything
jira
does
will
be
cloud
and,
and
so
we
see
that
the
end
of
linux
foundation's
hosting
of
algeria
instance
unless
jira
revises
their
their
stance.
Did
I
state
it
correctly
daniel.
C
Right
and
I
don't
think
atlassian
will
change
their
opinion,
they're
working
on
making
a
cloud
jira
work
with
more
user
accounts,
which
is
the
major
problem.
That
was
a
short
quick
discussion
on
the
dev
list
recently,
where
this
came
up
again
and
I
think
atlassian
are
up
to
50
000
users.
They
support
with
plans
to
go
up
to
100,
000
or
so,
and
I
think
we
have
130
000
users
in
our
user
directory.
Of
course,
the
vast
majority
of
those
are
unused
or
haven't
been
used
in
forever.
C
So
with
some
cleanup
we
might
be
able
to
migrate
there,
of
course,
assuming
that
lesion
sponsors
this,
because
otherwise
it
will
be
a
little
expensive.
So,
but
with
with
the
eol
announced,
I
think
for
early
2024.
C
I
would
be
hesitant
to
spend
a
lot
of
time
on
changes
to
our
hosted
jira,
especially
if
those
changes
would
potentially
make
it
more
difficult
to
migrate
off
afterwards,
because
we've
adapted
workflows
and
such
so
if
this
is
easy
to
do
sure
if
this
requires
work
from
us,
maybe
not
right.
B
A
Okay,
thanks
for
the
precision
I
I
I
took
the
backed
off
saying:
okay,
they
should
keep
still
hosted
so
yeah.
They
are
definitely
going
full
club.
Oh
crap,
that's
not
a
fun
one,
okay!
So
no
action
for
us
right
now.
That
will
be
a
wider
discussion,
a
community-wide
discussion,
then.
I
assume
thanks
next
issue.
Is
the
cpu
z
the
agent
mark?
I
assume
you
didn't
add
much
time
on
this.
One.
B
A
Okay,
before
removing
from
the
milestone,
can
I
ask
you
to
share
using
the
encrypted
subs
directory
the
credential
to
access
it
with
a
technical
user
that
can
sudo.
The
goal,
as
I
said
two
weeks
ago,
is
for
us
to
be
able
to
try
compiling
the
ruby
gem
for
puppets.
So
we
can
see
if
we
can
have
a
running
pattern
from
that
machine
which
will
solve
a
lot
of
issues,
because
we
already
have
puppet
managing
a
few
agents
so
that
will
automatically
install
everything
needed.
A
I
think
we've
already
written
so
we
otherwise
I
need
the
big
one
migrating
updates
jenkins
io,
so
the
update
center
on
another
cloud
for
bandwidth
reasons,
because
that
cost
a
lot
so
right
now
we
are
working
on
the
puppet
configurations
defended
the
heavy
loads.
A
We
have
reached
a
point
where
we
are
able
to
deploy,
configure,
apache
and
prepare
everything.
The
next
step
for
stefan
before
going
in
holidays,
will
be
to
update
the
all
the
script
that
we
use
for
the
releases
for
generating
the
update
json,
so
it
uploaded
also
to
the
new
virtual
machine
not
only
to
the
current
one
and
then
we'll
put
an
old
for
the
early
days
to
continue
that
end
of
august,
because
that's
a
sensitive
topic,
but
that's
almost
4k
per
month
of
bandwidth.
A
A
Nope
new
important
elements-
I
got
some
so
there's
been
a
topic
started
earlier
today,
I
think,
or
yesterday
about
cleanup
proposal
of
communication
channels
before
I
have
so
there
might
be
advices,
but
we
are.
I
want
to
restrict
the
discussion
only
on
the
jenkins
in
irc
channel,
so
only
the
channel
that
we
use
to
discuss.
I'm
not
mentioning
the
one
with
notification
connected
to
the
bot.
Only
the
one
we
use
there.
A
C
Maybe
that's
just
me,
but
I
probably
wouldn't
open
a
new
topic
just
to
ask
a
dumbass
question
or
what
I
suspect
might
be
a
dumbass
question
in
either
of
those
and
or
raise
an
issue
on
github.
C
C
Understand
correct
yeah,
so
sorry
I
I
understood
github
as
in
github
issues,.
A
A
For
me,
that
will
be
a
huge
improvement
moving
from
irc
to
matrix
guitar,
because
I've
continued
during
the
past
eight
years,
exactly
182
percent,
that
I've
met
that
refused
to
ask
a
question
to
the
jenkins
infrastructure
project
because
they
didn't
know
how
to
make
that
erc
thing
works.
There's
no
history,
they
didn't
know
whatever
and
I
pers
it
personally
took
me
three
years.
A
So
I
know
I'm
lazy,
I'm
not
the
best
expert,
but
honestly
irc
has
been
a
pain
during
the
last
decades
and
the
arguments
about
the
freedom
of
using
and
being
able
to
take
over.
That
was
a
really
important
and
foundational
argument,
but
since
the
takeover
by
freenod
last
year
or
two
years
ago,
all
the
mess
that
made
us
to
move
to
liberat
chat
for
supporting
the
room.
A
Now
I
don't
really
see
unless
we
host
it
ourself.
I
don't
really
see
a
solution.
So,
for
me,
guitar
is
the
let's
say
it's
commercial,
it's
running
on
someone
else's
machine,
so
we
are
still
at
risk
of
someone
being
able
to
take
over
that
series
that
still
exists,
but
at
least
it's
really
easy
to
use.
It
provide
multiple
the
barrier
before
being
able
to
post
a
message
is
close
to
zero.
A
You
have
seven
way
to
authenticate
together
on
one
click,
so
I
don't
mind
switching
from
irc
to
guitar
if
it
helps
bringing
currency,
but
I
agree
with
daniel.
I
don't
see
the
point
of
having
a
discourse
thread
channel
room.
I
don't
know
the
wording
on.
I
don't
see
the
point
right
now
because
of
what
daniel
said,
but
there
might
be
use
cases.
I
don't
know,
maybe
eventually
for
announcements.
A
A
A
A
Something
they
didn't
put
on
the
clean
up
proposal.
It's
the
mailing
list
for
jenkins
infrared,
the
public
one.
A
So
I'm
thinking
about
I'm
taking
talking
about
the
jenkins
dash
infrared
google
groups
right.
B
Somebody
else
must
be
processing
and
I'm
used
to
processing
others
I've.
I
don't
find
the
mailing
list
especially
helpful
for
me,
but
it's
low
volume
so.
C
A
C
No
opinion,
I
don't
think
I
use
it
enough
to
really
have
an
opinion
about
that.
A
A
A
If
we
also
ask
that
question
in
the
mailing
list,
should
we
keep
the
mailing
list
and
see
feedbacks
from
people,
and
if
we
don't
here
for
strong
feedback,
we
could
just
stop
using
it
and
archive
it,
which
means
we
keep
the
private
one
and
communication
will
be
either
on
guitar
for
real-time
communication
and
eventually
we
could
think
about
this
course,
whatever
room,
if
it's,
if
it
solve
a
problem.
Otherwise
not
it
asynchronous.
Communication
already
happened
on
the
help
desk
github
issue
so,
and
here
sounds
good
for
everyone.
D
A
New
topics-
I
don't
know
there-
are
a
set
of
new
topics.
If
it's
okay
for
everyone,
I
won't
raise
them,
given
that
you
already
have
enough
work
there.
The
only
one
to
have
an
eye
on
is
the
gdk
update
for
11
and
17..
A
That
might
or
might
not
happen
in
the
opening
days.
It
already
happened,
and
it's
already
available
on
the
virtual
machine
agent
template.
It
has
been
automatically
picked,
which
means
windows,
linux
on
intel
and
iran.
A
If
it's
okay
for
everyone,
I
will
try
to
split
the
update
process
between
these
two
exotics
platform
and
the
others
they
will
have.
They
could
eventually
have
a
minor
different
version
gdk,
but
they
are
not
connected
to
the
controller
and
not
not
used.
A
A
We
need
to
start
working
and
updating
this
on
the
jenkins
official
images,
either
controller
and
agents
on
the
agents
because
we
used
we
depend
on
this
element
for
our
weekly
builds
for
the
core.
So
that's
the
reason
why
we
use
an
older
version
because
we
point
to
an
older
remoting
version
that
has
been
accelerated
by
whatever
they
checked
yesterday
discovered
yesterday,
with
the
change
from
semantic
versioning
to
the
new.
A
Whatever
long
version
pattern
that
we
use
for
plugins,
the
remoting
component
is
also
following
this
one
and
our
update
process
for
the
date
sealer
is
configured
to
monitor
for
semantic
versions.
So
it's
not
able
to
pick
new
version
from
now,
so
we
need
to
move
it
to
use
latest
version
that
should
allow
us
to
update
jenkins
ci
infra
packaging.
A
A
So
I
we
should
urge
to
update
that
to
avoid
that
kind
of
world
support
issues
from
end
users.
At
least.
We
are
aware
that
could
happen.
The
infrastructure
jenkins
infrastructure
is
not
concerned
by
that
problem,
though,
because
all
our
machines
are
still
running
on
ubuntu
18,
which
is
still
lts,
supported
and
used
sequel
version
one.
So
our
current
gdk11
is
okay.
A
A
A
No
just
a
warm
welcome
and
thank
you
to
everyone.
I'm
really
happy
to
work
with
all
of
you
and
I'm
really
really
happy
of
the
interaction
and
all
the
things
I've
learned.
I'm
continuously
learning.
So
now
I'm
gonna
go
to
holidays
and
I
hope
you
will
have
a
nice
end
of
week
nice
out
weekend
and
see
you
in
one
week
or
two
weeks,
depending
on
who
is
speaking,
I'm
now
stopping
the
recordings
here.