►
From YouTube: Support Release Review - 12.7
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).
B
B
C
D
D
Okay,
so
basically,
this
feature
introduces
a
new
status
of
for
pipelines,
waiting
status
and
it
prevents
running
multiple
pipelines
for
for
the
same
environment.
So
let
me
show
you
how
it
works
on
a
very
simple
example:
so
I
have
a
project
here
and
it's
right
now,
it's
configured
without
the
resource
group.
So
it's
just
a
super
simple
dining
project
that
waits
for
50
seconds,
till
the
completion
and
I'm
writing
it
on
Chevron,
in
order
to
be
as
quick
as
possible.
So.
D
Okay,
so
I'll
just
make
some
change
here
and
it's
important
to
note
that
right
now,
I
have
concurrency
set
to
like
something
that
is
not
equal
to
one.
So
because
if
we
set
the
value
to
1
on
the
run
aside,
then
it
will
be
just
so
there
we'll
be
a
limit
of
one
job.
So
quite
now
the
concurrency
is
settled
so,
okay
right
now,
I
am
changed.
D
F
So
like,
how
is
it
different
from
parallel
pipe
lines
like
parallel
pipe
lines,
you
also
have
the
same
thing
right,
like
one
rose,
has
to
wait
for
the
other
one.
When
we're
running
federal
pipe
lines,
is
it
like?
If
one
is
it
something
similar
like
I,
am
waiting
for
one
out
finishing
the
pipeline
of
one
pipe
line,
one
and
whatever
the
output
we
can
use
in
pipeline?
Is
it
something
like
that.
D
F
D
D
It
can
be
judged
by
our
documentation,
so
this
recommendations
that
is
mentioned
in
the
bullets
review
dock.
As
a
use
case.
We
can
think
of
the
point
physical
devices,
for
example,
so
it
says
if
you
have
more
than
one
physical
device
and
each
one
can
be
deployed
to,
but
there
can
be
only
one
deployment
per
device.
D
D
F
D
So
because
at
first
I
was
I
was
trying
to
test
it
and
I
didn't
realize
that
I
had
previously
set
against
one
on
my
Runner
and
I
was
like
trying
to
do
it
and
they
didn't
work
at
all.
So
I
was
confused.
Then
I
figure
out
that
I
had
said
to
one
after
I
changed
it
to
hi.
Earlier
it's
started
working
started,
showing
this
wait
in
status.
E
F
D
D
G
G
E
E
D
F
D
F
B
Okay,
Cooper,
okay,
so
I
think
this
one
because
mostly
I,
remember
quite
a
lot
of
customer
tickets,
which
happened
when
their
box
was
released
automatically
and
these
defaulted
to
on
so
remember,
we
got
quite
a
few
customers
in
I.
Don't
want
this
debt
I
don't
want
this
pipeline
because
it
doesn't
look
pretty
and
by
default
whenever
they
create
a
project,
they
got
a
faulty
debt
and
pipe
pipeline.
B
So
that's
what
caught
my
attention,
though,
so
the
documentation
link
it's
restricted
to
wash
only-
and
the
note
here
is
that
interesting
I'll
come
back
to
that
later,
but
as
supposedly
will
delete
all
related
objects
bills
logs
after
tax
triggers,
which
is
cool
okay.
So
let's
do
them.
So
here
we
have
a
project
with
just
a
couple
of
pipelines.
C
B
B
B
B
B
B
B
B
I
only
did
this
demo
yesterday,
so
only
to
follow
up
and
check
your
issues
to
see
if
we
have
an
issue
for
gallito
related
objects,
such
as
log
box,
so
the
logs
are
still
there
so
I'll
go
and
follow
up
with
that
and
see
personal
inclination.
I
could
also
test.
We
have
an
API
with
fully
took
pipeline,
so
run
that
test
and
see
if
it
deletes
a
job
box.
So
it
might
be
a
handling
issue,
I'm
suspecting,
that's
pretty.
F
B
D
C
D
Happens
so,
for
example,
there
is
merge,
request
that
is
merged
and
that
had
some
pipeline
and
so
associated
digit.
So
we
remove
this
pipeline.
How
this?
How
the
energy
quest
UI
looks
like
after
that
I
mean
it
gives
me.
There
is
a
reference
to
the
pipeline,
and
it
said
it
is.
It
is
saying
that
the
pipeline
was
completed,
something
this
I.
F
B
G
D
D
Stretcher,
because
previously
when
I
was,
this
was
great
okay,
so
I
have
to
check
to
let
me
okay,
let
me
try
once
again
this
strange.
C
D
Was
interested
didn't
work,
but
right
now
you
see
that
this
video
is
grayed
out
and
user
cannot
change
the
name.
But
it's
important
to
point
out
that
admin
user
still
can
change
this
name.
So
I'm
not
sure.
Maybe
there
is
some
bug
like
it's
not
being
a
white
previously
I
didn't
so
previously.
I
was
still
able
to
change
the
name
who
is
enabled
ready,
so
I'll
probably
test
its
several
times
and
check
if
there
are
any
specific
steps
for
that
yeah.
But
overall,
that's
it
that's
how
its
it
looks
like
and.
D
D
B
B
F
D
B
B
Okay,
so
this
one
is
the
design
management
it's
been
added
to
geo,
so
geo
is
robust
in
the
gate
projects
and
we're
gradually
adding
on
the
other
objects.
So
this
is
the
first.
It's
still
alpha.
The
design
management
assets
are
now
being
replicated
from
when
to
you
to
another
view,
which
is
quick,
so
we'll
come
back
to
some
of
the,
and
it
is
awesome.
Well,
I'll
show
you
why
it's
also
ok,
so
actually,
here,
I.
B
B
So
this
little
frog
I
said
behind
the
scenes:
wiki
it
it
manages
these
objects.
The
graphical
objects
is
an
LS
s
file,
so
they
get
stored
under
gait
lab
real
share
health
Isis
objects.
So
this
is
one
to
you.
One
and
I
only
have
one
file,
so
we
can
prove
that
that's
a
frog
in
a
moment.
The
idea
behind
here
is
on
the
Geo
host.
You
should
be
able
to
go
to
the
same
directory.
B
Okay,
so
probably
number
two,
so
you
look
here:
we
got
this
one
by
default,
Gio
has
to
be
hashed
storage,
so
it's
better,
but
it's
not
as
as
human
friendly,
I
think
we're
all
going
to
have
to
get
used
to
them,
and
here
the
object
is
now
across
which
is
quick.
Now
it
is
alpha.
So
what
that
means
at
the
moment
is
Gio
will
quite
happily
replicate
new
objects,
there's
no
verification
at
the
moment.
B
B
So
when
you're
looking
at
Gio
and
what's
the
expectation
is
listen
but
about
a
good
like
to
see
how
GU
is
going
you'll
see
at
the
moment
is
mostly,
the
database
is
fully
verified.
The
projects,
the
repos
and
the
wikis.
Everything
else
is
a
little
bit
mostly
new
and
that's
that's
common
I
think
that's
going
to
be
a
contribute
goal
is
to
have
a
framework
that
manages
a
verification
process
and
how
these
objects
are
kept.
In
sync,.
B
Because
it's
hash
storage,
it's
a
requirement
of
Geo
that
you
use
hash
and
storage.
So
normally
you
would
see
here
you
have
like
project
names
and,
and
who
knows,
but
when
you
can
graph
the
hash
storage,
you
just
get
hashes
and
we
can
see
quite
difficult
to
tell
what
that
is.
We
can
verify
that
at
least
it
so.
B
B
B
B
Mr.
froggy
I.
B
B
So
that's
one
way
that
is
a
real
console
command.
I
think
you
can
do
as
well.
Well
you
it's
like
the
hash,
if
you're
trying
to
find
it
on
the
file
system,
but
you
can
find
it
from
from
the
GUI
using
this
I
like
it
I,
don't
like
this
all
at
symbol.
It
just
means
you
can
autocomplete,
which
is
a
nuisance
and
aromatics
Aldridge
yeah
I.
D
G
C
G
I'll
be
referring
to
here,
we
go
so
thanks
for
listening
to
my
Tech
Talk
that
I
play
is
I,
survived,
upgrading
to
chat
3.0.
Ask
me
anything
so
I'll
give
a
brief
overview
of
what's
happening
with
the
child
upgrade.
So
the
biggest
change
here
is
that
you
do
need
to
do
some
manual
intervention
in
order
to
actually
upgrade
to
2.0,
and
the
primary
reason
is
because
we
are
updating
and
immutable
of
you
in
the
nginx
ingress.
G
So
this
means
that
the
effector
services
actually
need
to
be
deleted,
and
then
we
created
you
can
actually
just
upgrade
in
place
and
the
secondary
reason
is:
if
you're
using
the
Bandit
progress
chart,
we
actually
did
a
major
upgrade
from
adding
like
a
zero
point.
X
released
were
one
point
actually,
so
it's
a
big
version
job
and
because
of
that,
the
thing
that
changed
is
that
the
name
of
the
key
that
starts
the
application
database
secret
has
changed.
So
we
need
to
do
with
that.
B
G
G
Where
it,
it
does
not
because
the
if
I,
using
the
bundle
ostrich
at
the
recommended
way
for
you
to
upgrade
actually
to
to
affect
off
the
database
and
then
restore
it
again.
So
you
know
the
data
is
not
affected
in
any
case
and
if
you
are
not
using
the
bandit
post
racetrack,
if
you
have
your
own
external
post,
press
or
you're,
managing
your
own
chat,
then
this
is
the
non-issue
completely.
So
the
only
thing
you
need
to
do
is
to
sort
of
DVI
services,
and
we
created
data.
G
So,
while
upgrading
to
3.0
I
thought,
I'll
have
a
bit
of
fun
trying
to
break
the
upgrade
in
every
way
possible,
so
the
first
thing
I
did
was
to
try
to
go
directly
to
3.0
without
doing
any
of
the
manual
steps.
So
what
I
got
was
this
message,
which
is
a
great
field,
so
you
can
actually
get
the
reason
why
the
upgrade
field
from
this
upgrade
check
pot.
G
If
you
do
a
describe,
you
can
actually
see
the
reason
why
you
feel
so
in
this
case,
the
reason
why
I
thought
was
yeah
I
try
to
upgrade
without
redoing
any
of
the
manual
steps
and
they
caught
that
which
is
cool,
so
I
think
the
primary
way
they
catch
that
yeah
the
primary
way
they
catch.
That
is
actually
to
check
whether
the
database
secrets,
as
you
present
I
suspect,
is
not
so
much
that
they're
present
as
whether
you
are
still
using
the
whole
key
for
it.
G
So
once
I
delete
the
database
secret
I
tried
the
same
thing
again:
upgrading
without
doing
any
of
the
other
manual
intervention.
Steps
and
I
got
a
different
message
this
time,
and
this
is
new
to
me.
Actually,
it
says
that
you
actually
need
to
upgrade
to
the
latest
minor
version
before
moving
on
to
the
major
version
of
the
chart.
So
in
this
case,
I
was
actually
upgrading
from
three
point.
G
Five
point
five.
So
it
stopped
me
because
I
needed
to
upgrade
to
two
point:
six,
if
I
being
the
3.0,
so
did
something
interesting
here.
I
suspect
you
actually
need
to
bear
in
mind
a
keylock
version
and
the
chart
version
when
upgrading.
So
you
need
to
make
sure
that
you're
upgrading
to
the
key
lab
or
the
latest
give
that
minor
version,
and
then
you
also
need
to
make
sure
they
are
upgrading
to
the
latest
chat
minor
version
before
upgrading
to
the
next
major
version.
So
that's
something
interesting.
G
So
this
is
a
you
have
to
have
a
purine
check
to
stop
you
from
doing
stuff
like
that
as
well.
So
next
I
try
to
I
mean
I.
Okay
off
the
tech
upgrade
problem
and
I
try
to
upgrade
without
actually
deleting
the
existing
services.
So
I
do
get
this.
Failure,
which
is
yeah,
is
immutable,
so
I
mean
test
requests
refer.
If
you
follow
documentation,
you
will
not
run
into
this
problem.
G
One
thing
interesting
here
is
for
this
step.
I
also
tried
not
setting
this
get
migrations
in
able
to
false.
So
if
you
try
to
do
that,
yeah,
the
migrations
will
fail
to
run
because,
as
father
agrees,
that
way,
she
deleted
the
database
credentials
so
yeah
all
the
parts
are
in
a
bad
state,
so
remember
to
set
that.
G
So
this
is
where
is
finally
upgraded.
I
mean
I
finally
been
a
good
boy
and
follow
the
instructions
so
as
part
that
I'm
at
the
end,
the
way
she
asked
you
to
do
to
run
a
post
database
upgrade
script
which
basically
resource
the
previous
backup.
You
took
in
the
free
upgrade
script,
and
then
he
runs
all
the
migrations,
so
that's
all
fun
and
all.
But
when
I
try
to
run
the
script,
it
actually
gave
me.
G
This
error
like
declare
a
and
edit
option
so
a
bit
of
searching
reviews
that
we
actually
need
to
use
bash
for
to
use
this
associative
arrays
and
the
default
bash
on
Mac
OS
is
actually
3.2.
So
we
need
to
actually
upgrade
or
install
a
little
version
of
bash
for
Mac
OS
before
we
are
able
to
run
the
script.
G
So
if
you
notice
here,
I
actually
ran
the
command
again,
but
this
time,
using
the
fashion
stuff,
I
blue
instead
of
the
system
version,
so
that
she
ran
well
I,
set
a
TN
very
difficult
for
some
reason
that
I
can
remember
some
invalid
cracked
or
something
I'm,
not
sure
if
it's
the
part
in
the
script
or
just
about
for
Mac,
OS
or
C.
Shell
doesn't
say
nice,
which
she
feels
like
that
no
idea.
C
G
G
D
D
F
D
G
So
I
have
to
admit
that
I
actually
ran
into
this
as
well.
My
child
upgrade
cost
an
intermediate
stage,
and
this
was
the
common
I
had
to
run
to
as
she
delete
all
the
stuff
that
was
added
in
Chopin
in
chat
tree,
but
not
in
two
point:
six,
so
yeah,
it's
the
whole
list
of
stuff.
You
need
to
delete
to
get
it.
D
D
G
I
think
one
thing:
I
research
done
after
doing
this
crazy
preventive
anything
is
that
maybe
you
could
try
using
helm
row
back
to
row
back
to
a
known,
good
state,
but
I
didn't
want
to
do
that,
because
I
had
already
migrated
the
database
at
that
point
and
I
was
kind
of
reluctant
to
do
it
over
again.
So
yeah.
B
B
G
I'm
not
sure,
actually
so
when
I
encountered
that
the
first
thing
I
did
was
actually
get
a
path
to
see
what
wasn't
working
and
then
I
noticed
that
there
was
an
upgrade
check
pod,
which
I'm
guessing
is
what
they
used
to
do.
The
pre
upgrade
check
so
similar
to
omnibus
the
Installer
will
stop
you
if
you
try
to
do
something
it
doesn't
like
so
I
just
described
that
part
to
see
if
there's
any
messages,
and
there
was
so
I,
don't
think
it's
any
I.
Don't
think
this
is
very
special.
B
G
Think
that
it's
definitely
a
case
for
adding
this
to
the
troubleshooting
section.
The
updating
in
that
meeting
job
I,
don't
think
we
have
section
which
says
check
the
upgrade
chat,
pod.
B
B
B
G
G
It
stopped
me
from
upgrading
beyond
that,
so
it's
very
similar
to
the
Omnibus
check
way
if
you
try
to
upgrade
to
a
major
version
without
upgrading
to
the
latest
minor
version
in
the
previous
release.
Actually
tell
you,
please
update
with
that
before
trying
to
move
on
to
the
next
major
release
so
yeah
that
there
are
great
jackpot,
actually
stops
you
if
you
try
to
upgrade
from
minor
from
a
chat
version.
G
G
Because
I
think
that's
been,
let
me
see
okay,
it
looks
like
they
try
to
keep
it
in
sync
someone.
So
if
you
move
from
so
in
this
case,
11
11
to
12,
it
actually
moves
up
a
major
version
here:
I'm
I'm
guessing
this
is
a
special
case
because
of
those
breaking
changes
which
they
introduced.
So
you
actually
need
to
do
that.
Menu,
intervention.
B
Yeah,
thank
you.
That's
terrific!
Thank
you.
Okay,
looking
through
the
list,
I
think
we're
done
I'll
tidy
up
the
list.
It's
only
putting
it
in
the
table
forms
it
should
the
change,
cadence
and
I'm
sure
2.8
wouldn't
be
any
different,
hey.
Anyone
else
went
to
demo
make
some
comments
before
we
before
we
wrap
up
yeah.