-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support embedding Build Monitor in other dashboards #223
Comments
Ha! Embedded mode is a use case I haven't anticipated for :-) OK, so there's a couple of things at play here:
It seems like the best way to solve your problem though would be to introduce an "embedded" mode, with no navigation UI (which means the display would have to be configurable using URL parameters perhaps? #54) and just the job status. This doesn't solve the problem of too many jobs though. To get rid of this one we'd probably need a better support for CloudBees Folders (#130) to display accumulated status of a group of jobs. Thoughts? Best, |
I also really would appreciate this fully embeddable mode. I would only need the header and footer tags removed to fit into our dashboards. Since our dashboard and monitoring service are not under the same domain I cannot inject css into the iframe and do it myself. |
hello out there,
why has v1.9 another view than v1.6? I'm working with iFrames to display different machines.
so at the moment I always use the 1.6+build.164 instead of 1.9+build.201605021413 (reason see attached image)
on v1.9 I have to scale text to 2 that I can nearly read the text, but I have to scroll
on v1.6 i have to scale text to 0.3 to fit the bars in the frame and no scroll
possible to adapt the view of v1.6 to v1.9?
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34423127-support-embedding-build-monitor-in-other-dashboards?utm_campaign=plugin&utm_content=tracker%2F580790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F580790&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered: