[JIRA] (OVIRT-634) sending POST/PUT to gerrit to ... set a topic for example.

[eyal edri [Administrator] (oVirt JIRA)]

     [ https://ovirt-jira.atlassian.net/browse/OVIRT-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

eyal edri [Administrator] reassigned OVIRT-634:
-----------------------------------------------

    Assignee: Shlomo Ben David  (was: infra)

> sending POST/PUT to gerrit to ... set a topic for example.
> ----------------------------------------------------------
>
>                 Key: OVIRT-634
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-634
>             Project: oVirt - virtualization made easy
>          Issue Type: By-EMAIL
>            Reporter: Martin Mucha
>            Assignee: Shlomo Ben David
>
> Hi,
> I'd like to ask, whether:
> a) is even possible to pass requests to do some modifications on gerrit
> b) if it is, then when I'd be glad if you can inform me, what I'm doing wrong in following command [1]
> c) if it's not currently possible to pass such requests, I'd like to ask if they can be allowed.
> Motivation: I have quite often longer topics, like 10 patches. Due to our work style they need to be rebased often and reverified. Or I need to specify same reviewers to all of them. etc. etc. This means I have to open *all* of them (takes ages to load) and do same actions over and over, which is time waste. Also, gerrit is (apparently) not designed to work under 'heavy' load, which means, that quite often page isn't loaded successfully. For example change is loaded, but allegedly I'm not logged in (which is not true), and because of that I have to hit refresh. This means, that I'm generating a lot of unnecessary load for gerrit server, while what I'd actually like to do is for example set topic to 10 patches, for which I do not need whole detail with all revisions to be loaded.
> [1]
> curl --digest -v -H Content-Type:application/json -u "mmucha:pass" -X PUT https://gerrit.ovirt.org/changes/58620/topic -d '{"topic":"test"}'
> this return 403, and I'd like to know, if this is because of error in this command, or because this type of operations are generally not allowed.
> Thanks,
> M.



--
This message was sent by Atlassian JIRA
(v1000.184.1#100008)