This is the successor of https://github.com/as-ideas/ideas-dash. ideas-dash is no longer being maintained.
- To run the example just run ./whazzup-example/src/main/java/io/github/whazzabi/whazzup/example/ExampleDash.java
Create a Spring-Boot-Application and add this dependency
<dependency>
<groupId>io.github.whazzabi</groupId>
<artifactId>whazzup-core</artifactId>
<version>${latest-whazzup-version}</version>
</dependency>See the ./whazzup-example module for an example.
CSS customization can be done by adding a file called src/main/resources/static/custom.css.
Currently two different designs are supported:
- Rows with more colors
- Columns with a more minimalistic view
You can switch the current design in the options (click 'show options')
- CheckResults can be grouped in the UI. Thats what Groups are for
- Teams are used as filters. This way many teams can share (no team specified) checks/results or have checks executed that only concern them and not interfere with other teams
Jenkins can be queried for build results if you provide JenkinsChecks via a CheckProvider. JenkinsJobListCheckProvider may come in handy for you as it parses the complete list of jenkins jobs for specified patterns and creates JenkinsChecks automatically. No more manual configuration for these.
Jira can be queried for issues (Bugs, Stories, Whatever). You may like to take a look at JiraQueryBuilder as a starting point for creating JiraChecks.
FabricCheck
DataDog can be queried for monitors. Just provide DataDogChecks via a CheckProvider.
- Open and old pull requests
- Failed Github Actions
- Stale Branches
Art is supported as well in theory. This was not used in a while and may prove unstable.
Statushub is supported as well. Markup will be parsed for css-classes (incident)
Cloudwatch is supported as well. Just initialize a CloudWatchCheck providing your aws-id, secret and aws region (instantiate different checks for different regions).
You can connect philips hue to the dash to indicate the overall state more "physically".
What you have to do:
- Connect the hue-bridge to the same network as the computer running the dash. if you want to connect it directly you need to enable a dhcp-server on the machine. For windows you could use something like http://www.dhcpserver.de/ (dont forget to add firewall exceptions).
- Find the bridge IP and go to http://bridge.ip/debug/clip.html
- Create new developer by firing a POST request with a payload like this: {"devicetype":"my_hue_app#gaffa"} against /api and holding the key on the bridge at the same time (following http://www.developers.meethue.com/documentation/getting-started) - you will receive a 'username' which you shall enter in the "key" - field of yana-dash.
- If you want to register a new light, POST a request against /api/key/lights with a payload like this: {"deviceid":["34AFBE"]} (deviceide being the serial on the bulb)
- Fire a GET request against /api/yourkey/lights and find the light you want to use
- Enter the bridge ip, the key and the light # in the hue configuration in the dash ui
Create a new release on github, give it a new semver version and write down the changes in the release. When the release is created, github action will run and deploy this version to maven central.