►
From YouTube: Mobile DevOps - Google Play Integration Demo
Description
Integration Docs
https://docs.gitlab.com/ee/user/project/integrations/google_play.html
Fastlane Docs
https://docs.fastlane.tools/actions/upload_to_play_store/
Generate a Service Account Key
https://developers.google.com/android-publisher/getting_started
Sample Project
https://gitlab.com/gitlab-org/incubation-engineering/mobile-devops/demo-projects/android_demo
A
Hi
folks,
today,
I'd
like
to
share
a
quick
demo
on
how
to
use
the
new
Google
Play
integration
in
gitlab
to
automate
your
releases
to
the
Google
Play
Store
to
get
started,
go
to
the
integration
section
under
the
project.
Settings
in
here
you'll
see
an
option
to
add
the
Google
Play
integration
to
your
project,
then,
on
the
integration
page
you'll
see
inputs
for
the
package
name
and
service
account
key
the
package
name
is
simply
the
name
for
your
application,
so
something
like
com.getlab.androiddemo.
A
The
service
account
key
is
a
Json
file
which
can
be
obtained
by
following
the
instructions
on
this
page,
which
I'll
link
in
the
video
description
below
the
process
walks
through
creating
a
service
account
in
a
Google
Cloud
console,
then
creating
a
key
then
authorizing
that
key
with
a
Google
Play
Store
once
you've
completed
the
process,
you'll
have
a
Json
file
that
can
be
uploaded
to
configure
the
integration.
With
all
the
information
entered,
we
can
verify
everything
works
by
clicking
the
test.
A
Settings
button
looks
like
everything
works,
so
we
can
go
ahead
and
click
save
changes
if
your
app
hasn't
been
uploaded
to
the
Google
Play
console.
Yet
you
might
get
an
error
when
testing
the
settings,
you
can
still
save
changes
and
test
the
settings
again
after
the
app
has
been
added
with
the
integration
enabled
the
supply
package
name
and
Supply
Json
key
data,
CI
variables
will
be
added
to
our
pipelines.
These
are
protected
variables,
so
they
will
only
be
added
to
pipelines
running
on
protected
branches
or
tags.