Review Board Extension : Custom Email Notification
Hi All, I want to send email notification as part of my extension implementation. Is there anyway to re-use review board email notifications module? Kindly share your thoughts.. Regards, Parthiban P. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgrading Review Board from 1.0.5.1 to 2.0.15
Thanks Christian
Is enough to run?
easy_install -U django_evolution
Best
El lunes, 13 de abril de 2015, 21:13:50 (UTC-6), Christian Hammond escribió:
Hi Rodrigo,
This is due to a bug in the current version of Django Evolution. We have
fixes pending for a release. I'll work to get that out tonight. Tomorrow,
upgrade the django_evolution package, and you should be good.
Christian
On Monday, April 13, 2015, Rodrigo Castro rodrigo@gmail.com
javascript: wrote:
Hello,
I am trying to upgrade rb from 1.0.5 to 2.0.15 (in the attachment the old
db schema)
I am following this steps.
1. Install a fresh new 2.0.15
2. Restore the old 1.0.5 database (in replace of the newer one that I
just installed)
3. Execute rb-site upgrade /var/www/rb.searchrev.com/
But I am getting the following errors.
[root@reviewboard conf]# rb-site upgrade /var/www/rb.searchrev.com/
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- begin log output --
Creating tables ...
Creating table extensions_registeredextension
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Creating table site_localsite_admins
Creating table site_localsite
Upgrading Review Board from 1.0.5.1 to 2.0.15
There are unapplied evolutions for auth.
There are unapplied evolutions for contenttypes.
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for hostingsvcs.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
There are unapplied evolutions for site.
Adding baseline version for new models
Evolutions in attachments baseline: file_attachment_orig_filename,
file_attachment_file_max_length_512, file_attachment_repo_info,
file_attachment_repo_path_no_index,
file_attachment_repo_revision_max_length_64
Evolutions in site baseline: localsite_public
Evolutions in hostingsvcs baseline: account_hosting_url,
account_hosting_url_max_length_255, account_unique_together_baseline
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
The stored evolutions do not completely resolve all model changes.
Run `./manage.py evolve --hint` to see a suggestion for the changes
required.
The following are the changes that could not be resolved:
The application markup has been deleted
In model reviews.DefaultReviewer:
In field 'repository':
Property 'null' has changed
In model reviews.ReviewRequest:
In field 'repository':
Property 'null' has changed
CommandError: Your models contain changes that Django Evolution cannot
resolve automatically.
In a second attempt I read I need to copy some data from the newer
database in order to complete the upgrade.
in the old database
insert into django_evolution select * from rb_install.django_evolution;
insert into django_project_version select * from
rb_install.django_project_version;
and then try again the upgrade
But after that I am getting this error.
[root@reviewboard conf]# rb-site upgrade /var/www/rb.searchrev.com/
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- begin log output --
Creating tables ...
Creating table extensions_registeredextension
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Creating table site_localsite_admins
Creating table site_localsite
Upgrading Review Board from 1.0.5.1 to 2.0.15
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
No evolution required.
--- end log output ---
Resetting in-database caches.
Traceback (most recent call last):
File /usr/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==2.0.15', 'console_scripts',
'rb-site')()
File /usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py,
line 1885, in main
command.run()
File
Re: Issue 3446 in reviewboard: ReviewRequestFieldsHook and email notfications
Comment #4 on issue 3446 by nitesha...@gmail.com: ReviewRequestFieldsHook and email notfications https://code.google.com/p/reviewboard/issues/detail?id=3446 +1. Without this, I plan to just patch reviewboard/notifications/email.py and replace reviewboard/templates/notifications/review_request_email.html and reviewboard/templates/notifications/review_request_email.txt. Of course, this makes maintenance uglier. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Review Board Extension : Custom Email Notification
Parthiban, It's possible that the SpiffyEmailMessage class and some of the utility functions might be useful to you. Beyond that, everything else should just be set up for you to use Django's built-in e-mail APIs. -David On Tue, Apr 14, 2015 at 1:48 AM Parthiban parthi...@gmail.com wrote: Hi All, I want to send email notification as part of my extension implementation. Is there anyway to re-use review board email notifications module? Kindly share your thoughts.. Regards, Parthiban P. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hide repository from New Review Request
Publicly accessible is used for access control (and will restrict whether people can see review requests posted against that repository). The check-box you want is Show this repository -David On Tue, Apr 14, 2015 at 5:53 PM MoonWalker daniel.cabrera...@gmail.com wrote: hi, We are in the process to migrate some of our repos to Git and I would like to keep the history of the old repos . On admin-Repositories-My repo-Access control-Publicly accessible I turned off this option and I was expecting to do not see this repo when I am in New Review Request, but this repo still show up. Am I missing something here? Cheers -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hide repository from New Review Request
Thank you for your help David :-). Apologize for the trivial and silly question. I have been migrating our repos for +12hrs :-/. Time to take a brake and sleep thx again for your help :-) On Wednesday, April 15, 2015 at 10:54:42 AM UTC+10, David Trowbridge wrote: Publicly accessible is used for access control (and will restrict whether people can see review requests posted against that repository). The check-box you want is Show this repository -David On Tue, Apr 14, 2015 at 5:53 PM MoonWalker daniel.c...@gmail.com javascript: wrote: hi, We are in the process to migrate some of our repos to Git and I would like to keep the history of the old repos . On admin-Repositories-My repo-Access control-Publicly accessible I turned off this option and I was expecting to do not see this repo when I am in New Review Request, but this repo still show up. Am I missing something here? Cheers -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Hide repository from New Review Request
hi, We are in the process to migrate some of our repos to Git and I would like to keep the history of the old repos . On admin-Repositories-My repo-Access control-Publicly accessible I turned off this option and I was expecting to do not see this repo when I am in New Review Request, but this repo still show up. Am I missing something here? Cheers -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 3845 in reviewboard: When reviewing the updated diff, original comments should be visible for verification
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3845 by viney.ya...@gmail.com: When reviewing the updated diff, original comments should be visible for verification https://code.google.com/p/reviewboard/issues/detail?id=3845 ReviewBoard Version: 2.0.6 URL of the page containing the problem: http://server/r/94/diff/1-2/ OS: Windows 7, Browser: FIrefox 37.0.1 Steps to reproduce the problem: 1. Post a review for a file between version A and version B. 2. Post some comments. 3. Close the comment. 4. Update the diff with new code (version C) 5. Now check the changes done to address the comments (i.e. diff between B and C). What do I see: The comments given in step 2 above are not visible when I want to see the changed done to address the comments. So I have to open a separate tab to see what the comment were and switch between the tabs for verification. Expected output: The comments were given on version B. So when viewing the diff between versions B and C, the comments should also be visible. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: How to access local site?
The URL will be your reviewboard URL plus /s/trial_reviewboard1/ -David On Mon, Apr 13, 2015 at 9:53 PM shilpageo shilpa.anan...@gmail.com wrote: Hi, I have reviewboard site /trial/reviewboard/ . In which I have created local site of name trial_reviewboard1. What is url of local site? How can I access it? -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Upgrading Review Board from 1.0.5.1 to 2.0.15
Thank you Christian,
I confirm It works!
El lunes, 13 de abril de 2015, 21:13:50 (UTC-6), Christian Hammond escribió:
Hi Rodrigo,
This is due to a bug in the current version of Django Evolution. We have
fixes pending for a release. I'll work to get that out tonight. Tomorrow,
upgrade the django_evolution package, and you should be good.
Christian
On Monday, April 13, 2015, Rodrigo Castro rodrigo@gmail.com
javascript: wrote:
Hello,
I am trying to upgrade rb from 1.0.5 to 2.0.15 (in the attachment the old
db schema)
I am following this steps.
1. Install a fresh new 2.0.15
2. Restore the old 1.0.5 database (in replace of the newer one that I
just installed)
3. Execute rb-site upgrade /var/www/rb.searchrev.com/
But I am getting the following errors.
[root@reviewboard conf]# rb-site upgrade /var/www/rb.searchrev.com/
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- begin log output --
Creating tables ...
Creating table extensions_registeredextension
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Creating table site_localsite_admins
Creating table site_localsite
Upgrading Review Board from 1.0.5.1 to 2.0.15
There are unapplied evolutions for auth.
There are unapplied evolutions for contenttypes.
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for hostingsvcs.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
There are unapplied evolutions for site.
Adding baseline version for new models
Evolutions in attachments baseline: file_attachment_orig_filename,
file_attachment_file_max_length_512, file_attachment_repo_info,
file_attachment_repo_path_no_index,
file_attachment_repo_revision_max_length_64
Evolutions in site baseline: localsite_public
Evolutions in hostingsvcs baseline: account_hosting_url,
account_hosting_url_max_length_255, account_unique_together_baseline
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
The stored evolutions do not completely resolve all model changes.
Run `./manage.py evolve --hint` to see a suggestion for the changes
required.
The following are the changes that could not be resolved:
The application markup has been deleted
In model reviews.DefaultReviewer:
In field 'repository':
Property 'null' has changed
In model reviews.ReviewRequest:
In field 'repository':
Property 'null' has changed
CommandError: Your models contain changes that Django Evolution cannot
resolve automatically.
In a second attempt I read I need to copy some data from the newer
database in order to complete the upgrade.
in the old database
insert into django_evolution select * from rb_install.django_evolution;
insert into django_project_version select * from
rb_install.django_project_version;
and then try again the upgrade
But after that I am getting this error.
[root@reviewboard conf]# rb-site upgrade /var/www/rb.searchrev.com/
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- begin log output --
Creating tables ...
Creating table extensions_registeredextension
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Creating table site_localsite_admins
Creating table site_localsite
Upgrading Review Board from 1.0.5.1 to 2.0.15
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM
(reviewboard.scmtools.plastic.PlasticTool) in database
No evolution required.
--- end log output ---
Resetting in-database caches.
Traceback (most recent call last):
File /usr/bin/rb-site, line 9, in module
load_entry_point('ReviewBoard==2.0.15', 'console_scripts',
'rb-site')()
File /usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py,
line 1885, in main
command.run()
File
