►
From YouTube: 2020 12 01 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
Topics:
I've
got
on
the
agenda
for
today
include
a
new
jenkins
infrastructure
contributor
latest
status
on
azure
storage,
outage
github,
publishing
of
the
release
war
files
from
tim.
If
he's
available,
weekly
release
status,
lts
release,
prep
windows,
docker
image
status
from
gareth,
if
you're,
okay
with
that
gareth
and
then
jira
migration
topics
of
any
any
other
items
that
should
be
put
on
our
agenda
for.
A
A
C
A
A
A
A
B
A
Use
an
interesting
idea:
yeah,
I
don't
know
I've.
That's
that's
a
very
good
idea.
I
proposed
let's
bring
that
question
to
next
week's
session,
or
maybe
we
bring
it
as
a
mailing
list
topic,
because
I
think
it's
a
good
idea.
We
we
know
that
we'd
switched
and
we
know
that
the
switch
has
been
operational
now
for
one
or
two
weeks.
B
B
A
B
A
B
Yeah,
I'm
not
sure
I
wouldn't
rely
on
that
too
much,
because
it
doesn't
mean
that
we
need
to
use
activity
and
statistics
are
really
estimated
right.
Okay,
our
metric
would
be
rather
download
or
something
like
that.
Not
absolute
cost.
A
B
I
got
that
so
many
people
here
downloading
producers
right
right.
A
Okay,
next
topic
was
weekly
release.
2.269
has
been
delivered,
the
build
completed
successfully
packaged
successfully
and
a
new
edition
from
tim
jacom,
the
the
war,
the
dev
file,
the
rpm
file
and
the
msi
were
uploaded
to
github,
so
they
are
now
visible
there
as
part
of
the
the
release
as
part
of
the
yeah,
the
github
action
base
or
the
github
release.
A
A
Okay
now,
in
terms
of
the
that
2.269
release,
the
change
log
has
been
merged
is
confirmed,
visible.
I
haven't
yet
confirmed
the
data
dog
checks
are
passing,
but
I
have
confirmed
that
the
exception
test
installs
for
debian
and
red
hat
are
passing.
So
as
far
as
I
can
tell,
the
weekly
release
was
successful
and
all
parts
of
it
ran
as
expected.
A
And
that
will
be,
if
I
recall
correctly,
that
is
started
interactively
so
launched
interactively
not
on
a
clock
and
we
then
watch
to
the
the
release
plan
to
confirm
that
it
is.
B
B
A
A
Right
right
and
my
assumption,
given
olivier's
current
current
status,
is
that
he's
he's
on
holiday
sort
of,
and
so
I
assume
that
mark
will
that
I
will
push
the
push
the
the
launch
button
early
tomorrow.
My
day.
B
Yeah,
it
just
gives
us
a
bit
more
time
the
day
but
yeah
since
the
us
time
zone
shouldn't
be
too
much
different.
A
A
Wonderful,
the
release
profile
is
ready,
damian
and
I
reviewed
it
today
and
merged
it,
and
the
change
log
and
upgrade
guide
pr
is
in
review,
but
I
believe
is
ready
to
merge.
I
would
love
to
have
if
you've
got
time.
Oleg
one
more
check
that
I
addressed
all
of
your
concerns.
A
B
A
B
So
in
order
to
put
ssh
cli
mode,
you
will
need
to
install
a
plugin
unless
it's
loaded
as
a
detached
plugin
from
my
understanding
that
it
would
be
still
detached
like
begin
in
the
very
beginning,
but
eventually
it
might
input
some
use
cases
configuration
management
tools
which
try
to
make
it
over
cli,
I'm
not
sure
whether
any
of
them
use
the
ssh.
B
D
Yeah
not
much
to
update
on
this
since
last
week.
The
prs
for
the
jenkins
docker
builds
are
waiting
to
be
merged,
but
I
think
we
were
gonna
hold
off
until
after
this
lts
released
had
gone
out.
A
D
A
Week,
all
right
next
topic,
we
wanted
to
one
of
the
hosts
with
tim
tim
here
oleg.
Would
you
like
to
defer
this
till
next
week?
Do
you
want
to
just
go
ahead
and
make
some
notes
on
it?
What
are
you,
what
are
you?
What
were
you?
Is
it
helpful,
without
tim
here
best
that
we
wait
till
he's
here?
B
All
right
so
yeah
I
can
summarize
how
it
works,
but
it's
basically
just
github
action
which
triggers
on
the
release
and
publishes
the
release
assets.
Every
time
you
cut
the
release
on
github
releases,
so
we
have
a
release
raptor,
which
prepares
the
change
log
graph,
and
once
you
cut
a
release
using
this
change
log
draft
the
another
github
action
will
go
and
automatically
find
release
keys
and
attach.
B
When
you
pop
the
release,
you
need
to
be
sure
that
the
packaging
stage
has
finished
so
that
you
have
artifacts
in
place
and
artifactory
you're
doing
linkedin
publishing.
Well,
you
need
publishing
stage
for
that,
because
it
also
publishes
the
installer
artifacts,
but
once
the
entire
pipeline
is
completed,
then
you
can
just
cut
the
release
and
everything
will
happen
automatically,
so
what
it
means
that
we
still
have
action
item
from
the
backlog
of
automatic
change,
lock,
publishing
so
right
now
we
have
tools
for
that.
B
D
B
B
A
Good
thank
you.
Now
there
was
some
discussion
about
how
to
how
to
the
disabled
distribution
of
a
release.
As
far
as
I
could
tell,
the
mailing
list
seemed
to
have
been
satisfied
with
that
disabled
process.
Any
objection,
any
exceptions
to
that
or
places
where
people
are
worried.
Oh,
we
need
a
way
to
hide
a
release.
Sometime
after
it
has
been
delivered.
A
Damian
had
pointed
out
that
there
might
be
a
concern
about
storage
limits,
but
did
the
research
and
github
the
limits?
Don't
look
like
they'll
affect
us
at
all?
They
won't.
Let
us
do
more
than
a
two
gig
file,
not
a
problem
and
no
limit,
apparently
on
bandwidth
and
as
far
as
I
can
tell
even
on
number
of
files,
so
I
think
we're
fine.
A
B
But
again,
if
we
think
about
the
release
process,
we
should
rather
at
least
artifacts
from
jenkins
pipelines.
Now
we
have
continuous
delivery
infrastructure
for
some
plugins,
so
the
recent
jeff
by
daniel
and
jason,
and
we
can
probably
integrated
there,
but
if
you
just
want
to
have
hpi
file
published
on
my
github
use
changelog.
Of
course
you
can
just
follow
the.
B
A
D
A
B
Yeah,
I
just
want
to
say
that
the
email
computation
injector
is
quite
complicated
because
it's
also
a
project
configuration.
So
unless
you
go
and
check
everything,
then
you
can
be
100
sure.