[GitHub] [beam] damccorm commented on pull request #23403: GA Migration PostCommit Javadoc

[GitBox <gi...@apache.org>]

damccorm commented on PR #23403:
URL: https://github.com/apache/beam/pull/23403#issuecomment-1262319413

   > The [Javadoc in Jenkins](https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_Javadoc/) uses some plugins to get reports of warnings like compilation issues and warnings and display the Javadoc site. So when we migrated the job to GitHub Actions, we were unable to fully migrate the job since the plugins don't exist in GA.
   
   **"display the Javadoc site"** To be clear, this doesn't actually publish the javadoc to the beam website, right? Or does it? What do you mean by display the Javadoc site?
   
   > We found there is a GitHub action which [publish the javadoc](https://github.com/MathieuSoysal/Javadoc-publisher.yml) in the [Github Pages](https://github.com/marketplace/actions/deploy-github-pages-site) inside the current repository into another branch but it requires to enable the GitHub pages. Or we could export the Javadoc dir, so it could be downloaded as an artifact inside the GA.
   
   Assuming this is just for developer purposes I think publishing it as an artifact is probably fine.
   
   > And for the Javadoc warnings metrics, it could be possible to get the data and push it to InfluxDB and connect it with Grafana. But for this one is just a concept at this point or an idea to solve the issue.
   
   @apilloud do you know if anyone uses these metrics? In general, would just appreciate your thoughts on what our requirements for this job actually should be.


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

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org