From: Damien R. <dam...@me...> - 2013-04-06 18:59:29
|
Hi John If you can spare the time, I would appreciate if you could have a look or at least give me a few pointers on how to troubleshoot the github integration to our tracker. Today I pushed a commit [1] that fixes issue #15678 for master branch. As far as I can tell, the github hooks were triggered OK, as the commits from my push are showing on the IRC log [2] Yet the issue [3] has not been updated as it usually is (I expected to see it marked as resolved and the changesets attached), and the changesets don't seem to be on the tracker at all [4]. Thanks in advance for your help is appreciated. Damien [1] https://github.com/mantisbt/mantisbt/commit/8ff8338 [2] http://www.mantisbt.org/irclogs/mantisbt/mantisbt_2013-04-05.log.html [3] http://www.mantisbt.org/bugs/view.php?id=15678 [4] http://www.mantisbt.org/bugs/plugin.php?page=Source%2Fsearch&repo_id[]=7&branch[]=&user_id=&author=&revision=&bug_id=&date_start_default=2000-1-1&date_start_year=2013&date_start_month=4&date_start_day=4&date_end_default=2013-4-5&date_end_year=2013&date_end_month=4&date_end_day=5&message=&filename= |
From: John R. <jo...@no...> - 2013-04-06 19:21:28
|
Just as a quick idea, since im not at home to check: with all the talk of new branches and so forth, are these commits happening on a branch that mantis isn't paying attention to? This is a configuration option in the mantisbt repo itself. On Apr 6, 2013 11:59 AM, "Damien Regad" <dam...@me...> wrote: > Hi John > > If you can spare the time, I would appreciate if you could have a look or > at > least give me a few pointers on how to troubleshoot the github integration > to our tracker. > > Today I pushed a commit [1] that fixes issue #15678 for master branch. > > As far as I can tell, the github hooks were triggered OK, as the commits > from my push are showing on the IRC log [2] > > Yet the issue [3] has not been updated as it usually is (I expected to see > it marked as resolved and the changesets attached), and the changesets > don't > seem to be on the tracker at all [4]. > > Thanks in advance for your help is appreciated. > Damien > > > [1] https://github.com/mantisbt/mantisbt/commit/8ff8338 > [2] http://www.mantisbt.org/irclogs/mantisbt/mantisbt_2013-04-05.log.html > [3] http://www.mantisbt.org/bugs/view.php?id=15678 > [4] > > http://www.mantisbt.org/bugs/plugin.php?page=Source%2Fsearch&repo_id[]=7&branch[]=&user_id=&author=&revision=&bug_id=&date_start_default=2000-1-1&date_start_year=2013&date_start_month=4&date_start_day=4&date_end_default=2013-4-5&date_end_year=2013&date_end_month=4&date_end_day=5&message=&filename= > > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |
From: Paul R. <pa...@ma...> - 2013-04-06 20:09:34
|
There's stuff there from January. Paul On Sat, Apr 6, 2013 at 8:21 PM, John Reese <jo...@no...> wrote: > Just as a quick idea, since im not at home to check: with all the talk of > new branches and so forth, are these commits happening on a branch that > mantis isn't paying attention to? This is a configuration option in the > mantisbt repo itself. > On Apr 6, 2013 11:59 AM, "Damien Regad" <dam...@me...> > wrote: > >> Hi John >> >> If you can spare the time, I would appreciate if you could have a look or >> at >> least give me a few pointers on how to troubleshoot the github integration >> to our tracker. >> >> Today I pushed a commit [1] that fixes issue #15678 for master branch. >> >> As far as I can tell, the github hooks were triggered OK, as the commits >> from my push are showing on the IRC log [2] >> >> Yet the issue [3] has not been updated as it usually is (I expected to see >> it marked as resolved and the changesets attached), and the changesets >> don't >> seem to be on the tracker at all [4]. >> >> Thanks in advance for your help is appreciated. >> Damien >> >> >> [1] https://github.com/mantisbt/mantisbt/commit/8ff8338 >> [2] http://www.mantisbt.org/irclogs/mantisbt/mantisbt_2013-04-05.log.html >> [3] http://www.mantisbt.org/bugs/view.php?id=15678 >> [4] >> >> http://www.mantisbt.org/bugs/plugin.php?page=Source%2Fsearch&repo_id[]=7&branch[]=&user_id=&author=&revision=&bug_id=&date_start_default=2000-1-1&date_start_year=2013&date_start_month=4&date_start_day=4&date_end_default=2013-4-5&date_end_year=2013&date_end_month=4&date_end_day=5&message=&filename= >> >> >> >> ------------------------------------------------------------------------------ >> Minimize network downtime and maximize team effectiveness. >> Reduce network management and security costs.Learn how to hire >> the most talented Cisco Certified professionals. Visit the >> Employer Resources Portal >> http://www.cisco.com/web/learning/employer_resources/index.html >> _______________________________________________ >> mantisbt-dev mailing list >> man...@li... >> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev >> > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |
From: Damien R. <dam...@me...> - 2013-04-09 14:55:13
|
John Reese <john@...> writes: > Just as a quick idea, since im not at home to check: with all the talk of > new branches and so forth, are these commits happening on a branch that > mantis isn't paying attention to? This is a configuration option in the > mantisbt repo itself. These are the facts: - no changesets were automatically imported into bugs database - this includes 1.2.x, master and master-2.0.x commits - after a manual import, 1.2.x and master commits were imported successfully - there have not been any commits since then, so I don't know if the issue is resolved or still exists for 1.2.x & master - master-2.0.x commits were not added by the manual import It is possible that the repo is not configured properly (there is no master-2.0.x branch defined), however, this used to work as there are 2.0.x changesets in the database. The most recent one is dated 2013-03-01 23:34:33 It is possible that some of the recent changes to the plugin may be the cause for that, I don't know. And > If you can spare the time, I would appreciate if you could have a look or > at least give me a few pointers on how to troubleshoot the github > integration to our tracker. :-) D |
From: John R. <jo...@no...> - 2013-04-09 22:44:30
|
Sorry for the delay in responding. If you can pull changesets from Github using "import latest", but changesets are not getting pushed by the Github hook, then it's likely that Github has changed the format of the hook payload, or the method in which they send the payload, in such a way that the SourceGithub plugin can't pull out the appropriate commit data. Unfortunately, since there isn't any proper logging framework for plugins, debugging the issue ends up as a matter of adding a bunch of debug file logging into Source and SourceGithub in various places to try and track down what's happening from the moment Github's hook connects to MantisBT. Thankfully, Github offers a "test hook" button that should trigger a new copy of the latest payload to be sent, so you can add logging to a file in /tmp, and use the test hook button to try and track down where things go sideways. I'd always meant to add this sort of debug logging throughout the SourceIntegration framework, but I never had the time to do it right, and considering how differently each plugin handles incoming commit payloads, there wasn't really a silver bullet other than adding a bunch of debug lines all over the framework and every single plugin. =/ Anyways, I unfortunately don't have the spare time to help debug this atm, but if it doesn't get tracked down soon, I'll try to set aside some time to see if I can help out. Cheers John Reese noswap.com On Tue, Apr 9, 2013 at 7:53 AM, Damien Regad <dam...@me...>wrote: > John Reese <john@...> writes: > > > Just as a quick idea, since im not at home to check: with all the talk of > > new branches and so forth, are these commits happening on a branch that > > mantis isn't paying attention to? This is a configuration option in the > > mantisbt repo itself. > > These are the facts: > > - no changesets were automatically imported into bugs database > - this includes 1.2.x, master and master-2.0.x commits > - after a manual import, 1.2.x and master commits were imported > successfully > - there have not been any commits since then, so I don't know if the issue > is resolved or still exists for 1.2.x & master > - master-2.0.x commits were not added by the manual import > > It is possible that the repo is not configured properly (there is no > master-2.0.x branch defined), however, this used to work as there are 2.0.x > changesets in the database. The most recent one is dated 2013-03-01 > 23:34:33 > > It is possible that some of the recent changes to the plugin may be the > cause for that, I don't know. > > And > > > If you can spare the time, I would appreciate if you could have a look or > > at least give me a few pointers on how to troubleshoot the github > > integration to our tracker. > > :-) > > D > > > > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |
From: Roland B. <ro...@at...> - 2013-04-10 14:02:11
|
I don't know any details about github integration and didn't have a deeper look what happens. Just as a hint https://github.com/blog/1457-upcoming-ip-address-changes When pulling from github the first time after this changes I got $ git pull Warning: Permanently added the RSA host key for IP address '204.232.175.90' to the list of known hosts. Maybe there is also some action needed on our server. John Reese <jo...@no...> hat am 10. April 2013 um 00:44 geschrieben: > Sorry for the delay in responding. > > If you can pull changesets from Github using "import latest", but > changesets are not getting pushed by the Github hook, then it's likely that > Github has changed the format of the hook payload, or the method in which > they send the payload, in such a way that the SourceGithub plugin can't > pull out the appropriate commit data. Unfortunately, since there isn't any > proper logging framework for plugins, debugging the issue ends up as a > matter of adding a bunch of debug file logging into Source and SourceGithub > in various places to try and track down what's happening from the moment > Github's hook connects to MantisBT. Thankfully, Github offers a "test > hook" button that should trigger a new copy of the latest payload to be > sent, so you can add logging to a file in /tmp, and use the test hook > button to try and track down where things go sideways. > > I'd always meant to add this sort of debug logging throughout the > SourceIntegration framework, but I never had the time to do it right, and > considering how differently each plugin handles incoming commit payloads, > there wasn't really a silver bullet other than adding a bunch of debug > lines all over the framework and every single plugin. =/ > > Anyways, I unfortunately don't have the spare time to help debug this atm, > but if it doesn't get tracked down soon, I'll try to set aside some time to > see if I can help out. > > Cheers > > > John Reese > noswap.com > > > On Tue, Apr 9, 2013 at 7:53 AM, Damien Regad > <dam...@me...>wrote: > > > John Reese <john@...> writes: > > > > > Just as a quick idea, since im not at home to check: with all the talk of > > > new branches and so forth, are these commits happening on a branch that > > > mantis isn't paying attention to? This is a configuration option in the > > > mantisbt repo itself. > > > > These are the facts: > > > > - no changesets were automatically imported into bugs database > > - this includes 1.2.x, master and master-2.0.x commits > > - after a manual import, 1.2.x and master commits were imported > > successfully > > - there have not been any commits since then, so I don't know if the issue > > is resolved or still exists for 1.2.x & master > > - master-2.0.x commits were not added by the manual import > > > > It is possible that the repo is not configured properly (there is no > > master-2.0.x branch defined), however, this used to work as there are 2.0.x > > changesets in the database. The most recent one is dated 2013-03-01 > > 23:34:33 > > > > It is possible that some of the recent changes to the plugin may be the > > cause for that, I don't know. > > > > And > > > > > If you can spare the time, I would appreciate if you could have a look or > > > at least give me a few pointers on how to troubleshoot the github > > > integration to our tracker. > > > > :-) > > > > D > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Precog is a next-generation analytics platform capable of advanced > > analytics on semi-structured data. The platform includes APIs for building > > apps and a phenomenal toolset for data science. Developers can use > > our toolset for easy data analysis & visualization. Get a free account! > > http://www2.precog.com/precogplatform/slashdotnewsletter > > _______________________________________________ > > mantisbt-dev mailing list > > man...@li... > > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter_______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Damien R. <dam...@me...> - 2013-04-15 19:32:14
|
Roland Becker <roland@...> writes: > Just as a hint > https://github.com/blog/1457-upcoming-ip-address-changes > > When pulling from github the first time after this changes I got > $ git pull > Warning: Permanently added the RSA host key for IP address '204.232.175.90' to > the list of known hosts. I think it's quite unlikely that an IP address change would cause the kind of issue we're seeing. John Reese <john@...> hat am 10. April 2013 um 00:44 geschrieben: > If you can pull changesets from Github using "import latest", but > changesets are not getting pushed by the Github hook, then it's likely > that Github has changed the format of the hook payload, or the method in > which they send the payload, in such a way that the SourceGithub plugin > can't pull out the appropriate commit data. Yeah, importing the latest works (except for the fact that Paul's 2.0 branch changesets don't get imported but I think that's just a configuration issue. John if you know what I should change to fix that, I'm sure Paul would be grateful ;) On the main problem now: I did a first check by adding a bunch of tracing statements in the checkin.php file, and realized that the page expects to receive a parameter 'data' [1], but based on my trace there is no such param provided by Github hook, so the just code ends with trigger_error in gpc_api. Which probably explains why it fails ;) But then I thought about it some more and thought that this really ought to be handled by the SourceGithub plugin, not by checkin.php, and that's when I realized that a pull request which I merged back in February [1] introduced a change in the precommit function, whereby the payload's repository name is compared against the display name of the repository instead of the "hub_name"). I'll try to revert that locally (on mantisbt.org) and we'll see at next push if the changesets are imported correctly. D [1] https://github.com/01-Scripts/source-integration/commit/aadde7eb |
From: John R. <jo...@no...> - 2013-04-15 19:59:18
|
On Mon, Apr 15, 2013 at 12:31 PM, Damien Regad <dam...@me...>wrote: > Yeah, importing the latest works (except for the fact that Paul's 2.0 > branch > changesets don't get imported but I think that's just a configuration > issue. > John if you know what I should change to fix that, I'm sure Paul would be > grateful ;) > Manage Repo -> Branch Names John Reese noswap.com |