I am new to jenkins and facing 2 issues.
Trying to restric some users to view only specific tabs. For example
if we have All, Dev1, Dev2 and Dev3 tabs I want a specific user to access only Dev1 and Dev2
tabs and they should not be seeing All and Dev3 tab. Is this possible in Jenkins
What ever jobs I add to Dev1, it is showing in All tabs as well. Can we restrict a job to appear only in Dev1 tab. Thanks
I suggest you start by reading the standard security setup page to understand how to enable authentication.
For authorization controls the matrix based authorization is pretty good, but the Role strategy plugin offers more detailed user controls.
Related
Currently, Jenkins add as a user any known user of Jenkins plus any user mentioned in a commit message.
This effectively means that if you are managing several projects in Jenkins instance and each project with tenths of developers then it is really hard to maintain.
Another side effect is that JENKINS_HOME/users are populated with one xml for each of these users, so Jenkins becomes somehow unmanageable. Not the end of the world, that's true, but at the same time you start seeing users from outside of team/organization.
So, is there any way to disable this behaviour?
Thak you so much.
I'm struggling with understanding if it is possible to hide certain tabs from TFS web interface based on specific user group. What I'm looking for is to hide Build/Release , Code tabs and if it is possible the configuration option (the gear button). From what I could find there was a "WorkItemOnlyView" default security group in previous versions of TFS that looked like what I wanted. Is it possible to accomplish something like this now?
You could make them "Stakeholders" access which removes their access to code/builds/release entirely in web portal. Then should see the web portal such as below screenshot:
Another way is restricting access in VSTS and TFS.
I am looking for a plugin that allows for a View level security. For example I had an AD group I wish to assign to have modification/Execute permissions to ALL jobs under a specific View.
I understand that Views are just filters on the main page of Jenkins but with the quantity of plugins out there I needed to ask.
The Role Strategy Plugin worked wonders for my organization.
https://plugins.jenkins.io/role-strategy/
You cannot control access at view levels but, you can play around with folder plugin to get the desired level of access
I'm in the process of implementing a workflow in Sitecore, and for that I have setup several different users with roles, where the security for the roles dictates the workflow process (nothing unusual).
One of these roles is a "CMS Publisher", and its job is to be last in the review process and to publish the item once it is accepted. The problem is that in the Publish tab, there is no "Publish" button. I know that it is possible to Auto-Publish items once they get into a final state, but I would like for this role to have access to that button as well. I figured it's a security setting on a content item somewhere, but I've searched the core/master database to no avail and the sdn provides zero information on this.
Thank you for your time.
Make your "CMS Publisher" role a 'member of' the built in "Sitecore Client Publishing" role and see if the button shows up.
There is a setting the web.config file that will require the Sitecore Client Publishing role to have both read and write access in order to publish an item. This setting is Publishing.CheckSecurity.
You can read a full explanation here.
I am using Jira for organizing user stories for my project on Agile approach. When I tried to close a user story it shows the status as ' Resolved', rather than 'Closed'.
Can someone help me how to change the user story status to closed?
Please post your suggestions and help.
Its a bit hard to answer such a vague question - so if you can ellaborate a bit on the customization you have done in your JIRA instance, it can help.
Some pointers:
JIRA is using workflows to manage the flow an issue can use.
The default workflow that comes with an installation of JIRA is called "jira" and looks like this: https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
Depending on the customization of your JIRA installation, you can either change the workflow to go from Open to Closed when you use the "Resolve" operation.
If you are not the JIRA administrator, different workflow transitions can have various properties and conditions and validators set on them, for example checking for permissions. So if you are a user that does not have permissions to do a certain transition - you can see if you can change it via the permissions administation panel, or again - in the workflow validations.