►
Description
Weekly demo issue - https://gitlab.com/gitlab-org/incubation-engineering/devops-for-mobile-apps/readme/-/issues/17
Handbook page - https://about.gitlab.com/handbook/engineering/incubation/devops-for-mobile/
A
This
is
our
issue
for
the
demo
today
and
so
I'll
kind
of
walk
you
through
this,
and
I
will
add
a
link
to
this
issue
in
the
description
of
the
recording
below
as
well,
if
you'd
like
to
get
to
it
that
way.
A
So
as
a
review,
the
mission
of
this
group,
the
devops
for
mobile
apps
group,
is
to
improve
our
capabilities
and
and
make
the
experience
better
for
mobile
engineers
working
in
gitlab
and
I've
got
a
link
to
our
direction
page
here
and
then
also
the
weekly
demos
link,
which
has
all
of
these
demos
for
the
last
few
weeks.
A
So
the
focus
this
week
has
been
continued
on
the
review
apps
for
mobile
feature
that
we've
been
working
on
and
as
a
review
or
a
reminder.
This
is
this
basically
provides
review,
app
functionality
right
within
the
merge
request
for
an
app,
so
I've
got
an
example
here
for
this
weather
app
we've
been
testing
with
and
the
way
this
works
is
you've
got
to
get
a
merge
request.
You've
got
some
changes
and
you
want
to
preview
it
before
either
merging
it
or
maybe
loading
it
onto
a
device,
or
something
like
that.
A
So
you
can
get
this
button
right
here
through
the
review
app
functionality,
and
this
will
open
the
app
in
appetize
and
you
can
just
boot
it
up
and
it
will
launch
and
you
can
click
around
and
test
it.
So
pretty
simple
interface.
A
So
the
majority
of
what
I've
been
working
on
this
week
is
kind
of
ironing
out
some
edge
cases
in
the
functionality,
so
I've
linked
to
a
merge
request
that
I've
been
working
on
for
the
appetize
cli,
and
this
is
a
tool
that
we
wrote
to
kind
of
make
this
interaction
work
better
with
appetize
and
give
us
the
ability
to
test
it.
And
things
like
that.
A
So
one
of
the
edge
cases
we
ran
into
is
that
when,
if
you're
doing
a
lot
of
changes
to
a
merge
request,
it
wasn't
always
cleaning
up
the
existing
review
apps
cleanly.
So
what
this
change
does?
Is
it
it
kind
of
changes,
the
upload
command,
so
that
it
will
either
create
a
new
app
if
it
doesn't
exist
or
update
the
existing
one?
If
it's
already
in
place?
So
there's
some
details
here
and
the
the
code
is
here.
A
If
you
feel
like
checking
that
out,
so
that's
going
pretty
well,
don't
quite
have
it
ironed
out
yet,
but
it's
getting
pretty
close,
so
I
hope
to
have
that
done
pretty
soon
next
week
and
then
there's
just
a
couple
of
changes
to
the
templates
as
well
to
support
this.
So
essentially,
what
we
needed
to
do
to
make
this
work
is
introduce
an
additional
artifact
into
the
pipeline.
A
So
there's
this
new
artifact
that
gets
created
here
and
that's
kind
of
what
helps
retain
that
information
between
the
different
pipeline
runs
outside
of
that
I've.
Just
kind
of
linked
to
some
of
the
other
examples
that
I've
been
working
with.
So
you
can
see
the
the
two
android
and
ios
example
review
apps
and
then
the
the
kind
of
sample
project
matrix
down
here
so
the
the
coming
up
next,
like
I
said,
going
to
be
polishing
off
the
that,
mr
for
the
appetized
cli.
A
Getting
that
finished
up
and
deployed
and
released
so
we'll
get
that
working
and
things
should
be
running
pretty
smoothly
after
that
and
then
so.
I'm
still
looking
for
a
few
more
folks
to
test
out
the
templates.
So
there's
a
link
here
to
this
issue
with
some
instructions
on
how
to
get
it
set
up,
and
so
you
can
take
a
look
at
that
and
then
provide
any
feedback
you
have
in
this
issue
as
well.
A
That
would
be
great
and
then
I'm
also
going
to
be
creating
kind
of
a
feature
focused
demo
video
to
to
share
it
with
folks.
So
I
think
this
will
help
get
some.
A
You
know
be
something
that
we
can
send
out
to
maybe
potential
users
that
want
to
try
it
out,
they're,
not
quite
sure
how
to
get
it
set
up,
or
things
like
that.
So
I'm
going
to
be
working
through
that
as
well.
Next
week,
so
that's
about
it
for
this
week,
thanks
for
watching
and
I'll
see
you
next
time.