With Ember-CLI you now need to run ember generate <addon-name>
to instantiate the addon into your application. This is also
true with sub-addons.
Using the above method, you can essentially run
ember generate <sub-addon-name>. The addon needs to be included
as a hard dependency in your package.json. We can then configure
our blueprint in blueprints/<addon-name>/index.js.
| #!/bin/bash | |
| # Based on work by Tiago Rodrigues | |
| # Here: http://trodrigues.net/presentations/buster-ci/#/24 | |
| # And here: https://gist.github.com/2630210 | |
| # Usage: | |
| # env BUSTER_HOME=/where/you/installed/buster ./buster-server.sh start|stop | |
| function buster_server_pid(){ | |
| echo `ps aux|grep buster-server|grep node|awk '{ print $2 }'` |
| $ java -jar jenkins-cli.jar -s http://localhost:9000 install-plugin findbugs | |
| findbugs is neither a valid file, URL, nor a plugin artifact name in the update center | |
| No update center data is retrieved yet from: http://updates.jenkins-ci.org/update-center.json | |
| findbugs looks like a short plugin name. Did you mean 'null'? | |
| # Specifying a full URL works! | |
| $ java -jar jenkins-cli.jar -s http://localhost:9020 install-plugin http://updates.jenkins-ci.org/download/plugins/AdaptivePlugin/0.1/AdaptivePlugin.hpi | |
| # Get the update center ourself |
