-
Bug
-
Resolution: Fixed
-
Major
If the permissions of an user are granted on organization membership rather than team membership. The PR from the user aren't considered trusted. But are considered if the user push directly to the repository.
- is blocked by
-
JENKINS-43426 Refactor UX for GitHub and Bitbucket branch sources
- Closed
- is duplicated by
-
JENKINS-45359 Collaborator with write access is said to not be trusted in the first PR when the project doesn't have a Jenkinsfile yet
- Resolved
-
JENKINS-40705 Multibranch Pipeline fails to index GitHub repos using GitHub readonly credentials
- Closed
-
JENKINS-37931 PR build can use PR's head/merge Jenkinsfile insted of master branch.
- Resolved
- is related to
-
JENKINS-37608 Configurability of GitHub Branch Source to use Scan User with only Read permission
- Resolved
- links to
- mentioned in
-
Page Loading...