gerrit

问题 If I have multiple patch set versions for one change in Gerrit, it seems like I can only submit the latest patch set version (because only that one has the necessary button). Is there an easy way to instead submit one of the old patch set versions of the same change, using only my web browser on that Gerrit instance? I know that I can fetch the wanted version of the patch set from my git client and push it as yet another new patch set version on top, but I would like to avoid having identical

问题 I have configured jenkins with gerrit trigger plugin to validate every commit we push to gerrit. I am expecting this trigger to include my latest change with original repo and make a build. But, it is cloning only repo project and compiling without my change. Below is my configuration settings for gerrit trigger in jenkins. Refspec: $GERRIT_REFSPEC Branches to build: $GERRIT_BRANCH Build trigger: Gerrit event Trigger on: patch set created Gerrit project: added project and branch Below is the

问题 I found that when clicking "Submit Patch Set" in the Gerrit web interface, it'll either simply add a commit to that branch, or create a merge commit if another commit was submitted just before. Example that creates 2 commit: The actual commit and a merge commit: User submits patchset A depending on commit O User submits patchset B depending on commit O Submit Patch Set A Submit Patch Set B --> Creates merge commit between O -> A and O -> B There is a "Rebase Change" button which is great but

问题 Still trying to learn how to use Gerrit and its process. Steps I did where Push first change1 to gerrit for review to HEAD:refs/for/develop Work on something else on same branch and push change2 to gerrit for review to HEAD:refs/for/develop Both commits have gerrit Change-ID lines So now I want to address issue for change1 so I did git checkout -b change1 <change 1's commit id> Made my changes and committed (adding the Change-ID to the commit message) git add . git commit Now when I do git

问题 I have a branch called v2.0 in gerrit. Now I want to the current stat of this branch as v2.0.1 . In my local repository I checked out the branch, then added the tag using git tag v2.0.1 Now I'm trying to push that to gerrit, but I'm not sure how. I tried this: $ git push origin v2.0.1 HEAD:refs/heads/v2.0 ! [remote rejected] v2.0.1 -> v2.0 (prohibited by Gerrit) How can I push the tag to gerrit? 回答1: After some googling, I found the answer: gerrit accepts only annotated tags. It's quite

问题 When I try to push my commits from git repository to gerrit remote repository from Linux environment in IntelliJ idea I get the following error: remote: ERROR: committer email address ***** [K remote: ERROR: does not match your user account.[K Even if I changed the settings to the correct ones for git and gerrit (I can see that at: git config -l from console), it still picks the old "wrong" email. What could be wrong? 回答1: you need to reconfigure your email $ git config user.email <your email

问题 As a git best practice, one should commit frequently, but to review the code you may need to review a patch consisting of multiple commits at once. Is there a way multiple commits can be reviewed and either merged or rejected at once? 回答1: No, Gerrit does not currently support batching commits into one review. However, there are a couple other options. At $DAYJOB, my team uses feature branches for larger changes. The smaller commits are reviewed/merged to the feature branch individually, but

问题 I'm just getting started using GitHub, Gerrit, and Hudson(Jenkins) together. And I need some thoughts on workflow. We'd like to use GitHub as our main remote repo. We'd like to use Gerrit primarily for code reviews, but also for build triggers in Hudson. At the moment, though, I'm having some trouble thinking through the workflow for this and would like to hear what others have done themselves. Thoughts? 回答1: I haven't directly used Gerrit, but I like the idea of intermediate and specialized

问题 I am trying to set up Sonar Gerrit - Jenkins Plugin on a Jenkins job. Context A Jenkins job is launched when a patch set is created to Gerrit Source are pulled with git, cppcheck analysis is launched and a sonar analysis is launched on preview mode. Post-Build action "Post SonarQube issues as Gerrit comments" is launched. Here are the Jenkins analysis logs for the third point. Getting Sonar Report from: [XX].sonar\sonar-report.json Report has loaded and contains 2950 issues Connected to

问题 I'm struggling to find a good workflow when two or more people are pushing patch-set's to the same change-set in Gerrit. I am trying to accomplish this with command-line Git commands (no git-review, IDE, etc). Pulling down the latest patch-set from the Gerrit server for a particular change is easy enough, but from there I'm not sure. I would think the process would be: fetch latest patch-set for change from server rebase against latest patch-set push But during the rebase it marks all