Have the same problem here! I do not want to create a pipeline for each
branch that I want to deploy, even if I can use templates. I want to have a
default branch to trigger the pipeline with and also be able occasionaly
trigger the pipeline with a different ${branch} parameter.
On Thursday, July 23, 2015 at 11:40:58 PM UTC+3, Jared wrote:
>
> I currently have a branch environment variable configured and intend on
> using it with git configured in material so a user can click 'run with
> options' and provide a particular branch to kick off our flow with.
> However, I cannot get the material to work with my ${branch} environment
> variable, the pipeline doesn't seem to kick off at all when I use ${branch}
> and when I use nothing, it assumes master. Is it possible to do what I'm
> trying?
>
--
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.
