[
https://issues.apache.org/jira/browse/BEAM-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648082#comment-16648082
]
Scott Wegner commented on BEAM-5672:
------------------------------------
re: Add it to the pr template: We have an existing PR template in GitHub, but
it's not specific to website changes. GitHub allows creating multiple PR
templates for a repository, but it seems the way to select a template is via
URL query parameters and is not triggered automatically i.e. based on changed
file path. I don't think this is a viable solution.
[PR 6669|https://github.com/apache/beam/pull/6669] pulls the website URL up to
the top-level Jenkins job page; I think this is sufficient until we can think
of nicer solutions.
> Staged URL should be posted to GitHub PR
> ----------------------------------------
>
> Key: BEAM-5672
> URL: https://issues.apache.org/jira/browse/BEAM-5672
> Project: Beam
> Issue Type: Sub-task
> Components: website
> Reporter: Scott Wegner
> Assignee: Alan Myrvold
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Website PRs are automatically tested and staged via Jenkins to a location on
> GCS: https://builds.apache.org/job/beam_PreCommit_Website_Stage_GCS_Commit/
> However, it's difficult to find the URL for the staged job; it's buried
> inside the Jenkins job, inside the Gradle scan, inside the log.
> I believe there's an API for posting back a context message to the pull
> request. If possible, we should push the URL so it's easily viewable from the
> pull request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
