Re: Binary build info

[Clayton Coleman]

And coming in 3.11 is an experimental command that lets you add a tar file
as a new layer in an image (or as a new “scratch” image), so it’s even
easier to tar up your source code as an image, and have builds trigger off
the image change.  The command is “oc image append —to= [layer as
tar.gz]” and does not require a local container runtime.

On Sep 10, 2018, at 9:42 AM, Ben Parees  wrote:



On Mon, Sep 10, 2018 at 4:25 AM, Jean-Francois Maury 
wrote:

> Hello,
>
> I have a question about binary builds. Once a binary build has been
> created through the instanciatebinary operation, can we use the clone
> operation to respawn a new build ? Will it use the previous input ?
>

Unfortunately not.  The content you upload to the build is streamed into
that build instance but not preserved anywhere, so it is not possible to
"rerun" that build w/o supplying the binary input again.

If you want a rerunnable binary build I would suggest doing a chained build
in which you:

1) perform a binary build that layers your uploaded content into an image
2) perform the "real" build which uses the "input from an image" feature to
extract the content from the image you produced in (1) and perform the
build.

You can then rerun build (2) at will since the image containing the input
content will still exist.



>
> Thanks
>
> --
>
> JEFF MAURY
>
> Red Hat
>
> 
>
> jma...@redhat.com
> 
> 
> @redhatjobs    redhatjobs
>    @redhatjobs
> 
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Ben Parees | OpenShift

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Binary build info

[Ben Parees]

On Mon, Sep 10, 2018 at 4:25 AM, Jean-Francois Maury 
wrote:

> Hello,
>
> I have a question about binary builds. Once a binary build has been
> created through the instanciatebinary operation, can we use the clone
> operation to respawn a new build ? Will it use the previous input ?
>

Unfortunately not.  The content you upload to the build is streamed into
that build instance but not preserved anywhere, so it is not possible to
"rerun" that build w/o supplying the binary input again.

If you want a rerunnable binary build I would suggest doing a chained build
in which you:

1) perform a binary build that layers your uploaded content into an image
2) perform the "real" build which uses the "input from an image" feature to
extract the content from the image you produced in (1) and perform the
build.

You can then rerun build (2) at will since the image containing the input
content will still exist.



>
> Thanks
>
> --
>
> JEFF MAURY
>
> Red Hat
>
> 
>
> jma...@redhat.com
> 
> 
> @redhatjobs    redhatjobs
>    @redhatjobs
> 
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Binary build info

[Jean-Francois Maury]

Hello,

I have a question about binary builds. Once a binary build has been created
through the instanciatebinary operation, can we use the clone operation to
respawn a new build ? Will it use the previous input ?

Thanks

-- 

JEFF MAURY

Red Hat



jma...@redhat.com


@redhatjobs    redhatjobs
   @redhatjobs

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users