[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title Daniel Jeznach closed an issue as Not A Defect Jenkins / JENKINS-55008 P4 Plugin generates ticket on slave that it does not use Change By: Daniel Jeznach Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title Daniel Jeznach commented on JENKINS-55008 Re: P4 Plugin generates ticket on slave that it does not use 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-55008 P4 Plugin generates ticket on slave that it does not use Change By: Paul Allen Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title Paul Allen commented on JENKINS-55008 Re: P4 Plugin generates ticket on slave that it does not use Are you able to login by setting the 'All Hosts' field in the 'Advanced' option on the Perforce Credential? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Change By:
Daniel Jeznach
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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Change By:
Daniel Jeznach
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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Change By:
Daniel Jeznach
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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach created an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-12-04 13:46
Priority:
Minor
Reporter:
Daniel Jeznach
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.
Add Comment
