use index.jelly to override main page, then no need to hide jenkins UI #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jan-molak
added a commit
that referenced
this pull request
Jul 27, 2014
(fix) index.jelly not main.jelly should be used to override Jenkins main page; This results with cleaner html DOM with no duplicate nodes.
|
Thanks for your help, @michaelneale! |
|
no probs - not entirely sure it gets rid of all my problems but it should work better like this (still learning the jelly!). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
index.jelly is rendered in preference to all the rest of jenkins - by using this instead of main - no need to hide things - and no strange dom with duplicate nodes - just a brand new UI for build monitor.