Basil Crow
Basil Crow
If you are not able to address this regression in a timely fashion, should the Enforcer rule be relaxed as a workaround?
We got lucky because https://github.com/jenkinsci/acceptance-test-harness/pull/711 (which I needed to avoid flakiness in core builds) happened to be present in 1.114, but I am concerned we may not be so lucky...
Many thanks to all who worked on this!
The workaround is to add all the `--add-opens` directives from https://github.com/x-stream/xstream/blob/cf61d543f17d284a7c878c27704857e2ebc08079/xstream/pom.xml#L261 to your Java invocation or to an `Add-Opens:` directive in `MANIFEST.MF`. In practice you will not need all of...
Does anyone have steps to reproduce this issue from scratch? I was thinking about moving the `--add-opens` lines from https://github.com/jenkinsci/docker-inbound-agent/blob/516b518fc78066d7f6ea271b548e32eb7e6db4fc/jenkins-agent#L133-L139 to an `` entry in Remoting's `MANIFEST.MF` (as in jenkinsci/jenkins#6356),...
So maybe we should conclude that these `--add-opens` directives aren't needed anymore and remove them? Though that could cause a regression if they are needed. Alternatively, we could convert them...
@shawngmc That stack trace seems to come from the controller, so I have no idea why you are posting it on an issue in the `docker-agent` repository.
Turns out there was no test coverage for this in the existing code base. I wrote a new test in jenkinsci/gitlab-plugin#1207 which reproduces the problem. The full stack trace: ```...
Incremental build 2.13.1-243.v04a926c036e7 is available for testing. The incremental build is available from: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/jackson2-api/2.13.1-243.v04a926c036e7/ @dhruv-dave @gandadil @jchychot @medanets-admin @r-work Can you please test the incremental build and confirm the issue...