[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Steph Gosling edited a comment on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 On Ubuntu 16.04 with 2.138.2 (as packaged by Canonical) setting the two properties does indeed appear to resolve: non- Jenkins admin -in-jenkins github users are able to browse projects, see console logs for builds Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Steph Gosling commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 On Ubuntu 16.04 with 2.138.2 (as packaged by Canonical) setting the two properties does indeed appear to resolve: non-Jenkins admin github users are able to browse projects, see console logs for builds Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Steph Gosling commented on JENKINS-42860 Re: RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Greg Smith Andres Montalban any insight into exactly what your scriptApproval.xml files looked like would be greatly appreciated. As of current LTS builds and plugins today I cannot cajole Jenkins into behaving (simply to get tags from a GitHub repo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46542) External way to set default parameter values for a pipeline job
Title: Message Title Steph Gosling commented on JENKINS-46542 Re: External way to set default parameter values for a pipeline job Another +1 for this feature, my use case is different but I'd say the usage isn't that specialised: I have a simple build CI/CD pipeline for a F/OSS project however the artifact it builds needs to be uploaded somewhere: for me this is a cloud object store. I do not want to leak object store buckets or paths that are specific to my companies' implementation of this project. I'd like to do it all within the same pipeline but as I can't I'm looking at the workflow plugin instead, simply to do the upload. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
