Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7552

Global option to require user to input svn credentials

    • Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Icon: Major Major
    • m2release-plugin
    • None

      Our normal builds are using a generic svn account, which is fine. However, for releases we would like the person who is doing the release to input his own svn credentials, as it is very useful to see from the svn log who has done the release.

      Supplying the credentials is currently possible, but it would be nice to have a global option to require the user to input the credentials to be able to guarantee releases are not done using the generic account (stored by Hudson).

          [JENKINS-7552] Global option to require user to input svn credentials

          James Nord added a comment -

          Have you tried checking out from a read only account - or an anonymous connection. That would do what you are asking for.

          James Nord added a comment - Have you tried checking out from a read only account - or an anonymous connection. That would do what you are asking for.

          syvalta added a comment -

          Good point. I agree it makes more sense to handle this at svn account level.

          syvalta added a comment - Good point. I agree it makes more sense to handle this at svn account level.

            Unassigned Unassigned
            syvalta syvalta
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: