Project homepage Mailing List  API Docs  Github Mirror 
{"schema":"libjg2-1", "vpath":"/git/", "avatar":"/git/avatar/", "alang":"en-US,en;q\u003d0.5", "gen_ut":1560964238, "reponame":"libwebsockets", "desc":"libwebsockets lightweight C networking library", "owner": { "name": "Andy Green", "email": "", "md5": "c50933ca2aa61e0fe2c43d46bb6b59cb" },"url":"", "f":3, "items": [ {"schema":"libjg2-1", "cid":"c4d912f6b7abcca9b4b1815a59040f9b", "oid":{ "oid": "5462529bcc10060ef4b959b2181da335ed9a7f71", "alias": [ "refs/heads/master"]},"blobname": "READMEs/", "blob": "## Need for CI\n\nGenerally if we're adding something that's supposed to work ongoing, the stuff\nshould be exercised in CI (at least Travis).\n\nIf there are few users for a particular feature, experience has shown that\nrefactors or other upheaval can easily break it into a state of uselessness\nwithout anyone noticing until later.\n\nTherefore here's a description of how to add something to the CI tests... this\nis certainly a nonproductive PITA and I have never been thanked for the work\ninvolved. But if the promise of the various features working is going to\nremain alive, it's necessary to include CI test where possible with new\nnontrivial code.\n\n## Integration points\n\n### cmake\n\n`.travis.yml` maps the various test activities to CMake options needed.\n\n### including dependent packages into travis\n\nSee `./scripts/`\n\n### performing prepared test actions\n\nSee `./scripts/`\n\n","s":{"c":1560964238,"u": 205}} ],"g": 1014,"chitpc": 0,"ehitpc": 0, "indexed":0 }