Commercial support planning and feedback
Hi everyone, Something that comes up every once in a while is the need for more private, one-on-one support through e-mail, chat, or phone, without posting to the public mailing list, and with more immediate responses. We are looking into providing commercial support plans for those companies that want them. These would be paid priority support plans, meaning that we'll handle these support requests before those on the mailing list. They would take place on our new private support tracker, meaning confidential data can be uploaded without fear that it'll be visible in a public place. Depending on the support plan, we'd also provide backports of patches (when possible) to older versions of Review Board as needed by customers. There are some more benefits, which I'll link to in a minute. We're working on putting this together, but want to put out feelers. If this is something your company may be interested in, I'd love to hear what sort of plan would cover your needs, or what your needs consist of. You can see our current thoughts on the breakdown of plans, benefits, and pricing: http://support.beanbaginc.com/customer/portal/articles/709788-commercial-support (The prices are based on the support plans of similar development tools and services.) I want to point out that our free support on this mailing list is not going away or changing. We will continue to provide support on here as time permits, just as we do today. We will, however, prioritize the paid plans over mailing list plans, which I don't expect will change response times much on this mailing list. (Think of it this way: A support request on a paid plan is set to wake me up at night, whereas free support on the mailing list will wait until after breakfast.) If you have thoughts on this, or if your company may be interested in being on the wait list for commercial support, please fill out the form below: http://bit.ly/U5hE1m You can also e-mail me directly with any questions. Thanks, Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Unable to post review from cvs commitinfo trigger
Hi, Opening a fresh post to avoid any old mess..need urgent help. I am trying to use post review with every cvs commit. Applying a trigger in cvs commitinfo file as follows $cat commitinfo /usr/bin/post-review --server=http://172.16.7.100:81 -- username=admin --password=admin --submit-as=vineet --repository- url=svn:/opt/cvsroot [user@svn test]$ cat .reviewboardrc REPOSITORY = 'svn:/opt/cvsroot' REVIEWBOARD_URL = 'http://172.16.37.170:81' Repository Information in reviewboard dashboard Path=svn:/opt/cvsroot Mirror Path=svn:/opt/cvsroot What error i get is - [user@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci -m BugID: 47300 update document.txt Post-review for /opt/cvsroot/test No supported repository could be accessed at the supplied url. If i remove --repository-url=svn:/opt/cvsroot from commitinfo file i get this error- [kapila.narang@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci - m BugID:47300 update document.txt Post-review for /opt/cvsroot/test The current directory does not contain a checkout from a supported source code repository. Need urgent help pls expert help meee :( -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Unable to post review from cvs commitinfo trigger
to Add more details- [kapila.narang@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci - m BugID:47300 update document.txt Post-review for /opt/cvsroot/test RBTools 0.4.1 Home = /home/kapilacvs No supported repository could be accessed at the supplied url. On Aug 27, 2:52 pm, cmuser kapilanar...@gmail.com wrote: Hi, Opening a fresh post to avoid any old mess..need urgent help. I am trying to use post review with every cvs commit. Applying a trigger in cvs commitinfo file as follows $cat commitinfo /usr/bin/post-review --server=http://172.16.7.100:81 -- username=admin --password=admin --submit-as=vineet --repository- url=svn:/opt/cvsroot [user@svn test]$ cat .reviewboardrc REPOSITORY = 'svn:/opt/cvsroot' REVIEWBOARD_URL = 'http://172.16.37.170:81' Repository Information in reviewboard dashboard Path=svn:/opt/cvsroot Mirror Path=svn:/opt/cvsroot What error i get is - [user@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci -m BugID: 47300 update document.txt Post-review for /opt/cvsroot/test No supported repository could be accessed at the supplied url. If i remove --repository-url=svn:/opt/cvsroot from commitinfo file i get this error- [kapila.narang@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci - m BugID:47300 update document.txt Post-review for /opt/cvsroot/test The current directory does not contain a checkout from a supported source code repository. Need urgent help pls expert help meee :( -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
RBTools review creating taking very long
Hi there,
Using post-review the review creation usually took in the order of a few
seconds. Now, all of a sudden, it takes almost 10 minutes. Nothing changed on
the server or clients as far as I am aware. I am troubleshooting it now and
turned on the '-debug' option of post review. I get the output listed below.
Every HTTP GETting command takes a good few seconds.
Any pointers would be much appreciated. I googled for similar things but could
not find any.
Best regards,
RBTools 0.4.1
Home = C:\Users\elarduse\AppData\Roaming
HTTP GETting api/
HTTP GETting http://HQDCTWS019:50001/api/info/
Using the new web API
HTTP GETting http://HQDCTWS019:50001/api/review-requests/581/
Attempting to set field 'target_groups' to 'DCTEmbedded' for review request
'581'
HTTP PUTting to http://HQDCTWS019:50001/api/review-requests/581/draft/: {'ta
rget_groups': 'DCTEmbedded'}
HTTP GETting http://HQDCTWS019:50001/api/repositories/
HTTP GETting http://HQDCTWS019:50001/api/repositories/?start=25max-results=
25
HTTP GETting http://HQDCTWS019:50001/api/repositories/1/
HTTP GETting http://HQDCTWS019:50001/api/repositories/1/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/2/
HTTP GETting http://HQDCTWS019:50001/api/repositories/2/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/3/
HTTP GETting http://HQDCTWS019:50001/api/repositories/3/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/4/
HTTP GETting http://HQDCTWS019:50001/api/repositories/4/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/5/
HTTP GETting http://HQDCTWS019:50001/api/repositories/5/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/6/
HTTP GETting http://HQDCTWS019:50001/api/repositories/6/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/7/
HTTP GETting http://HQDCTWS019:50001/api/repositories/7/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/8/
HTTP GETting http://HQDCTWS019:50001/api/repositories/8/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/9/
HTTP GETting http://HQDCTWS019:50001/api/repositories/9/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/10/
HTTP GETting http://HQDCTWS019:50001/api/repositories/10/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/11/
HTTP GETting http://HQDCTWS019:50001/api/repositories/11/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/12/
HTTP GETting http://HQDCTWS019:50001/api/repositories/12/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/13/
HTTP GETting http://HQDCTWS019:50001/api/repositories/13/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/14/
HTTP GETting http://HQDCTWS019:50001/api/repositories/14/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/15/
HTTP GETting http://HQDCTWS019:50001/api/repositories/15/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/16/
HTTP GETting http://HQDCTWS019:50001/api/repositories/16/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/17/
HTTP GETting http://HQDCTWS019:50001/api/repositories/17/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/18/
HTTP GETting http://HQDCTWS019:50001/api/repositories/18/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/19/
HTTP GETting http://HQDCTWS019:50001/api/repositories/19/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/20/
HTTP GETting http://HQDCTWS019:50001/api/repositories/20/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/21/
HTTP GETting http://HQDCTWS019:50001/api/repositories/21/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/22/
HTTP GETting http://HQDCTWS019:50001/api/repositories/22/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/23/
HTTP GETting http://HQDCTWS019:50001/api/repositories/23/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/24/
HTTP GETting http://HQDCTWS019:50001/api/repositories/24/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/25/
HTTP GETting http://HQDCTWS019:50001/api/repositories/25/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/26/
HTTP GETting http://HQDCTWS019:50001/api/repositories/26/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/27/
HTTP GETting http://HQDCTWS019:50001/api/repositories/27/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/28/
HTTP GETting http://HQDCTWS019:50001/api/repositories/28/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/29/
HTTP GETting http://HQDCTWS019:50001/api/repositories/29/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/30/
HTTP GETting http://HQDCTWS019:50001/api/repositories/30/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/31/
HTTP GETting http://HQDCTWS019:50001/api/repositories/31/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/32/
HTTP GETting http://HQDCTWS019:50001/api/repositories/32/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/33/
Re: SVN 1.7 support
Do you happen to recall if you stripped out the new 1.7 stuff from the diff, or did you modify pysvn or RB to handle the new content? We're about to try something to handle these as well, and are considering the pros/cons of both approaches. (I'd prefer the latter, but suspect implementing the former is much easier.) m@ On Thursday, August 23, 2012 8:38:50 AM UTC-5, Elardus wrote: I have. Just don’t ask me for the steps. They are long forgotten. But it was not too much of a hassle IIRC. Elardus *Elardus Erasmus* DigiCore Technologies (Pty) Ltd Embedded Software Engineer *Tel:* +27 12 450 2272 • *Fax:* +27 12 450 2311 ** *Email: *elar...@digicore.co.za javascript: *•* *Website: * www.ctrack.co.za *• Email *Disclaimerhttp://www.ctrack.co.za/about_ctrack/email_signature_disclaimer.aspx *From:* revie...@googlegroups.com javascript: [mailto: revie...@googlegroups.com javascript:] *On Behalf Of *Daniel Laird *Sent:* 23 August 2012 15:25 *To:* revie...@googlegroups.com javascript: *Subject:* SVN 1.7 support Has anyone managed to patch or modify reviewboard so that diffs generated under SVN 1.7 actually work with post-review and ReviewBoard? The upgrade to SVN is about to hit my department and it will be a shame to stop reviewing code as a result of this change Dan -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
RE: SVN 1.7 support
IIRC: - the sever (ubuntu) was upgraded to the latest 1.7 subversion - clients (on windows) were upgraded to the latest subversion (1.7.4 at that time) - RBtools on clients upgraded to 0.4.1. I did not strip out/modify anything. The only problem I ran into was that the diff.exe program of the svn client installation messed with my GNU diff.exe path. I sorted that and it worked. Now that I think about it, I may have upgraded pysvn on the server also since some compatibility issues were reported (google). Elardus Erasmus DigiCore Technologies (Pty) Ltd Embedded Software Engineer [cid:image90a104.JPG@c27b87cc.0b9e4341] Tel: +27 12 450 2272 * Fax: +27 12 450 2311 Email: elard...@digicore.co.za * Website: www.ctrack.co.zahttp://www.ctrack.co.za/ * Email Disclaimerhttp://www.ctrack.co.za/about_ctrack/email_signature_disclaimer.aspx From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of mxbraun Sent: 27 August 2012 16:29 To: reviewboard@googlegroups.com Subject: Re: SVN 1.7 support Do you happen to recall if you stripped out the new 1.7 stuff from the diff, or did you modify pysvn or RB to handle the new content? We're about to try something to handle these as well, and are considering the pros/cons of both approaches. (I'd prefer the latter, but suspect implementing the former is much easier.) m@ On Thursday, August 23, 2012 8:38:50 AM UTC-5, Elardus wrote: I have. Just don't ask me for the steps. They are long forgotten. But it was not too much of a hassle IIRC. Elardus Elardus Erasmus DigiCore Technologies (Pty) Ltd Embedded Software Engineer [https://groups.google.com/group/reviewboard/attach/ef2bb6a87cdee452/image892851.JPG@83b7751c.bc184850?part=4authuser=0] Tel: +27 12 450 2272 * Fax: +27 12 450 2311 Email: elar...@digicore.co.zajavascript: * Website: www.ctrack.co.zahttp://www.ctrack.co.za/ * Email Disclaimerhttp://www.ctrack.co.za/about_ctrack/email_signature_disclaimer.aspx From: revie...@googlegroups.comjavascript: [mailto:revie...@googlegroups.comjavascript:] On Behalf Of Daniel Laird Sent: 23 August 2012 15:25 To: revie...@googlegroups.comjavascript: Subject: SVN 1.7 support Has anyone managed to patch or modify reviewboard so that diffs generated under SVN 1.7 actually work with post-review and ReviewBoard? The upgrade to SVN is about to hit my department and it will be a shame to stop reviewing code as a result of this change Dan -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.comjavascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=eninline: image90a104.JPG@c27b87cc.0b9e4341
Re: SVN 1.7 support
Hmmm...Thanks for the data point. It's interesting that that setup isn't encountering any problems. We're running: - A Linux distro with SVN 1.7.6 built from source - pysvn 1.7.6, again built using the 1.7.6 source-built SVN version. - Diffs built with cygwin's SVN 1.7.5 client I haven't used post-review in testing, because some of our users don't use it. We're encountering problems with diff's containing property changes, which is basically the issue reported in Bug #5309. Thanks again, m@ On Monday, August 27, 2012 9:46:31 AM UTC-5, Elardus wrote: IIRC: - the sever (ubuntu) was upgraded to the latest 1.7 subversion - clients (on windows) were upgraded to the latest subversion (1.7.4 at that time) - RBtools on clients upgraded to 0.4.1. I did not strip out/modify anything. The only problem I ran into was that the diff.exe program of the svn client installation messed with my GNU diff.exe path. I sorted that and it worked. Now that I think about it, I may have upgraded pysvn on the server also since some compatibility issues were reported (google). *Elardus Erasmus* DigiCore Technologies (Pty) Ltd Embedded Software Engineer *Tel:* +27 12 450 2272 • *Fax:* +27 12 450 2311 ** *Email: *elar...@digicore.co.za javascript: *•* *Website: * www.ctrack.co.za *• Email *Disclaimerhttp://www.ctrack.co.za/about_ctrack/email_signature_disclaimer.aspx *From:* revie...@googlegroups.com javascript: [mailto: revie...@googlegroups.com javascript:] *On Behalf Of *mxbraun *Sent:* 27 August 2012 16:29 *To:* revie...@googlegroups.com javascript: *Subject:* Re: SVN 1.7 support Do you happen to recall if you stripped out the new 1.7 stuff from the diff, or did you modify pysvn or RB to handle the new content? We're about to try something to handle these as well, and are considering the pros/cons of both approaches. (I'd prefer the latter, but suspect implementing the former is much easier.) m@ On Thursday, August 23, 2012 8:38:50 AM UTC-5, Elardus wrote: I have. Just don’t ask me for the steps. They are long forgotten. But it was not too much of a hassle IIRC. Elardus *Elardus Erasmus* DigiCore Technologies (Pty) Ltd Embedded Software Engineer *Tel:* +27 12 450 2272 • *Fax:* +27 12 450 2311 *Email: *elar...@digicore.co.za *•* *Website: *www.ctrack.co.za *•** **Email *Disclaimerhttp://www.ctrack.co.za/about_ctrack/email_signature_disclaimer.aspx *From:* revie...@googlegroups.com [mailto:revie...@googlegroups.com] *On Behalf Of *Daniel Laird *Sent:* 23 August 2012 15:25 *To:* revie...@googlegroups.com *Subject:* SVN 1.7 support Has anyone managed to patch or modify reviewboard so that diffs generated under SVN 1.7 actually work with post-review and ReviewBoard? The upgrade to SVN is about to hit my department and it will be a shame to stop reviewing code as a result of this change Dan -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: SVN 1.7 support
I'm working on a patch for the property changes. Are there other things people are hitting that you can give me repro steps/example diffs for? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Mon, Aug 27, 2012 at 9:36 AM, mxbraun matthew.braun%intel@gtempaccount.com wrote: Hmmm...Thanks for the data point. It's interesting that that setup isn't encountering any problems. We're running: - A Linux distro with SVN 1.7.6 built from source - pysvn 1.7.6, again built using the 1.7.6 source-built SVN version. - Diffs built with cygwin's SVN 1.7.5 client I haven't used post-review in testing, because some of our users don't use it. We're encountering problems with diff's containing property changes, which is basically the issue reported in Bug #5309. Thanks again, m@ On Monday, August 27, 2012 9:46:31 AM UTC-5, Elardus wrote: IIRC: - the sever (ubuntu) was upgraded to the latest 1.7 subversion - clients (on windows) were upgraded to the latest subversion (1.7.4 at that time) - RBtools on clients upgraded to 0.4.1. I did not strip out/modify anything. The only problem I ran into was that the diff.exe program of the svn client installation messed with my GNU diff.exe path. I sorted that and it worked. Now that I think about it, I may have upgraded pysvn on the server also since some compatibility issues were reported (google). *Elardus Erasmus* DigiCore Technologies (Pty) Ltd Embedded Software Engineer *Tel:* +27 12 450 2272 • *Fax:* +27 12 450 2311 ** *Email: *elar...@digicore.co.za *•* *Website: *www.ctrack.co.za *• Email *Disclaimerhttp://www.ctrack.co.za/about_ctrack/email_signature_disclaimer.aspx *From:* revie...@googlegroups.com [mailto:revie...@**googlegroups.com] *On Behalf Of *mxbraun *Sent:* 27 August 2012 16:29 *To:* revie...@googlegroups.com *Subject:* Re: SVN 1.7 support Do you happen to recall if you stripped out the new 1.7 stuff from the diff, or did you modify pysvn or RB to handle the new content? We're about to try something to handle these as well, and are considering the pros/cons of both approaches. (I'd prefer the latter, but suspect implementing the former is much easier.) m@ On Thursday, August 23, 2012 8:38:50 AM UTC-5, Elardus wrote: I have. Just don’t ask me for the steps. They are long forgotten. But it was not too much of a hassle IIRC. Elardus *Elardus Erasmus* DigiCore Technologies (Pty) Ltd Embedded Software Engineer *Tel:* +27 12 450 2272 • *Fax:* +27 12 450 2311 *Email: *elar...@digicore.co.za *•* *Website: *www.ctrack.co.za *•** **Email *Disclaimerhttp://www.ctrack.co.za/about_ctrack/email_signature_disclaimer.aspx *From:* revie...@googlegroups.com [mailto:revie...@googlegroups.**com] *On Behalf Of *Daniel Laird *Sent:* 23 August 2012 15:25 *To:* revie...@googlegroups.com *Subject:* SVN 1.7 support Has anyone managed to patch or modify reviewboard so that diffs generated under SVN 1.7 actually work with post-review and ReviewBoard? The upgrade to SVN is about to hit my department and it will be a shame to stop reviewing code as a result of this change Dan -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/ http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard...@googlegroups.**com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/ http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard...@** googlegroups.com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send
Re: RBTools review creating taking very long
Hi,
The problem is that it's having to do an 'svn info' on each repository, due
to how you're associating the repository. Apparently that's become slower
than it used to be.
I'm not sure why it's trying to fetch that data at that point.
Can you show me the command line parameters you are using?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Aug 27, 2012 at 6:18 AM, Elardus Erasmus elard...@digicore.co.zawrote:
Hi there,
** **
Using post-review the review creation usually took in the order of a few
seconds. Now, all of a sudden, it takes almost 10 minutes. Nothing changed
on the server or clients as far as I am aware. I am troubleshooting it now
and turned on the ‘–debug’ option of post review. I get the output listed
below. Every “HTTP GETting” command takes a good few seconds.
** **
Any pointers would be much appreciated. I googled for similar things but
could not find any.
** **
Best regards,
** **
** **
RBTools 0.4.1
Home = C:\Users\elarduse\AppData\Roaming
HTTP GETting api/
HTTP GETting http://HQDCTWS019:50001/api/info/
Using the new web API
HTTP GETting http://HQDCTWS019:50001/api/review-requests/581/
Attempting to set field 'target_groups' to 'DCTEmbedded' for review
request
'581'
HTTP PUTting to http://HQDCTWS019:50001/api/review-requests/581/draft/:
{'ta
rget_groups': 'DCTEmbedded'}
HTTP GETting http://HQDCTWS019:50001/api/repositories/
HTTP GETting
http://HQDCTWS019:50001/api/repositories/?start=25max-results=
25
HTTP GETting http://HQDCTWS019:50001/api/repositories/1/
HTTP GETting http://HQDCTWS019:50001/api/repositories/1/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/2/
HTTP GETting http://HQDCTWS019:50001/api/repositories/2/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/3/
HTTP GETting http://HQDCTWS019:50001/api/repositories/3/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/4/
HTTP GETting http://HQDCTWS019:50001/api/repositories/4/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/5/
HTTP GETting http://HQDCTWS019:50001/api/repositories/5/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/6/
HTTP GETting http://HQDCTWS019:50001/api/repositories/6/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/7/
HTTP GETting http://HQDCTWS019:50001/api/repositories/7/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/8/
HTTP GETting http://HQDCTWS019:50001/api/repositories/8/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/9/
HTTP GETting http://HQDCTWS019:50001/api/repositories/9/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/10/
HTTP GETting http://HQDCTWS019:50001/api/repositories/10/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/11/
HTTP GETting http://HQDCTWS019:50001/api/repositories/11/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/12/
HTTP GETting http://HQDCTWS019:50001/api/repositories/12/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/13/
HTTP GETting http://HQDCTWS019:50001/api/repositories/13/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/14/
HTTP GETting http://HQDCTWS019:50001/api/repositories/14/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/15/
HTTP GETting http://HQDCTWS019:50001/api/repositories/15/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/16/
HTTP GETting http://HQDCTWS019:50001/api/repositories/16/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/17/
HTTP GETting http://HQDCTWS019:50001/api/repositories/17/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/18/
HTTP GETting http://HQDCTWS019:50001/api/repositories/18/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/19/
HTTP GETting http://HQDCTWS019:50001/api/repositories/19/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/20/
HTTP GETting http://HQDCTWS019:50001/api/repositories/20/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/21/
HTTP GETting http://HQDCTWS019:50001/api/repositories/21/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/22/
HTTP GETting http://HQDCTWS019:50001/api/repositories/22/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/23/
HTTP GETting http://HQDCTWS019:50001/api/repositories/23/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/24/
HTTP GETting http://HQDCTWS019:50001/api/repositories/24/info/
HTTP GETting http://HQDCTWS019:50001/api/repositories/25/
HTTP GETting
Re: Unable to post review from cvs commitinfo trigger
Is that directory you're running it in part of a CVS checkout? Set REPOSITORY to the name, not the path, of the repository you want to post to in Review Board. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Mon, Aug 27, 2012 at 5:18 AM, cmuser kapilanar...@gmail.com wrote: to Add more details- [kapila.narang@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci - m BugID:47300 update document.txt Post-review for /opt/cvsroot/test RBTools 0.4.1 Home = /home/kapilacvs No supported repository could be accessed at the supplied url. On Aug 27, 2:52 pm, cmuser kapilanar...@gmail.com wrote: Hi, Opening a fresh post to avoid any old mess..need urgent help. I am trying to use post review with every cvs commit. Applying a trigger in cvs commitinfo file as follows $cat commitinfo /usr/bin/post-review --server=http://172.16.7.100:81 -- username=admin --password=admin --submit-as=vineet --repository- url=svn:/opt/cvsroot [user@svn test]$ cat .reviewboardrc REPOSITORY = 'svn:/opt/cvsroot' REVIEWBOARD_URL = 'http://172.16.37.170:81' Repository Information in reviewboard dashboard Path=svn:/opt/cvsroot Mirror Path=svn:/opt/cvsroot What error i get is - [user@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci -m BugID: 47300 update document.txt Post-review for /opt/cvsroot/test No supported repository could be accessed at the supplied url. If i remove --repository-url=svn:/opt/cvsroot from commitinfo file i get this error- [kapila.narang@svn test]$ cvs -d :pserver:kapilap@svn:/opt/cvsroot ci - m BugID:47300 update document.txt Post-review for /opt/cvsroot/test The current directory does not contain a checkout from a supported source code repository. Need urgent help pls expert help meee :( -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Unable to authenticate against this repository using one of the supported authentication types.
No. I don't know how to set up an SSH key to use for RB. On 8月27日, 下午1时48分, Christian Hammond chip...@chipx86.com wrote: I'd need to know more about how you have your Git repository and your Review Board repository information configured. Did you set up an SSH key? Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Sun, Aug 26, 2012 at 10:00 PM, zhihang wang zhihang.w...@gmail.comwrote: Hello, I have installed reviewboard on ubuntu 10.04. I want to add a repository to reviewboard. My repository is managed by gitolite. But when I add a repository to reviewborad, it says: Unable to authenticate against this repository using one of the supported authentication types. How to resolve this problem? -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know athttp://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
