[JIRA] (JENKINS-41831) Github Org folder Configuration changes not affecting children in the folder (Regression?)
Title: Message Title Morgan Goose commented on JENKINS-41831 Re: Github Org folder Configuration changes not affecting children in the folder (Regression?) It worked! But yeah it was as you guessed, that the trouble with scanning caused the regression. I haven't verified that by reproducing, but I have verified that when scanning works (thanks again for the github org patch/fix) the settings do indeed propagate as expected. I think this can be considered closed, as when the system functions, it all works as expected. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41831) Github Org folder Configuration changes not affecting children in the folder (Regression?)
Title: Message Title Morgan Goose edited a comment on JENKINS-41831 Re: Github Org folder Configuration changes not affecting children in the folder (Regression?) [~stephenconnolly] It worked! But yeah it was as you guessed, that the trouble with scanning caused the regression. I haven't verified that by reproducing, but I have verified that when scanning works (thanks again for the github org patch/fix) the settings do indeed propagate as expected. I think this can be considered closed, as when the system functions, it all works as expected. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41820) Builds are not triggered on hook notifications
Title: Message Title Morgan Goose commented on JENKINS-41820 Re: Builds are not triggered on hook notifications Stephen Connolly I'm seeing the hooks work as you would expect. I was misunderstanding where the event for push was being sent from. I thought it would be on the repo itself, not the org. Now knowing this, everything is configured, and works as expected. That is aside from the case sensitivity, but you said you're working on that, and there is a user configurable workaround. thanks again for your work here Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Morgan Goose commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Stephen Connolly this seems to be working well! Thank you for the quick turn around here: 10:01:45 GitHub API Usage: Current quota has 3278 remaining (2 over budget). Next quota of 5000 in 48 min. Sleeping for 26 sec. Current wild guess at an ETA for official release is 2 weeks from now then? When that happens will the plugin updater let us override this, or because it's manual it'll sorta stick? I'm happy enough with the results of this that I'm thinking of using your cuts until the real release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41820) Builds are not triggered on hook notifications
Title: Message Title Morgan Goose commented on JENKINS-41820 Re: Builds are not triggered on hook notifications Stephen Connolly I can confirm Konstantin Nazarov's experience. After making my Github Org Folder's name lowercase, I'm getting builds tiriggered again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Morgan Goose commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Stephen Connolly this is still an issue. And on a scan of an Org initially, we are guaranteed to hit this limit, and never be able to complete the Org scan. How does one proceed in this event? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41820) Builds are not triggered on hook notifications
Title: Message Title Morgan Goose commented on JENKINS-41820 Re: Builds are not triggered on hook notifications Full contents of the suggested log root@jenkins-master-i-0eebe6880afeaaaf3:/var/lib/jenkins# cat jenkins.branch.MultiBranchProject.log [Wed Feb 08 17:48:28 UTC 2017] Received org.jenkinsci.plugins.github_branch_source.PullRequestGHEventSubscriber$SCMHeadEventImpl UPDATED event with timestamp Wed Feb 08 17:48:28 UTC 2017 Found match against / [Wed Feb 08 17:48:30 UTC 2017] Finished processing org.jenkinsci.plugins.github_branch_source.PullRequestGHEventSubscriber$SCMHeadEventImpl UPDATED event with timestamp Wed Feb 08 17:48:28 UTC 2017. Matched 0. It doesn't look like there is much helpful information in that log. When I look into the hooks in Github I notice that Jenkins hasn't configured them to send the Push event. That seems like a large omission for this plugin to be making? Stephen Connolly is that configurable in any way in the UI? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-41820) Builds are not triggered on hook notifications
Title: Message Title Morgan Goose updated an issue Jenkins / JENKINS-41820 Builds are not triggered on hook notifications Change By: Morgan Goose Attachment: Screen Shot 2017-02-08 at 9.58.35 AM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41831) Configuration changes of the Org not affecting children in the folder
Title: Message Title Morgan Goose commented on JENKINS-41831 Re: Configuration changes of the Org not affecting children in the folder Note: Screen Shot 2017-02-07 at 3.42.50 PM.png is the Org config Screen Shot 2017-02-07 at 3.43.06 PM.png is a single project's config Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41831) Configuration changes of the Org not affecting children in the folder
Title: Message Title Morgan Goose created an issue Jenkins / JENKINS-41831 Configuration changes of the Org not affecting children in the folder Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Screen Shot 2017-02-07 at 3.42.50 PM.png, Screen Shot 2017-02-07 at 3.43.06 PM.png Components: github-organization-folder-plugin Created: 2017/Feb/08 1:18 AM Priority: Minor Reporter: Morgan Goose It doesn't look like removing options for what to build PR/Fork/Origin Branches/etc works, after adding them. Specifically, I added to the default, then later removed them, all on the Org config, and the child branches only ever reflected the change of addition, and didn't remove the options as was done on the containing org folder. Add Comment
[JIRA] (JENKINS-41121) GitHub Branch Source upgrade can cause a lot of rebuilds
Title: Message Title Morgan Goose commented on JENKINS-41121 Re: GitHub Branch Source upgrade can cause a lot of rebuilds Stephen Connolly I'd like to clarify, that I only installed those two plugins manually after multiple plugins failed to load saying that these versions were required. All of those complaining plugins were shown as having updates available and were updated in the suggested way (via the plugin update center web UI). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41121) GitHub Branch Source upgrade can cause a lot of rebuilds
Title: Message Title Morgan Goose commented on JENKINS-41121 Re: GitHub Branch Source upgrade can cause a lot of rebuilds But there are already plugins available for update that explicitly require this version of the scm plugin. Withholding the release is breaking Jenkins stacks. Letting users only upgrade partially, causes Jenkins to suggests resolution of "old data" via Deleting said data. If a core plugin is the hub of any number of spoke plugins that require it's use, it's seem pretty disruptive to not release them all at the same time? I've already grabbed the two hpi files, and installed manually: github-organization-folder-1.6.hpi scm-api-2.0.2.hpi from https://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ Was this release standard? Or did it follow a different track than usual? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41121) GitHub Branch Source upgrade can cause a lot of rebuilds
Title: Message Title Morgan Goose commented on JENKINS-41121 Re: GitHub Branch Source upgrade can cause a lot of rebuilds Stephen Connolly It doesn't look like the scm-api >= 2.0 has actually been released: http://updates.jenkins-ci.org/download/plugins/scm-api/ Are you sure that this can be closed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
