[ros-users] [Discourse.ros.org] [Buildfarm] How to completely remove a package from a build farm's status page?

[P. J. Reed]

I've set up a private build farm that we're using to build our packages, and so far everything's working well.  It's configured to point at and load packages from an internal, private GitLab server that we use, and I've been able to bloom >130 of our packages that it has successfully built and pushed to our apt repository.

We've got an internal clone of rosdistro, where we've modified the index.yaml file to add a seconds distribution.yaml file to the indigo and kinetic distributions (the only ones we support), and those distribution files have a "swri" tag in them; then, in all of the build.yaml files in our ros_buildfarm_config repository, we have a tag_whitelist that contains "swri".  So far, so good; our build farm only builds packages that we add to our custom distribution.yaml file and not ones that get merged in to the main distribution.yaml file when we update from the main rosdistro repo.

There's one problem: When I first set up the build farm, there was a brief period where I had not added the tag_whitelist yet, and there was an update to the "tornado" package and our build farm decided to build it.  It's not building any more now that the whitelist is in place, and I've manually gone through the filesystem on the master, slave, and repo computers and removed every file I can find referencing "tornado", but somehow when the indigo_default.html page gets generated on the repo server, and it says that ros-indigo-tornado 4.2.1-1 exists in the "building" repository for Tsource.

Why is that entry still being added, and how can I remove it?

Thanks in advance!

-- 
P. J. Reed, Senior Research Analyst
(210) 522-6948
Intelligent Vehicle Systems (http://ivs.swri.org)
Applied Sensing Department (http://appliedsensing.swri.org)
Southwest Research Institute (http://www.swri.org)






---
[Visit Topic](http://discourse.ros.org/t/how-to-completely-remove-a-package-from-a-build-farms-status-page/911/1) or reply to this email to respond.