Would removing the dev job for your repository be an option?
That may work, but then I will not get notified if a build fails?
Yes, the testing jobs. (PR and dev) are completely separate processes from the actual builds (binarydeb etc) and you will still get email about them failing if they fail. Disabling the testing jobs will avoid the notifications of being unstable due to tests failing by not running them at all.
Our system tests are in a separate package (but in the common repository), would you recommend not releasing it?
In general if the system tests are not designed to be used by downstream users, we recommend not releasing them. The test packages don't have a lot of value to be gained from being installable individually and running against the binary releases installed on the system as the binary installation should have been QAd before release.
You can add a ignored list in the release repsitory such as: https://github.com/ros-gbp/ros_comm-r...
Would removing the dev job for your repository be an option? That's the
sourcestanza in thedistribution.yamlof the ROS distribution you target.The answer to the question is "you can't", I believe.
That may work, but then I will not get notified if a build fails? Our system tests are in a separate package (but in the common repository), would you recommend not releasing it?