[JIRA] (JENKINS-39562) Jenkins 2.19.2 returns "Forbidden" when configured for WildFly Deployer Plugin

2016-11-11 Thread vglos...@cpocommerce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vance Gloster commented on  JENKINS-39562  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins 2.19.2 returns "Forbidden" when configured for WildFly Deployer Plugin   
 

  
 
 
 
 

 
 As a workaround, you can use a shell script, as described here: https://blog.codecentric.de/en/2015/01/automated-wildfly-deployments-shell-scripting/  
 

  
 
 
 
 

 
 
 

 
 
 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-39562) Jenkins 2.19.2 returns "Forbidden" when configured for WildFly Deployer Plugin

2016-11-07 Thread vglos...@cpocommerce.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vance Gloster created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39562  
 
 
  Jenkins 2.19.2 returns "Forbidden" when configured for WildFly Deployer Plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Dan Dillingham  
 
 
Components: 
 wildfly-deployer-plugin  
 
 
Created: 
 2016/Nov/07 7:52 PM  
 
 
Environment: 
 Ubuntu 14.04.4. Java 1.8. Wildfly: 10.1.0.FINAL. Jenkins: 2.19.2. Jenkins in standalone mode. Google Chrome version 53.0.2785.116 (64-bit).  
 
 
Labels: 
 jenkins plugin  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Vance Gloster  
 

  
 
 
 
 

 
 The Wildfly Deployer Plugin requires that the Jenkins WAR file be edited. wildfly-cli-8.2.1.Final.jar must be added to the /WEB-INF/lib directory inside the WAR file. When I do this and deploy it to my Wildfly server, whenever I go to the Jenkins URL, the browser just shows the word "Forbidden". When I deploy the unaltered Jenkins WAR file, it works fine. When I try running the plugin without modifying the WAR file, it reports "FATAL: Unable to initialize command context." I am trying to get this running for the first time; I have not had it running previously. All the other functionality of Jenkins works perfectly. If you want me to upload the modified WAR file I can do it, but it is large.