@featurepeek/circleci - npm Package Compare versions

Comparing version 0.0.6 to 0.0.7

.DS_Store

index.js

		@@ -21,2 +21,3 @@ #!/usr/bin/env node
		const repo = process.env.CIRCLE_PROJECT_REPONAME
		const branch = process.env.CIRCLE_BRANCH
		const build = process.env.CIRCLE_BUILD_NUM
		@@ -32,3 +33,5 @@ const dirDepth = process.argv[2].replace(/^\.\//, '').split('/').length
		cutdirs: ARTIFACTS_DEPTH + dirDepth,
		pr_url: process.env.CIRCLE_PULL_REQUEST,
		org,
		repo,
		branch,
		},
		@@ -35,0 +38,0 @@ }

package.json

README.md

		# @featurepeek/circleci

		For GitHub and CircleCI
		For GitHub and CircleCI. See [documentation](https://docs.featurepeek.com/docs/circleci/).

		When a PR kicks of CI, and the build succeeds, artifacts are uploaded to CircleCI's artifacts service. Then our script sends a POST to `https://api.featurepeek.com/api/v1/TBD/static/circleci` with a body like

		```json
		{
		"artifacts_url": "https://circleci.com/api/v1.1/project/github/featurepeek/wandb-core/8/artifacts",
		"cutdirs": 6,
		"org": "featurepeek",
		"repo": "wandb-core",
		"branch": "new-feature-branch",
		}
		```

		Let me know if you want more info here. These [Built-in Env Vars](https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables) are helpful and easy to add.

		`cutdirs` is passed to `wget`. It's useful for trimming off the initial `0/root/project` at the front of every artifacts path. You'll only need it if you do indeed use wget. wget is useful because it retains directory hierarchy of the artifacts instead of saving everything in a flat directory. But if you don't use wget, you can ignore it.

		See the `download.sh` file for bash script to download the files saved in artifacts.

New alerts