[JIRA] (JENKINS-42472) Rollback folder
Title: Message Title bryan patton created an issue Jenkins / JENKINS-42472 Rollback folder Issue Type: Bug Assignee: Greg Peters Attachments: console.txt, jenkinserr.txt Components: websphere-deployer-plugin Created: 2017/Mar/03 4:42 PM Environment: beta 1.4.2 Priority: Minor Reporter: bryan patton There appears to be a bug with the rollback function where the .war extension is hard coded rather than using the provided file name/extension. Add Comment
[JIRA] (JENKINS-42257) Test Connection Works - Deploy Fails
Title: Message Title bryan patton updated an issue Jenkins / JENKINS-42257 Test Connection Works - Deploy Fails Change By: bryan patton Comment: Worked with Greg Peters to resolve this. Thanks Greg. We needed to include com.ibm.ws.webservices.thinclient_8.5.0.jar in the web-inf/lib directory in order to resolve this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42257) Test Connection Works - Deploy Fails
Title: Message Title bryan patton commented on JENKINS-42257 Re: Test Connection Works - Deploy Fails Worked with Greg Peters to resolve this. Thanks Greg. We needed to include com.ibm.ws.webservices.thinclient_8.5.0.jar in the web-inf/lib directory in order to resolve this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42257) Test Connection Works - Deploy Fails
Title: Message Title bryan patton assigned an issue to Greg Peters Jenkins / JENKINS-42257 Test Connection Works - Deploy Fails Change By: bryan patton Assignee: Greg Peters Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42257) Test Connection Works - Deploy Fails
Title: Message Title bryan patton resolved as Fixed We needed to include com.ibm.ws.webservices.thinclient_8.5.0.jar in the web-inf/lib directory in order to resolve this. Jenkins / JENKINS-42257 Test Connection Works - Deploy Fails Change By: bryan patton Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-42257) Test Connection Works - Deploy Fails
Title: Message Title bryan patton created an issue Jenkins / JENKINS-42257 Test Connection Works - Deploy Fails Issue Type: Bug Assignee: Unassigned Attachments: Capture.PNG, error.txt Components: websphere-deployer-plugin Created: 2017/Feb/22 4:14 PM Environment: Jenkins ver. 2.32.2 websphere-deployer: 1.3.4 was 8.5 Labels: was websphere-deployer-plugin websphere Priority: Blocker Reporter: bryan patton I have spent hours trying to figure out how to resolve this apparent conflict but have had no success. The test connection works; however the test connection appears to not care about the validity of the credentials so it doesn't appear to be a very clear indicator. I have gone through the additional steps of verifying the certificate installation and CAN connect using SSLPoke on the assigned port. We have copied the jar files from the WAS server to the plugins/websphere-deployer//web-inf/lib directory . I have tried including the slf4j jar files in both the plugins/websphere-deployer//web-inf/lib and the jenkins lib files; neither was met with any difference. The issue appears to be two fold. One there appears to be an issue with the jar files and a potential library conflict? This is of minor concern except that it seems to be preventing me from getting a real error. Second I seem to having trouble making the connection work. We are working with cluster
[JIRA] (JENKINS-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title bryan patton edited a comment on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I am having the same issue and to compound it when rebuilding the project task it will work correctly. It appears to be a difference between Jenkins identifying the credentials and binding them and or not. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title bryan patton commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I am having the same issue and to compound it when rebuilding the project it will work correctly. It appears to be a difference between Jenkins identifying the credentials and binding them and not. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
