Hi,

I just installed the beta version, and had few problems.

1. Gerrit configuration was lost, and I had to add a new server.

2. Manual triggering from search didn't work. After following steps and
testing after everyone it started to work
    - I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
    - Changed server from Any Server to specific one
    - Touched every field in Project configuration (pattern, branch)
Then it started to work. After it started to work, I changed server back to
Any Server and Branch Specifier back to $GERRIT_REFSPEC and it seems to be
working.

Pushing to gerrit seems to be working, at least after I did those previous
steps.

I'll keep the beta version running and report if there's other problems.


On Thu, Nov 28, 2013 at 5:40 PM, Sandell, Robert <
[email protected]> wrote:

> The notify parameter is not something you can set (yet), there is probably
> still much that can be done to enhance the usage of the REST API.
>
> The only thing that is used from the command settings is the contents of
> the message.
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Øyvind Harboe
> *Sent:* den 28 november 2013 10:24
> *To:* [email protected]
> *Cc:* [email protected]
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>
>
> Hi Robert,
>
> I installed the beta because I would like to switch from the ssh commands
> to REST API commands in order to more carefully manage which email
> notifications are sent out.
>
>
> Is there any documentation or pointers on how I can change the line below,
> which adds a comment that a build was started, to the REST API command to
> do the same, but set notify=NONE?
>
>      gerrit approve <CHANGE>,<PATCHSET> --message 'Build Started
> <BUILDURL> <STARTED_STATS>' --verified <VERIFIED> --code-review
> <CODE_REVIEW>
>
>
>
> REST API feature that I would like to use:
>
>
> https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#review-input
>
>
>
>
>
>
>
> On Tuesday, November 26, 2013 4:15:19 PM UTC+1, Robert Sandell wrote:
>
> I just released version 2.11.0-beta-1 of the Gerrit Trigger plugin. It
> contains some great new features by some great contributors, the release
> notes are on the wiki [1].
>
> The support for multiple Gerrit servers required quite a lot of
> refactoring in central parts of the plugin that potentially could affect
> everything, so I released a beta  that should be available in the
> experimental update center [2] within the normal waiting period. And I am
> looking for some brave people who can help us test it and provide me with a
> hint if it is good enough for a “normal” release or if there is anything
> major in need of fixing before.
>
>
>
> Thanks,
>
> Bobby
>
>
>
> [1] https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger
>
> [2] Set your update center to
> http://updates.jenkins-ci.org/experimental/update-center.json
>
>
>
>
>
> *Robert Sandell*
>
> Software Tools Engineer
>
> SW Environment and Product Configuration
>
> Development Environment
>
>
>
> Sony Mobile Communications
>
> Tel: +46 (0)10 80 12721
>
> sonymobile.com
>
>
>
> [image: SONY make.believe]
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" 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/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" 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/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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/groups/opt_out.

Reply via email to