Deploying war results in loss of MANIFEST.MF contents

Legacy Execution
1

Octopus Server: 2018.6.1

While deploying a .war file using the “Deploy to Tomcat via manager” step, the step upacks the war file, then uses java.exe to re-pack it (we don’t have any extra features like variable substitution enabled).
When it does this, we loose the contents of the MANIFEST.MF file, which contains our build label (version) and other details we use.
In our existing war file we have:
META-INF/MANIFEST.MF
contents:
Manifest-Version: 1.0
Build-Time: 20141212-1443
Build-Java: 1.7.0_67
Build-OS: Windows Server 2008 R2
Built-By: yyy_xxx
Build-Jdk: 1.7.0_67
Build-Label: 2.1.0
Created-By: Apache Maven 3.1.1
Build-Host:
Archiver-Version: Plexus Archiver

After octopus upacks then repacks the file, the contents are:
Manifest-Version: 1.0
Created-By: 1.8.0_121 (Oracle Corporation)

Is there any options to have octopus preserve the contents of the MANIFEST.MF between unpacking and re-packing? In my case I’m not even doing any variable substitutions so I technically don’t even need it to be unpacked.

2

Hi,

Thanks for contacting us. I’ve managed to reproduce the problem and have created an issue for it. https://github.com/OctopusDeploy/Issues/issues/4733 I’m currently working on a fix and will update the issue.

Thanks
Cam MacFarland

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.