Hi Lari,
Thanks for launching this discussion. There's a lot to do to improve
contributor experience, esp for newcomers I think.
One of the pain points is obviously the CI flakyness and I believe we are
all aware of that.
Related to that, we have the pulsarbot to relaunch the tests that failed
but
Hi Yu,
> For these special doc PRs, can we set them to run only build (compile)
> tests and skip other code tests?
If code is updated, the build & tests shouldn't be skipped in the current
solution.
If we'd like to make the build faster and skip unnecessary tests, we would need
a more advance
Thank you Lari!
Except for updating .md docs, we need to update various API docs [1]. These
docs are generated from code automatically (annotations in code files).
For these special doc PRs, can we set them to run only build (compile)
tests and skip other code tests?
~~
[1]
Admin API d
On 2022/09/01 08:36:11 Yu wrote:
> # 1
> For pure doc PRs (only update .md files), do they run the same tests as
> code PRs?
> If so, can we set them to run only doc-related tests and skip code tests
> (since they're easily failed)?
> In this way, docs can be iterated faster.
The solution is alrea
Hi Lari,
Thanks for raising this up! May I know your thoughts on these questions?
# 1
For pure doc PRs (only update .md files), do they run the same tests as
code PRs?
If so, can we set them to run only doc-related tests and skip code tests
(since they're easily failed)?
In this way
I'm sharing my experience about finding the reason why the build fails. This
has been frustrating.
In the past, it has been a challenge to find the reason why the build fails.
Not that we don't have the information about the failure, but the challenge is
that there's too much information. :)
L
