Skip to content

Conversation

@snuyanzin
Copy link
Contributor

What is the purpose of the change

The hotfix commit which skips web ui build while javadoc:aggregate task
After that this task for me locally takes about 20 sec instead of 1.5 min

Brief change log

compile.sh

Verifying this change

existing tests

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): ( no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): ( no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: ( no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable )

@snuyanzin snuyanzin changed the title [hotfix][javadoc] Skip skip-webui-build while javadoc:aggregate [hotfix][javadoc] Use skip-webui-build while javadoc:aggregate Jan 11, 2026
@flinkbot
Copy link
Collaborator

flinkbot commented Jan 11, 2026

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

$MVN javadoc:aggregate -DadditionalJOption='-Xdoclint:none' \
-Dmaven.javadoc.failOnError=false -Dcheckstyle.skip=true -Denforcer.skip=true -Dspotless.skip=true -Drat.skip=true \
-Dheader=someTestHeader > ${javadoc_output}
-Dheader=someTestHeader -Pskip-webui-build > ${javadoc_output}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something wrong is happening with azure

compile takes more than 2 hours for the recent master build https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=71583&view=results

at the same time with this change it takes only one hour https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=71589&view=logs&s=ae4f8708-9994-57d3-c2d7-b892156e7812&j=52b61abe-a3cc-5bde-cc35-1bbe89bb7df5

At the same time I still tend to think that the problem is somewhere on azure or Alibaba (we use their server there) side, since there is no noticeable change in GHA

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to skip the tests short term. Is there a Jira to track this issue and maybe include the Jira number in a comment here.

Copy link
Contributor Author

@snuyanzin snuyanzin Jan 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't think it is short term, there is no javadocs in web ui build, so anyway it doesn't make sense to include it while building javadoc

in case of hotfix it doesn't make sense to create a jira imho

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok that makes sense- thanks for the extra detail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants