cossacklabs / themis / #7575
88%
master: 83%

LAST BUILD BRANCH: release/0.15.0
DEFAULT BRANCH: master
Ran
Jobs 1
Files 73
Run time 8s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 87.707%. Remained the same
#7575

push

travis-ci

web-flow 
Simplify JsThemis packaging (#618)

* Improve JsThemis packaging

Add package-lock.json file into the repo. It is recommended to keep this
file committed into VCS. GitHub analyzer will scan it to see if there
are known security vulnerabilities in our dependencies.

Update the package.json file, add some missing metadata fields that we
fill in for WasmThemis. Also, add modern "mocha" as dev dependency.

Add an .npmignore file to prevent internal files from being packed into
the resulting distribution package.

* Move and simplify JsThemis installation targets

First of all, move them into the dedicated makefile from the main one.
Introduce a proper file target that will build the package in the build
directory (not simply "./build"). This is more friendly to systems where
the source directory is mounted as read-only, with a separate writable
build directory.

Unfortunately, "npm pack" always spits out its results into the current
directory. We have to cd into the build directory before calling it.

Also, since we don't really need to have multiple versions in the build
directory, we can rename the result into just "jsthemis.tgz" and avoid
doing all that awk magic to extract the version.

Note the use of "abspath". We need to ensure that we refer to correct
files, and for "npm install" to install the archive without treating
"build/jsthemis.tgz" as a scoped package name.

* Simplify JsThemis unit test launch

Add an npm target "test" to run "mocha" for our tests. This makes is
possible to develop and test JsThemis directly from its source directory
(like WasmThemis) and also packages the tests so that can be used by
other developers to verify our package after installation.

These changes make it possible to remove the preparation step from unit
test runs of JsThemis. We can now simply do "make test_js", without
installing it into the source root and running "make prepare_tests_all".

* Convenience "jsthemis" ta... (continued)

3767 of 4295 relevant lines covered (87.71%)

19360.32 hits per line

Jobs
ID Job ID Ran Files Coverage
1 #7575.1 0
87.71
Source Files on build #7575
Detailed source file information is not available for this build.