[ 
https://issues.apache.org/jira/browse/LUCENE-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Muir resolved LUCENE-4295.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0
                   5.0

I turned this on in hudson. Its likely to be very slow. I think it would 
actually be better if it were a separate jenkins task that ran say, twice a 
week.

But for now we just can't leave packaging etc untested until release time, its 
too painful.
                
> smoke test an unsigned release in hudson nightly
> ------------------------------------------------
>
>                 Key: LUCENE-4295
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4295
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>             Fix For: 5.0, 4.0
>
>         Attachments: LUCENE-4295.patch
>
>
> Currently to build a release, its a huge battle to get the smoke tester "up 
> to speed"
> so the checks are actually current and everything works, and its python so
> its pretty fragile (no compile time checking).
> So I think its time to do this in the nightly build, otherwise release 
> managers, python
> gurus, policeman, and whoever just likes punishment has to do a lot of work 
> before the release
> to adapt to all the changes: its easier to keep this stuff maintained 
> incrementally.
> We need a top-level task 'nightly-smoke' that does prepare-release-no-sign 
> for lucene + solr,
> then smoke tests it and fails if the smoke tester fails.

--
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]

Reply via email to