►
From YouTube: SIG Interoperability Meeting - Sept. 1, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
Okay,
you
should,
I
guess,
I'm
not
at
home.
Actually,
I'm
in
the
sun.
B
Yeah
for
a
hakka
garden,
so
I
found
a
spot.
A
B
Great,
so
I
will
assume
there
are
some
basic
housekeeping
things
to
be
taken
care
of
at
the
beginning.
A
A
A
I
am
just
adding
the
zoom
information
to
the
channel
in
case
folks.
B
Yes,
lucerne
usually
runs
hacker
garden
meetings
on
the
first
first
date
of
the
month,
so
that's
today
and
yesterday
we
had
also
hager
got
in
basel,
which
runs
on
the
last
wednesday
of
the
month
nice.
So
we
got
back-to-back
sessions.
B
Yeah
there
there
is
one
box,
there's
not
a
bug.
It's
a
feature
that
I
really
want
to
work
on.
It's
a
little
bit
big,
that's
something
that
you
can
hack
in
like
three
hours.
If
you
usually
do
this
kind
of
sessions
for
at
most
four
hours,
but
we'll
see
and
and
the
whole
point
is
just
to
work
on
an
open
source
break
of
your
choosing
and
help
that
particular
community
with
a
contribution.
A
A
Okay,
well,
let's
go
ahead
and
get
started.
We
don't
have
a
whole
lot
to
talk
about
before
we
go
ahead
and
present.
This
will
all
be
recorded,
so
we'll
be
able
to
share
with
folks
that
weren't
able
to
make
it
today.
A
Here
is
the
agenda
that
we
have
right
now
I,
as
far
as
open
action
items,
I
don't
think
we
have
anything
right
now
we
did
get.
Let's
take
a
look
at
this.
We
did
get
a
place
for
the
tools
resources
that
did
get
added
in
here
in
this
section
in
the
this
is
the
production
site,
but
the
preview
site
there's
an
area
there.
That
includes
our
tools.
A
A
A
I
added
a
section
of
these
notes
a
little
further
up
with
upcoming
talks,
so
that
we
could
help
with
some
scheduling
bits
right
there.
Awesome
kubella
is
interested
in
talking
in
october,
which
I'm
very
excited
about
cool.
A
A
B
Let's
see
if
I
can
share
the
screen
desktop
yes,
here
we
go
all
right,
so
you
should
be
seeing
our
terminal
window.
Okay,
so
well,
first
off!
Thank
you
very
much
for
your
time
and
there
are
many
things
that
I
can
say
about
this
particular
product.
I'm
just
going
to
take
about
30
minutes
or
so,
and
the
idea
is
that
I
will
describe
the
problem
that
I
encounter
before
this
project
existed.
B
B
I've
been
doing
this
for
the
past
18
years
now
and
most
of
my
experience
is
related
to
the
java
sphere,
java
languages,
scrubians
or
many
others
and
but
the
product
that
I'm
going
to
describe
today,
even
though
it
was
born
in
the
jbm
and
it's
based
on
java.
It
can
work
with
any
other
project
that
may
not
necessarily
be
java.
B
Many
of
those
tools
are
either
command
line
tools
or
desktop
applications,
so
that
was,
I
writing
a
desktop
application
using
my
favorable
tools
and
my
favorite
libraries,
and
once
I
finish
that
task
well,
the
next
thing
is
set
it
up
free
so
that
users
or
consumers
may
find
it
and
and
just
make
use
of
it
right
and
the
well
as
a
regular
developer.
It's
very
easy
to
think.
Well,
here's
the
link
to
my
git
repository
and
here
are
the
instructions
on
how
you
can
build,
save
binary
and
off.
B
You
go
be
merry,
but
that
actually
doesn't
work
very
well
for
our
end
users
for
our
customers,
because
what
they
will
expect
would
be
to
download
the
binary
or
consume
the
binary
in
the
typical
way
that
they
used
to.
So,
if
you
are
on
a
mac,
you
might
prefer
to
use
macports
or
homebrew
to
download
and
install
a
binary
or
a
cask
using
a
an
ui
application.
B
If
you're
on
linux,
it
may
be
a
flat
pack
or
snapcrap
or
rpm
deviant
something
else,
and
then
from
windows
you
might
prefer
winged
or
similar
fix
right,
it's
possible
to
do
this
for
java.
It's
just
that
writing
the
integration
for
each
one
of
those
package,
managers
or
deployment
options
takes
a
while,
and
you
kind
of
have
to
become
a
little
bit
of
an
expert
only
have
to
read
a
lot
of
documentation
to
really
get
going
with
each
one
of
those.
So
when
I
was,
I
was
finished
with
this
application.
B
I
have
no
idea
how
to
make
this
work.
Your
users
will
expect
more
things
being
besides
having
access
to
the
source
repository
and
instruction
how
to
build
this
binder.
Okay.
So
I
took
a
pause
for
a
moment
and
started
working
with
other
languages
and,
of
course,
like
many
of
you,
I
gravitated
towards
the
goal
language
and
I
started
again
writing
command
line
applications,
and
I
found
I
faced
myself
in
the
same
problem
once
I
have
a
command
line
tool.
How
do
I
make
sure
that
users
can
consume
it?
B
Okay,
but
luckily
for
me
in
the
case
of
go,
there
is
already
a
project
that
gives
you
that
it's
called
go
release,
so
your
child
got
released
with
a
simple
configuration
file.
What
kind
of
binaries
you
want
to
compile
and
where
you
would
like
to
distribute
these
binaries,
so
it
may
be
homebrew
snapcraft,
maybe
something
else
you
might
even
create
docker
images,
and
the
additional
thing
that
will
happen
is
that
gold
releaser
will
calculate
a
change
location.
B
All
your
commit
history,
push
a
gift
release,
sign
files
with
other
pgp
or
six
stars
cosign,
and
so
many
other
bells
and
wishes.
The
point
is
that
when
I
saw
this
I
said
wow.
This
is
great.
This
is
what
I
really
like
to
use
for
my
go
projects,
but
I
would
also
would
like
to
do
this
for
my
java
projects,
but
there
was
no
option
for
that.
B
B
So
what
if
there
was
a
way
to
use
both
projects,
or
at
least
the
ideas
about
projects,
how
goal
release
works
and
how
jbank
solved
the
problems
for
java,
but
together
and
that's
exactly
how
this
project
jvlisser
came
out
to
be
so?
What
it
is,
is
it's
a
simple
tool
that
you
supply
the
binaries
with
the
build
tools
that
you
currently
use
and
now
I'm
showing
not
just
java
build
tools,
but
I'm
also
showing
non-java
b2.
So
it
may
be
node
application.
Maybe
it's
a
cli,
maybe
it's
a
rust
application.
B
It
can
even
be
elixir
bash
or
something
it
doesn't
matter,
whatever
build
tool
that
you
use
today.
You
continue
to
use
it
to
create
the
binaries
you
want
to
release
and
then,
alongside
those
binaries,
you
pass
an
additional
model
file,
some
sort
of
configuration
to
the
general
releaser
tool
and
as
benefit
you
can
create
git
releases
in
popular
services.
Github
gitlab
gita,
the
free
versions
and
the
editor
privations
is
the
same,
at
least
from
the
point
of
view,
the
tool
you
can
create.
B
If
you
want
to
files
that
will
talk
to
the
different
package
managers
for
which
we
have
plenty
of
them,
we'll
see
there
in
a
moment,
and
you
can
also
announce
when
a
release
is
posted.
You
can
go
to
twitter,
you
can
go
to
sulip.
Basically
man,
you
can
send
an
email.
You
can
do
a
lot
of
things.
B
How
does
it
do
it?
Well,
it
has
a
series
of
commands
that
you
can
invoke
if
you
look
at
the
top
one,
the
orange
one.
This
performs
everything
this
will
create
a
git
release,
which
is
the
blue
column.
It
will
create
all
the
files
required
for
the
package
manager,
which
is
the
the
purple
call
in
the
mill.
B
Animal
also
announced
your
project
in
case
that
you
have
any
announces,
and
if
you
were
to
look
just
on
the
blue
column,
these
will
be
the
different
steps
that
you
must
follow,
or
at
least
the
tool
will
follow
will
create
a
changelog
for
you
calculate
checksums
for
all
particular
binaries.
You
have
configured
if
you
have
configured
any
with
different
algorithms.
B
You
can
sign
those
binaries
with
pgp
cosine,
something
else
you
can
upload
to
additional
places
such
as
amazon
s3
or
an
http
server,
sftp
many
different
locations
and
finally
create
a
git
release
with
all
the
assets
and
whatnot.
So
this
is
exactly
what
it
does
in
terms
of
integration
already
mentioned
a
few,
but
this
is
the
full
gamut
that
we
have
at
the
moment.
B
If
you
want
to
release
to
a
git
service,
github
github
enterprise,
gitlab,
github
enterprise,
your
own
custom,
gta
instance
running
whenever
you
want
code
work
which
is
based
on
gta
or
if
there's
none
of
this,
you
can
still
at
least
create
a
tag.
Some
sort
interact
a
little
bit
with
the
git
backend,
but
there
are
some
features
that
I'll
be
missing.
For
example,
creating
a
git
release
such
as
what
github
and
gitlab
understand
is
not
possible
in
git
services
such
as
bitbucket.
B
In
terms
of
package
managers,
there
are
12
of
them,
so
there's
app
image
for
linux.
As
for
linux
and
mac
home
report,
mac
and
linux,
chocolaty
for
windows,
docker
images
flatback
for
linux
to
jbank,
which
works
for
pretty
much
any
platform,
markzware
store
for
osx
scope
is
like
homebrew,
but
for
windows.
B
B
These
are
all
the
ones
that
are
currently
listed
and
if
there's
something
that
is
not
listed
here,
but
it
uses
incoming
webhooks
or
a
regular
http
post
output
that
will
support
us
through
the
http
or
the
webhooks
announcer
in
terms
of
inputs.
The
things
that
you
built
already
today
that
you
could
release
with
this
tool.
B
We
have
binary
distributions
again.
These
binaries
can
be
created
with
any
any
any
kind
of
language
that
you're
currently
using
today,
and
you
have
to
sip
them
or
tar
or
create
a
tar
file
for
these
institutions.
Specifically,
you
put
the
executable
or
the
script
in
the
bin
directory.
There
may
be
a
config
file
or
a
conf
directory,
etc.
Leave
whatever
is
all
those
additional
files
or
resources
required
by
the
application.
B
In
order
to
run,
you
may
create
a
single
jar
on
an
uber
chart,
it's
very
typical
in
java
world
to
have
one
single
jar
file
that
contains
all
dependencies
and
it's
executable
again
in
the
java
world.
We
have
something
called
jailing
distributions.
This
is
a
java
runtime
that
is
bundled
with
your
production
code,
so
you
don't
have
to
tell
your
customers
hey,
install
that
particular
version
of
java
in
order
to
run
the
application.
Just
comes
everything
within
or
you
may
create
a
native
executable
for
a
particular
platform
using
rbi
and
native
image.
B
B
So
if
you
use
java
releaser
and
just
a
passion
number,
that's
just
the
production
code
and
you
need
a
java
runtime
to
run
it
or
you
can
use
there
really
the
standalone
version
which
bundles
a
java
runtime
so
just
unzip
and
run
or
you
can
use
an
executable
version.
The
native
one
created
graphic
and
again
it's
just
unzip
and
run
there's
no
need
for
java
to
be
installed
on
your
system.
B
For
linux,
we
have
a
handful
more
of
package
managers.
We
have
additionally
to
the
previous
one
that
we
mentioned.
We
have,
we
have
flat
pack.
We
also
have
an
image
and
rpm
coming
from
fedora,
copper
and
likely
like
we
saw
before
you
can
download
specific
files,
and
in
this
case,
besides
just
regular
linux
compiled
with
galaxy,
we
also
support
linux
compiled
with
muscles.
B
So
this
is
what
you
typically
will
run
on:
linux
alpine
and
finally
on
windows,
same
installers
or
same
package
managers
as
before,
as
the
command
jbag
in
this
case
scoop
or
download
a
particular
version
that
suits
your
specific
setup.
You
want
to
use
just
the
production
code
or
the
standalone
native.
There
are
so
many
different
choices.
B
You
may
also
run
the
cli
as
a
set
of
docker
images.
Jerry
seriously
is
based
on
ubuntu
and
the
other
because
of
the
name
is
based
on
linux
alpine.
So,
whichever
would
you
want
to
use
now
based
on
all
these
options,
and
given
that
geralizer
in
itself
is
a
java
application
and
a
cli
tool,
you
might
be
wondering,
does
chair
release
a
release
itself
as
some
it
so
happens?
That
is
actually
the
case
since
the
first
release.
B
As
a
matter
of
fact,
we
have
set
up
the
build
in
such
case
that
whenever
we
push
a
commit
to
the
main
branch
that
triggers
a
new
snapshot,
build
and
ends
up
with
something
that
we
like
to
call
the
early
access
release.
So
many
of
these
binaries
that
I
showcased
before
are
available
to
you
on
every
push
domain
and
when
we
want
to
release
unstable
release,
we
just
click
on
we
just
trigger
at
the
ui
on
github,
where
the
break
is
hosted
and
that
builds
everything
with
the
same
configuration
file.
B
So
you
may
have
early
access
or
rolling
early
access
snapshots
naturally
releases
how
you
want
to
call
it
and
stable
releases
with
the
same
tool
with
the
same
configuration
or,
if
anything,
fails
or
you
want
to
use.
The
very
bare
bones
thing
is
just
as
long
as
you
have
java
8
running
somewhere,
you
can
download
a
specific
uber
jar
using
that
script
called
getreleaser.java
run.
It
does
launch
the
the
specific
version
and
then
just
run
it
like
any
other
java
over
jar,
and
this
will
come
in
handy
in
a
few
moments.
B
When
we
talk
about
continuous
integration.
So
far,
we
have
discussed
how
to
run
the
command
as
as
a
command
line
tool,
but
there's
also
integrations
in
the
case
of
the
java
space.
Okay,
because
this
is
where
the
tool
was
born,
you
can
run
it
as
a
maven
plugin
as
an
apache
end
task
or
as
a
gradle
plugin.
B
B
There
is
recently
we
had
an
integration
to
dagger
and
many
of
these
services.
What
they
will
do
is
just
locate
either
the
docker
images
download
the
uber
jar
or
locate
the
binary
that
runs
for
that
particular
platform,
unpack
and
run
it's
just
as
simple
as
that,
if
any
of
those
or
if
there's
any
other
ci
service.
That
is
not
mentioned
here,
and
if
you
will
be
interested
to
know
more
about
that,
we
just
get
in
touch
with
us.
B
So
with
that
in
mind,
this
is
basically
the
the
the
the
whole
theory.
Let
me
show
you
a
quick
set
of
examples
very
very
quickly,
so
I
have
here
on
github
a
very
basic
maven
project.
It
could
be
anything
I
decided
to
make
it
maven,
and
this
is
a
very
trivial
command
line
application.
You
run
it
and
it
says
hello
world.
B
If
you
look
at
the
commits,
oh,
not
that
one,
the
the
commit
messages
there's
just
one
liners,
they
have
a
prefix
and
some
text.
It
so
happens
that
these
prefixes
match
a
convention
called
conventional
commits.
You
can
use
any
format
that
you
want
any
conventions,
and
once
you
do,
you
may
have
additional
benefits
when
using
your
list,
it
doesn't
have
to
be
commercial
commits.
It
has
to
be
your
own
conventions
and
you
tell
your
user
what
to
do
with
those
conditions.
B
B
That's
not
what
I
want
anyway,
I
can,
let's
check
which
version
of
the
journeys
that
I
have
jared
isa.
I'm
running
the
latest
version
released
just
last
weekend
and
you
can
install
it
many
ways.
I
prefer
to
install
it
using
sdk
man
and
that's
how
we
can
tell
that
all
that's
all
the
different
versions
that
I
can
have
access
to.
So
that's
pretty
good.
So
again,
without
having
any
binaries
and
just
having
access
to
this
source
code,
I'm
going
to
say
the
following:
generalism
release
autoconfig.
B
So
I'm
going
to
ask
you
alisa
to
read
information
from
the
git
repository.
So
what
is
the
remote
name?
What
is
the
default
branch?
What's
the
name
of
the
repository
and
all
those
things,
and
I'm
also
going
to
tell
it
release
project
version,
zero,
nine,
zero,
just
give
it
a
name
or
a
number,
and
let's
see
what
happens
well,
cherry
reserve
has
not
been
properly
configured.
We
have
something
that
is
missing.
This
particular
version,
so
we're
missing
a
project.
Copyright,
I'm
missing
a
project,
description.
B
Okay,
so
we
pass
those
now
project
copyright
and
we
say
that
will
be
2022
and
my
name
and
the
project
description
will
be.
I
don't
know
app
for
whatever
it
is
so
now
we
know
this.
Oh
it's
not
copyright!
Sorry!
I
think
I've
changed
something
recently
and
maybe
I
can
change
to
a
different
portion
of
their
demo.
Yep
hold
on
a
second
generally,
sir
release.
B
B
B
The
model
this
model
tells
me
some
metadata
about
the
project
that
may
be
reused
by
many
different
places,
so,
for
example,
the
package
managers
or
when
you
announce
a
project
or
when
you
assemble
their
project,
so
some
basic
information,
that's
the
name
of
the
project
description
authors
license.
Copyright
may
be
inferred
by
the
authors
and
the
inception
here
and
some
other
properties.
B
It
also
tells
chair
lisa
that
I
want
to
release
the
github
for
every
lease
I
want
to
override
and
maybe
also
be
able
to
update
assets.
I
want
to
sign
any
commits
or
tags
that
get
created.
I
will
suppose
to
a
discussion
category
with
this
name
and
some
basic
conventions
on
how
I'm
going
to
format
the
change
logs
notice
that
I
say
something
like
conventional
commits.
If
I
didn't
do
this,
I
would
have
to
specify
a
set
of
rules
on
how
I
would
like
the
changes
to
be
formatted.
B
I
would
like
to
sign
the
artifacts.
I
would
like
to
also
create
a
homebrew
formula,
and
these
are
the
two
artifacts
that
are
making
use
of
a
zip
file
and
a
tor
file.
Those
will
be
created
using
my
extender,
build
tool
in
this
case,
we'll
be
maven
and
notice
that
this
file
uses
some
sort
of
a
special
name.
This
is
actually
mustache
templates,
so
for
those
of
you
that
have
seen
front-end
development
mustache
has
been
very
popular
over
there
and
we
use
them
as
variables
or
value
placeholders.
B
B
So
when
I
go
here
and
do
a
refresh
notice
that
now
there
is
a
release
here,
I
click
on
that
one,
and
I
get
this
change
log
and
all
these
categories
appear
because
of
the
conventions
and
the
prefixes
that
I'm
following
there
is
a
here,
are
all
the
assets
and
there's
a
button
here.
That
says
john
discussion
because
remember
that
I
put
a
discussion
category
that
goes
into
announcements
and
it
goes
right
there,
but
it
doesn't
stop
here.
B
Remember
that
I
also
posted
a
homebrew
formula,
which
was
just
updated
a
moment
ago,
and
here
we
go.
This
is
the
homebrew
formula
that
if
you
go
in
into
the
command
line
and
say
brew,
install
I'll
be
right
up
app,
then
it
will
solve
a
very
basic
cli.
Now
this
is
the
very
basic
of
the
tool
it
works
on
github,
gitlab
and
the
others.
I
can
show
you
if
I,
if,
if
I
wanted,
I
can
show
you
how
these
projects,
I
believe,
can
the
address
is
gitlab.com.
B
B
So
if,
for
whatever
reason,
you
need
to
have
a
mirror
or
your
sources
in
github
and
gitlab,
and
you
want
to
have
releases,
then
you
can
use
it
almost
with
the
same
release
model
file
or
if,
for
whatever
reason
you
need
to
fully
migrate
from
one
to
the
other,
then
you
can
keep
having
releases
just
by
updating.
Instead
of
saying
I
want
to
release
the
github
I
just
released
to
gitlab
and
boom.
There
you
go.
B
There
are
more
stuff
that
you
can
see
later.
For
example,
the
other
project
is
hosted
on
github
our
releases.
As
said
mentioned
earlier.
We
make
them
using
journalism
itself,
so
we
follow
our
own
conventions,
how
to
generate
change
logs
and
there's
a
bunch
of
binaries
and
that
are
added
as
assets
and
all
of
these
are
generated
by
your
eraser
itself,
based
on
just
four
basic
binaries.
So
there
are
many
things
that
can
happen.
B
The
project
is
hosted
on
github.
The
project
has
its
own
website
and
there's
plenty
of
documentation
on
how
you
may
use
the
tool
for
it
on
advantage.
There's
the
guides
for
all
the
continuous
integrations
one.
For
example,
if
we
were
to
look
at
k-file
actions,
it
tells
you
all
the
settings
that
you
may
use
to
configure
and
run
releases
on
github.
B
If
you
want
to
use
dagger,
which
is
the
most
recent
one
well
here
we
go
just
use
the
alpha
package
for
jeff
lisa
and
configure
your
jagger
pipeline
and
off.
You
go
many
other
things
that
you
can
do
here
and
you
can
also
search
for
markets
so
now
going
to
the
slides
and
we're
almost
at
the
end
of
the
presentation.
B
So
what's
coming
on
the
future,
I
did
mention
bitbucket
before
an
atlassian
and
that's
something
that
people
have
been
asking
us
for
supporting
that's
something
that
we'll
be
looking
in
the
future
there's
also
astro
devops.
There
are
so
many
other
git
services
out
there
that
we
may
support
in
the
future
other
packages
such
as
winget,
which
is
quite
popular
on
windows.
B
It's
just
that
when
you
use
the
tool
you
have
to
have
an
additional
configuration
setting
to
say
map
certain
values
that
java
understands,
for
example,
when
it
resolves
the
platform
name,
which
is
linux,
x86
64
for
rust
and
elixir.
They
prefer
something
that
is
called
the
target
triplet,
which
is
a
vendor
a
cpu
and
our
architecture.
So
we
have
to
do
some
translation
right
now.
You
have
to
do
it
manually.
B
It's
part
of
the
dsl
in
that
goes
in
the
model
file,
but
in
the
future
you
will
simply
be
able
to
say
I
want
this
product
to
be
seen
as
a
ros
project.
So
those
translations
happen
automatically
and
anything
else
that
roster
elixir
might
require.
In
order
to
do
proper
releases,
then
charizard
will
also
figure
out
a
way
to
support
those
things.
B
So
I
have
some
links
that
I
already
showed
you,
the
the
website
is
clarissa.org
and
the
project
is
hosted
on
github.
We
have
an
open
collective
for
sponsorship
and
we
also
have
a
twitter
account,
like
most
people
do
nowadays
and
most
projects
where
we
post
announcements
or
things
that
are
coming
up
on
projects
that
we
have
found
that
are
interesting
and
that
use
the
tool
or
anything
that
is
related
to
the
the
project
itself.
B
B
New
features
bug
fixes,
so
there's
there's
a
link
for
the
issue
tracker
and
there's
a
link
for
the
discussions
where
just
pretty
much
hang
out
and
solve
any
questions
that
users
may
have.
So
with
that.
I
thank
you
again
very
much
for
your
time.
A
B
Yes,
for
example,
in
the
javaspace
there
is
a
very
popular
framework
called
quarkus.
They
have
a
cli
tool
and
they
use
geralizer
to
publish
their
cli
tool.
There
is
a
bunch
of
for
whatever
reason
journalism
is
quite
popular
with
a
graphic
native
images
projects,
so
there
are
like
four
or
five
different
projects
like
this.
Some
of
them
connect
to
kafka.
There
is
some
project
called
casey
cuddle,
kcctl
that
the
name
is
inspired
by
cube
cuddle.
I
this.
I
guess
this
is
always
a
problem.
B
How
do
you
should
pronounce
it
or
I'll
say
cuddle?
So
what
this
thing
does
is
connect
to
cat
connect.
It's
a
command
line,
application
that
that
interacts
with
kafka
and
it's
written
in
java
and
uses
ground
native
image
and
uses
quakers
as
well.
It's
actually
the
first
early
adapter
and
there
are
other
projects
that
either
build
with
a
spring
or
just
plain
java
and
native
images
that
use
it.
B
A
B
It
depends
if
you
use
the
cli,
it
is
suspected
that
the
build
tool
creates
the
artifacts,
and
then
you
will
invoke
the
java
lisa
on
its
own.
If
you
use
it
as
a
maven
plugin,
then
you
may
use
travelizer
as
part
of
the
overall
maven
execution
session.
As
part
of
the
reaction,
there
is
one
feature
that
was
added
recently
to
jerry
said
is
called
execution
hooks
that
allows
you
to
invoke
external
commands
before
and
after
the
execution
on
each
one
of
the
steps.
So,
as
we
saw
change,
log
package
publish
all
those.
B
So
if,
for
some
reason
you
wanted
to
make
maven
to
be
run
before
jolisa
and
just
one
command,
you
could
hook
up
maven
as
an
as
an
execution
to
hook
on
giarlissa
and
simply
say
generalizer
release,
and
this
will
ensure
that
maven
is
wrong.
First
and
then
jurisa
performs
its
his
goals
or
does
its
behavior.
A
One
of
the
experiences
that
I've
had
in
java
package
land
has
been
triggering
my
release
and
having
some
portion
of
the
workflow
fail,
which
leaves
me
in
a
state
where
I've
generated
a
release,
but
maybe
it
doesn't
build
or
something
along
those
lines.
How
does
how
does
j
releaser
handle
failures.
B
In
this
case
specific
case
for
package
managers,
there
is
a
flag
called
continuing
error,
so
if,
for
some
reason,
you're
building
a
docker
image
and
the
git
release
has
already
been
posted
and
you
want
to
continue
publishing
the
package
managers
and
one
of
them
fails,
you
don't
want
the
whole
release
process
to
fail.
You
can
simply
say
well
if
this
particular
package
manager
were
to
fail.
B
B
It's
actually
both
depending
on
your
target,
for
example,
sdk
man
is,
is
just
something
that
tells
you
where
you
can
download
things
and
handle
versions
on
installers.
But
in
this
case
a
chocolat
is
a
proper
package
manager
that
relies
on
nougats
and
jelliser
can
define
the
manifest
required
to
to
build
those
nugets,
and
you
still
have
to
invoke
the
choco
command.
You
know
to
build
and
publish.
A
So
let
me
see
if
I
have
this
right:
maybe
we
differentiate
between
language,
so
j
releaser
doesn't
help
with
language
package
management
pack
of
package
managers,
but
it
expects
that
you've
already
pushed
to
pipei
or
j
to
maven
central
or
something
like
that.
But
then,
when
you
get
to
operating
system
level,
package
managers,
that's
where,
like
j
releaser,
does
tons
of
work.
B
Is
that
right,
yeah
publication
to
maybe
central
is
optional.
As
a
matter
of
fact,
you
can
work
with
the
artifacts
that
you
may
have
locally
on.
Whenever
you
build
the
things,
it
also
has
an
option
to
download
artifacts
as
an
extra
step,
so,
regardless
of
your
operating
system,
you're
able
to
download
assets
templates
or
so
many
other
things
that
are
required
in
order
for
the
release
to
happen,
and
this
will
be
independently
of
your
build
tool
of
choice.
B
All
right
well,
thank
you
very
much
for
the
questions,
and
it
goes
without
saying
that
I'm
quite
excited
about
this
project
has
been
proved
to
be
very
useful
to
my
the
the
own
projects
that
I
that
I
have
and
the
own
projects
that
I
work
with
other
people
and
the
early
adopters
that
I've
been
using
the
project,
and
I
really
would
like
to
drive
home
the
point
that
just
being
able
to
run
things
luckily
as
much
as
you
can
and
then
just
push
it
to
ci
to
remote
and
just
have
it.
A
Yeah
thanks
andres.
This
was
really
really
cool
presentation,
something
I
want
to
play
with
a
little
bit
on
the
side
myself,
especially
with
integrating
with
ci
I'm
interested
in
that.
So
any
last
questions
from
anyone
else
before
we
wrap
it
up.