[JIRA] [ghprb-plugin] (JENKINS-33121) "Commit status build result" uses wrong context
Title: Message Title David Tanner commented on JENKINS-33121 Re: "Commit status build result" uses wrong context Make sure that the context is being set as part of the trigger, and not as a build step, either pre or post. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ghprb-plugin] (JENKINS-26591) Workflow support for GitHub Pull Requests Builder Trigger
Title: Message Title David Tanner commented on JENKINS-26591 Re: Workflow support for GitHub Pull Requests Builder Trigger I am not sure how to make these compatible, and if it will take more work than just changing over from AbstractProject to Job. If anyone would like to have a go at it I will be sure to review the PR and get it released. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ghprb-plugin] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title David Tanner commented on JENKINS-32556 Re: Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin @jglick I have addressed the bug you mentioned with https://github.com/jenkinsci/ghprb-plugin/pull/279 I am not sure how to configure the plugin to work with Job instead of AbstractProject. I got hung up on my first pass with scheduling a build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [aws-beanstalk-publisher-plugin] (JENKINS-32877) AWS Beanstalk Plugin should be able to use server role credentials
Title: Message Title David Tanner commented on JENKINS-32877 Re: AWS Beanstalk Plugin should be able to use server role credentials https://github.com/jenkinsci/aws-beanstalk-publisher-plugin/blob/aws-beanstalk-publisher-plugin-1.5.6/src/main/java/org/jenkinsci/plugins/awsbeanstalkpublisher/AWSEBEnvironmentUpdater.java#L50-L58 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [aws-beanstalk-publisher-plugin] (JENKINS-32877) AWS Beanstalk Plugin should be able to use server role credentials
Title: Message Title David Tanner closed an issue as Done The latest version of the plugin is built to handle this situation. You are not required to input the key and secret key information. Jenkins / JENKINS-32877 AWS Beanstalk Plugin should be able to use server role credentials Change By: David Tanner Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [aws-beanstalk-publisher-plugin] (JENKINS-29576) AWS EC2 IAM Role no longer working with update to plugin
Title: Message Title David Tanner resolved as Fixed Removed null pointer exception, and merged patch. If the credentials are null then they will be passed as such to the AWS sdk with the expectation that the user has other means set up to provide credentials. If the credentials are null, however, then it will be logged during the build. Jenkins / JENKINS-29576 AWS EC2 IAM Role no longer working with update to plugin Change By: David Tanner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ghprb-plugin] (JENKINS-27659) java.io.IOException: Cannot determine sha1 of the commit. The status cannot be reported
Title: Message Title David Tanner closed an issue as Not A Defect This appears to be an issue with the Git client, not the Ghprb plugin. Look at the stack trace and you will notice there isn't anything from the plugin there. Also, the status updates at the end successfully. Jenkins / JENKINS-27659 java.io.IOException: Cannot determine sha1 of the commit. The status cannot be reported Change By: David Tanner Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ghprb-plugin] (JENKINS-25227) Trigger build with comment when previous was ok
David Tanner commented on JENKINS-25227 Trigger build with comment when previous was ok What doest your global config have set for Test phrase? 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] [ghprb-plugin] (JENKINS-25235) NPE on run()
David Tanner commented on JENKINS-25235 NPE on run() I am not sure how that could happen while the trigger is running. That line is helper.run(), and when .start() is called helper is initialized, or else it never calls super.start(). Are there more errors in the logs than that one? 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] [ghprb] (JENKINS-24954) "Test PASSed" comments added even if "Published Jenkins URL"
David Tanner commented on JENKINS-24954 "Test PASSed" comments added even if "Published Jenkins URL" Found the bug. PR #50 Added a curly brace to line 167 probably unintentionally. I have fixed the problem, and it will be released with 16-5. 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] [ghprb] (JENKINS-24954) "Test PASSed" comments added even if "Published Jenkins URL"
David Tanner resolved JENKINS-24954 as Fixed "Test PASSed" comments added even if "Published Jenkins URL" Change By: David Tanner (16/Oct/14 5:04 PM) Status: Reopened Resolved Resolution: Fixed 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] [ghprb] (JENKINS-24954) "Test PASSed" comments added even if "Published Jenkins URL"
David Tanner commented on JENKINS-24954 "Test PASSed" comments added even if "Published Jenkins URL" @Matthias I did some digging and the Use comments... flag is only used when the plugin is unable to update the status. It is honored, the message is something else and as Leandro stated removing the text from the two fields is currently the only way to remove those messages. It would take another setting to be able to tell the plugin not to make comments ever. 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] [ghprb] (JENKINS-24954) "Test PASSed" comments added even if "Published Jenkins URL"
David Tanner resolved JENKINS-24954 as Not A Defect "Test PASSed" comments added even if "Published Jenkins URL" Change By: David Tanner (15/Oct/14 8:00 PM) Status: Open Resolved Assignee: Honza Brázdil David Tanner Resolution: Not A Defect 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] [ghprb] (JENKINS-24954) "Test PASSed" comments added even if "Published Jenkins URL"
David Tanner commented on JENKINS-24954 "Test PASSed" comments added even if "Published Jenkins URL" It should be fixed in the latest, 16-3 and I am also releasing 16-4 now, so it should be available tomorrow. 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] [ghprb] (JENKINS-24820) Environment is not fulfilled
David Tanner
commented on JENKINS-24820
Environment is not fulfilled
Using the cron job will set the ${sha1} variable. At my company Jenkins is only available behind our firewall so we can't use webhooks either. Make sure that there are no other triggers enabled, and it should be fine. Please advise if you are still seeing issues.
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] [ghprb] (JENKINS-24145) latest ghprb plugin broken for gihub enterprise users
David Tanner commented on JENKINS-24145 latest ghprb plugin broken for gihub enterprise users Is anyone still experiencing this 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Was the branch deleted or changed before the build ran or something? When I first got things running here there were several times that someone would close the PR just after Jenkins picked it up. But I don't recall this being the error. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception What is special about that pull request, or the branch that it is pulling from? 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] [ghprb] (JENKINS-24447) latest ghprb plugin still broken for github enterprise users athough JENKINS-24145 marked as resolved
David Tanner commented on JENKINS-24447 latest ghprb plugin still broken for github enterprise users athough JENKINS-24145 marked as resolved I added a workaround for enterprise versions, if the apiURL contains api/v3 then it won't call the listCommits method at all. I hope this works until the github plugin is updated. v1.14-6 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception I can very easily create this null pointer error if there is nothing checked out using the git scm. As long as I have that set then there is a last build revision. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Following the lines that lead to the commit notifier I don't understand how this line gets null for the lastRevision. Can you please PM me the log from one of the failed builds? 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] [ghprb] (JENKINS-24145) latest ghprb plugin broken for gihub enterprise users
David Tanner resolved JENKINS-24145 as Fixed latest ghprb plugin broken for gihub enterprise users Surrounded the offending call with try-catch in version 1.14-5. Change By: David Tanner (20/Aug/14 8:24 PM) Status: Open Resolved Resolution: Fixed 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] [ghprb] (JENKINS-22736) Cannot 'Create Access Token' After Upgrading to 1.11.2
David Tanner commented on JENKINS-22736 Cannot 'Create Access Token' After Upgrading to 1.11.2 Make sure your username and password are set before trying to create the access token. Try it on the latest version and let me know what happens. 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] [ghprb] (JENKINS-22831) Github Project/Repo URL is case sensitive
David Tanner resolved JENKINS-22831 as Won't Fix Github Project/Repo URL is case sensitive The case for github project URLs are case sensitive. https://help.github.com/articles/error-repository-not-found http://stackoverflow.com/questions/14225547/are-git-repository-names-case-sensitive http://stackoverflow.com/questions/6650488/why-are-github-project-document-page-urls-case-sensitive-what-are-the-negative https://metacpan.org/pod/App::GitHub::FindRepository Change By: David Tanner (19/Aug/14 11:09 PM) Status: Open Resolved Resolution: Won't Fix 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] [ghprb] (JENKINS-20472) Allow retriggering of a build
David Tanner resolved JENKINS-20472 as Won't Fix Allow retriggering of a build Best to use the Rebuild plugin for jenkins instead. https://wiki.jenkins-ci.org/display/JENKINS/Rebuild+Plugin Change By: David Tanner (19/Aug/14 10:59 PM) Status: Open Resolved Resolution: Won't Fix 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] [ghprb] (JENKINS-19640) Prefer comments over status
David Tanner commented on JENKINS-19640 Prefer comments over status There is a global setting for this, "Use comments to report results when updating commit status fails" If this isn't what you need I can see about adding something. 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] [ghprb] (JENKINS-19103) ghprb slows Jenkins startup to a crawl
David Tanner commented on JENKINS-19103 ghprb slows Jenkins startup to a crawl Has anyone experienced this issue in the last few versions? 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] [ghprb] (JENKINS-18577) Add support for multiple GitHub endpoints
David Tanner commented on JENKINS-18577 Add support for multiple GitHub endpoints I can see the benefit of defining multiple github endpoints, but I don't think in the job is the place to define them. I would rather that the option is set in the main configuration, and then you can just add as many as you want, then choose the desired endpoint(s?) in the job. This might take a revamp of the main config so it matches something like the nodejs plugin. (first one that came to mind) 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] [ghprb] (JENKINS-17901) Add blacklist functionality
David Tanner commented on JENKINS-17901 Add blacklist functionality So the feature to build all pull requests is in the current version, just not a black list. I am not sure how beneficial a blacklist would be, or what the true desire for it is. If you would like to submit a pull request I will check it out and we can get some feedback from the community. 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] [ghprb] (JENKINS-17097) Changes are not present in builds started by a pull request
David Tanner commented on JENKINS-17097 Changes are not present in builds started by a pull request The issue that I have run into here is that the commit list doesn't provide any guaruntee that the email will be available, or that it will belong to the right person. I have added a parameter that specifies who the author is of the latest commit, but it might be possible to create a list of committers from github. Checkout the latest plugin and let me know if more is desired. 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] [ghprb] (JENKINS-16242) Github pull request builder - branch to merged before build
David Tanner resolved JENKINS-16242 as Not A Defect Github pull request builder - branch to merged before build Change By: David Tanner (19/Aug/14 10:34 PM) Status: Open Resolved Resolution: Not A Defect 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] [ghprb] (JENKINS-16242) Github pull request builder - branch to merged before build
David Tanner commented on JENKINS-16242 Github pull request builder - branch to merged before build This functionality exists in the plugin ghprb as presently constituted. If there is anything missing, please open something more specific to the desired functionality. 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] [ghprb] (JENKINS-16174) add documentation and help
David Tanner commented on JENKINS-16174 add documentation and help More information has been added to the plugin since this was created, is there anything missing that you would still like to see? 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] [ghprb] (JENKINS-24145) latest ghprb plugin broken for gihub enterprise users
David Tanner commented on JENKINS-24145 latest ghprb plugin broken for gihub enterprise users See issue 178 in github. Created a patch pull request or github-api. 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] [ghprb] (JENKINS-24145) latest ghprb plugin broken for gihub enterprise users
David Tanner commented on JENKINS-24145 latest ghprb plugin broken for gihub enterprise users Would you please post the URL you are using for the project here? Getting the file not found issue I have related to not adding the github API key. I can't test the url you gave me, so I am assuming it is a private repo. From everything that I can find the URL is saved and never altered. 1. Check your API key to make sure it has access to your enterprise github repo 2. Post the URL that is being entered on the Manage Jenkins page. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner
commented on JENKINS-23641
Builds are failing due to GitHubCommitNotifier exception
This is something happening in the github plugin. Is it only happening when there isn't a previous build?
https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java
Bar.java
@Override
public boolean perform(AbstractBuild build, Launcher launcher, BuildListener listener) throws InterruptedException, IOException {
BuildData buildData = build.getAction(BuildData.class);
String sha1 = ObjectId.toString(buildData.getLastBuiltRevision().getSha1());
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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner updated JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Change By: David Tanner (11/Aug/14 4:07 PM) Affects Version/s: current Component/s: github Component/s: ghprb 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] [ghprb] (JENKINS-22781) Do not trigger build when diff hasn't change
David Tanner commented on JENKINS-22781 Do not trigger build when diff hasn't change I have noticed this behavior when I have the build all checkbox marked. Otherwise the logs record there was a change, but nothing to trigger the build. Check your setting. 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] [ghprb] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
David Tanner commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception This doesn't appear to be an issue with ghprb. Is there any more to the stack trace? 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.
