1_3_x build instructions

[Brandon Furtwangler]

I'm trying to locate build/test instruction for the 1_3_x branch.  I'm sure this has been asked before, but the search is failing me.

The contribute.markdown(in 1_3_x branch) file refers vaguely to "Ruby, RubyGems and Rake" with no further instructions (unless I've overlooked something?).  In later branches (like master) CONTRIBUTING.md goes into a bit more detail, however I'm running into an error when trying to apply those instructions to 1_3_x.'

I've installed ruby on windows:

• Ruby 2.0.0-p451

And added the bundle gem (instruction missing).

Then I ran 'bundle' from the root of the repo and as the instructions suggest to install the ruby dependencies.  I get the following error:

C:\Users\Brandon\Documents\GitHub\Hadron\submodules\jasmine-1.3.1 [(28329d5...)]> bundle

DL is deprecated, please use Fiddle

Don't run Bundler as root. Bundler can ask for sudo if it is needed, and

installing your bundle as root will break this application for all non-root

users on this machine.

The source :rubygems is deprecated because HTTP requests are insecure.

Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.

Updating https://github.com/pivotal/jasmine-gem.git

Fetching gem metadata from http://rubygems.org/.........

Fetching additional metadata from http://rubygems.org/..

Resolving dependencies...

Could not find gem 'jasmine-core (~> 2.0.0) x86-mingw32', which is required by

gem 'jasmine (>= 0) x86-mingw32', in any of the sources.

I'm not a ruby guy, so I'm not sure how to proceed.  Any advice.

Thanks,

Brandon

[Davis W. Frank]

We don't guarantee that any Jasmine core development can be done on Windows. Version 1.3 could be even worse.

The error you're running into has to do with naive gem version matching in 1.3. But I'm not sure if pinning to the correct versions of everything will get you far.

It may be simpler to bring up a VM with Linux on it to build Jasmine 1.3, since it sounds like you need this from the other thread.

--dwf

--
You received this message because you are subscribed to the Google Groups "Jasmine Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jasmine-js-de...@googlegroups.com.
To post to this group, send email to jasmine...@googlegroups.com.
Visit this group at http://groups.google.com/group/jasmine-js-dev.
For more options, visit https://groups.google.com/d/optout.

--
thx,

--dwf

[Brandon Furtwangler]

Hi Davis, thanks for the quick response.  

I was hoping to get the process of building our jasmine fork integrated into our CI workflow (which requires Windows for the devices we're targeting) however it sounds like that might not be possible.

I'll probably end up doing a one-off build in a VM as you suggested, and just using the resulting library, however I'm curious if you think it would be a significant work to extract some subset of the build process into something that only depend on node.

It looks like the only files we need are jasmine.js, jasmine-html.js, and jasmine.css. build_distribution.rb appears to produce these files, and isn't doing anything too complicated...maybe I'll explore that route.

-Brandon