Enable jar file deployments for Azure app service #1386
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SC-96592
Deployment of jar files via the Deploy an Azure App Service step in Octopus Server is currently disabled. This PR is in response to a feature request to support jar deployment.
The existing implementation for war files is not suitable for jar deployment because the file contents are extracted on deployment. The Kudu service supports jar deployment via the /api/publish?type=jar endpoint, which renames the jar to app.jar and places it within the wwwroot directory on the app service. By default, the app service is not capable of running jar files, so a startup script or command is required (eg.
java -jar /home/site/wwwroot/app.jar)Testing this PR requires a sandbox app service configured to support Java, with a startup command to execute the jar.
No Octopus branch instance is available for this PR yet due to build failures