[JIRA] (JENKINS-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Igor Milos edited a comment on JENKINS-50298 Re: Use p4trust file if credential's Trust fingerprint is blank We deploy a p4 trust file on all our servers, including Jenkins slaves, and we export the variable P4TRUST to point to it.We would like p4-plugin in Jenkins to use this set up (the P4TRUST and the file) when we try to configure an SSL connection.However, this doesn't work - we get a fingerprint error. The only way to make p4-plugin establish an SSL connection, which is not really usable at scale, is to unset the P4TRUST variable and enter the fingerprint manually in the configuration. Obviously, this This approach based on manual input does not scale ( for us as we have 100s of connections more than 20 Jenkins master servers to configure) maintain and would require an undesirable exception in our deployment process. The risk is that if the fingerprint changes a manual procedure does not guarantee that all of the Masters will be updated, causing connection failures. We are therefore at this stage unable to use SSL connections effectively from p4-plugin, which runs contrary to our companies internal Security policies.This is a major issue in our adoption of Jenkins / Perforce CI pipeline. 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-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Igor Milos commented on JENKINS-50298 Re: Use p4trust file if credential's Trust fingerprint is blank Hello, is this fixing this issue going to be put in the road map? 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-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Igor Milos edited a comment on JENKINS-50298 Re: Use p4trust file if credential's Trust fingerprint is blank We deploy a p4 trust file on all our servers, including Jenkins slaves, and we export the variable P4TRUST to point to it.We would like p4-plugin in Jenkins to use this set up (the P4TRUST and the file) when we try to configure an SSL connection.However, this doesn't work - we get a fingerprint error. The only way to make p4-plugin establish an SSL connection, which is not really usable at scale, is to unset the P4TRUST variable and enter the fingerprint manually in the configuration. Obviously, this approach is does not scale (we have 100s of connections to configure) and creates would require an unacceptable undesirable exception in our deployment process.We are therefore at this stage unable to use SSL connections effectively from p4-plugin, which runs contrary to our companies internal Security policies.This is a major issue in our adoption of Jenkins / Perforce CI pipeline. 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-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Igor Milos commented on JENKINS-50298 Re: Use p4trust file if credential's Trust fingerprint is blank We deploy a p4 trust file on all our servers, including Jenkins slaves, and we export the variable P4TRUST to point to it. We would like p4-plugin in Jenkins to use this set up (the P4TRUST and the file) when we try to configure an SSL connection. However, this doesn't work - we get a fingerprint error. The only way to make p4-plugin establish an SSL connection, which is not really usable at scale, is to unset the P4TRUST variable and enter the fingerprint manually in the configuration. Obviously, this approach is does not scale (we have 100s of connections to configure) and creates an unacceptable exception in our deployment process. We are therefore at this stage unable to use SSL connections effectively from p4-plugin, which runs contrary to our companies internal Security policies. This is a major issue in our adoption of Jenkins / Perforce CI pipeline. 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-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Igor Milos updated an issue Jenkins / JENKINS-50298 Use p4trust file if credential's Trust fingerprint is blank Change By: Igor Milos Priority: Minor Major 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.