You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2024/01/08 16:53:00 UTC

[jira] [Commented] (FLINK-34026) Azure Pipelines not running for master and the release branches since 4a852fe

    [ https://issues.apache.org/jira/browse/FLINK-34026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804373#comment-17804373 ] 

Matthias Pohl commented on FLINK-34026:
---------------------------------------

[~martijnvisser] [~lincoln] [~yunta] [~jingge] Someone with access might need to check the Ververica-owned VM (if my suspicion with the repo-sync is correct).

> Azure Pipelines not running for master and the release branches since 4a852fe
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-34026
>                 URL: https://issues.apache.org/jira/browse/FLINK-34026
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System / CI
>            Reporter: Matthias Pohl
>            Priority: Blocker
>
> It appears that [no Azure CI builds|https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary] are triggered for {{master}} (and possibly the release branches) since 4a852fee28f2d87529dc05f5ba2e79202a0e00b6.
> The [PR CI workflows|https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=2] appear to be not affected. I suspect some problem with the repo-sync process.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)