On Wed, Feb 7, 2018 at 6:53 PM danielle.90 <[email protected]> wrote:
> Is this design possible with GoCD? > > Our first challenge. > > 1. Splitting the build pipeline up by files within the GIT commit. For > example, For every file in the git commit, we want to start a new, separate > pipeline instance to process each file individually. > No. GoCD respects the atomicity of each material as we see it as critical to good pipeline design. The atomic boundary of a change set sets and expectation for what should reasonably work. I don’t see how pulling a single file out of a change set could result in something that is intended or actually works, so think I might must be misunderstanding what your team is trying to do. and; > > 2. Can we use if/else logic in our pipeline? We need to have logic in our > pipeline that will run different stages based on a condition. I.e. if build > stage fails, go to QA\QC stage, if build passes, go to deploy stage > A GoCD job can execute an optional set of tasks on failure. This is typically for cleanup. But there is no suppprt of conditional stage execution based upon failure. GoCD supports the notion that a broken pipeline should stop the production line. And, of course, GoCD can notify your team when a pipeline fails. -- 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.
