Yes I have been surprised at how many users are running Jenkins in
Tomcat, or at least how vocal they have been. My gut feeling is that
dropping Level 2 support for traditional servlet containers is a
non-trivial project: e.g. collecting telemetry to quantify current
usage of traditional servlet
On Tue, Nov 29, 2022 at 6:29 PM James Nord wrote:
> if you can not use tomcat or $container then Jenkins must not be a war,
> which has a large overlap but is subtly different
>
Interesting…so if the basic Jenkins download were to physically switch
format somehow, then it would no longer be
> Not sure if there was a thread somewhere in which this topic was
discussed in writing, but my personal recommendation would be to formally
drop support for running in a general servlet container, so that you could
only use the bundled Winstone/Jetty via `java -jar jenkins.war` (we could
even
https://github.com/jenkinsci/packaging/pull/350
https://github.com/jenkins-infra/jenkins.io/pull/5747
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Yeah, you have to set up some stuff in the Tomcat config for it to work.
https://stackoverflow.com/questions/66274652/jenkins-no-valid-crumb-was-included-in-request/71961904#71961904
On Mon, Nov 28, 2022 at 10:13 AM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
>
I think slide has also found out that csrf tokens are also broken,
something about ips not being passed properly.
On Mon, Nov 28, 2022 at 8:47 AM 'Jesse Glick' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> On Mon, Nov 28, 2022 at 9:29 AM Mark Waite
> wrote:
>
>> Mark Waite
On Mon, Nov 28, 2022 at 9:29 AM Mark Waite
wrote:
> Mark Waite to propose a pull request documenting the web application
> server support policy […]
>
>-
> -
> -
>
> Many people are saying that “should work” but we don’t test them
> […]
> -
>
>
