Live data from Hacker News

Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

blog.bitbucket.org

61–70 of 73 posts

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#61

It's too bad this is git only for now. Is there any plan to add support for mercurial repositories?

For the beta, only Git repositories are supported. We have plans to support Mercurial in the future.

Great to hear. Looking forward to trying out Pipelines once hg support is ready.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#62

Earlier quoted context omitted.

Serious question... are you using HG because of history, or do people actively choose HG over Git for new projects still? Have used both, they are so close, seems "odd" to go for the way less popular one, barring you have a really old HG repo and haven't bothered to switch.

I prefer mercurial over git and will choose it every time for new projects unless there's some other concern preventing that. Mercurial has a number of features that git never implemented - in particular revsets. I also prefer the hg CLI over the git CLI. Mercurial has sane, concise online help, and a lot of work went into the design of the command-line to be consistent, composable, and made of pieces that do one thi…

Seconding this sentiment. Far, far, prefer hg to git. TortoiseHg blows away the Git UI's as well, IMO. I always feel like i'm poking around in the dark on SourceTree.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#63
post #55

Based on the video, this appears to require Docker [1] I can only with for support of FreeBSD/Jails. [1] https://www.youtube.com/watch?time_continue=122&v=p5KgjeZB8W...

I think they're saying they run the pipeline builds using docker containers. It's how they can build easily based on any branch. Ie. what they use behind-the-scenes, not what you need to be using. Although I'm somewhat doubting myself now...

That's correct. Bitbucket Pipelines uses Docker as an execution environment for builds. However, if the goal of your build is to produce a container, whether Docker or otherwise, Bitbucket Pipelines cannot do that at this time.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#65
post #64

I got beta access, created a custom docker image and got my tests to run however lots of them are failing because I need redis. Is there a way to add Redis server?

Currently not inside pipelines. You could create your own redis and connect to that. Best option is to stub/mock redis in the tests.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#67
post #29

Earlier quoted context omitted.

While we don't have the "recipe" documented in an example repository, GAE does have right knobs and levers that would make it possible to use Bitbucket Pipelines with GAE. Give it a try! And, even if we haven't made an example repository yet, don't rule it out.

I'd love to, I just have no idea where I would even start. Any advice?

My Travis config deploys to App Engine. Have a look at these two files:

https://github.com/GoogleCloudPlatform/golang-samples/blob/m...

https://github.com/GoogleCloudPlatform/golang-samples/blob/m...

Those might be useful for configuring Bitbucket Pipelines.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#70

Will Pipelines remain free for Bitbucket Cloud users?

It's FREE during the beta. We will have more information to share about pricing closer to the general availability time.

Well, here is to hoping it will remain free after the beta.
Post reply on HN