rtyler
/
blueocean-plugin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
blueocean-plugin/blueocean-web
History
Ivan Meredith 574aed8ce3 [JENKINS-36209] Queued activity items (#389) 
* [JENKINS-36209] Queued items now show in activties

* Remove unneeded changes from routes

* Fix whitespace issues

* Fix linting

* Style changes

* Fixed pipeline steps

* Fix linting

* Add tests and make queues work for multibranch projects

* Remove destructering from RunDetailsHeader

* Extract common function for mapping runs

* Optimize imports

* Remove whitespace

* Remove inline CSS

* Fix typo

* Fix isCompleted Function

* Add timer icon to emtpy state

* Bump JDL version

* Try waiting for start of anything that is in the queue first

* Fix NPE

* Disable Multibranch test for now
 		2016-08-08 14:27:54 +12:00
..
src Merge pull request #381 from jenkinsci/feature/JENKINS-37007-favorites-animations 2016-07-29 09:18:57 -04:00
README.md big cleanup of dev docs (#203) 2016-05-26 13:51:46 +10:00
gulpfile.js Add a "Try Blue Ocean UI" button in classic Jenkins 2016-06-09 19:10:11 +01:00
package.json [JENKINS-36209] Queued activity items (#389) 2016-08-08 14:27:54 +12:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-08-05 19:55:29 +10:00

README.md

Web middleware

This module mostly contains middleware for serving up "/blue" GUI. In general, you shouldn't need to modify stuff in for plugins or features as it is infrastructure. Move along.

Look for blueocean.js for excitement.

how this works with Javascript

Jenkins-js-modules and friends are used to power this. Look in src/main/js in any plugin.

If you wish to make changes to blueocean.js in this plugin, then you will need to install gulp (http://gulpjs.com/), and then run cd blueocean-plugin && mvn hpi:run in a separate terminal.

Then run:

$ gulp bundle:watch

(or run gulp, after each change) in this directory. This will pick up any changes. If you are editing any other UI modules, run the same in their respective directories.