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

   Hi @damccorm 
   I am reaching out to get feedback on this job, we previously discussed it 
with @kerrydc to leave it to the bottom of the queue since we have the 
following issue:
   - 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.
   
   We want to check if the job can be left in Jenkins and think of a plan of 
action for the next steps regarding this job?
   
   We currently have some alternatives like:
   - 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.
   - 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.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to