[
https://issues.apache.org/jira/browse/BEAM-13135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kozyrev updated BEAM-13135:
--------------------------------
Description:
As an Apache Beam *maintainer* who develops examples, katas, or unit tests, I
want to have a validation step in the CI pipeline for my Pull Request into the
Apache Beam repository. This step should check tagged objects for Playground
and give feedback in PR if something went wrong.
*Acceptance criteria:*
# Search Tags in the Apache Beam codebase
# Tag format validations for objects
# Compilation validation for tagged objects
# Verification for running ability in the Playground environment
# Feedback sends in Pull Request
*Scenario:* CI script found object available for Playground usage
*Given:* CI is triggered for new PR
*When:* CI script scan file in apache beam repository
*And:* File contained Playground tag
*Then:* CI Validates this file for usage in Playground
*Given:* CI found tagged object
*When:* CI runs validation for tag format
*And:* Validation is complete
*Then:* CI starts the compilation for this object
*Given:* CI found tagged object
*When:* CI runs validation for tag format
*And:* Validation is failed
*Then:* CI task ends with an error and feedback received to PR
–
*Given:* Validation is complete
*When:* CI runs compilation for object
*And:* Compilation is complete
*Then:* CI starts the run step for this object
–
*Given:* Validation is complete
*When:* CI runs compilation for object
*And:* Compilation is failed
*Then:* CI task ends with an error and feedback received to PR
–
*Given:* Compilation is complete
*When:* CI runs object's code in Playground
*And:* Run step is complete
*Then:* CI Ends successfully
*Given:* Compilation is complete
*When:* CI runs object's code in Playground
*And:* Run step
*Then:* CI task ends with an error and feedback received to PR
was:
As an Apache Beam *maintainer* who develops examples, katas, or unit tests, I
want to have a validation step in the CI pipeline for my Pull Request into the
Apache Beam repository. This step should check tagged objects for Playground
and give feedback in PR if something went wrong.
*Acceptance criteria:*
# Search Tags in the Apache Beam codebase
# Tag format validations for objects
# Compilation validation for tagged objects
# Verification for running ability in the Playground environment
# Feedback sends in Pull Request
*Scenario:* CI script found object available for Playground usage
*Given:* CI is triggered for new PR
*When:* CI script scan file in apache beam repository
*And:* File contained Playground tag
*Then:* CI Validates this file for usage in Playground
*Given:* CI found tagged object
*When:* CI runs validation for tag format
*And:* Validation is complete
*Then:* CI starts the compilation for this object
*Given:* CI found tagged object
*When:* CI runs validation for tag format
*And:* Validation is failed
*Then:* CI task ends with an error and feedback received to PR
–
*Given:* Validation is complete
*When:* CI runs compilation for object
*And:* Compilation is complete
*Then:* CI starts the run step for this object
–
*Given:* Validation is complete
*When:* CI runs compilation for object
*And:* Compilation is failed
*Then:* CI task ends with an error and feedback received to PR
–
*Given:* Compilation is complete
*When:* CI runs object's code in Playground
*And:* Run step is complete
*Then:* CI Ends successfully
*Given:* Compilation is complete
*When:* * *CI runs object's code in Playground* *
*And:* Run step
*Then:* CI task ends with an error and feedback received to PR
> [Playground] Validate step in Beam CI pipelines for Playground objects
> ----------------------------------------------------------------------
>
> Key: BEAM-13135
> URL: https://issues.apache.org/jira/browse/BEAM-13135
> Project: Beam
> Issue Type: New Feature
> Components: beam-playground
> Reporter: Ilya Kozyrev
> Priority: P3
> Labels: beam-playground-devops, beam-playground-sprint-3,
> beam-playground-sprint-4
>
> As an Apache Beam *maintainer* who develops examples, katas, or unit tests, I
> want to have a validation step in the CI pipeline for my Pull Request into
> the Apache Beam repository. This step should check tagged objects for
> Playground and give feedback in PR if something went wrong.
> *Acceptance criteria:*
> # Search Tags in the Apache Beam codebase
> # Tag format validations for objects
> # Compilation validation for tagged objects
> # Verification for running ability in the Playground environment
> # Feedback sends in Pull Request
> *Scenario:* CI script found object available for Playground usage
> *Given:* CI is triggered for new PR
> *When:* CI script scan file in apache beam repository
> *And:* File contained Playground tag
> *Then:* CI Validates this file for usage in Playground
>
> *Given:* CI found tagged object
> *When:* CI runs validation for tag format
> *And:* Validation is complete
> *Then:* CI starts the compilation for this object
>
> *Given:* CI found tagged object
> *When:* CI runs validation for tag format
> *And:* Validation is failed
> *Then:* CI task ends with an error and feedback received to PR
> –
> *Given:* Validation is complete
> *When:* CI runs compilation for object
> *And:* Compilation is complete
> *Then:* CI starts the run step for this object
> –
> *Given:* Validation is complete
> *When:* CI runs compilation for object
> *And:* Compilation is failed
> *Then:* CI task ends with an error and feedback received to PR
> –
> *Given:* Compilation is complete
> *When:* CI runs object's code in Playground
> *And:* Run step is complete
> *Then:* CI Ends successfully
>
> *Given:* Compilation is complete
> *When:* CI runs object's code in Playground
> *And:* Run step
> *Then:* CI task ends with an error and feedback received to PR
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
