On Thu, Jul 14, 2016 at 3:16 AM, Russell Stather <[email protected]>
wrote:

> We are trying to build a plugin to build task branches from bitbucket. We
> have the basics of it working but are struggling to figure out when the
> plugin returns the list of "revisions since", how does go determine which
> revisions to build. We kind of imagined that it would schedule all these
> revisions to be built but it seems to be making arbitrary decisions about
> which one to build...
>

What do you mean, "arbitrary" and what are you returning? You'll need to
make sure that the fingerprint you've chosen is correct too - it should be
something that changes, if the configuration changes.

Here's another idea I've been thinking about, for branch-based builds. I
haven't had the time to make a demo for this: Now that the "config in
repository
<https://docs.google.com/document/d/1_eGZaqIz9ydnYQJ_Xrcb3obXc-T6jIfV_pgZQNCydVk/pub>"
code is in, it might be worth trying it out for this. Suppose you have
pipeline-A1-master.gopipeline.json and it works, then upon a new branch
being created (say, based on a web hook), you can have something which
clones that file and creates pipeline-A1-branch1.gopipeline.json with an
appropriate name for the pipeline.

Now, you'll see two separate pipelines on the dashboard, with their own
lifecycle, rather than having one pipeline for both master and branch
builds. This might be desirable to some.

Once the branch is merged, deleting that newly created file deletes the
pipeline from the dashboard. This can be done automatically as well - based
on a web hook. I'm no fan of branch-based setups, but I think this could
work well for GitHub PRs as well.


Anyway, getting back to your original question: If you can explain it with
a little more detail, Sumanth or someone else here can help.

Cheers,
Aravind

-- 
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.

Reply via email to