• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • Jenkins Master running on Windows Server 2008 R2 Standard SP1

      The P4TICKET variable will randomly disappear in jobs running on the Jenkins Master. This is job specific as other jobs running on the Master will continue to use the ticket properly. This causes any jobs that rely on the existence of the P4TICKET variable to randomly fail. So far I have not found a reliable work around to force the jobs to start using P4TICKETS in it's P4 commands again. Forced logout/login with -a and restarts of Jenkins and the Master Node have not worked.

          [JENKINS-24375] p4ticket randomly dropped from job execution

          Sam Caswell added a comment -

          I have managed to find one work around. p4 logout -a on the master server, then run the offending job in Jenkins to force a p4 login. This appears to kick-start the use of the p4 ticket and the creation of the P4TICKET variable again.

          Sam Caswell added a comment - I have managed to find one work around. p4 logout -a on the master server, then run the offending job in Jenkins to force a p4 login. This appears to kick-start the use of the p4 ticket and the creation of the P4TICKET variable again.

            Unassigned Unassigned
            scaswell Sam Caswell
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: