Re: Revised RFS: jenkins 1.409.3-1 (new)
On 03/01/2012 11:00, James Page wrote:
Hi Damien
Hi James!
war/src/main/webapp/WEB-INF/update-center-rootCAs/hudson-community
This certificate (well its parent in fact) is used by Jenkins centrally
to sign updates/plugins etc that are published to the jenkins update
centers; I think this should be retained as it ensures that the Jenkins
web application trusts signed content Jenkins upstream (which is
important as we will never package all 400 plugins...).
Ok, I got you point. But you have to describe this to FTP Master,
otherwise they will think its just a binary blob. Maybe also describe
how to edit this one (with keytool I suppose).
Zip files (should be dropped)
test/src/main/resources/*.zip
test/src/main/resources/plugins/tasks.hpi
test/src/test/resources/hudson/maven/*.zip
test/src/test/resources/hudson/tasks/junit/*t.zip
test/src/test/resources/hudson/tasks/test/*.zip
test/src/test/resources/hudson/ClassicPluginStrategyTest/*.zip
test/src/test/resources/hudson/security/*.zip
test/src/test/resources/hudson/tasks/*.zip
test/src/test/resources/hudson/model/DependencyGraphTest/*.zip
test/src/test/resources/hudson/model/JobTest/*.zip
Sample svn repository (maybe generated from something else ?)
test/src/main/preset-data/svn-repo/
The test project contains the integration tests for Jenkins; I think
that is unlikely that we will ever be able to execute this in full
without dropping most of the content for DFSG compliance and completely
devaluing the effort; I would proposed that we drop test/* from the
upstream archive.
If you are happy with my proposed approach I'll re-package the upstream
tarball with a +dfsg and push to the git repository
Yes, that's fine for me.
Cheers,
Reply to: