Avoid external dependencies

[dpordomingo]

Depends on #230 src-d/ci#58 src-d/ci#60 src-d/ci#61

Use src-d/ci:v1 to avoid external dependencies

[dpordomingo]

Travis fails because #230 has not been yet merged

[smacker]

CI is failing on make build-app

[dpordomingo]

@smacker ptal #231 (comment)

[smacker]

aaah. I got it! You can't create this PR on top of #230 because that one for another branch.

[dpordomingo]

@smacker #230 was already merged so this PR build already passed; could you ptal again ;)
thanks!

[smacker]

approved, but I still think it's not a good idea to maintain CI fork inside code-annotation project.

[smacker]

@bzz maybe you also want to take a look

[bzz]

approved, but I still think it's not a good idea to maintain CI fork inside code-annotation project.

totally see @smacker point and agree

Sorry, I must have missed that, but what was the original reason for having https://github.com/src-d/code-annotation/tree/ci ?

[dpordomingo]

@bzz since we cannot use srcd/ci:v1, I found the following alternatives:

• (a) keep relying on carlosms/ci:add-drone-v1, dependency outside the company; wich can be deleted without our control and which requires extra overhead for maintenance,
• (b) push this new branch to a new one into srcd/ci, for example, srcd/ci:v1.1-candidate; I'm not sure if we should push our stuff there, and use it instead of srcd/ci:v1
• (c) try to merge the new features into srcd/ci:v1 → Set VERSION for Drone CI ci#58 Replace '/' char from version ci#60 waiting since Feb 28th
• (d) create our own srcd/apps-ci → please, no,
• (e) keep this new branch inside this repo

I choose (e) until (c) is unblocked, what would you purpose?

[dpordomingo]

internal branch (e) is no longer needed since src-d/ci#58 src-d/ci#60 src-d/ci#61 PRs were just merged