Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push test coverage reports to IPFS; proxy and serve over HTTP #80

Closed
btc opened this issue Sep 15, 2014 · 1 comment
Closed

Push test coverage reports to IPFS; proxy and serve over HTTP #80

btc opened this issue Sep 15, 2014 · 1 comment
Labels
help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature

Comments

@btc
Copy link
Contributor

btc commented Sep 15, 2014

The Golang toolchain allows you to generate nifty html test coverage reports. Proposal:

  1. Push to go-ipfs origin
  2. CI server runs tests
  3. CI server generates html coverage reports
  4. CI server pushes the html coverage reports to an IPFS node. Node publishes the files.
  5. Developer http://www.ipfs-dev.io/coverage/
  6. On a VPS, HTTP server proxies request to local IPFS node. Node queries swarm and returns results.
  7. Coverage reports are displayed in the browser.

The benefits are three-fold:

  1. improve test coverage -> improve software quality
  2. Dogfood an interesting use-case for IPFS as a web datastore. -> improve toolchain, api
  3. Be able to detect problems in the network early and often (on every commit!) -> improve network reliability
@btc btc added kind/enhancement A net-new feature or improvement to an existing feature help wanted Seeking public contribution on this issue labels Sep 15, 2014
@whyrusleeping
Copy link
Member

im gonna loop in @mappum here because he is better at web stuff than i am.

@jbenet jbenet closed this as completed Mar 28, 2015
@aschmahmann aschmahmann mentioned this issue Sep 22, 2020
72 tasks
@aschmahmann aschmahmann mentioned this issue Feb 18, 2021
73 tasks
ribasushi pushed a commit that referenced this issue Jul 4, 2021
update go.mod to remove unnecessary dependencies
ariescodescream pushed a commit to ariescodescream/go-ipfs that referenced this issue Oct 23, 2021
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Feb 25, 2022
fix: correct the default-datastore config profile
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Feb 25, 2022
…store

fix: correct the default-datastore config profile
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Mar 4, 2022
…store

fix: correct the default-datastore config profile
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Mar 4, 2022
…store

fix: correct the default-datastore config profile
hacdias pushed a commit that referenced this issue Nov 29, 2023
* feat(block options): add store codec
* refactor: BlockPutSettings.CidPrefix

Removes duplicated fields and replaces them with cid.Prefix

Codec, MhType and MhLength were  already in prefix, and we already return
prefix. A lot of duplicated values and code responsible for syncing them
did not really need to exist.

* test: CIDv1 raw and dag-pb cases
* chore: release 0.7.0

Co-authored-by: Marcin Rataj <[email protected]>

This commit was moved from ipfs/interface-go-ipfs-core@a3374d9

This commit was moved from ipfs/boxo@aca3a18
hacdias pushed a commit that referenced this issue Nov 29, 2023
* feat(block options): add store codec
* refactor: BlockPutSettings.CidPrefix

Removes duplicated fields and replaces them with cid.Prefix

Codec, MhType and MhLength were  already in prefix, and we already return
prefix. A lot of duplicated values and code responsible for syncing them
did not really need to exist.

* test: CIDv1 raw and dag-pb cases
* chore: release 0.7.0

Co-authored-by: Marcin Rataj <[email protected]>

This commit was moved from ipfs/interface-go-ipfs-core@a3374d9

This commit was moved from ipfs/boxo@aca3a18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants