[JIRA] (JENKINS-61803) Configure Global Security should accept both entries: default and per project
Title: Message Title Ron Gebauer commented on JENKINS-61803 Re: Configure Global Security should accept both entries: default and per project Maxime Hochet the order is also important. You need to set the per project base before default … because otherwise always default is used. I also do not understand why I can prioritize 2 options … but it seems this is is the case. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205647.1585920015000.9700.1586783640212%40Atlassian.JIRA.
[JIRA] (JENKINS-57697) [Error Handling] Error message not saying what fails
Title: Message Title Ron Gebauer created an issue Jenkins / JENKINS-57697 [Error Handling] Error message not saying what fails Issue Type: Bug Assignee: Steve Springett Components: dependency-track-plugin Created: 2019-05-27 08:30 Environment: Jenkins 2.150.3 Plugin Version 2.1.0 Priority: Major Reporter: Ron Gebauer If the project key is invalid I got inside Jenkins and error about invalid payload. Via REST-Client I get the correct Error which tells me that the project key was invalid. Maybe the error from Dependency Track should be shown or the mapping needs to be optimized. Add Comment
[JIRA] (JENKINS-54928) SCM changes are not noticed and SCMpoll starts the build based on the cron.
Title: Message Title Ron Gebauer created an issue Jenkins / JENKINS-54928 SCM changes are not noticed and SCMpoll starts the build based on the cron. Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-11-28 20:28 Environment: Jenkins 2.138.3 auf CentOS 7 Labels: bitbucket-branch-source-plugin bitbucket Priority: Blocker Reporter: Ron Gebauer After updating to version 2.2.13/14/15 the pipelines don't recognize that a SCM change has already been built and try to rebuild it for every cron run. When I go back to version 2.2.12 the change is recognized immediately and the endless building has an end. For more information just let me know. Add Comment
