Hi,
I have installed Review Board on Centos 7.
I tried to access the reviewboard site(http://). The below lines
are appears on the page
Manual server updates required
Permission problems
The data directory must be writable by the web server. On Linux/Unix/Mac,
you can fix this by typing:
Bill,
Ah OK that makes more sense. I'm not sure if we have the resources to
devote to developing and supporting dynamic web hook URLs in RB itself.
Theoretically you could reuse most of the existing webhook framework in
an extension to send to a custom URL.
Also if you're using post-review
Hi Barret,
Yes it is, the {issuekey} is a bug ID in JIRA, which looks like
{MYPROJECT-123}, and we customized the official post-commit script with
RBTools to post it as the bug number on the review request. After that we
can click the "Bugs" field and jump into JIRA very happpy.
But the
Hi Bill,
What exactly would {issueKey} be? Is that the bug number on the review
request?
Regards,
Barret
On Tue, 17 Jan, 2017 at 7:41 PM, Bill Hoo wrote:
Hi Christian,
Thanks for the reply. If we search in this group or Google, we can
find a lot of questions like "How to
Hi Christian,
Thanks for the reply. If we search in this group or Google, we can find a
lot of questions like "How to integrate ReviewBoard and JIRA?", if dynamic
URL still a technical problem, can we provide an official extension for
this feature or at least a plan on it? After all JIRA is a
Hi,
What rbt land will do is merge your local branch into your upstream branch
(like master) and then delete the local branch. Upstream won't need to know
about the branch, and you don't need to push it.
So:
$ git checkout master
$ rbt land my-branch
$ git push
That should be all
(Hrm. I wrote this days ago and apparently never sent it. Sorry!)
Hi Bill,
Thanks for the kind words :)
WebHooks today don't have any kind of dynamic URL support. What would
"{issuekey}" come from in Review Board?
An option is to build a simple extension that listens for the necessary
signals
Glad it's working!
If your settings_local.py was updated with a new password, the web server
would have needed a restart. Otherwise, there shouldn't have been any kind
of caching at play. Either way, works now :)
Christian
On Mon, Jan 16, 2017 at 07:45 wrote:
> Ok I rerun
Hey John,
We did. We have a fix that just finished going through review and landed in
our release-2.5.x branch last night. You can pull that out and apply it
locally if you want. We hope to release later this week or early next
(we're going to be quite swamped with something Thursday through
The repo contains a lot of branches and "stuff" that we don't want to
survey (and we don't want to make things to complicated for our users
ho well...), so the repo path points directly to the "trunk" of our
development.
Too much history and not enough forward thinking at the time...
10 matches
Mail list logo