►
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
we
found
out
why
things
are
right.
That
is
perfectly
fine.
I
wanted
to
quickly
discuss
something
else.
If
I
find
it
again,
this
was
a
bigger
pull
request
on
the
on
the
up
timer.
A
No,
I
don't
find
it
again.
Let
me
check.
A
So
this
was
alright.
This
was
quite
old
from
july,
so
here's
someone
who
is
this
jonathan
aristisabal
updated
everything
to
go
mod
with
go
1.18.
So
it's
a
huge
change.
A
I
did
the
quick
verification
so
go
build
graph
and
mod
verify
everything
works,
but
I
have
not
yet
tested
this
in
our
productive
pipelines
right.
Is
there
any
objection
to
merging
this
or.
B
Yeah
I'm
trying
to
remember,
I
don't
know
whether
we
cut
releases
of
this
or
whether
it
just
rebuilds
from
head
of
main
I'd,
have
to
look
at
the
the
docker
file
to
see
what
it's
doing.
B
A
Good
now.
A
We
have
or
successfully
migrated
most
of
our
pipelines
to
the
new
concourse.
I
am
I'm
sorry
last
week
or
this
week
I
scaled
out
the
course
a
little
bit.
We
just
had
two
workers.
C
A
A
Yeah,
this
is
not
what
we
want
to
have
okay,
so
we
can
scale
up
this
and
yeah.
We
also
have
to
to
update
the
whole
concourse
project
because
it's
migrated
away
from
quark
secrets
to
kabul,
secrets
jen,
okay,
good.
This
will
be
our
job
and
it's
not
so
urgent,
but
only
then
we
will
get
the
new
concourse
version,
yeah
good.
A
We
just
went
through
everything.
Cats
is
failing
because
we
need
a
new
receive
deployment
release
and
in
cf
deployment.
Basically,
the
bush
disaster
recovery
backup
result,
backup,
restore
tests
are
failing,
we
will
analyze
this
and
our
goal
is
to
cut
a
new
cf
deployment
release
still
on
bionic
on
this
pipeline.
So
to
get
the
screen
until
the
end-
and
I
would
say
then
the
migration
is
done.
C
B
A
C
C
C
C
Nothing
else,
there's
there's.
Definitely
it's
all
in
the
main
group,
because
there
is
a
lot
more
pipelines
than
that.
Don't
know
why
what
the
are.
B
A
B
Okay,
again
very
easy:
it's
just
rebuilding
the.
I
think
these
are
the
runtime
ci
images.
C
Oh,
the
relent
pipeline
permissions
must
have
been
changed.
The
the
relevant
concourse
permissions
must
have
been
changed
ahead
of
the
the
the
like
team,
the
github
team,
destruction
event.
C
We,
it
might
have
been
me,
I
don't
remember
anymore,
but
the
the
teams
that
it's
the
only
the
only
teams
allowed
on
it
are
are
our
pivotal
teams
now.
So
I
don't
know
if
there's
a
we've,
probably
never
added
the
working
group
team
to
it.
B
D
D
A
Okay
good,
so
I
have
cf
deployment,
conquest
tasks
uptimer
and
build
docker
images,
good
yeah.
Well,
so
whenever
those
are
visible
again
for
us
accessible
again,
then
we
can
move
them.
A
C
A
Okay
yeah.
So
then
the
next.
A
Bigger
topic
is
the
switch
to
jammy
stem
cell,
so
the
the
overall
idea
is
yeah
somewhat
similar
to
the
switch
from
trusty
oxeneal
to
bionic.
So
we
more
or
less
do
a
hard
up
major
upgrade
in
cf
deployment.
A
B
D
Need
it
yeah
at
the
moment
all
our
internal
landscapes
are
still
on
bionic,
but
we
tested
that
they
work
on
gemmy
and
we
would
maybe
even
faster
switch
over
to
gemmy
than
the
cf
deployment
pipelines.
It
depends
a
bit
when
the
next
version
comes
out,
so
we
don't
need
to
release
the
bionic
validation.
I
mean
we
could
do
just
a
hard
switch
and
if
somebody
complains
we
we
can
talk.
D
I
know
a
little
bit
from
the
background
that
there
might
be
questions
like
hardened
stem
cell
and
and
flips
compliancy
etc,
which
is
only
I
don't
know
based
on
bionic.
So
sooner
or
later
I
am
sure
that,
for
instance,
stefan
clevens
will
ask
just
for
a
statement
from
the
working
group.
Do
you
support
bionic?
Yes
or
no?
And
I
mean
it's
a
very
valid
answer
to
say
no,
we
stopped
which
only
support
the
jammy
stem
cells
and
if
something
should
be
changed,
then
yeah
it
needs
to
be
decided
and,
of
course,
resource
allocation.
D
Blah
blah
blah
is
unnecessary,
but
the
mechanics
here
supports
one
stem
cell
and
this
one
is
going
to
change.
B
Yeah,
I
think
that
that's
that's
fair,
because
I,
when
we
switched
over
to
bionic
from
from
xenial,
we
didn't
get
any
questions
any
comments
from
anybody
that
everyone
was
perfectly
fine.
D
I
remember
that
we
were
actually
using
bionic
already
at
sap
for
one
or
two
years
and
while
the
cf
deployment
validation
worked
still
on
xenia
and
we
had
no
issues,
so
it's
the
abstraction
is
pretty
far
away
and
yeah.
But
you
never
know
this
time.
We
are,
I
think,
pretty
close.
D
That's
something
we
should
do.
We
should
announce
with
also
announce
that
there's
a
new
major
cf
deployment
version
version,
22
that
comes
with
jammy
and
we
stop
the
support
of
bionic.
We
have
such
an
official
announcement
from
the
working
group.
I
think
that's
good,
and
then
we
see
on
the
reactions
if
yeah
and
then
can
ask
also
okay,
you
need
bionic.
B
D
D
It's
just
three
red
boxes
here,
right,
wow,
sure.
D
C
B
Choosing
jammy
appropriately,
I'm
trying
to
recall
what
we
did
for
bionic
ahead
of
time,
but
there
are
some
places
where
tooling
looks
at
the
stem
cell
and
it
would,
you
know,
just
make
sure
that
it
handles
jeremy
and
then
yes,
it's
just
a
case
of
updating
that
pipeline
to
look
at
the
jammy
stem
cells
on
bosch
io
instead
of
ionic.
A
In
the
change
in
the
coding
is,
this
is
rather
the
easy
task
I
mean.
I've
proposed
now
go
away.
A
From
your
your
pipeline
templating,
this
is
already
quite
nice.
You
change
two
lines
and
re-run
the
templating,
and
there
you
are
okay.
Now,
of
course,
we
will
then
have
to
make
this
deploy
this
on
concourse
and
see
if
it's
green,
okay,
good.
A
Yeah,
so
that
would
be
roughly
the
jammy
road
map
yeah,
okay,
so
yeah
we
have
already
sorted
out
some
the
the
details
with
carson,
so
yeah.
From
from
my
side,
I
think
we
have
enough
input
to
work
until
the
next
working
group
meeting.