ros-infrastructure/jenkins_tools

jenkins_tools's Issues

does not generate devel jobs when version is not set

In Hydro several repos do not specify a version number in the source.yaml and therefore have no devel job: http://jenkins.ros.org/job/_hydro-reconfigure-devel-jobs/234/console

pre-release tests failing: <foo> is not a package name nor a repository name

I am seeing this while running pre-release tests of packages that have not yet been released. In both cases, the package was converted from a unary stack, and it is both a package name and a repository name.

For details, see: http://answers.ros.org/question/59802/runtimeerror-multi_level_map-is-not-a-package-name-nor-a-repository-name/

email on successful prereleases

They're only emailing on failure and unstable and back to normal.

Jobs are getting a lot of white space in their console output

Refiling from ros-infrastructure/rosdoc_lite/issues/14

The console output now has tons of whitespace. Something must be printing blank lines. This makes the logs almost unreadable.

job generation is failing to open a file for writing and crashing

This is probably a failure to create the temp directory.

While we're looking at this the folder seems to be hard coded to /tmp/workspace. Is that necessary?

http://jenkins.willowgarage.com:8080/job/_fuerte-reconfigure-doc-jobs/135/console

Started by timer
Building on master in workspace /var/lib/jenkins/jobs/_fuerte-reconfigure-doc-jobs/workspace
[workspace] $ /bin/sh -xe /tmp/hudson8696979435589961911.sh
+ generate_jenkins_doc fuerte --delete
Cloning into '/tmp/tmp4OumBq'...
Building list of repos for distro fuerte
Created Jenkins instance
Traceback (most recent call last):
  File "/usr/bin/generate_jenkins_doc", line 97, in <module>
    main()
  File "/usr/bin/generate_jenkins_doc", line 75, in main
    jenkins_tools.run_jenkins_periodic(jenkins_instance, u, a, job_name, "[email protected]", "nightly", "doc", [ros_distro, s], info['username'], priority=30)
  File "/usr/lib/pymodules/python2.7/jenkins_tools/run_jenkins.py", line 107, in run_jenkins_periodic
    _update_jenkins_job(jenkins_instance, jc, ubuntu_distro, arch, job_name, email, script, script_args, user_name, params, matrix=matrix, priority=priority)
  File "/usr/lib/pymodules/python2.7/jenkins_tools/run_jenkins.py", line 76, in _update_jenkins_job
    with open('/tmp/workspace/gen_jobs/%s.xml' % job_name, 'w') as f:
IOError: [Errno 2] No such file or directory: '/tmp/workspace/gen_jobs/doc-fuerte-image_pipeline.xml'
Build step 'Execute shell' marked build as failure
Sending e-mails to: [email protected]
Finished: FAILURE

Jenkins workspaces can not be wiped

pbuilder seems to create the files under the user root which Jenkins can't remove. E.g. any doc job.

devel and doc builds are deadlocking on the flock

udevd appears to be locking the file too. After a few retries repeatedly failing it has stopped failing.

root@host03:~# strace -p 9201
Process 9201 attached - interrupt to quit
flock(3, LOCK_EX^C <unfinished ...>
Process 9201 detached
root@host03:~# readlink /proc/9201/fd/3
/var/cache/pbuilder/jenkins_tools.trusty.amd64-0.4.1.updatelock
root@host03:~# lsof /var/cache/pbuilder/jenkins_tools.trusty.amd64-0.4.1.updatelock
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF    NODE NAME
flock    9201 root    3u   REG  253,3        0 1408567 /var/cache/pbuilder/jenkins_tools.trusty.amd64-0.4.1.updatelock
udevd   25361 root    3r   REG  253,3        0 1408567 /var/cache/pbuilder/jenkins_tools.trusty.amd64-0.4.1.updatelock

invalid urls to .inv files

https://github.com/ros-infrastructure/jenkins_tools/blob/master/doc/conf.py#L219-L225

Do not call apt-get update inside the job

We have setup puppet properly to update the required packages automatically.