I need some help for solving my design issue of GO CD pipeline. 1. I have a main pipeline window, in which I want to define some stages; these stages should hold the new pipeline itself. To provide more clarity--> When the stage to be build, it should start another pipeline which is not inside the mail pipeline. When this stage pipeline is succeeded, it should update the status of the stage (of main pipeline) as success, and then it should trigger the next stage of main pipeline (which turn is nothing but a different pipeline itself). The concepts of fan in and fan out doeswork work here , because in Fan in and Fan out, when the stage is successfully completed, it triggers the diffrent pipeline which has been mapped, but in that case the triggered pipeline is considered as totally separate entity which dont have any association with main pipeline.
Is there any way, to achieve this where we can make a separate pipeline as a stage in main pipeline and update the status of pipeline as the status pf the stage (of main pipeline)? 2. Is there any way, where in we can have separate SVN materials for each stage? For example, I have 3 stages and each stage require a separate SVN repository as material, So instead of making these svn material common for pipeline (which is the structure of GOCD ), I can specify exclusively that This particular svn material should work only for this stage and other stages should be unaffected. Means even the svn commit should only build that stage, and not the other stages in that pipeline . Is there any way for this? Or any workaround for this? Please provide some answered or some trigger points for this design. -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
