P4CLIENT changes to null

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major
    • Component/s: p4-plugin
    • None
    • Environment:
      Windows XP, with 4 build slaves.

      I'm seeing an unusual issue where environment variables are getting clobbered. Most often I see this on long builds (in excess of an hour), and it usually appears as the P4CLIENT environment variable being set to 'null'. I've also seen a similar (probably related) issue where the P4_CHANGELIST variable becomes unset partway through long builds.

            Assignee:
            Rob Petti
            Reporter:
            cbieneman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: