You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would allow users to generate the prerelease command line for repositories which are not listed in the rosdistro yet. Currently they first need to add the repo with at least a source entry, wait for that to be merged, run the prerelease, and then do a bloom release. While they are iterating locally they are potentially already getting notification emails for the devel jobs from the farm (if not disabled explicitly. So this feature would drastically improve the workflow for users imo.
That sounds useful to me. It would also imply finally fixing #31. I don't have any spare cycles to do either right now. Maybe if I finish with my Lunar releases relatively quickly I can use some of my ROS 1 time for it.
Once this has been implemented the second part of this recent wiki should be reverted and the option to specify external repos should be mentioned explicitly.
This would allow users to generate the prerelease command line for repositories which are not listed in the rosdistro yet. Currently they first need to add the repo with at least a source entry, wait for that to be merged, run the prerelease, and then do a bloom release. While they are iterating locally they are potentially already getting notification emails for the devel jobs from the farm (if not disabled explicitly. So this feature would drastically improve the workflow for users imo.
For each "external" repo the user has to provide:
The repository information is passed using the
--custom-repo
argument describe in https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/jobs/prerelease_jobs.rst#run-for-custom-repositoriesThis would also "solve" #14 since this feature would be a superset of what is requested there.
The text was updated successfully, but these errors were encountered: