fuel-dev team mailing list archive

[Andrew Woodward <xarses@xxxxxxxxx>]

Why don't we have the meat of the Jenkins jobs in the repo so changes
like this don't cause issues between branches?

On Wed, Apr 16, 2014 at 9:10 AM, Aleksandra Fedorova
<afedorova@xxxxxxxxxxxx> wrote:
> I've made temporary workaround for stable/4.1 fuel-web branch for now.
>
> We will soon rework the stackforge-verify-fuel-web Jenkins job and split
> it into 4.1 and master branches, so they will use separate virtual
> environments.
>
> --
> Aleksandra Fedorova
>
> On Mon, 2014-04-14 at 14:24 -0700, Dmitry Borodaenko wrote:
>> I've backported all RabbitMQ3 related fixes to stable/4.1:
>> https://review.openstack.org/#/c/87371/
>> https://review.openstack.org/#/c/87379/
>> https://review.openstack.org/#/c/87383/
>>
>> However the fuel-web CI still seems to be broken for 4.1, it insists
>> on testing fuel_upgrade_system which doesn't exist in stable/4.1:
>> https://fuel-jenkins.mirantis.com/job/stackforge-verify-fuel-web/2932/console
>>
>> Anyone knows how to fix that?
>>
>> Thanks,
>> -DmitryB
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp



-- 
Andrew
Mirantis
Ceph community