- Added config file for bitbucket pipelines - Changed ubuntu version to a newer one

#15 Declined
Deleted repository
default (51fbd168d675)
  1. Pol Marcet

These days I’ve been looking for a Travis-like option to be able to see if everything is compiling properly. I’ve tried two:

  • Pipelines: this is the default option for bitbucket, and it’s quite simple to set up. It supports Docker. The only disadvantage is that in the free plan we would have only 50 min of compilation time. While I’ve taken the time down to a minute, that would only leave us with 50 goes a month.
  • Codeship: Codeship has two ways of working, the basic mode which doesn’t support Docker. Regardless of that, it achieves some really good times (lower a minute, around 35 seconds). There’s also the Pro mode, which while it does support Docker, it is a lot slower (4 min) and in my personal experience (Maybe I’m just really bad at configuring it) doesn’t conserve files between steps. There is a thing called “volumes” but seemed to not work adequately. I’ll probably give it another try in the future, but I don’t have much more time to put in for the moment. In both cases, we would have 100 compilations a month. I’ll leave here the commands for the basic mode:

Setup Commands (you will see I used sudo. It’s not a mistake, It did not build without root permissions. ¯\_(ツ)_/¯)

mkdir build
cd build
sudo cmake ..
sudo make -j$(nproc)

Test Commands (those can be run in parallel, so it’s preferable to put here stuff after the build)

sudo make install

Also, I updated the version of ubuntu in the Dockerfile to an accual one. 14.04 is old.

Comments (4)

  1. Braden Obrzut

    We support Ubuntu releases as long as Canonical does, so until April 2019, 14.04 is our target. Since Qt is ABI stable any binary compiled against 14.04 will run on 16.04 and 18.04 just fine. Thus the point of the Dockerfile at this time was to make it easier to check that Doomseeker builds with CMake 2.8.12 and Qt 5.2.

    On an unrelated note, I notice you fork Doomseeker for every change you’re submitting. Not that it really matters, but I’m fairly sure you can create bookmarks and send pull requests based on them. If this is just how you prefer to work that’s fine, just want to make sure you’re aware.

    1. Pol Marcet author

      Oh, did not think of the long term support. 😕 tomorrow when I get access to my computer, I'll change that.

      I didn't know anything about bookmarks, it simply was the quickest way to make a pull request the first time. I simply deleted my local files and leaved stuff in my Bitbucket account 😅

  2. Zalewa

    Sorry for having this lying unattended for a while. I’ll make my own fork and try out those pipelines there, then merge your work.