lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From NightOwl888 <...@git.apache.org>
Subject [GitHub] lucenenet issue #206: API Doc site generator using DocFx script
Date Fri, 01 Jun 2018 10:01:17 GMT
Github user NightOwl888 commented on the issue:

    https://github.com/apache/lucenenet/pull/206
  
    > We could potentially use some automation to overwrite the main Lucene.Net website
and add a new subfolder for each version of docs right from the [Lucene.Net Release](https://teamcity.jetbrains.com/project.html?projectId=LuceneNet_PortableBuilds&tab=projectOverview)
step.
    
    Come to think of it, we wouldn't want to push them to the server at that stage. We should
probably just have TeamCity package up a 3rd `.zip` file with both the generated docs and
website. This 3rd package could possibly be part of the release (if only to keep track of
the release artifacts for the long term).
    
    Ideally, there would be a TeamCity task after `Lucene.Net Release` (perhaps rolled into
`Lucene.Net MyGet Deploy`) where the docs would be unzipped and pushed onto a staging web
server where they could be evaluated during the release vote (provided we can get a staging
server location).
    
    Then there would be a final TeamCity task to do the same to the production web server
after the release vote passes. 
    
    Both of these TeamCity build configurations would potentially have identical steps and
artifacts with different areas to push to, so we could use the same TeamCity template to create
`Lucene.Net Pre-Vote Deploy` and `Lucene.Net Post-Vote Deploy` build configurations in TeamCity
to make it clear what to do and when.


---

Mime
View raw message