viktorbenei

Got it, thanks for the feedback, I'll add it for an internal discussion with the team, much appreciated! :)

Bitrise.io ! ;) (CTO here)

Added bonus: most of our tools are open source, e.g. you can use the same runner which we use to run the builds on our build VMs ( https://www.bitrise.io/cli ) to run the bitrise config/build anywhere the CLI can run. Happy to answer any questions!

Bitrise can do that too, and has Xamarin support as well - https://www.bitrise.io/

(I'm the CTO there)

Bitrise.io | Budapest (Hungary) | Full-time | Onsite

Bitrise is a Continuous Integration and Delivery platform focusing on mobile development. We help developers to automate their every-day tasks so they can go back to building great apps and have more time for their ideas. We'd like to create an ecosystem for software developers which they can use to build, test and distribute their apps in a way that it feels natural and fun. We take being open very seriously and we love to automate everything!

We'll soon update our jobs site ( https://www.bitrise.io/job ), looking for right now:

- Web Dev (both front & backend positions, Senior & Junior too)

- Tooling: work on our open source tools which make Bitrise awesome ( https://www.bitrise.io/cli )

- Developer Experience (DX) Engineer

- Infra Engineer

And a lot more. If you're interested in working for a YC company in Europe, feel free to ping us, there's always a place for great devs in our team ;)

I do the same, and in addition the phone sits face down on my desk, to prevent me getting distracted by the notification led.

Bitrise! Both the open source CLI (https://www.bitrise.io/cli) and bitrise.io (hosted service).

I'm obviously biased (CTO and Co-founder), but I love automation, that's why I'm part of the bitrise team in the first place ;)

The CLI is similar to something like rake, but the config lives in a single file which can be moved anywhere, and you can get a list of available "tasks" (workflows in the bitrise terminology) by running `bitrise workflows` or `bitrise run` without any parameter.

There's also an open source editor (UI) available for it (https://discuss.bitrise.io/t/offline-workflow-editor-workflo...), which is now part of the "base plugins" which gets installed by the Bitrise CLI. It's also really light weight, as the CLI is a single binary distribution (written in Go).

Great idea! We're working on the public API right now, after that native apps would be awesome!

Feel free to create a feature request at https://discuss.bitrise.io/c/feature-request with your notes about what you'd like to see in the apps! ;)

Thank you - we're determined to keep providing the best solution, YC will definitely help in that ;)

Thanks for the kind words, it means a lot to us! :)

Thank you for the kind words, we try to do our best! ;)

We definitely agree and will focus on it more in the future!

P.S.: if you want to you can do it, we CI/CD the bitrise.io website/servers through bitrise too, but you will have to use the Script step extensively right now

Sure, the CLI supports both Mac and Linux (we plan to support Windows in the future). As our Linux build environments are Ubuntu containers, you should have the best support there (actually on any Debian based distro, auto dependency management is only implemented for `apt` right now for example).

Couple of additional things:

- Local CLI / runner: http://devcenter.bitrise.io/bitrise-cli/

- Trigger Map, to configure what to build when: http://devcenter.bitrise.io/webhooks/trigger-map/

- Linux/Android image available as an open Docker container: http://devcenter.bitrise.io/docker/run-your-build-locally-in...

- Open source, offline workflow editor (UI, beta): https://discuss.bitrise.io/t/offline-workflow-editor-workflo...

- (GitHub,) Bitbucket and GitLab (full API) support, and additional webhook support for Slack (trigger a build from Slack), visualstudio.com, gogs, deveo git repos through the open source Webhook processor (https://github.com/bitrise-io/bitrise-webhooks) - the last two were contributed by the community ;)

Just some notes for the CLI:

- It's the same runner which is used for running the builds on https://www.bitrise.io/

- You can run the same build config (YML) with it both on https://www.bitrise.io/ and on your Mac/Linux

- CLI [home page](https://www.bitrise.io/cli) | [docs](http://devcenter.bitrise.io/bitrise-cli/) | [GitHub](https://github.com/bitrise-io/bitrise)

(disclaimer: CTO here)

Do you have any issue with Bitrise? Just curious (CTO here)

You can use fastlane on Bitrise.io if you want to, and you can use the Bitrise CLI locally (https://www.bitrise.io/cli), similar to fastlane.

https://www.bitrise.io/ ;)

Well, if they would provide an easy way to run a virtualized MacOS, something what Microsoft does with their vagrant machines (Windows with different Internet Explorer versions) would go a long way.

https://developer.microsoft.com/en-us/microsoft-edge/tools/v...

Quick, simple and easy to run and test with.

I completely agree, just wanted to add that there are options for iOS / macOS CI in the cloud, like ours ( https://www.bitrise.io - we have a free plan for freelancers ) or Travis / Circle. Not on commodity hardware of course, and you most likely won't have macOS as an option on AWS/GCE/Azure in the near future either.. (we use a private vSphere system right now)

If you're interested in iOS & Android dev / automation tools you should check out https://fastlane-tools and https://www.bitrise.io/cli . The two projects have a fair amount of overlap, but handle a couple of key concept differently (e.g. built in modules in fastlane vs decentralized step library in bitrise). I'm more than happy to help you get started if you would decide to contribute to bitrise

Exactly what I needed, thank you!

The tab groups feature was pretty much the only reason why I used Firefox as my primary work browser, as it managed the separation of projects / topics..

Does anyone know any alternatives (for Firefox or other browser) which can help with the visual clutter of managing 30+ tabs in an efficient way, and can handle groups as well?

[Disclaimer: Co-founder of https://www.bitrise.io , one of the alternatives mentioned on ship.io 's page]

Back when we started only a handful of CI services were available for iOS developers. One of them was CISimple which was later aquired and rebranded as ship.io . Our motivation to start our own service was that none of the available hosted services at the time were flexible enough to handle the projects we were working on.

Ship.io did improve a lot, allowing custom scripts to be executed, but, at least for us, they always seemed to be too locked down, too much of a black box.

This is exactly why we recently introduced our [open source CLI](https://github.com/bitrise-io/bitrise), so that you can run your CI and other automation configurations on your own machine if you want to, and of course in the (highly unlikely ;) case we would decide to close the shop you can still export your configuration and run it anywhere you want to.

I remember, just a few months ago, we felt that ship.io had a spy in our team, as they introduced new features almost at the same time we did (Slack support, Deliver support, ...).

It's surprising they closed so quick, they had quite an active marketing team and released new features frequently. I guess this decision was not up to the people who actually worked on the product, most likely they failed to meet the (monetary) expectations of their parent company.

Fairwell old friend, we'll always remember you!

Thanks, I'll definitely give Selenium a try!

We do a really simple trick. We have one Dockerfile, which we use for dev and for production, every configuration difference is handled through environment variables (which is easy to manage with docker-compose, Ansible, etc.), so you can run the same image everywhere and change the environment configuration to switch between dev/test/prod.

So to solve the live reload problem we do only one thing in development which we don't do anywhere else: the Dockerfile copies all the current source files into the image, but we run the container with a mounted volume of the source code - which in dev mappes exactly the same way the Dockerfile defines the src copy.

This way when you create the image and start the dev container it won't change anything, but as the src is mounted on top of the included src in the image the regular (Rails) auto reload works perfectly.

For test and prod we just simply don't do any volume mounting at all, and use the baked in src directly.

Easy and fast everywhere, all you have to control is how and when the images are created (ex: we do a full clean checkout in a new directory before building a test image, to ensure it only contains committed code. EDIT: by test I mean for local testing, while you're working on revisions, a CI server does the automatic testing).

+1 for pricing, and a suggestion: start accepting money as soon as you can. I think this post summarises it quite well why it's important http://thenextweb.com/entrepreneur/2015/06/13/43-lessons-gro...

Good luck and thanks for the great product!