You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Otherwise, even the .war file is copied to here: /home/tomcat/tomcat/webapps/ , /home/tomcat/tomcat/webapps/{app name} directory will be empty after tomcat started. .war is not exploded since {app name} direction exists already.
Also tested on 'tds deploy rollback'. It has the same problem.
The text was updated successfully, but these errors were encountered:
Thanks @Stelminator, I will try that later.
More background: the problem was found with a rpm generated by a sbt jenkins job. All rpms generated by maven jobs do not have this problem 'cuz mappings were done on exploded .war files instead of .war file itself. The quick fix we figured out yesterday was having this line in packaging.scala file:
rpmPost := Option("sudo rm -r /home/tomcat/tomcat/webapps/{app directory name}")
Otherwise, even the .war file is copied to here: /home/tomcat/tomcat/webapps/ , /home/tomcat/tomcat/webapps/{app name} directory will be empty after tomcat started. .war is not exploded since {app name} direction exists already.
Also tested on 'tds deploy rollback'. It has the same problem.
The text was updated successfully, but these errors were encountered: