[almighty] Build Service and Build Provider Integration

[Charles Moulliard]

On Tue, Sep 27, 2016 at 10:00 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> Do you mean that you will support what OpenShift has developed (include
>>>>
>>> PipelineStrategy within OpenShift Template BuildConfig) and which is
>> described here -
>> https://docs.openshift.org/latest/architecture/core_concepts
>> /builds_and_image_streams.html#pipeline-build
>>  ?
>> If this is the case, this vision is a bit different from what I propose
>> here: https://redhat-microservices.github.io/docs/#_introduction_2 where
>> a
>> commit pushed in a Git Repo will trigger the pipeline job of Jenkins as a
>> webhook has been configured within Gogs/Gitlab .... Can we align our
>> positions ?
>>
>
> using web hooks is exactly what we expect the pipeline to be triggered by.
>
> >> You are right. OpenShift BuildConfig supports Jenkins Pipeline that we
can trigger using a webhook (https://docs.openshift.org/
latest/dev_guide/builds.html#webhook-triggers).


> afaik the same is used by openshift which then on top add the notion of
> image streams
> - is it that notion you want to avoid/remove ?

>> This is an interesting question that we must address together.


> btw. first time I hear about redhat-microservices.github.io .... care to
> introduce it ?
>

>> The RedHat Microservices Github repo has been created to manage
quickstarts/demos/projects ... that we will develop to promote the
Developer experience around OpenShift for Vert.x, WildFly Swarm, SpringBoot
containers

>
> /max
> http://about.me/maxandersen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160927/8168e5f0/attachment.htm>