[JIRA] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
chris vecchione
created JENKINS-22136
Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Issue Type:
Bug
Assignee:
Thorsten Heit
Components:
crowd2
Created:
11/Mar/14 8:20 PM
Description:
The Jenkins Crowd2 plugin security plugin functionality NOT working as described (expected) in the 'Project-based Matrix Authorization Strategy':
1) Crowd group (call the group "X_TEST") given read-only permissions for all jobs in the Project-based Matrix Authorization Strategy within the jenkins application's 'Configuration Global Security' link.
2) While configuring a job (project) called "JobX_test" , I checked (true) the 'Enable project-based security' option and added crowd group "X_TEST" to the 'User/group' with all job related permissions (read | discover | build | workspace | configure...etc.). Saved it.
3) Note: No other group is enabled within the job ("JobX_test").
4) User "X" who is part of the "X_TEST" group only logs in and can NOT configure (nor build) the job ("jobX_test").
5) IF I increase the overall group's ("X_TEST") permissions to build and configure in the application's 'Configuration Global Security' link, THEN the user can build or configure the job ("JobX_test")!
So, bottom line, application permissions overrides the individual 'project-based security' permissions! It should be the opposite functionality in which individual 'project' permissions supercedes the applications's security settigns for the group (or user) as described in the following link:
https://wiki.jenkins-ci.org/display/JENKINS/2012/01/03/Allow+access+to+specific+projects+for+Users(Assigning+security+for+projects+in+Jenkins)
Project:
Jenkins
Priority:
Critical
Reporter:
chris vecchione
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
chris vecchione updated JENKINS-22136 Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Change By: chris vecchione (11/Mar/14 8:22 PM) Description: TheJenkinsCrowd2pluginsecuritypluginfunctionalityNOTworkingasdescribed(expected)intheProject-basedMatrixAuthorizationStrategy:1)Crowdgroup(callthegroupX_TEST)givenread-onlypermissionsforalljobsintheProject-basedMatrixAuthorizationStrategywithinthejenkinsapplicationsConfigurationGlobalSecuritylink.2)Whileconfiguringajob(project)calledJobX_test,Ichecked(true)theEnableproject-basedsecurityoptionandadded thesame crowdgroupX_TESTtotheUser/group security withalljobrelatedpermissions(read|discover|build|workspace|configure...etc.).Savedit.3)Note:Noothergroupisenabledwithinthe job project (JobX_test).4)UserXwhoispartoftheX_TESTgrouponlylogsinandcanNOTconfigure(norbuild)thejob(jobX_test).5)IFIincreasetheoverallgroups(X_TEST)permissionstobuildandconfigureintheapplicationsConfigurationGlobalSecuritylink,THENtheusercanbuildorconfigurethejob(JobX_test)!So,bottomline,applicationpermissionsoverridestheindividualproject-basedsecuritypermissions!Itshouldbetheoppositefunctionalityinwhichindividualprojectpermissionssupercedestheapplicationsssecuritysettignsforthegroup(oruser)asdescribedinthefollowinglink:https://wiki.jenkins-ci.org/display/JENKINS/2012/01/03/Allow+access+to+specific+projects+for+Users(Assigning+security+for+projects+in+Jenkins) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione updated JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug Change By: chris vecchione (07/Mar/14 10:51 PM) Issue Type: Improvement Bug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22004) JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures
chris vecchione created JENKINS-22004 JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures Issue Type: Bug Assignee: Unassigned Components: jira Created: 28/Feb/14 11:20 PM Description: JIRA does NOT create new issue (ticket) for a new build job IF there are no build successes. In other words: 1) I create a new Jenkins free project (build job) 2) The first execution - build job #1 - fails. 3) JIRA does not create a ticket (Create jira issue plugin does not work). It seems I need a build successful first and manual JIRA build jobname synchronization on jira administrative site. Project: Jenkins Priority: Major Reporter: chris vecchione This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-22004) JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures
chris vecchione commented on JENKINS-22004 JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures To add: the create jira issue plugin ONLY executes when the new jenkins build project: 1)had a previous build successful 2) and manually synched on jira administrative site This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione updated JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug Change By: chris vecchione (27/Feb/14 3:47 PM) Due Date: 21 14 / Feb Mar /14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione
commented on JENKINS-21766
Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug
Also (this should not need to be stated but in case): the 'Create jira issue' UI should add this new field ("Issue Type") allowing user input.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione created JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: jira Created: 11/Feb/14 5:24 PM Description: Need the Jenkins 'Create Issue type' plugin to be more dynamic / configurable to allow for different default jira issue type. Utilizing Jenkins Jira plugin version 1.39 Currently, jenkins project will only create an issue typoe of 'Bug'. We need the default configurable to align with the issue types created in jira for the project. Ideally an Issue Type drop-down box. Also, a nice feature is makeing the new issue 'Summary' be configurable with the same plugin. Due Date: 21/Feb/14 12:00 AM Environment: Linux Project: Jenkins Priority: Major Reporter: chris vecchione This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione updated JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug Change By: chris vecchione (11/Feb/14 8:55 PM) Description: NeedtheJenkinsCreateIssuetypeplugintobemoredynamic/configurabletoallowfordifferentdefaultjiraissuetype.UtilizingJenkinsJirapluginversion1.39Currently,jenkinsprojectwillonlycreateanissue typoe type ofBug.Weneedthedefaultconfigurabletoalignwiththeissuetypescreatedinjirafortheproject.IdeallyanIssueTypedrop-downbox. Also,anicefeatureismakeingthenewissueSummarybeconfigurablewiththesameplugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
chris vecchione
commented on JENKINS-21766
Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to bug
To be more exact we would like the "issue.setType("1") call be configurable like the other fields: Project Key | description | summary | assignee within the following code:
https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraSession.java
public RemoteIssue createIssue(String projectKey, String description, String assignee, RemoteComponent[] components, String summary) throws RemoteException {
RemoteIssue issue = new RemoteIssue();
issue.setProject(projectKey.toUpperCase());
issue.setDescription(description);
issue.setSummary(summary);
issue.setAssignee(assignee);
issue.setType("1");
issue.setComponents(components);
RemoteIssue createdIssue;
createdIssue = service.createIssue(token, issue);
return createdIssue;
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-environment] (JENKINS-20132) ERROR: [JENKINS-18403] JDK 5 not supported to run Maven; ERROR: Could not find local repository for 2.2.1
chris vecchione resolved JENKINS-20132 as Not A Defect ERROR: [JENKINS-18403] JDK 5 not supported to run Maven; ERROR: Could not find local repository for 2.2.1 Yorxdan wsa correct = not a jenkins build plugin issue. Pelase close Change By: chris vecchione (11/Feb/14 9:53 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-21776) Jenkins jira comment text typo
chris vecchione created JENKINS-21776 Jenkins jira comment text typo Issue Type: Bug Assignee: Unassigned Attachments: CommentIssue_typo_Feb2014.png Components: jira Created: 11/Feb/14 10:30 PM Description: Jenkins jira issue update plugin has a text error in spelling when adding a comment to an existing issue: typo on the word "failing" (should not be "falling") "Job is not falling but the issue is still open." The correct English should be: "Job is not failing but the issue is still open." Due Date: 14/Feb/14 12:00 AM Project: Jenkins Priority: Major Reporter: chris vecchione This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-20454) Enhance functionality to allow Editable Email Notification plugin to utilize Crowd2 plugin for group recipient lists
chris vecchione commented on JENKINS-20454 Enhance functionality to allow Editable Email Notification plugin to utilize Crowd2 plugin for group recipient lists Alex, I didn't think of this - how can i access the crowd plugin objects? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
