search

keithpitt / vendor

Dependency management for iOS and OSX development
http://www.vendorkit.com
MIT License
99 stars 7 forks source link

Using vendor for continuous integration #15

Open jasperblues opened 12 years ago

jasperblues commented 12 years ago

Let's say you have a library module that's shared by several other modules. (iOS and OSX to complicate things).

It's great to use Vendor to do continuous integration, especially with the feature that allows pulling straight from git. (Or alternatively the CI server could publish the library module on successful builds).

When using git, t's necessary to to a git pull or clean the ${user.home}/.vendor directory. It would be great to mark a library as requiring the latest version available.

burtlo commented 12 years ago

This is similar to the command bundle update. So the idea would be you could type: vendor update

Do you think the command should attempt to update the source found within the application, as long as no modifications have been made against the previous version?

rayh commented 12 years ago

I currently blow away the git cache directory in .vendor on my CI machine to make sure I get the latest code. It would be better to have a Vendorfile.lock that, similar to Bundler, pins you to a specific commit/version, so your local and CI builds don't use different code.