Hi! I'm using Phabricator for project management and I'd like to use GoCD to build changes submitted to code reviews. What I'm trying to achieve is automatic builds on new revisions. Someone submits code to review, Phabricator triggers GoCD pipeline, build succeeds or fails and the results are sent back to Phabricator. According to Phabricator documentation, the best way to handoff changes to CI tools is by using "staging areas" (https://secure.phabricator.com/book/phabricator/article/harbormaster/). Currently, I'm using a manual staging area, which is just an another git repository that gets the submitted changes in a specific manner as devised by Phabricator. Every change in this repository is characterized by two tags - "diff" and "base". It looks like this:
$ git tag phabricator/base/3 phabricator/base/4 phabricator/base/8 phabricator/diff/3 phabricator/diff/4 phabricator/diff/8 By diffing tags with corresponding numbers we can get all commits that went into particular change. I'm thinking about writing a material plugin that would "watch" such repository (staging area) and would get triggered by Phabricator to build requested revisions. I'm new to GoCD and I have only limited experience with Java so I thought I'd ask a few questions before rolling up my sleeves: - Is this a good idea for a material plugin? - Would that anyhow go against things are done in GoCD? - Do you see any immediate drawbacks of this approach? I hope that my intent is clear but if not, please ask, I'll try to elaborate. Thanks, Krzysztof -- 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.
