[
https://issues.apache.org/jira/browse/SOLR-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238702#comment-13238702
]
Steven Rowe commented on SOLR-3268:
-----------------------------------
{quote}
add a final step to the jenkins build script that fails if "svn status | wc -l"
returns non-zero?
it wont't ensure no changes are made to src/, but it should ensure no changes
are made to src/ unless explicitly allowed by an svn:ignore
{quote}
I don't remember which one(s), but I recall that at least one file is (was?)
produced by a Solr test and svn:ignore'd. In order for Hoss's suggestion to be
fully effective, we should stop svn:ignore'ing test outputs (outside of
{{build/}} or other already ignored directories). I'll see what's being
svn:ignore'd now.
> remove write acess to source tree (chmod 555) when running tests in jenkins
> ---------------------------------------------------------------------------
>
> Key: SOLR-3268
> URL: https://issues.apache.org/jira/browse/SOLR-3268
> Project: Solr
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0
>
> Attachments: SOLR-3268_sync.patch
>
>
> Some tests are currently creating files under the source tree.
> This causes a lot of problems, it makes my checkout look dirty after running
> 'ant test' and i have to cleanup.
> I opened and issue for this a month in a half for
> solrj/src/test-files/solrj/solr/shared/test-solr.xml (SOLR-3112),
> but now we have a second file
> (core/src/test-files/solr/conf/elevate-data-distrib.xml).
> So I think hudson needs to chmod these src directories to 555, so that solr
> tests that do this will fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
