Maybe not? Our naming for jenkins has been
job_(PreCommit|PostCommit)_(Java|Python|Go|Website){_action}.groovy.
There is already a legacy job_PreCommit_Website_Stage.groovy, which stages on
beam-site.
And a new job_PreCommit_Website_Stage_Test.groovy for verifying the website.
Naming it job_StageWebsite would be inconsistent with the other jobs.
When the change from beam-site to beam is done, then
job_PreCommit_Website_Stage.groovy can be deleted and this one renamed.
[ Full content available at: https://github.com/apache/beam/pull/6546 ]
This message was relayed via gitbox.apache.org for [email protected]
