Custom Policies frontend for Red Hat Insights

1. yarn

2. yarn start

   • starts webpack bundler and serves the files with webpack dev server

• yarn verify will run linters and tests
• Travis is used to test the build for this code.
  • You are always notified on failed builds
  • You are only notified on successful builds if the build before it failed
  • By default, both push events as well as pull_request events send notifications

To run locally, we need the following:

1. Run insights proxy
2. Run custom-policies-ui-frontend application.

In order to run it locally, you need to have insights-proxy repository placed under PROXY_PATH. Start the proxy by running:

yarn proxy

Install the dependencies:

yarn

and run the application:

yarn start

After that, you can head to the dev page or the prod page.

You will likely need to accept the certificates of these pages and the websocket page

For more info refer to Insights Frontend Starter App README

Deployments come from the .travis/custom_release.sh file. Push to certain branches to deploy to certain environments:

Anytime a build of the master branch happens, Travis builds and pushes a new commit to the ci-beta & qa-beta branch in your build repo. Pull requests on master will not be deployed until they are merged, but they will be built to assure linting, snapshots, etc. are working as expected.

master -> qa-beta & ci-beta prod-beta -> prod-beta master-stable -> qa-stable & ci-stable prod-stable -> prod-stable

When you want to test your code with unit tests please use jest which is preconfigured in a way to collect codecoverage as well. If you want to see your coverage on server the travis config has been set in a way that it will send data to codecov.io the only thing you have to do is visit their website (register), enable your repository and add CODECOV_TOKEN to your travis web config (do not add it to .travis file, but trough travis-ci.org)