Christian, thanks for your reply.
I think that the best way of using *RBTools post* in out case is with *-r*,
because each developer's change pushed to GIT may have different commit
message (summary passed to RB) and process should not wait for confirmation
in case of review request matching problem.
>From your response I assumed that RB API does not provide method which
returns review request ID according to given repository/branch name and
some API extension should be written by us?
Regards,
Lukasz
W dniu piątek, 26 października 2018 09:54:48 UTC+2 użytkownik Lukasz
napisał:
>
> Hello All!
> I have a question related to RBTools app (version 1.0.1).
>
> We have the following workflow - user pushes his changes to some
> defect/task branch (GIT) and post-receive hook calling RBT (post) creates a
> new review request in ReviewBoard (3.0.9).
>
> It's OK by the time when developer decides to push some new changes or fix
> to the same GIT branch. We expect that previously created review request
> would be updated with new revision and the same ID, but instead we have
> another review request with new ID.
>
> We are using the following command:
>
> rbt post --debug --publish --submit-as={user_id} --server=http://{RB_url}
> --username={user_id} --password={user_passwd} --disable-proxy
> --repository={repo_name} --branch=master --bugs-closed={defect_branch}
> --target-people={user_id} master..{defect_branch}
>
>
> We tested* --update* option but it's doesn't match proper review request
> ID and whats more - asking for update confirmation (we need a "silent" call
> without user prompt).
>
> Best option would be to use *-r {review_request_id}* argument, but there
> are several issues:
>
> 1. It's not the recommended way according to your blog:
> https://blog.beanbaginc.com/2014/12/08/5-tips-for-your-rbtools-workflow/
> ("*It’s much nicer. Get in the habit of using -u**. It’s the wave of the
> future.*").
>
> 2. We need to know the *review request ID *for the particular defect/task
> branch. What is the best way to get it without our changes, using built-in
> methods? Via RB API? We haven't found any useful examples.
>
> To sum up, we want to use RBT command in GIT post-receive hook, which
> creates new review request in ReviewBoard if changes are pushed for
> defect/task branch for the first time and updates this review request with
> new revisions for each GIT push on this branch (without user confirmation:
> Update? Yes/No).
>
> We would be grateful for any help or example - how the RBT command line
> should looks like.
>
> Best regards,
> Lukasz
>
>
>
>
--
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
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
