lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [lucenenet] NightOwl888 commented on issue #229: Updates docs build
Date Fri, 16 Aug 2019 03:45:37 GMT
NightOwl888 commented on issue #229: Updates docs build
   > Looks like the build server doesn't execute with changes based on PRs so you might
have to give it a nudge and see how it goes.
   That would be because I haven't investigated setting up the PR options yet.
   I pulled down your changes and pushed them up to Azure DevOps. This time it failed much
   BTW - You could potentially setup your own Azure DevOps account, add a Lucene.NET project
to it pointing to your GitHub fork, and use the `azure-pipelines.yml` to run the build. This
will allow you to check whether it works and iterate more quickly. On the last step of the
"Create build pipeline" workflow, you see the "run" button but it doesn't give you any options
to enter variables. After you click it, you can cancel the first build, then enter variables.
They have hidden them pretty well, though.
   1. Navigate to `<your organization>` > `<your project>` > Pipelines >
   2. Select the pipeline on the left, then click the "Edit" button on the right
   3. If you setup your project as "public", you will see a "Variables" button at the top
right of the page. If it is private, you need to click the ellipsis in the corner and choose
"Triggers", then once that page opens there will be a "Variables" tab.
   You will probably want to set:
   1. `GenerateDocs` = `true`
   2. `RunTests` = `false`
   We will probably end up changing the exact location the doc generation happens in the pipeline,
but for now this will get you started so you can work out how to get it running.
   Once it runs all the way through, the files will be zipped and added as a `docs` build
artifact [on the Summary tab of the build](,
which you can then download and verify.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message