Re: Go Dashboard for other projects

[Dmitry Vyukov]

On Thu, Sep 12, 2013 at 10:00 PM, Chris Manghane <cm...@google.com> wrote:
>
>
>
> On Thu, Sep 12, 2013 at 10:25 AM, Dmitry Vyukov <dvy...@google.com> wrote:
>>
>> On Thu, Sep 12, 2013 at 9:17 PM, Chris Manghane <cm...@google.com> wrote:
>> > Hi Dmitry,
>> >
>> > I'd say it's almost there depending on how much of the dashboard
>> > functionality you want. I added changes to the dashboard so that it uses
>> > the
>> > same VCS-specific logic as `go get` does. Currently, it's able to build
>> > gccgo (by pulling down the GCC svn repo and the googlecode repo for
>> > gofrontend) with a bit of direction, but it's far from automatic with
>> > SVN.
>> > On the other hand, they should work pretty well for the dashboard if you
>> > have control over the repo and can take advantage of the meta
>> > go-imports. If
>> > we add a few checks, it should work just fine for Git repos, though.
>>
>>
>> Thanks!
>> What is "go-imports"?
>
>
> I might be calling them by the wrong name, but I was referring to the `<meta
> name="go-imports">` mentioned here: http://golang.org/cmd/go/.
>
>>
>> I would like to use build dashboard for a completely different
>> project, not related to golang in any way. I want to setup a different
>> appengine app and write own all.bash script. Ideally, that's all I
>> need to do, but I have not tried.
>
>
> You might be able to do this a lot easier by using the VCS package added to
> go.tools
> (https://code.google.com/p/go/source/browse?repo=tools#hg%2Fgo%2Fvcs) and
> rolling your own dashboard workflow.

+golang-dev

that's what I want to avoid. I want to reuse dashboard app and the
local builder as well.