Post jobs to lava fails if the nano-lava rootfs variant doesn't exist

[Fathi Boudra]

Since 2012-06-13 (yesterday), we can't reach Jenkins API:
Failed to reach https://ci.linaro.org/jenkins/job/quantal-armhf-nano-lava/lastSuccessfulBuild/buildNumber.

When we try to access the page with a browser:
Status Code: 404

[Deepti B. Kalakeri (deeptik)]

I am able to access the https://ci.linaro.org/jenkins/view/Ubuntu%20Build%20Service/job/quantal-armhf-nano/lastSuccessfulBuild/ and https://ci.linaro.org/jenkins/view/Ubuntu%20Build%20Service/job/quantal-armhf-nano/lastSuccessfulBuild/<buildnumber>. Can you tell me is the link https://ci.linaro.org/jenkins/job/quantal-armhf-nano-lava/lastSuccessfulBuild/buildNumber is correct ?

[Fathi Boudra (fboudra)]

On 14 June 2012 09:59, Deepti B. Kalakeri wrote:
> I am able to access the
> https://ci.linaro.org/jenkins/view/Ubuntu%20Build%20Service/job/quantal-
> armhf-nano/lastSuccessfulBuild/ and
> https://ci.linaro.org/jenkins/view/Ubuntu%20Build%20Service/job/quantal-
> armhf-nano/lastSuccessfulBuild/<buildnumber>. Can you tell me is the
> link https://ci.linaro.org/jenkins/job/quantal-armhf-nano-
> lava/lastSuccessfulBuild/buildNumber is correct ?

Got it. We use nano-lava rootfs for LAVA jobs now.
quantal-armhf-nano-lava doesn't exists.

[Fathi Boudra (fboudra)]

Fix-Released:
- disable post build to LAVA for quantal-armhf-lt-panda. We don't want it daily yet.
- create quantal-armhf-nano-lava rootfs variant. We'll be ready to enable daily testing when needed.