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

Regexp-driven validation of client workspace names

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • p4-plugin
    • None

      It would be great to add possibility of workspace name validation according to naming policy, which should be defined in the global configuration.

      Proposed features:

      • Show error notifications if user enters wrong client workspace name
      • Fail creation of the workspace if client name violates naming policy

          [JENKINS-18378] Regexp-driven validation of client workspace names

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Oleg Nenashev added a comment -

          Pull request with the first option: https://github.com/jenkinsci/perforce-plugin/pull/31

          Oleg Nenashev added a comment - Pull request with the first option: https://github.com/jenkinsci/perforce-plugin/pull/31

          Oleg Nenashev added a comment -

          Merged into the main branch...

          Oleg Nenashev added a comment - Merged into the main branch...
          Oleg Nenashev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          lata kopalle added a comment - - edited

          hi oleg,
          am guessing this does not include #2, right? i couldn't find an option to check 'fail on bad workspace name' or something. (it would be so cool if we can have a pre-populated client spec based on global set pattern, but i guess that would make another ticket).

          thanks!
          lata

          lata kopalle added a comment - - edited hi oleg, am guessing this does not include #2, right? i couldn't find an option to check 'fail on bad workspace name' or something. (it would be so cool if we can have a pre-populated client spec based on global set pattern, but i guess that would make another ticket). thanks! lata

          Oleg Nenashev added a comment -

          Yes, #2 has not been implemented.
          BTW, It is quite strange that you don't see error notifications.

          I'll reopen issue and check it.

          Oleg Nenashev added a comment - Yes, #2 has not been implemented. BTW, It is quite strange that you don't see error notifications. I'll reopen issue and check it.

          Oleg Nenashev added a comment -

          Reopened issue according to Lata's comments

          Oleg Nenashev added a comment - Reopened issue according to Lata's comments
          Oleg Nenashev made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          lata kopalle added a comment -

          sorry, i edited my comment, i am able to see the error on a bad workspace name. i just wanted to know about the #2. thanks!

          lata kopalle added a comment - sorry, i edited my comment, i am able to see the error on a bad workspace name. i just wanted to know about the #2. thanks!

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: