On 20/03/2019 16.47, Julien HENRY wrote:
Hi Olivier,
Any suggestion on how to achieve this? Basically I would like to take a
copy of the update center corresponding to the oldest version of Jenkins
we support, and use it in our ITs. This page
<https://github.com/jenkinsci/acceptance-test-harness/blob/master/docs/SUT-VERSIONS.md>
give several ways to control plugin versions, but I haven't found a way
to point the update center to a local json file for example.
You would have to assemble update center for that Jenkins version is
some way. By assemble I mean identify plugin versions that does not
require newer Jenkins core while still having dependencies satisfied.
The idea with modified json file is clever, but I am not sure if someone
has ever tried that. I have just tested that it can be injected in via
`-Dupdate_center_url=file:update-center.json` java property property,
but it misbehaves in case the url got cached earlier. To fix that, [1]
needs to be updated not to cache custom `update_center_url`.
[1]
https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/update_center/CachedUpdateCenterMetadataLoader.java#L38
--
oliver
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/a546dd6c-c420-b427-c89f-71e1e1188534%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
