opendev/storyboard-webclient
Code Issues Proposed changes
OpenStack Task Tracking Browser Client
939 Commits 1 Branch 0 Tags 8 MiB
JavaScript 53.4%
HTML 41.1%
SCSS 4.3%
Shell 0.6%
Smarty 0.5%
master
Go to file
Monty Taylor 870f34f815 Stop using deprecated javascript jobs 
We want to remove these from zuul-jobs, but we have to stop using them
here first.

v10 is old and not usable on regular OSes anymore. But the storyboard
toolchain doesn't work on more modern node. In the absense of interest
in updating the toolchain off of grunt and on to more modern things,
we should just leverage the docker builds.

If we need a new tarball of javascript somewhere, a job could be built
to extract the contents from the container image.

Change-Id: Iad25e6fd0dc392425e9d2a24d909785d1a12c5ef
2024-06-03 16:47:00 -07:00
bin Remove bower and add yarn support 2017-12-23 10:40:35 -06:00
src Update default contact in error message template 2021-10-14 17:20:59 +00:00
test Make the docs-draft build point to storyboard-dev 2016-05-19 14:19:55 +00:00
.eslintignore Fix post job by setting some variables 2019-03-15 14:30:59 +00:00
.eslintrc Render descriptions and comments as Markdown 2015-09-22 10:04:53 +00:00
.gitignore Remove bower and add yarn support 2017-12-23 10:40:35 -06:00
.gitreview OpenDev Migration Patch 2019-04-19 19:25:36 +00:00
.zuul.yaml Stop using deprecated javascript jobs 2024-06-03 16:47:00 -07:00
bindep.txt Bindep cleanup and JavaScript updates 2021-11-27 14:29:57 +00:00
Dockerfile Build container images 2020-03-28 11:03:34 -05:00
Gruntfile.js Reinstate "Add transpiling as a step in the build process" 2019-10-26 11:42:53 +01:00
karma.conf.js Fix post job by setting some variables 2019-03-15 14:30:59 +00:00
LICENSE Initial commit 2014-01-14 18:49:39 -08:00
package.json Reinstate "Add transpiling as a step in the build process" 2019-10-26 11:42:53 +01:00
protractor-integration.conf.js Initial proposal for integration tests 2015-04-07 11:05:19 +02:00
protractor.conf.js Enabled eslint:strict 2015-03-16 14:02:36 -07:00
README.md Add Worklists and Boards to About Page 2016-08-17 01:00:18 +09:00
tox.ini Update node to v10 2020-03-28 11:03:36 -05:00
yarn.lock Bindep cleanup and JavaScript updates 2021-11-27 14:29:57 +00:00

README.md

StoryBoard Web Client

A WebClient for the OpenStack StoryBoard project.

Project Resources

Getting Started

First of all be sure to have tox installed on your machine then:

  • Install the virtualenv containing nodejs: tox -evenv
  • Source the new path containing grunt: source .tox/venv/bin/activate
  • Now you can launch the grunt tasks of storyboard-webclient, by default run the development server with the following command: grunt serve

NPM Commands

The following are commands that may be used during project development.

  • npm run lint: Runs a linter on the javascript sources files of the project, this will help us keeping style consistency across our files and can reduce the risk of bugs.
  • npm run clean: Erases the temporary folders created by various grunt tasks, such as reports, cover and dist.
  • npm run build: Compile and packages our code.
  • npm run serve: Development server - runs a build and sets up concurrent watchers that will automatically lint, test, and refresh the code when a change is detected.
  • npm run test-unit: This command will create a clean build against which our unit tests will be run. For more information, please see karma-unit.conf.js
  • npm run test-integration: This command will create a clean build against which our functional tests will be run. For more information, please see protractor-integration.conf.js
  • npm run test-functional: This command will create a clean build against which our functional tests will be run. For more information, please see protractor.conf.js

Grunt tasks

For more detailed development, the following commands are available via grunt. To run them, you will need to install grunt globally: npm install -g grunt.

  • compile: Compiles all of our sources in the dist directory.
  • package: Built code into a release package.
  • serve:dist: This task performs a full build of our application, and then runs that source in a local web server. It does no watching, it simply hosts the files.
  • serve:prod: This task is identical to 'server:dist', with the exception that it will proxy the API requests against the production API. USE WITH CAUTION