►
A
I
have
a
issue
that
I'm
gonna
share
here,
so
I'll
share
my
screen.
So
this
is
the
this
is
the
demo
issue
for
this
week
and
so
something
I've
added
to
the
the
issue
that
I'll
put
in
all
of
these
here
is
just
a
little
section
on
our
mission.
This
is
if,
if
anyone
has
you
know
kind
of
new
to
these
demos
and
hasn't
seen
these
before,
you
get
an
idea
of
what
we're?
A
What
we're
all
about
so
devops
for
mobile
apps
is
a
single
engineering
group
and
we're
our
goal
is
to
improve
the
experience
for
developers
that
are
building
mobile
mobile
apps,
and
so
this
there's
a
link
in
here
to
the
handbook
page
and
then
I've
also
linked
to
the
weekly
demos
issue,
which
is
a
place
where
we'll,
where
we
post
these
updates
each
week,
and
you
can
go
there
and
check
that
check
those
out
and
catch
up
on
old
ones,
and
things
like
that
cool
so
into
this
week's
update.
A
So
this
week
I
kind
of
focused
on
the
idea
of
the
mobile
review
apps.
This
is
something
that
has
come
up
in
a
number
of
conversations
with
customers
and
users,
and
it
seems
like
it
would
be
a
really
helpful
feature
for
a
lot
of
people.
A
So
I
started
to
dig
into
that,
and
I
read
this
blog
post
andrew
fontaine
created
a
while
back
kind
of
walking
through
how
to
set
this
up
with
a
with
a
service
called
appetize
appetize
provides
a
mobile
device
emulator
in
the
browser,
and
it's
got
a
very
nice
simple
to
use
api.
A
So
I
took
that
blog
post
and
started
to
work
up
what
a
prototype
ci
template
might
look
like
for
something
like
this,
and
so
what
I
did
is
I
started
with
just
a
standard
build,
so
I've
got
an
android
app
here
with
just
kind
of
a
standard
pipeline
with
the
build
in
the
test
stages
and
in
the
build
stage
we
do
output
an
artifact,
and
so
that's
where
the
the
apk
gets
created
as
part
of
that
build
step.
A
So
then,
what
I,
what
I
worked
on
was
basically
building
in
two
more
steps.
As
part
of
the
process,
this
was
part
of
the
blog
post
that
andrew
had
written
as
well.
A
He
added
a
step
for
starting
the
review
out
and
one
for
stopping
it,
and
so
there's
there's
two
more
steps
in
here
and
one
one
starts
that
app
and
actually
does
the
deploy
to
appetize
and
the
other
one
is
a
manual
step
to
stop
it,
so
it
would
actually
go
and
delete
that
that
deployment
from
appetize,
and
so
you
can
see
that
this
this
pipeline
here
works
as
well,
and
then
the
final
link
I
have
here
is
is
actually
just
the
the
mr
and
this
actually
shows
the
review
app
we're
leveraging
all
the
functionality
that
already
exists
in
gitlab
to
do
review
apps.
A
So
I
can
click
this
here
and
it
will
pop
open
I'll
link
straight
to
the
app
and
appetize
and
I
click
play
it
launches
the
app
and
there
it
is,
and
now
I
can
see
the
app
that
I've
just
deployed
with
whatever
changes
were
were
made
as
part
of
that
deployment.
So
that's
that's
pretty
cool.
A
I
thought
that
was
a
really
nice
workflow
and
you
know
very,
very
easy
to
use
for
folks.
So
then,
what
I
was
working
on
was
trying
to
figure
out
a
way
to
make
this
as
simple
as
possible
to
add
into
an
existing
pipeline,
and
so
this
is
actually
the
diff
view
of
that
merge
request.
A
I
just
took
a
screenshot
put
it
in
here
and
literally.
The
only
things
that
are
needed
are
to
add
the
two
stages
here.
So
review
start
interview
stop
and
then
I've
tried
to
build
this
up
as
a
include.
So
the
android
mobile
review,
app
document,
ci
yaml
file
isn't
included.
So
you
just
include
that
add
those
stages,
and
then
you
get
all
that
mobile
review
app
functionality.
A
So
pretty
simple:
it's
it
works
nice
in
the
happy
path,
there's
still
some
edge
cases
that
I
need
to
work
out,
but
I'll
kind
of
walk
through
how
it
all
works.
So
there's
there's
sort
of
three
parts
to
it.
The
first
is
that
you
need
an
appetized
api
token,
so
you
need
an
account.
They
do
have
a
free
plan.
A
A
This
basically
has
these
two
two
stages
here
and
they
they
set
up
the
the
configuration
for
doing
the
review
app
telling
it
to
only
only
work
on
branches,
not
on
master.
A
So
basically
these
these
will
only
kick
off
when
we're
doing
merge
requests,
and
then
this
is
the
the
script
that
gets
executed
in
order
to
do
the
deployment,
and
then
it
actually
produces
this
review
and
artifact,
which
we
use
to
to
do
the
destroy
step
later
same
thing,
kind
of
down
here
and
there's
a
install
this
gem,
and
then
we
do
the
destroy
with
the
environment
variable
that
gets
set
here.
A
So
that's
how
that
works
and
then
to
to
make
this
command
line
tool
work
here.
This
mobile
review
command,
I
put
together
a
quick
ruby
command
line
tool
which
is
in
this
repo.
Here
I
need
to
come
up
with
a
better
name,
but
naming
is
hard,
so
this
is
what
we're
going
with
for
today,
the
the
functionality
is
is
pretty
straightforward.
There's
there's
kind
of
two
steps
in
here:
deploy
and
delete.
A
It
sets
up
some
environment
settings
and
this
the
deploy
step
here
actually
leverages
vaseline,
which
I
think
I
can
do
this
without
all
those
extra
dependencies.
But
that's
that's
kind
of
where
I
started
with
this
today,
so
it
uses
a
fastlane
action
to
actually
do
the
appetized
deployment
and
then
the
destroy
is
actually
just
a
simple
http
delete
request.
So
that's
what
that
happens
down
here.
A
So
that's
that's
how
that
works
so
so
yeah,
those
those
things
kind
of
mix
those
together-
and
we
get
this
very
simple
interface
to
be
able
to
set
up
a
review
app
on
an
existing
pipeline.
A
So
so
far
I've
tested
it
with
the
materialistic
app
and
it
works
the
weather
test
app.
I
tried
it
out
and
it
didn't
work.
This
is
because
the
apk
has
a
different
name
than
what
I
was
expecting.
A
So
we
need
to
make
that
more
configurable,
so
I'll
work
on
that-
and
I
haven't
tried
this
with
ios
yet
at
all
that
will
be
kind
of
the
next
step
in
the
process,
so
that
is
where
we're
at
with
the
mobile
view
app
stuff.
Today
I
have
a
section
in
here
on
other
findings,
so
this
is
sort
of
on
to
a
different
topic.
These
are
just
other
things
that
I
found
this
week
that
that
were
kind
of
helpful
in
this
space
as
well.
A
So
the
first
item
here
I
have
listed
is
a
docker
android
project
on
github,
which
is
actually
a
pretty
neat
project.
They
they
set
up
a
number
of
docker
images
that
have
different
permutations
of
the
android
sdk
jdk
gcp,
different
versions,
and
so,
depending
on
what
your
app
needs
you
can,
you
can
kind
of
find
everything
you
need
sort
of
pre-built
there.
This
is
something
previously
that
I
would
have
been
looking
for
to
slim
down
those
the
ci
files.
A
This
right
here
is
an
example
of
one
of
them,
so
this
is
just
the
version
30
of
the
android
sdk
without
any
other
dependencies,
and
so
we're
able
to
get
everything
we
need
there
and
I
have
to
do
any
custom
scripts
to
set
up
the
builds.
A
The
second
item
here
this
is
the
the
gitlab
build
cloud
for
mac
os
beta
released
last
week.
So
I
was
as
part
of
the
release
last
week
and
I
tested
it
out.
It
was
very
easy
to
set
up-
and
I
got
it
running
in
this-
build
here
where
I'm
using
to
using
it
to
test
one
of
the
test.
Apps
super
easy
to
set
up
worked
really
well,
and
then
I
linked
to
the
docs
and
the
vm
types
and
images
as
well.
A
The
third
thing
that
I
have
listed
here
is
just
some
other
existing
appetized
deployment
tools.
These
are
other
ways
that
I
might
think
about
interacting
with
appetize
as
part
of
this
ci
template
they're,
a
little
like
one
of
them
is
not
has
not
been
maintained
in
a
while
and
others
have
kind
of
more
custom
interfaces.
A
So
it
might
not
be
the
right
thing,
but
I'm
just
listing
them
here
for
completeness,
so
that
is
that
section
so
coming
up
next,
I
want
to
take
another
pass
of
the
ruby
cli
clean
that
up
and
and
see.
A
If
we
can
limit
those
dependencies,
I
don't
think
we
need
all
the
gems
that
it
relies
on
right
now
and
then
do
a
little
bit
more
testing
with
the
ci
template
handling
for
edge
cases
and
video
cases
and
then
eventually
move
that
into
like
a
proper
ci
template
so
that
it
can
be
included
through
the
the
template
keyword
in
the
ciaml
file.
A
I'm
looking
for
folks
that
want
to
test
this
with
their
own
projects
too.
So
if
you've
got
an
android
project
and
want
to
try
it
out,
let
me
know
I
can
help
you
get
set
up
on
that
too,
and
then
lastly,
the
ios
template
so
we'll
we'll
get
that
going
as
well.
So
that's
it
for
this
week
as
always
comments
on
the
issue.
Let
me
know
if
there's
anything
you'd
like
more
information
on
or
extra
details
or
just
yeah
any
other
thoughts.
You
have
thanks.