we are using Jenkins LTS 2.150.1, Is it possible to hide the nodes/slaves list (by default at the lower left side of the screen) from "regular" users (i.e - not admins).
Is it even possible?
Am I missing something?
I tried:
looking in the configuration of the server, couldn't find any "switch" or anything of that sort to hide it.
looking for a plugin to do that, but couldn't find anything that isn't changing the entire "look and feel" of the basic jenkins theme.
Seems to be that this feature is not added yet. See this ticket.
Related
I was hopping to have an easy way to customize the display behavior of the Grails fields plugin after reading its docs, but I just realized that it demands an enormous effort as there is no available templates to start from.
I can see the display functionality is hard-coded in FormFieldsTagLib (from methods like renderDefaultInput() ) but I think it is imperative to have the templates themselves (or a way to generate them, somewhat like generating static scaffolding in Grails).
I can see no consistent (and reasonable) way to customize display behaviors for the Grails fields plugin without that. Am I missing something?
Imagine the use case where someone wants to change the boolean default rendering just to display the field label after (and not before) the checkbox, and keep it available to all the boolean fields within its application. Which concerns will he need to handle regarding if the field is required, has errors, prefix and so on? When all he needed was just moving two divs around.
Grails version: 2.5.4, fields-plugin version: 1.5.1
You aren't missing something. You'd have to re-create the existing implementation of each field type rendering in a template for use with the plugin. There isn't a way to generate a file to start with (like scaffolding).
I won't bore you with the historical reason as to why this is the case, but if you do create a set of base templates it would be a good idea to contribute back to the plugin.
I had an issue with the <f:table> tag, and found this post, which led me to find the base or default template inside the plugin repo.
Take a look at
https://github.com/grails3-plugins/fields/tree/master/grails-app/views
That may help you finding some default templates, along with the official doc and this answer on where to put the override.
Hope it helps you.
Is there any setting I can change in Jenkins to make /consoleText the default page for console outputs? Right now, I have to click on console, and then click on the View as plain text link to get this page.
PS: I'm open to "hack" suggestions, if there's no way to officially do this in Jenkins.
Edit: While I'd be perfectly happy with just making /consoleText as the default page, what would be even better would be to replace the View as plain text link with a View dynamic log link, so that I can access the console link too, in case I need it.
You can try the Sidebar-Link Plugin which will give you the ability to add side links on various Jenkins pages like the build, top level, etc.
I am currently working on Umbraco CMS and want to manage hierarchy like master -> home -> TestPage
but i can't find structure tab anymore, can anyone know where to find it in newer version ?
You should probably be looking in the upper right corner. :) I think what you're looking for is "Compositions" or the "Permissions" to allow certain doctypes under other doctypes.
Update:
From the comments it seems like you want to make nested content types. This is still possible in the exact way it was possible before, right-click on the document type that you want to use as a parent and choose "Create".
Is there a way to change the help link in the toolbar dropdown in the new visual editor of MediaWiki?
I tried setting
"visualeditor-help-link":"mw:Help:VisualEditor/User guide/de"
in
"extentsions/VisualEditor/modules/ve-wmf/i18n/de.json"
as proposed here, but then my MediaWiki could not parse the JSON file. My goal is to link to the MediaWiki help page, that can be found here. The normal version:
"visualeditor-help-link":"[https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/de]"
did not work, neither did this:
"[[{{MediaWiki:visualeditor-helppagelink}}|Hilfe]]"
You should never ever change the source code of MediaWiki core or any extension. It makes an upgrade process much more hard and complicated. There are other ways to achieve a high customization of the user interface language :)
For your problem, it should be enough to create the following page in your wiki (like any other page, but you need the editinterface user right, which is assigned to sysops by default):
MediaWiki:visualeditor-help-link
Put the link you want to use into the textarea (without any wikitext, e.g. "Help:VisualEditor" (without any ")) and save the page.
After reloading the VisualEditor (maybe you need to clear your browser's cache using Ctrl + F5) the link should point to the new target you specified in the message above. If you use a message cache, it is maybe needed to rebuilt it.
In order to make sure that obsolete versions of the product aren't selected for a work item's iteration, I would like to be able to cloak certain iteration nodes from view, when opening a new work item.
For example, if the current production version of my site is 3.5, and 3.6 and 4.0 are in development, I want to make sure that when a user creates a new work item, versions that are older than 3.5 (e.g. 3.4, 2.7) will not be selectable.
I can conceive of a way to do this creating a custom control, but I'd like to avoid those, as they'd require development of both desktop and web controls, and would have to be deployed to all users.
Any ideas, directions, or just an "it can't be done", would be appreciated.
Thanks,
Assaf.
I am not sure if you can hide it as a selection.
However you can set the security for "Edit work items in this node" to deny and they will not be able to save workitems with the area or iteration selected.
I'm 90% sure it can't be done.
I haven't tried this myself:
Along the line of access control, I believe if you deny "View this node" permission on a user then she will not be able to see this node at all. Be aware that she will probably not be able to see the work items that are under this node, but I guess you are fine with that.
Another thing to note is that this solution might not work with Administrators (because if all Administrators are denied view permission and cannot see the area path then it's lost forever).