-
Improvement
-
Resolution: Fixed
-
Major
-
None
Today the context is the same for all configured Tomcat containers. I would need to specify another context in a Tomcat container, which override the configured one.
A Pull Request will shortly follow.
- links to
[JENKINS-51440] Configure alternative context for each Tomcat container
Adrien Lecharpentier
added a comment - Sorry, I didn't see the message before. I don't know why this is assigned to me, I never worked on this.
I'll see what I can do, but normally, an email to the dev-list should be sent.
Adrien Lecharpentier
added a comment - Sorry, I didn't see the message before. I don't know why this is assigned to me, I never worked on this.
I'll see what I can do, but normally, an email to the dev-list should be sent. Thank you alecharp
I don't know why this is assigned to me, I never worked on this.
I did assign it to you, see my comment on 2018-06-28, because I was looking for someone help to push this forward.
Robin Jansohn
added a comment - Seems to be a duplicate of JENKINS-3624 , right? Robin Jansohn
added a comment - Closing in favor of the older issue JENKINS-3624 . Hello, I'm not sure the work done in JENKINS-3624 covers the requirement here. JENKINS-3624 focuses on manager path whereas this patch adds the possibility to have a different application's context path for each container. The important change in my PR the TomcatAdapater#redeployFile override
Would you accept an updated PR to achieve this?
Robin Jansohn
added a comment - Yes, please add it as an advanced option and add a help description for the new field.
Robin Jansohn
added a comment - Yes, please add it as an advanced option and add a help description for the new field. 
alecharp After your presentation yesterday at ParisJUG, as you seems to keep an eye on Jenkins plugins ecosystem, I think you may help me to find someone to review this pull request?