ByteInternet / hypernode-vagrant / 156

Builds Branch Commit Type Ran Committer Via Coverage
156 update-gem-to-0.0.6 build 0.0.6 gem push vdloo travis-ci pending completion   set done
155 master Merge pull request #128 from ByteInternet/add-default-hostname-to-configuration add default hostname to configuration push web-flow travis-ci pending completion   set done
154 master remove uneccesary tap ui tap in domain name test Pull #128 web-flow travis-ci pending completion   set done
153 add-default-hostname-to-configuration remove uneccesary tap ui tap in domain name test push vdloo travis-ci pending completion   set done
152 master Merge pull request #132 from ByteInternet/add-xenial-image add empty xenial image push web-flow travis-ci pending completion   set done
151 master hypernode vagrant runner can start xenial base Pull #133 web-flow travis-ci pending completion   set done
150 hypernode-vagrant-runner-can-start-xenial hypernode vagrant runner can start xenial base push vdloo travis-ci pending completion   set done
148 add-xenial-image add empty xenial image currently this is an empty Ubuntu 16 image and no Hypernode yet, by adding this as an option to the settings already we can use the perhipheral tooling around hypernode-vagrant to run automated tests during development. push vdloo travis-ci pending completion   set done
149 master add empty xenial image currently this is an empty Ubuntu 16 image and no Hypernode yet, by adding this as an option to the settings already we can use the perhipheral tooling around hypernode-vagrant to run automated tests during development. Pull #132 web-flow travis-ci pending completion   set done
147 master add empty xenial image currently this is an empty Ubuntu 16 image and no Hypernode yet, by adding this as an option to the settings already we can use the perhipheral tooling around hypernode-vagrant to run automated tests during development. Pull #132 web-flow travis-ci pending completion   set done
146 add-xenial-image add empty xenial image currently this is an empty Ubuntu 16 image and no Hypernode yet, by adding this as an option to the settings already we can use the perhipheral tooling around hypernode-vagrant to run automated tests during development. push vdloo travis-ci pending completion   set done
145 master Merge pull request #131 from ByteInternet/do-not-write-called-processerrors-to-stdout-after-run-command-failure do not write CalledProcessErrors to stdout push web-flow travis-ci pending completion   set done
142 master Merge pull request #130 from ByteInternet/do-not-buffer-hypernode-vagrant-runner-stdout do not buffer hypernode-vagrant-runner stdout push web-flow travis-ci pending completion   set done
141 master do not buffer hypernode-vagrant-runner stdout write the output of the command that runs in the machine to stdout directly Pull #130 web-flow travis-ci pending completion   set done
140 do-not-buffer-hypernode-vagrant-runner-stdout do not buffer hypernode-vagrant-runner stdout write the output of the command that runs in the machine to stdout directly push vdloo travis-ci pending completion   set done