[Client|Job] - Issues #44, #49 - Initial WIP code towards crumbs
[Client] - Issues #49 - Changed the way we identify if Jenkins uses crumbs. The user don't have to worry about sending it in the configuration
[Client] - Issues #49 - Changed the way we identify if Jenkins uses crumbs. The user don't have to worry about sending it in the configuration
[Client] - Issues #49 - Attempt to call the API after dealing with the password conversino stuff
Merge pull request #52 from arangamani/master

Pull changes from master
Add gemspec
Add message to ApiException
Merge WIP crumbs support
Whoops, removed handle_exception
Change post config code
Again, fixing posting new config
crumb as a header
pulled WIP code from downstream and merged master back to get ready for development
updated the crumb code and fixed tests
fixed node and view functional specs
more fixes
fixed the restart/reload on system - apparently jenkins returns a 503 on these calls if CSRF is enabled
apparently 503 is returned just because follow redirects was enabled - pulling code back
Performance improvements for crumb support

* Use proper exceptions and error messages when using crumbs
* Improve performance by storing the crumb in a hash instead of fetching it for every POST request - refetch if it expires
updated travis setup

* Added a setup_crumb script which copies the updated config.xml with crumb enabled
* Run the func tests once again when crumb is enabled