►
A
Hey
everyone,
my
name
is
darby,
and
this
is
the
devops
for
mobile
apps
demo
for
january
5th.
2022..
The
issue
on
my
screen
right
here
is
an
issue
that
I've
created.
That's
going
to
capture
all
the
notes
and
links
for
this
update,
and
I'm
going
to
include
this.
I
couldn't
include
a
link
to
this
in
the
video
description
below
on
youtube,
so
you
can
get
to
all
of
the
all
the
notes
there.
A
So
the
topic
for
this
update
is
kind
of
following
up
on
the
last
update
from
before
the
break,
which
was
adding
this
secure
files
api
into
gitlab.
I've
got
an
mr
that's
open
here
that
kind
of
talks
through
the
change,
how
it
works,
how
the
apis
work
and
things
like
that.
But
I'll
go
through
this
again,
because
I've
had
some
feedback
and
made
some
changes
to
this,
and
I
think
it's
it's
getting
into
a
better
state
now
so
kind
of
starting
off.
A
The
idea
here
is
to
be
able
to
provide
a
way
to
upload
binary
files
into
gitlab,
so
you
can
use
those
files,
then,
in
your
ci
pipelines-
and
this
is
this-
is
a
big
deal
for
mobile
teams,
because
they
have
provisioning
profiles
and
secure
certificates,
and
things
like
that.
That
need
to
be
part
of
the
build
process
and
there's
not
a
good
way
to
do
this
right
now,
so
just
to
kind
of
walk
through
some
quick
examples.
Here.
A
This
api
supports
uploading
of
a
file,
a
listing
listing
of
files
in
the
project,
getting
an
individual
file
downloading
a
file
and
then
deleting
a
file,
and
so
what
I'm
going
to
do
is
walk
through
some
examples
over
here
that
I've
got
I've
got
this
all
running
locally
in
my
gdk.
So
let
me
just
grab
this
link
here,
and
so,
if
I
run
this,
this
is
going
to
make
a
get
request
using
this
local
private
token
that
I
have
to
the
projects
project
id
secure
files
path.
A
When
I
run
that
I
get
an
empty
array
back,
because
I
don't
have
any
files
in
this
project.
Yet
so,
let's
go
ahead
and
create
some.
I've
got
a
couple
files
here
locally
in
this
folder,
so
I've
got
the
demo
provisioning
profile
and
then
this
upload
keystore
file,
and
so
I'm
just
going
to
upload
those
and
so
doing
this.
To
do
this,
I'm
going
to
send
a
post
request
to
the
secure
files
endpoints
give
the
file
a
name
and
then
tell
the
tell
curl
where
the
the
file
is
coming
from.
A
I'm
also
piping
this
output
to
jq
just
so,
we
can
see
the
output
a
little
bit
more
clearly.
So
I'm
going
to
run
that
and
I
get
this
response
from
the
api.
So
it
tells
me
the
file
name,
the
permissions,
there's
a
and
then
there's
a
checksum
that
comes
back,
and
so
this
is
going
to
be
a
way
that
we
can
then
validate
in
the
runner
that
the
the
file
that
we've
got
is
the
file
that
we
expect.
A
So
so
we'll
do
that
again
for
the
second
file
here
and
there
we
go,
and
now
we
have
two
files
up
there
and
then,
if
I
run
that
that
first
command
again
I'll,
you
can
see
that
I've
got
both
of
those
files
coming
back
there
and
then
let's
say
I
wanted
to
download
one
of
these
locally
and
clear
this.
I
shouldn't
have
done
that.
A
I
need
the
file
id
okay,
so.
A
So
I
want
to
get
file
id
17
here
and
that's
going
to
download
that
file,
and
then
you
can
see
here
that
the
file
that
I
downloaded
here
demo.mobile
provision
has
been
downloaded
and
that
is
the
the
same
file
sizes.
I
guess
it
has
a
different
name,
but
it's
the
same
file
file
size
as
the
upload
key
store,
jks
so
remove
that
file,
because
we
don't
need
that
anymore
and
then
I
think
I
accidentally
uploaded
an
additional
file
here.
So
let's
see
yep,
I
got
three
in
here.
A
A
Now
I
just
have
the
two
files
that
I
was
expecting
to
have
there,
so
so
that's
a
quick
kind
of
overview
of
the
api
interactions.
The
other
thing
that
I
did
this
week
is,
I
created
a
a
very
basic
like
runner
integration,
so
we've
got
these
files
that
are
available
within
gitlab.
A
How
do
we
use
them,
then,
on
the
ci
jobs,
and
so
I
created
this
this
little
ruby
script
here
and
what
this
does
is
this
allows
you
to
download
the
script
to
your
your
runner
and
then
execute
it
to
pull
in
all
the
secure
files
for
a
given
project,
so
I'll
walk
through
this
real
fast
here,
but
there's
a
download
path.
A
So
when
that's
all
done,
then
you've
got
the
files
locally
and
and
then
you
can
go
and
use
them
in
your
ci
jobs.
I've
got
a
test
ci
configuration
here
that
I've
been
using
to
test
this
locally.
So
just
one
simple
step
and
there's
a
few
things
that
I'm
I'm
kind
of
just
echoing
some
debug
information
here.
But
this
is
really
the
the
two
things
that
that
we
really
need
to
do
so
we
go
and
download
the
script
from
from
the
public
project.
A
Where
I've
stored
this
and
then
we
just
run
it
and
then
I'm
just
echoing
out
the
the
output
of
that
folder
here,
so
we
can
see
that
it
worked.
So
I've
got
a
job
here.
This
failed
earlier
because
I
didn't
have
any
files,
so
I'm
going
to
retry
it
now
that
we've
got
some
files
in
the
project.
A
All
right-
and
it's
done
so-
we
can
see
that
we've
echoed
out.
You
know
our
ruby
version,
our
project
id
and
so
on,
and
then
the
script
is
executing
here.
There's
a
little
bit
of
output
that
comes
from
the
script,
that's
saying
it
download
the
file
and
saved
it
and
then
and
then
we
did
the
ls
command
here
to
see
that
the
the
files
are
showing
up
in
that
folder
locally
on
the
runner.
So
so
it's
kind
of
showing
that
it
all
works.
A
So
and
then,
if
we
go
back
over
here.
A
You
can
see
that
these
are
the
two
files
that
I
had
uploaded:
there's
the
mobile
provisioning
profile,
which
is
12k
and
then
the
2.7
k
for
the
upload
key
store.
So
so
that's
all
kind
of
flowing
through
as
we
would
expect,
so
that
is
kind
of
the
main
parts
that
I
wanted
to
show
today.
A
I
think
the
the
next
steps
here
there's
there's
a
few
to
do's
that
I
have
within
this,
mr
some
things
that
I
want
to
follow
up
on
and
then
I
just
need
to
get
some
more
folks
to
take
a
look
at
it
and
provide
some
feedback.
So
I'm
going
to
continue
to
work
on
that
over
the
next
week
and
hopefully
get
this
thing
ready
for
proper
review
and
maintain
a
review
pretty
soon.
So
we
can
can
get
this
in
and
start
testing
it
out
thanks
for
watching.