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

P4 Plugin generates ticket on slave that it does not use

XMLWordPrintable

      I have job with configured P4 repository and following execute shell:

      env | grep -P '^P4'

      This job is executed on node js-qata-u16. I log into that node and log out of perforce:

      $ p4 logout
      User xbuild.qa logged out.

      Now I run jenkins job, which displays following data in log:

      + env
      + grep -P ^P4
      P4_CLIENT=jenkins-js-qata-u16-p4test-0
      P4_TICKET=BA9C6CDCD5455D69DB94338D74729738
      P4_USER=xbuild.qa

      But on js-qata-u16 node I do:

      $ p4 tickets
      p4master:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171

      This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.

          [JENKINS-55008] P4 Plugin generates ticket on slave that it does not use

          Daniel Jeznach created issue -
          Daniel Jeznach made changes -
          Description Original: I have job with configured P4 repository and following execute shell:

          {{env | grep -P '^P4'}}

          This job is executed on node js-qata-u16. I log into that node and log out of perforce:

          {{$ p4 logout}}
          {{ User xbuild.qa logged out.}}

          Now I run jenkins job, which displays following data in log:

          {{+ env}}
          {{ + grep -P ^P4}}
          {{ P4_CLIENT=jenkins-js-qata-u16-p4test-0}}
          {{ P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}
          {{ P4_USER=xbuild.qa}}

          But on js-qata-u16 node I do:

          {{$ p4 tickets }}
          {{p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}}

          This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.           		New: I have job with configured P4 repository and following execute shell:

          {{env | grep -P '^P4'}}

          This job is executed on node js-qata-u16. I log into that node and log out of perforce:

          {{{{$ p4 logout}}}}
          {{User xbuild.qa logged out.}}

          Now I run jenkins job, which displays following data in log:

          {{{{+ env}}}}
          {{+ grep -P ^P4}}
          {{P4_CLIENT=jenkins-js-qata-u16-p4test-0}}
          {{P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}
          {{P4_USER=xbuild.qa}}

          But on js-qata-u16 node I do:

          {{$ p4 tickets}}
          {{ {{p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}}}}

          This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.
          Daniel Jeznach made changes -
          Description Original: I have job with configured P4 repository and following execute shell:

          {{env | grep -P '^P4'}}

          This job is executed on node js-qata-u16. I log into that node and log out of perforce:

          {{{{$ p4 logout}}}}
          {{User xbuild.qa logged out.}}

          Now I run jenkins job, which displays following data in log:

          {{{{+ env}}}}
          {{+ grep -P ^P4}}
          {{P4_CLIENT=jenkins-js-qata-u16-p4test-0}}
          {{P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}
          {{P4_USER=xbuild.qa}}

          But on js-qata-u16 node I do:

          {{$ p4 tickets}}
          {{ {{p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}}}}

          This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.           		New: I have job with configured P4 repository and following execute shell:

          {{env | grep -P '^P4'}}

          This job is executed on node js-qata-u16. I log into that node and log out of perforce:

          {{$ p4 logout}}
          {{User xbuild.qa logged out.}}

          Now I run jenkins job, which displays following data in log:

          {{+ env}}
          {{+ grep -P ^P4}}
          {{P4_CLIENT=jenkins-js-qata-u16-p4test-0}}
          {{P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}
          {{P4_USER=xbuild.qa}}

          But on js-qata-u16 node I do:

          {{$ p4 tickets}}
          {{p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}}

          This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.
          Daniel Jeznach made changes -
          Description Original: I have job with configured P4 repository and following execute shell:

          {{env | grep -P '^P4'}}

          This job is executed on node js-qata-u16. I log into that node and log out of perforce:

          {{$ p4 logout}}
          {{User xbuild.qa logged out.}}

          Now I run jenkins job, which displays following data in log:

          {{+ env}}
          {{+ grep -P ^P4}}
          {{P4_CLIENT=jenkins-js-qata-u16-p4test-0}}
          {{P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}
          {{P4_USER=xbuild.qa}}

          But on js-qata-u16 node I do:

          {{$ p4 tickets}}
          {{p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}}

          This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.           		New: I have job with configured P4 repository and following execute shell:

          {{env | grep -P '^P4'}}

          This job is executed on node js-qata-u16. I log into that node and log out of perforce:

          {{$ p4 logout}}
          {{User xbuild.qa logged out.}}

          Now I run jenkins job, which displays following data in log:

          {{+ env}}
          {{+ grep -P ^P4}}
          {{P4_CLIENT=jenkins-js-qata-u16-p4test-0}}
          {{P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}
          {{P4_USER=xbuild.qa}}

          But on js-qata-u16 node I do:

          {{$ p4 tickets}}
          {{p4master:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}}

          This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.

          Paul Allen added a comment -

          Are you able to login by setting the 'All Hosts' field in the 'Advanced' option on the Perforce Credential?

          Paul Allen added a comment - Are you able to login by setting the 'All Hosts' field in the 'Advanced' option on the Perforce Credential?
          Paul Allen made changes -
          Labels New: P4_SUPPORT

          Daniel Jeznach added a comment -

          Hi, yes, I am able to login. Looks I was not aware this option is even there, but fortunately this solves my issue. Thank you.

          Daniel Jeznach added a comment - Hi, yes, I am able to login. Looks I was not aware this option is even there, but fortunately this solves my issue. Thank you.
          Daniel Jeznach made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            daniel_jeznach_img Daniel Jeznach
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: