relative-ci / agent Goto Github PK

Allow running relative-ci-agent from outside of the config directory.

npx relative-ci-agent --config-dir packages/components
# or
npx relative-ci-agent -c packages/components

The dependency yargs was updated from 13.2.2 to 13.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yargs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Currently it is not possible to send arguments to the agent from the Webpack plugin:

This invalidates passing options to the agent to allow passing env variables not detected by env-ci.

I would be nice if you could allow passing the args object from the Webpack plugin constructor parameters and thus allowing manually specifying CI variables

Hello,
I can't use your product because of an error at build time.

I have imported @relative-ci/agent into my webpack config file then it broke the build with the following error:

You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer

Could you help ?
Thank you

https://relative-ci.com/documentation/setup/webpack-plugin

Apologies if this is not the place for this. I have been trying to get my solution setup with rci, but am hitting a wall.

The track I followed to setup:

• npm install --save-dev @relative-ci/agent
• configure RelativeCiAgentWebpackPlugin
• configure RELATIVE_CI_KEY in our circle-ci

and after all that I can see this output in my pipeline:

Running "webpack:prod" (webpack) task
 relative-ci:agent {
 relative-ci:agent   includeCommitMessage: true,
 relative-ci:agent   stats: {
 relative-ci:agent     context: '/root/project/static/compiled/scripts/webpack-stats.json',
 relative-ci:agent     assets: true,
 relative-ci:agent     entrypoints: true,
 relative-ci:agent     chunks: true,
 relative-ci:agent     modules: true
 relative-ci:agent   },
 relative-ci:agent   enabled: '1'
 relative-ci:agent } +0ms

and then

RelativeCiAgentInvalid webpack stats structure, please make sure webpack stats configuration is correct

this leads me to believe it is working, but no stats are being displayed on the relative-ci dashboard and no additional logging is available.

A few things about this project:

• multiple entry files
• webpack-stats is output into the dir 'static/compiled/scripts/webpack-stats.json'

Problem

We are currently concatenating the fork owner with the branch name. This can cause conflicts if the branch name already includes the separator and requires extraction of the fork name in multiple places.

Solution

Collect and send the fork owner as as distinct parameter

Rel: relative-ci/bundle-stats#19

Replace the import from @bundle-stats/utils/lib/webpack with @bundle-stats/plugin-webpack-filter

I was trying this out with a gatsby site hosted at Netlify. But env-ci doesn't support Netlify(semantic-release/env-ci#125) and the build failed. I had added the RELATIVE_CI_SLUG key but for some reason getting the branch from git metadata failed, could be the way netlify clones the repo.

Instead of my build failing because of that, wouldn't it be better if we let the build continue and instead don't send any stats as sending a stats report isn't vital to the build.

We could send a mail alert, or log errors during the build.

Is it possible that the CLI exits with a non-zero status (e.g. process.exit(1)) if it encounters an error, such as missing "key" parameter or missing relativeci.config.js file?

Motivation

I'm using RelativeCI in CircleCI by calling the agent CLI in one of the steps of a job. I realized that even if the agent fails to send the statistics due to an error, let say a missing "key" parameter, the job is still marked as successfully completed because the agent CLI returns a zero exit-code.

If the CLI returns a non-zero exit code if failed to send statistics, CircleCI can mark this step has failed.

Thank you very much!

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

• allow to provide custom env variables when env-ci is not able to pick up the CI env variables
• add documentation

after running npm install I'm currently getting this error.

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"5.28.0" from the root project
npm ERR!   peer webpack@"^4.0.0 || ^5.0.0-rc.1" from @relative-ci/[email protected]
npm ERR!   node_modules/@relative-ci/agent
npm ERR!     dev @relative-ci/agent@"1.5.0" from the root project
npm ERR!   6 more (babel-loader, directory-named-webpack-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0" from [email protected]
npm ERR! node_modules/grunt-webpack
npm ERR!   dev grunt-webpack@"4.0.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

I wonder if allowing an additional v in the peer deps would do the trick? I'm not certain if npm is able to pickup the -rc.1 version as being the same as the following full release version

"peerDependencies": {
    "webpack": "^4.0.0 || ^5.0.0-rc.1" || "^5.0.0"
  }

https://www.jenkins.io/doc/book/pipeline/jenkinsfile/#using-environment-variables

rel: semantic-release/env-ci#249

The devDependency eslint-plugin-import was updated from 2.18.2 to 2.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

• show size
• save payload for debugging

Allow to override env-ci values when we don't want to rely on the CI env variables(eg: Github action pull_request event)

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency eslint-config-airbnb-base was updated from 14.0.0 to 14.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-airbnb-base is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Problem

Users have to install one large package that might include not necessary dependencies

Solution

Break the current package into multiple packages that will include only what is necessary for each case:

• @relative-ci/agent - CLI
• @relative-ci/agent-webpack-plugin
• @relative-ci/agent-next-plugin
• @relative-ci/agent-gatsby-plugin
• @relative-ci/agent-rollup-plugin

Run the agent in a github action

Rel: relative-ci/bundle-stats#1256

env-ci extracts the slug using ``${env.BUILDKITE_ORGANIZATION_SLUG}/${env.BUILDKITE_PROJECT_SLUG}`, but on buildkit:

• BUILDKITE_ORGANIZATION_SLUG is the buildkite organization and might differ from repo organization
• BUILDKITE_PROJECT_SLUG (obsolete) is the buildkite project slug (buildkite organization/buildkite project name)

ref: https://buildkite.com/docs/pipelines/environment-variables

relative-ci:agent env-ci environment variables {
  isCi: true,
  service: 'buildkite',
  slug: 'rltv/rltv/example',
  branch: 'update-agent',
  pr: undefined,
  build: '9',
  buildUrl: 'https://buildkite.com/rltv/example/builds/9',
  commit: '1b6a3c967ada2e7f85f9ea12d25fd3e4523edd5e',
  commitMessage: undefined

Can someone fix the error showing in the jsconfig.json?

node is not a valid option here.

The dependency core-js was updated from 3.4.6 to 3.4.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

core-js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

We've recently had a breach on our end of our API keys. It would be awesome if relative-ci had the ability to regenerate the key for RELATIVE_CI_KEY

webpack/webpack#11406