validation of private launchpad branches only works for lp prefix

Bug #952886 reported by jenkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
JenkinsPBuilderPlugin
New
Low
Unassigned

Bug Description

Lets imagine I have a private project P and user U who has the permissions to branch the trunk.
With the current state of pbuilder plugin I need to add something following to the jenkins job configuration:

Main Branch: bzr+ssh://<email address hidden>/+branch/P

While an lp project, the plugin doesn't validate this as a valid entry and gives the following error:
Only launchpad registered projects are supported at the present moment.

OTOH, the configuration works even with the error so fixing this would only enhance the user experience.

PS: other option how to solve this would be to make jenkins use the credentials of user U. I however can not use this approach as I need to use more than 1 private user/private projects.

Changed in jenkins.pbuilder.plugin:
importance: Undecided → Wishlist
importance: Wishlist → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.