[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Brice Figureau commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Same issue. Downgrading Git and Git client as explained in previous comments has solved the issue. Note that the 'Set GitHub commit status (universal)' is also affected. 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-50122) Incorrect permissions with non Multibranch based Pipeline jobs
Title: Message Title Brice Figureau commented on JENKINS-50122 Re: Incorrect permissions with non Multibranch based Pipeline jobs I've pushed a fix in PR#99 that happens to work for us. 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-50122) Incorrect permissions with non Multibranch based Pipeline jobs
Title: Message Title Brice Figureau created an issue Jenkins / JENKINS-50122 Incorrect permissions with non Multibranch based Pipeline jobs Issue Type: Bug Assignee: Sam Gleske Components: github-oauth-plugin Created: 2018-03-12 16:30 Environment: Jenkins 2.89.4 LTS running on Debian 9. Labels: github authorization Priority: Major Reporter: Brice Figureau We're using the Github OAuth plugin since a couple of days with the use repository permission flag activated. This means Jenkins will look the user permissions through the Github permission on the repository of the looked item. This works fine for all our regular jobs, but gives only READ/BUILD permissions on pipeline jobs. I think the problem is that we don't use the Multibranch Pipeline plugins and thus fGithubRequireOrganizationMembershipACL.getRepositoryName fails to return anything meaningful. Using the jenkins console, I could find that getRepositoryName throws a NullPointerException on those pipeline jobs. I believe that the code should test for the presence of the BranchProperty before dereferencing it, and if this property doesn't exist, it should simply call getTypicalSCM() on the project.
[JIRA] [google-play-android-publisher-plugin] (JENKINS-25933) Credentials for the configured Google Account could not be found when registering only one Google Play credential
Brice Figureau created JENKINS-25933 Credentials for the configured Google Account could not be found when registering only one Google Play credential Issue Type: Bug Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 05/Dec/14 2:38 PM Description: After creating a Google Play credentials as explained in the Wiki for this plugin, and configuring the job where I see the credential pop-up listing my only user. But when the job executes, I get this error: 15:05:12 Upload failed: org.jenkinsci.plugins.googleplayandroidpublisher.UploadException: Credentials for the configured Google Account could not be found 15:05:12 at org.jenkinsci.plugins.googleplayandroidpublisher.GooglePlayPublisher.getServiceAccountCredentials(GooglePlayPublisher.java:39) 15:05:12 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:301) 15:05:12 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) 15:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) 15:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) 15:05:12 at hudson.model.Build$BuildExecution.post2(Build.java:182) 15:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) 15:05:12 at hudson.model.Run.execute(Run.java:1731) 15:05:12 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 15:05:12 at hudson.model.ResourceController.execute(ResourceController.java:88) 15:05:12 at hudson.model.Executor.run(Executor.java:232) Looking at the config.xml for this job shows that there is no "googleCredentialsId" field (which explains the stacktrace above). After I added a second credential, the build worked correctly, and the config.xml was correct. Steps to reproduce: Start with no google play account credentials stored Create one, upload the p12 file Setup a new job, the credential pop-up lists the only user Run the build Environment: Linux Debian Wheezy Project: Jenkins Labels: exception google Priority: Major Reporter: Brice Figureau 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] [s3] (JENKINS-21594) JENKINS-16025 broke non-wirldcard S3 upload
Brice Figureau created JENKINS-21594 JENKINS-16025 broke non-wirldcard S3 upload Issue Type: Bug Affects Versions: current Assignee: Michael Watt Components: s3 Created: 31/Jan/14 12:38 PM Description: The fix for JENKINS-16025 broke the case when you're trying to upload to S3 a single file without using a wildcard. For instance: bucket: bucket/path/to/artifact source: *.tar.gz will correctly upload all tar.gz to the destination bucket in the /path/to/artifact folder. But: bucket: bucket/path/to/artifact source: myfile.tar.gz will unfortunately upload the myfile.tar.gz content into the 'artifact' directory. Project: Jenkins Priority: Major Reporter: Brice Figureau 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] [s3] (JENKINS-21594) JENKINS-16025 broke non-wirldcard S3 upload
Brice Figureau commented on JENKINS-21594 JENKINS-16025 broke non-wirldcard S3 upload This is fixed in this PR: https://github.com/jenkinsci/s3-plugin/pull/21 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.
