Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Not A Defect
    • Component/s: p4-plugin
    • Environment:
    • Similar Issues:

      Description

      I cannot create a new p4 workspace with below configuration.

       

      =Source Code Management================================================

      Perforce Software
      Perforce Credentials

      Add
      Help for feature: Perforce Credentials
      Workspace behaviour
      [Help]
      Character Set Help for feature: Character Set
      Workspace name
      ${JOB_NAME}
      Help for feature: Workspace name
      Not currently connected to a Perforce server
      Pin the workspace to the build host

      Options
      ALLWRITE CLOBBER COMPRESS LOCKED MODTIME RMDIR
      Help for feature: Options
      Line Endings Help for feature: Line Endings
      Type Help for feature: Type
      Stream
      View Mappings
      //TEAM/AUTOBOT/ACCESS/DEV/SLR750/lib/src/... //${JOB_NAME}/lib/src/...
      //TEAM/AUTOBOT/ACCESS/DEV/SLR750/lib/scripts/... //${JOB_NAME}/lib/scripts/...
      //TEAM/AUTOBOT/ACCESS/DEV/SLR750/resources/... //${JOB_NAME}/resources/...
      //TEAM/AUTOBOT/ACCESS/DEV/SLR750/sit_tc_pool/feature_test/lte/... //${JOB_NAME}/sit_tc_pool/feature_test/lte/...
      //TEAM/AUTOBOT/ACCESS/DEV/SLR750/sit_tc_pool/feature_test/lte/0_conf_folder/gconf_ytl_TMX_40104_40107_Intra_FA_Inter_eNB.py //${JOB_NAME}/gconf.py
      //TEAM/AUTOBOT/ACCESS/DEV/SLR750/sit_tc_pool/feature_test/lte/0_conf_folder/TestCase/SIT_YTL_Call_RT_3Days_TestCase.txt //${JOB_NAME}/TestCase.txt
      Help for feature: View Mappings
      Server ID
      Populate options
      [Help]
      REPLACE missing/modified files Help for feature: Auto cleanup and sync
      DELETE generated files Help for feature: Auto cleanup and sync
      Sync with MODTIME for consistency check
      QUIET Perforce messages Help for feature: Auto cleanup and sync
      Clean up Review actions

      Pin build at Perforce Label
      Help for feature: Auto cleanup and sync
      Parallel sync

      Advanced...
      Polling build filters
      Add new build filter
      Repository browser Help for feature: Repository browser

       

       

      =Error Log=============================================================
      Started by user
      anonymous
      [EnvInject] - Loading node environment variables.
      Building on master in workspace /var/lib/jenkins/workspace/YTL_Intra_FA_Auto_Configuration_of_Colocated_Cells
      ... p4 client -o YTL_Intra_FA_Auto_Configuration_of_Colocated_Cells -
      p4 client -o YTL_Intra_FA_Auto_Configuration_of_Colocated_Cells
      ... p4 info -
      p4 info
      ... p4 client -o YTL_Intra_FA_Auto_Configuration_of_Colocated_Cells -
      p4 client -o YTL_Intra_FA_Auto_Configuration_of_Colocated_Cells
      ... p4 client -i -
      p4 client -i Error in client specification. 'client_form_in' validation failed: Traceback (most recent call last): File "/tmp/tmp.125824.135.py", line 56, in <module> for line in client_spec.view: File "build/bdist.linux-x86_64/egg/P4.py", line 102, in __getattr_ KeyError: 'View'
      P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
      'client_form_in' validation failed:
      Traceback (most recent call last):
      File "/tmp/tmp.125824.135.py", line 56, in <module>
      for line in client_spec._view:
      File "build/bdist.linux-x86_64/egg/P4.py", line 102, in _getattr_
      KeyError: 'View'

      ERROR: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
      'client_form_in' validation failed:
      Traceback (most recent call last):
      File "/tmp/tmp.125824.135.py", line 56, in <module>
      for line in client_spec._view:
      File "build/bdist.linux-x86_64/egg/P4.py", line 102, in _getattr_
      KeyError: 'View'

      Robot results publisher started...
      -Parsing output xml:
      Failed!
      hudson.AbortException: No files found in path /var/lib/jenkins/workspace/YTL_Intra_FA_Auto_Configuration_of_Colocated_Cells with configured filemask: output.xml
      at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:77)
      at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:54)
      at hudson.FilePath.act(FilePath.java:998)
      at hudson.FilePath.act(FilePath.java:976)
      at hudson.plugins.robot.RobotParser.parse(RobotParser.java:49)
      at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:217)
      at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:239)
      at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:736)
      at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:682)
      at hudson.model.Build$BuildExecution.post2(Build.java:186)
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:627)
      at hudson.model.Run.execute(Run.java:1762)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:97)
      at hudson.model.Executor.run(Executor.java:421)
      Finished: FAILURE

        Attachments

          Activity

          Hide
          p4karl Karl Wirth added a comment -

          I am reviewing all the open jobs and the error message looks like it is being generated by a custom trigger on your system. Is this now working? If not and if you have a Perforce support contract please email support@perforce.com so I can investigate the trigger.

          Show
          p4karl Karl Wirth added a comment - I am reviewing all the open jobs and the error message looks like it is being generated by a custom trigger on your system. Is this now working? If not and if you have a Perforce support contract please email support@perforce.com so I can investigate the trigger.
          Hide
          p4karl Karl Wirth added a comment -

          No response so closing for now. Looking at error this is a custom trigger violation on the Perforce side. Creating the workspace manually with P4 (p4 client) should also cause the same error.

          Show
          p4karl Karl Wirth added a comment - No response so closing for now. Looking at error this is a custom trigger violation on the Perforce side. Creating the workspace manually with P4 (p4 client) should also cause the same error.
          Hide
          p4karl Karl Wirth added a comment -

          At this moment assume this is an environmental problem with custom Perforce form in triggers. Happy to assist further if I am wrong and 'p4 client' using the same mapping does not throw the same error.

          Show
          p4karl Karl Wirth added a comment - At this moment assume this is an environmental problem with custom Perforce form in triggers. Happy to assist further if I am wrong and 'p4 client' using the same mapping does not throw the same error.

            People

            • Assignee:
              Unassigned
              Reporter:
              taehun777 Ted Kim
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: