Hello Andy,
On Tue, 14 May 2013 20:17:54 +0800 Andy Green andy.green@linaro.org wrote:
[]
Anybody can update the job configuration.
What does that actually mean?
Is the "job configuration" at a URL that I can turn off my notifications? Why not stick this URL in the notification?
I spent ten minutes wandering around the links to ci.linaro.org that were in the email, logged in, looked for something to turn off... nothing.
I'm glad if it stopped... but if there will be people like me who did not configure the job but will get notifications, we should help these guys gain control of the mails they're sent.
Andy, just to sum up other responses given, for a proper process to follow:
1. A link you got in email, https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/... leads to a particular *build* of a *job* (aka "project").
2. From that page, you can get to *job* page by "Back to Project" or just clicking a breadcrumb. This should be pretty intuitive. The page is https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/
3. Each job on ci.linaro.org lists its maintainer(s): "Maintainer: Scott Bambrough". Those persons should be primary contact for any q's about a job.
4. We don't want people to just unsubscribe from notifications, we want them to (co)maintain jobs. If you, TI tree maintainer (sorry if I'm out of loop and you're no longer work on that) is not interested in notification from that job, that's good indication that the job should be *disabled* and stop wasting resources to produce results in which primary stakeholders are not interested. So, what you did here is right - escalate this to get proper resolution. The job is disabled now.
5. LAVA team (after merger with Infrastructure team) is responsible for ci.linaro.org maintenance, we're glad to cover any issues if job's maintainer is not easily reachable. (It may take some time when LAVA/Infra fully align our processes, sorry about extra hops the requests may need to go thru before that).
Thanks!
-Andy
-Andy
-------- Original Message -------- Subject: Build failed in Jenkins: LT-TI-working-tree-3.4_panda-es-omap4plus #250 Date: Tue, 14 May 2013 00:14:07 +0000 (UTC) From: ci_notify@linaro.org To: scottb@linaro.org, andy.green@linaro.org, usman.ahmad@linaro.org, n-dechesne@ti.com
See https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/250/
Started by timer [EnvInject] - Loading node environment variables. Building remotely on Precise-64 3exec (i-5033053c) in workspace https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/ws/ Checkout:LT-TI-working-tree-3.4_panda-es-omap4plus / https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/ws/
- hudson.remoting.Channel@10a7a7:Precise-64 3exec (i-5033053c)
Using strategy: Default Last Built Revision: Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf (origin/tilt-3.4) Cloning the remote Git repository Cloning repository git://git.linaro.org/landing-teams/working/ti/kernel.git git --version git version 1.7.9.5 Fetching upstream changes from origin Commencing build of Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf (origin/tilt-3.4) Checking out Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf (origin/tilt-3.4) [copy-to-slave] Copying 'builddeb', excluding nothing, from 'file:/var/lib/jenkins/userContent/' on the master to 'https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus/ws/' on 'Precise-64 3exec (i-5033053c)'. [LT-TI-working-tree-3.4_panda-es-omap4plus] $ /bin/sh -xe /tmp/hudson2373270767559071380.sh
- rm -rf lci-build-tools
- export hwpack_type=panda
- export board_types=panda-es
- export kernel_config=omap4plus_defconfig
- export kernel_flavour=omap
- export
git_web_url=http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git
- export lava_test_plan=ltp,pwrmgmt,lt_ti_lava
- export
toolchain_url=http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-ar...
- bzr branch lp:linaro-ci lci-build-tools
You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See "bzr help launchpad-login". Branched 148 revisions.
- ./lci-build-tools/jenkins_kernel_build_inst
- test -z omap
- test -z ''
- rootfs_type=nano-lava
- test -z
http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git
- test -z panda
- test -z ''
- submit_job=1
- test -z ltp,pwrmgmt,lt_ti_lava
- test -z
http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-ar...
- wget -cq
http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-ar... Build step 'Execute shell' marked build as failure
Cheers,
Fathi Boudra Builds and Baselines Manager | Release Manager Linaro.org | Open source software for ARM SoCs