[
https://issues.apache.org/jira/browse/FLINK-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139398#comment-17139398
]
Robert Metzger commented on FLINK-18125:
----------------------------------------
Thanks.
I believe it is impossible to figure out from a branch in flink-ci/flink what
the actual diff of the change is. With builds properly triggered from a pull
request, GitHub can tell us the base branch (master, release-1.11).
In order to solve this, we would need to change cibot to include the
base-branch in the mirrored branch (such as: {{ci_$PRID_$COMMIT_$BASEBRANCH}}).
[~chesnay] Do you have a better idea? Do you think such a change to cibot would
be feasible?
Note to self: My work so far is recorded here:
https://github.com/rmetzger/flink/tree/FLINK-18125-skip-e2e-docs
> Skip CI execution on documentation pull requests
> ------------------------------------------------
>
> Key: FLINK-18125
> URL: https://issues.apache.org/jira/browse/FLINK-18125
> Project: Flink
> Issue Type: Improvement
> Components: Build System / Azure Pipelines
> Reporter: Robert Metzger
> Priority: Major
>
> In order to save some resources, we can skip the CI execution on
> documentation-only changes (whole changeset).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
