►
From YouTube: Introduction to Shipwright - Jason Hall, Red Hat
Description
Introduction to Shipwright - Jason Hall, Red Hat
Shipwright (https://shipwright.io) is a framework for declaring and executing image builds. It boasts a pluggable architecture that allows for many common build strategies including CNCF Buildpacks, Kaniko, Buildah, s2i and others. Shipwright is built on Tekton, and adds a higher-level focus on simply building container images. So far it's mainly been developed in a partnership between Red Hat and IBM, but all contributions are welcome. This talk will introduce Shipwright, describe how it takes advantage of Tekton's platform, and demo how to use a built-in build strategy to deliver images using Buildpacks.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
Here's
a
brief
agenda
of
what
we'll
go
over
first
up.
What
is
shipwright,
why
do
I
want
it?
How
do
I
use
it?
How
does
it
work
we'll
do
a
quick
demo
and
then
I'll?
Let
you
in
let
you
know
what's
next:
first,
what
is
shipwright
shipwright
bills
itself
as
a
framework
for
building
container
images
on
kubernetes,
it's
built
on
techton.
Another
cdf
project
tekton
is
a
reliable,
versatile,
flexible,
powerful,
ci,
cd
workflow
engine
tekton
and
shipwright
both
run
on
kubernetes
shipwright
plans.
To
do
one
thing
well
and
that
is
build
container
images.
A
A
So,
let's
talk
a
little
bit
more
about
why
you'd
want
it
normally,
if
we
were
in
person,
I
would
do
an
audience
participation
poll
I'd
ask
everyone
to
raise
their
hands
instead,
I'll
just
ask
you
to
quietly
privately
raise
your
hand
wherever
you
are.
Whenever
you
are
watching
this
during
your
deployment
process,
do
you
build
container
images
from
source
from
some
source
from
some
source
in
a
github
repo
say
I
do
do
you
want
to
do
that
when
you
do
that?
Do
you
want
to
do
it
securely
reliably
and
easily?
A
Shipwright
aims
to
do
one
thing:
well
it
fetches
source,
it
builds
it
into
a
container
image
and
it
pushes
that
image.
It
takes
your
code,
it
does
stuff,
it
pushes
an
image,
that's
it
what
stuff
it
does
in
the
middle,
there
is
configurable
with
some
powerful
built-in
options
which
we'll
discuss
in
a
little
bit.
A
A
The
build
type
is
the
the
main
one
that
you
would
interact
with
on
a
day-to-day
basis,
a
build
defines
the
general
build
process
for
pulling
source,
doing
something
to
it.
Pushing
an
image
this
this
example
yaml
here
describes
a
build
called
my
build
that
pulls
source
from
github.com
supercorp,
slash
back
end.
It
uses
build
packs
to
build
that
source,
and
then
it
pushes
the
image
to
registry
that
super
pork
dot
is
when
you
define
this
yaml,
you
apply
it
to
your
cluster,
with
cuddle,
apply
or
any
number
of
other
kubernetes
tools.
A
A
In
this
example,
the
credentials
to
pull
from
github
are
in
a
kubernetes
secret,
called
github
pull
creds
and
the
credentials
to
push
to
my
registry
are
in
registry,
push
creds
either
way
even
with
auth
included.
This
is
only
15
lines
of
yaml,
so
it's
not
all
that
bad.
But
when
you
create
this
build,
it
doesn't
actually
do
anything.
It
just
kind
of
sits
there.
A
It
describes
an
intent,
describes
a
plan
for
building
source
in
pushing
an
image,
but
it
doesn't
do
it
when
you
create
it
in
order
to
actually
run
the
build,
you
create
a
build,
run
object.
This
api
should
feel
familiar
to
people
who
are
already
familiar
with
tecton,
but
if
you
don't,
if
you're
not
familiar
with
tekton,
that's
fine
when
you
create
a
build
run,
you
reference.
The
build
plan
that
you
want
to
execute
here.
A
Now,
when
I
create
this
configuration
in
kubernetes,
it
will
start
to
run.
We
can
check
on
its
status
with
coop
cuddle,
get
and
see
that
it
is
ongoing.
The
status
conditions
there
says,
succeeded
unknown.
I
don't
know
if
it
succeeded
yet
when
it
succeeds,
that
status
will
change
to
true
and
indicate
that
it
has
succeeded
or
if
something
went
wrong,
it
will
say
status,
condition
failed
with
a
helpful
error
message
to
tell
you
a
little
bit
more
about
what
went
wrong.
There's
a
lot
more
involved
in
the
status
here.
A
So
let's
dig
into
that
strategy.
A
little
bit
from
before
where's
that
come
from
the
build
strategy
is
sort
of
the
magic
of
shipwright
it
lets.
You
declare
how
that
source
should
become
that
image.
It's
2021
there
are
like
50
different
ways
to
build
a
container
image.
Now,
in
this
example,
we're
using
cncf
build
packs,
it's
a
great
extensible
option.
A
It
builds
source
code
from
any
from
many
many
languages
into
an
image
without
needing
to
write
a
doctor
file,
which
is
great,
but
there
are
plenty
of
other
tools
you
might
reach
for,
and
a
number
of
common
strategies
are
provided
out
of
the
box
by
shipwright.
If
you
use
a
docker
file,
you
could
build
that
image
with
builda
or
conoco
or
build
kit.
If
you
want
to
take
source
directly
into
a
container
image,
you
can
use
build
packs
or
s2i
or
code.
A
A
Shipwright's
implementation,
when
you
create
a
build
run,
is
actually
pretty
simple.
It
offloads
most
of
the
real
hard
work
to
actually
execute
on
tekton
tekton
has
been
a
great
foundation.
It's
reliable,
it's
extensible!
It's
got
a
lot
of
battle
testing.
There's
a
great
community,
constantly
improving
it.
A
A
A
A
A
Docker
run,
will
touch
the
image
and
run
it
and
show
hello
cdcon
welcome
back
so
now
what
shipwright
has
built
your
image
and
pushed
it
to
your
registry,
but
the
short,
the
the
story
is
not
over
yet
shipwright
isn't
a
one-stop
shop.
Remember
it
does
one
thing:
well,
it's
one
tool
in
your
toolbox:
shipwright
won't
deploy
your
images,
it
won't
test
or
validate
your
images
and
it
won't
scan
images
or
enforce
policies
on
them.
The
container
ecosystem
has
a
number
of
tools
to
do
these
already.
Techton
can
do
these
things
jenkins.
A
A
A
A
main
thing
we
want
to
do
is
simplify
and
stabilize
the
api
toward
a
stable,
v1
api.
You
can
build
things
on
another
headline
feature
we
want
to
work
on
this
year
is
automating,
build,
runs
or
continuous
delivery.
Interesting
that
I
would
be
talking
about
this
at
continuous
delivery
con.
Basically,
we
want
to
watch
the
repo
that
you
configure
and
push
an
image
every
time
that
repo
changes
we
want
to
build
this
on
tekton
triggers
another
area
of
improvement.
A
Is
we
want
to
work
on
the
cli
so
that
you
can
specify
a
build
of
source
locally
on
your
machine
so
that
you
can
say
ship
right?
Here's
some
source
that
I
have
been
hacking
on.
I
would
like
you
to
build
an
image
in
the
cluster
and
the
shipwright
cli
called
ship
should
also
be
able
to
show
you
the
logs
of
the
executions
of
build,
runs
past
and
current.
A
So
that's
shipwright,
if
you're
in
a
hurry.
This
is
the
only
slide
you
need.
Shipwright
will
build
container
images
in
kubernetes.
You
can
choose
your
own
build
strategy,
it's
built
on
techton.
It
does
one
thing
well
and
we
plan
to
steadily
improve
it
toward
a
stable,
v1
api,
but
wait.
There's
more
shipwright
power's
ibm
code
engine,
which
is
a
serverless
platform
from
ibm
shipwright
handles
the
building
of
source
into
an
image
to
run
on
that
platform.
A
A
Lastly,
I'd
be
remiss
to
mention
I
remiss
if
I
didn't
mention
all
the
wonderful
humans
who
have
helped
get
us
here,
I'm
only
a
very
small
part
of
this.
All
of
these
people
have
been
working
on
this
for
a
very
long
time
and
if
you'd
like
to
see
your
name
listed
on
that
slide
in
future
versions
of
this
talk
come
and
join
us.
You
can
find
docs
and
examples
at
shipwright.io
come
say
hi
on
the
shipwright
channel.
In
the
kubernetes
slack,
we
have
weekly
community
meetings
where
you
can
come
and
tell
us.
A
A
Normally,
if
we
were
in
person,
I
would
hand
these
out
after
the
talk,
but,
alas,
we
are
not.
Instead,
if
you
feel
comfortable,
send
me
your
address
and
I'll
say
I'll
mail
you
a
sticker
to
if
you
don't
feel
comfortable,
I
completely
understand
next
time
we
do
this
in
person
I'll
be
the
guy
with
a
bunch
of
stickers.
A
A
Hello,
can
people
hear
me,
can
you
hear
me
hello?
Oh
okay,
good
yeah,
so
thank
you.
That's
shipwright!
I
have.
I
have
asked
some
polls
if
you
have
not
seen
the
polls
in
the
talk,
I
I
said
raise
your
hand
quietly
in
your
room
by
yourself.
I
didn't
realize
the
platform.
Would
let
you
actually
answer
in
the
poll.
Yeah
there's
actually
also
a
few
bits
of
information
that
have
changed
since
that
talk
has
recorded
things
move
quite
quickly
in
the
ship
right
in
the
shipwright
world.
A
A
A
But
if
you
are
one
of
those
two
people
or
one
of
those
one
of
the
people
who
agrees
with
those
two
people,
let
me
know
what
what
you
do
in
your
cicd
pipeline,
what
inspired
shipwright
to
be
developed
initially.
Thank
you
matthew.
That's
a
very
good
question,
one
that
I
hope
to
get
the
answer
to
correctly,
because
the
decision
to
make
shipwright
was
predates
my
time
working
on
the
project.
A
Shipwright
has
a
lot
of
its
roots
in
a
project
at
red
hat
called
openshift
builds.
Openshift
builds.
Does
what
it
says.
It's
a
it's
a
tool
service
in
an
openshift
cluster
to
let
you
build
container
images
very
similar
to
how
shipwright
looks
it's,
I'm
going
to
say
this
diplomatically.
It's
a
bit
old,
it's
a
bit.
A
If
I
am
saying
things
that
are
lies,
and
there
are
people
that
who
know
these
things
that
are
able
to
correct
me,
please
do
it's
very
much
a
black
box
and
could
not
be
extended
easily
yeah.
Thank
you.
Adam
yeah,
one
of
the
one
of
the
improvements
that
that
shipwreck
makes
over
openshift
builds.
V1.
Is
that
it's
intended
to
be
extended
through
the
use
of
build
strategies?
A
A
Yes,
sorry,
the
question
from
hiroyuki
is,
I
might
have
missed.
Your
explanation
is
build.
Is
the
build
container
custom
resource
namespace?
The
answer
is
yes,
so
each
namespace,
sorry
each
build
exists
in
the
cluster.
They
can
reference
cluster
scopes
build
strategies.
Those
are
the
only
sort
of
cluster
scope,
things
that
that
shipwreck
provides
right.
Now
you
can
also
have
namespace
build
strategies,
but
yeah
so
builds
and
build
runs
exist
in
namespaces,
which
lets
you
control
our
back
on
them,
control
limits
and
things
like
that
in
the
namespace.
A
Yeah,
I
will.
I
will
once
again
reiterate
my
offer
for
stickers.
I
completely
understand
if
you
don't
feel
comfortable
emailing,
a
stranger
on
the
internet,
but
if
you
do
feel
comfortable
emailing
a
stranger
on
the
internet,
I
will
send
you
a
sticker
through
the
mail
and,
if
not
next
time,
we're
doing
one
of
these
in
person.
A
I
will,
I
will
be
the
one
throwing
stickers
at
everybody,
whether
you,
whether
you
want
them
or
not,
yeah
any
more
any
more
questions,
anything
about
how
shipwright
works,
how
you
might
use
it
where
the
name
comes
from,
I'm
not
actually
sure
where
the
name
comes
from.
Maybe
one
of
the
old
timers
on
the
project
could
could
enlighten
me
on
the
the
origin
of
the
name?
A
A
So
that's
a
good
question.
One
of
the
things
that
I
mentioned
in
the
talk,
and
also
is
something
that
I
think
we
could
go
into
more
detail
here
is
shipwright
intends
to
make
the
local
dev
experience
also
easier
ish.
One
of
the
things
that
we
want
to
do
is
be
able
to,
with
shipwright
running
on
a
cluster,
be
able
to
use
a
local
cli
to
say
upload
my
source
directly
from
here,
without
committing
it
to
a
git
repo
or
putting
it
anywhere
else.
A
Upload
my
source
from
here
to
the
cluster,
build
it
in
the
cluster
stream
logs
back.
Tell
me
how
the
how
the
build
went.
That's
sort
of
a
bridge
experience
between
completely
building
locally
on
docker.
You
know
with
like
docker,
build
on
my
local
machine
and
something
like
shipwright
in
the
sense
that
you
use
it
as
your
ci
cd
tool
where
you
commit
to
a
repo
and
that
triggers
a
being
able
to
iterate
on
code
locally,
send
it
to
a
cluster.
Have
it
build?
A
A
You
know
the
need
for
being
able
to
run
a
tecton
pipeline
from
your
local
source,
yeah
that
that
get
history
and
then,
if,
if
I
feel
ashamed
of
it,
I
go
back
and
and
force
push
over
it,
but
sometimes
I
just
can't.
I
just
can't
bring
myself
to
do
what
I
have
to.
I
have
to
show
my
50
that
didn't
work
that
didn't
work,
try
to
fix,
try
to
fix,
try
to
fix.
A
A
A
I'm
curious
if
people
use
docker
build
in
their
cluster,
so
so
shipwright
and
tekton
are
very
focused
on
running
inside
the
cluster,
and
I
know
there
are
security
pitfalls
with
running
docker
build
inside
of
a
kubernetes
cluster.
Please
don't
do
that.
So
I'm
curious
if
people
have
or
people
that
are
using
docker
build,
are
doing
it
inside
a
kubernetes
cluster
or
if
they
just
do
it
locally.
A
A
A
I
would
love
to
answer
more
questions.
If
anybody
has
any
oh,
how
have
you,
how
did
you
find
the
process
of
applying
to
become
cdf
project?
Thank
you,
matthew.
That's
a
very
good
question.
I've
found
it
to
be
very
easy
so
far.
I
was
a
little
afraid
of
it
because,
because
it's
a
process,
you
know
you're
applying
to
be
approved
for
something,
but
it
turned
out.
It
was
mostly
just
write.
A
markdown
document
fill
out
a
quiz
poll.
A
Quiz
questionnaire
is
probably
the
adult
word
for
it,
and
all
of
the
questions
were
easy.
You
know,
are
you
open
source?
Do
you
have
people
contributing
to
this?
What
are
your?
What
are
your
plans?
What's
your
roadmap
and
luckily
we
we
already
had
those
mainly
the.
I
think
I
mean
I'm
not
sure,
but
I
think
that
the
project
would
have
been
approved
and
and
joined
by
now,
if
it
wasn't
for
the
ongoing
toc
elections
also
currently
happening.
A
So
there
was
a
bit
of
a
a
bit
of
a
snag
with
the
outgoing
toc
members
didn't
want
to
approve
something
before
the
incoming
toc
members
came
in
and
there
was
an
election
ongoing.
So
I
think
we're
mainly
just
in
a
holding
pattern
for
that
definition
now
that
now
that
that's
done,
that
shouldn't
be
an
issue,
but
that's
really
the
only
snag
and
that's
mainly
just
to
sit
and
wait
until
a
new
thing
happens.
So
yeah
the
the
process
has
been
fantastic.
A
A
Yeah,
I
guess
to
to
you
know,
continue
vamping
for
time.
If
you
are
interested
in
learning
more
go
to
shipwright.io,
we
have
community
meetings
on
mondays
at
it's
9
a.m.
Eastern
time
I
promise
we
are
all
very
nice,
come
and
join
us
in
the
shipwright
channel
on
the
kubernetes
slack
we'd
love
to
answer
questions,
arrange
meetings,
give
demos
talk
about
whatever.
Whatever
you
want.
A
A
A
Yeah
any
more
any
more
questions,
we
have
a
few
more
minutes
left
before
this
wraps
up
all
right.
Once
again,
if
you,
if
you
are
comfortable
sending
me
your
email
or
sending
me
an
email
with
your
information,
I
will
send
you
some
stickers
they're
around
here
somewhere.
I
should
well
they're
around
here
somewhere,
but
yeah
otherwise
come
say
hi
in
the
slack
or
in
any
of
the
various
chat
rooms
associated
with
this
event,
come
to
adam
and
enrique's
talk
tomorrow.
It
should
be
great.