►
Description
In this demo, Ben will demonstrate the latest features from ECE-Tools 2002.1.1 and 2002.1.2 releases.
A
A
A
We
also
now
support
mariadb
versions
up
to
10.4,
as
well
as
versions
of
elasticsearch
version
7.,
which
version
of
these
software,
your
particular
site,
is
going
to
be
compatible
with,
is
going
to
depend
upon
what
version
of
magento
your
site
is
running.
So
I
encourage
you
to
take
a
look
at
the
software
compatibility
version
matrix
on
our
dev
docs
site
to
see
what
versions
of
the
software
you
should
use,
but
rest
assured
that
ece
tools
is
now
compatible
with
these
versions.
A
The
zen
framework
has
renamed
itself
to
laminas
and
so
there's
a
corresponding
change
that
you
must
make
to
the
autoload
section
for
that
laminas
namespace
and
so
we've
updated
our
validator
of
that
area
in
order
to
be
compatible
with
either
version
of
that
namespace.
Depending
upon
what
version
of
the
framework
you
currently
have
installed,.
A
As
you
can
see
from
this
table,
these
codes
are
roughly
segmented
out
based
upon
their
severity,
as
well
as
what
phase
of
the
deployment
process
they
came
from.
So
errors
from
the
build
phase
are
all
less
than
100.
Errors
from
the
deployment
phase
are
in
the
100
to
200
range
in
the
post.
Deploy
and
more
general
errors
have
a
little
bit
of
an
overlap
in
the
200
range,
and
then
warnings
are
in
the
1000
2000
3000
4000
ranges
all
respectively.
A
A
We've
made
these
messages
easy
for
them
to
be
machine,
parsable
and
readable,
and
get
data
out
to
you
in
order
to
diagnose
any
kind
of
errors
or
warnings
that
came
up.
So
let's
take
an
exam
and
take
a
look
at
an
example
of
one
of
these
messages
you
can
see
we
have
the
error
code
included,
and
I
know
from
that
previous
slide.
The
errors
in
the
2000
range
are
warnings
from
the
deployment
phase.
A
A
We
have
the
error
message
itself.
In
this
case
it
is
related
to
the
php
version
of
magento
2.4.0
that
I'm
using
and
then.
Lastly,
almost
all
of
the
errors
and
warnings
that
ece
tools
generate
now
include
a
suggestion,
and
so
that
is
included
in
our
json
file
as
well,
and
so
this
will
give
you
a
little
bit
of
in
context
information
about
how
to
possibly
resolve
any
of
these
errors
or
warnings
as
they
come
up
and
help
you
to
more
easily
diagnose
and
resolve
them
in
a
quick
manner.
A
We
have
reordered
when
patches
get
applied
during
the
build
process,
so
patches
will
be
now
be
applied
to
your
site,
almost
at
the
very
beginning
of
the
build
process.
This
is
in
order
to
resolve
some
issues.
We
had
around
compiling
the
di
xml
file.
If
that
those
patches
had
been
added,
we've
added
a
new
redis
backend
variable.
A
We've
added
the
option
for
some
more
verbose
output
when
you're
running
the
config
dump
the
config
import
or
the
module
enable
commands.
So
you
can
get
some
more
details
about
what's
happening
when
you
run
those
and,
lastly,
we've
added
some
more
explicit
warnings
when
you're
running
the
database
dump
command
from
ece
tools
and
more
and
specifically,
we'll
give
you
more
clearer
warnings
that
this
will
temporarily
put
your
site
into
maintenance
mode
while
that
dump
is
occurring
forward
finish.
A
A
A
We
also
now
have
a
page
on
the
dev
doc
site
that
lists
out
all
of
the
error
codes
that
ece
tools
will
generate,
as
well
as
the
message
that
goes
along
with
them.
So
if,
for
whatever
reason,
you
just
have
the
error
code
from
your
cicd
pipeline,
you
can
go
to
this
page
and
see
what
the
actual
message
and
underlying
condition
was.