Hi,
Several builds became "unstable" (in jenkins term) without changes in the jobs: IOERROR: BUILD-INFO.txt is not present in build.
Obviously, it seems BUILD-INFO.txt is now enforced and some jobs are still using EULA.txt mechanism.
While I don't have any issues with (en)forcing users to use BUILD-INFO.txt, I would have expected some notifications to allow job maintainers to adjust the builds as appropriate. Once again, it isn't the kind of changes to deploy the release week.
Cheers,
We are seeing similar errors on the android build which publish the build-info.txt.
On 26 February 2013 12:20, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi,
Several builds became "unstable" (in jenkins term) without changes in the jobs: IOERROR: BUILD-INFO.txt is not present in build.
Obviously, it seems BUILD-INFO.txt is now enforced and some jobs are still using EULA.txt mechanism.
While I don't have any issues with (en)forcing users to use BUILD-INFO.txt, I would have expected some notifications to allow job maintainers to adjust the builds as appropriate. Once again, it isn't the kind of changes to deploy the release week.
Cheers,
Fathi Boudra Release Manager | Developer Platform Tech Lead Linaro.org | Open source software for ARM SoCs
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
W dniu 26.02.2013 07:50, Fathi Boudra pisze:
Several builds became "unstable" (in jenkins term) without changes in the jobs: IOERROR: BUILD-INFO.txt is not present in build.
Obviously, it seems BUILD-INFO.txt is now enforced and some jobs are still using EULA.txt mechanism.
While I don't have any issues with (en)forcing users to use BUILD-INFO.txt, I would have expected some notifications to allow job maintainers to adjust the builds as appropriate.
Once again, it isn't the kind of changes to deploy the release week.
Fully agree on that. As CI is used a lot and we depend on it's results any changes which affect builds should be done in first 1-2 weeks of month - in a week after monthly release and with enough time left before components release. Otherwise it makes releases harder as now I have to find out WTH that build-info.txt is, what should be there (pointer to docs anyone?) and migrate jobs to use it.
On 26 February 2013 10:14, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
W dniu 26.02.2013 07:50, Fathi Boudra pisze:
Several builds became "unstable" (in jenkins term) without changes in the jobs: IOERROR: BUILD-INFO.txt is not present in build.
Obviously, it seems BUILD-INFO.txt is now enforced and some jobs are still using EULA.txt mechanism.
While I don't have any issues with (en)forcing users to use BUILD-INFO.txt, I would have expected some notifications to allow job maintainers to adjust the builds as appropriate.
Once again, it isn't the kind of changes to deploy the release week.
Fully agree on that. As CI is used a lot and we depend on it's results any changes which affect builds should be done in first 1-2 weeks of month - in a week after monthly release and with enough time left before components release. Otherwise it makes releases harder as now I have to find out WTH that build-info.txt is, what should be there (pointer to docs anyone?) and migrate jobs to use it.
http://wiki.linaro.org/Platform/Infrastructure/Publishing http://bazaar.launchpad.net/~linaro-automation/linaro-license-protection/tru...
У уто, 26. 02 2013. у 08:50 +0200, Fathi Boudra пише:
While I don't have any issues with (en)forcing users to use BUILD-INFO.txt, I would have expected some notifications to allow job maintainers to adjust the builds as appropriate. Once again, it isn't the kind of changes to deploy the release week.
Just to clarify the situation here: this was an error on our part. Code to enforce them has landed early in this cycle, and was supposed to be deployed then. That didn't happen, and with some recent fixes, we deployed the latest trunk which included those changes.
I've reverted specifically those changes which are apparently not well tested. They'll be re-introduced early on next cycle when there's time to fix problems (the checks themselves are obviously broken, as evidenced by android builds).
Cheers, Danilo
-
Danilo Šegan -
Fathi Boudra -
Marcin Juszkiewicz -
Vishal Bhoj