two otopi builds in a single jenkins job

[Gil Shinar]

Hi,

Pushed a patch that will add clean workspace before build starts. This
will solve the presence of old rpms under the workspace.
Downgraded the gerrit trigger plugin on the jenkins. That did added back
the retrigger link to the builds.

Thanks a lot, David.
Gil

On 03/14/2016 02:30 PM, David Caro wrote:
> On 03/14 14:11, Gil Shinar wrote:
>> Hi,
>>
>> Investigating a bit it does seems like dirty environment because I saw
>> in the console log that it had only build the 1.5.0*.src.rpm so it means
>> that the 1.4.2*.src.rpm were there before.
>> During the cleanup phase I can see the following:
>>
>> *15:55:47 **Making sure there are no device mappings... **15:55:47 **Removing the used loop devices... **15:55:48 **losetup: invalid option -- 'D' **15:55:48 ****15:55:48 **Usage: **15:55:48 **losetup loop_device give info **15:55:48 **losetup -a | --all list all used **15:55:48 **losetup -d | --detach <loopdev> [<loopdev> ...] delete **15:55:48 **losetup -f | --find find unused **15:55:48 **losetup -c | --set-capacity <loopdev> resize **15:55:48 **losetup -j | --associated <file> [-o <num>] list all associated with
>> <file> **15:55:48 **losetup [ options ] {-f|--find|loopdev} <file> setup **15:55:48 ****15:55:48 **Options: **15:55:48 **-e | --encryption <type> enable data encryption with specified <name/num> **15:55:48 **-h | --help this help **15:55:48 **-o | --offset <num> start at offset <num> into file **15:55:48 **--sizelimit <num> loop limited to only <num> bytes of the file **15:55:48 **-p | --pass-fd <num> read passphrase from file descriptor <num> **15:55:48 **-r | --read-only setup read-only loop device **15:55:48 **--show print device name (with -f <file>) **15:55:48 **-v | --verbose verbose mode **15:55:48 ****15:55:48 ****15:55:48 **Usage: **15:55:48 **losetup loop_device give info **15:55:48 **losetup -a | --all list all used **15:55:48 **losetup -d | --detach <loopdev> [<loopdev> ...] delete **15:55:48 **losetup -f | --find find unused **15:55:48 **losetup -c | --set-capacity <loopdev> resize **15:55:48 **losetup -j | --associated <file> [-o <num>] list all associated with
>> <file> **15:55:48 **losetup [ options ] {-f|--find|loopdev} <file> setup **15:55:48 ****15:55:48 **Options: **15:55:48 **-e | --encryption <type> enable data encryption with specified <name/num> **15:55:48 **-h | --help this help **15:55:48 **-o | --offset <num> start at offset <num> into file **15:55:48 **--sizelimit <num> loop limited to only <num> bytes of the file **15:55:48 **-p | --pass-fd <num> read passphrase from file descriptor <num> **15:55:48 **-r | --read-only setup read-only loop device **15:55:48 **--show print device name (with -f <file>) **15:55:48 **-v | --verbose verbose mode*
>>
>>
>> I think that this error interferes with the cleanup procedure. Am I wrong?
> This issue should not be related to the dirty workspace, though it should be
> fixed too (not critical or anything, happens because on el6 the losetup tool
> does not have the -D option to free all the loop devices :/)
>
>>
>> As for the retrigger link, I have no idea if it is missing on purpose or
>> should I fix that.
>> Can someone please assist?
> About the triggers:
>
>       Project created events requires 2.12
>
> from http://jenkins.ovirt.org/gerrit-trigger/server/gerrit.ovirt.org/
>
> :(, something is not ok there
>
>> Thanks
>> Gil
>>
>>
>> On 03/14/2016 09:39 AM, Yedidyah Bar David wrote:
>>> Hi all,
>>>
>>> Yesterday I worked on some change to otopi [1].
>>>
>>> Changeset 3 failed jenkins.
>>>
>>> Changeset 4 [2] succeeded, but was wrongly pushed to a somewhat-old parent.
>>>
>>> Then I rebased locally and pushed again, changeset 5 [3].
>>>
>>> In changeset 4, the version in master was 1.4.2-something.
>>>
>>> After the rebase, the version was 1.5.0-something.
>>>
>>> For some reason, changeset 5's build [3] built both 1.4.2- and 1.5.0- .
>>>
>>> Any idea why? Some dirty environment?
>>>
>>> Also, I now tried to run it again. I do not have a "retrigger" link,
>>> so I tried using [4], input the changeset number, marked patchset 5,
>>> pressed 'Trigger Selected', and now I see on the side:
>>>
>>> Triggered Builds
>>>      54697,5
>>>      No jobs triggered for this event
>>>
>>> Best,
>>>
>>> [1] https://gerrit.ovirt.org/54697
>>> [2] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/57/
>>> [3] http://jenkins.ovirt.org/job/otopi_master_create-rpms-el7-x86_64_created/58/
>>> [4] http://jenkins.ovirt.org/gerrit_manual_trigger/
>> _______________________________________________
>> Infra mailing list
>> Infra at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>