Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable a broken test until we upgrade to Metrics 1.7.8 (via Quarkus upgrade) #1796

Merged
merged 1 commit into from
Jan 18, 2022

Conversation

rsynek
Copy link

@rsynek rsynek commented Jan 18, 2022

See micrometer-metrics/micrometer#2947.

JIRA

Referenced pull requests

Checklist

  • Documentation updated if applicable.
  • Upgrade recipe provided if applicable.
How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:
  • for a pull request build please add comment: Jenkins retest this
  • for a specific pull request build please add comment: Jenkins (re)run [optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests
  • for a full downstream build
    • for jenkins job: please add comment: Jenkins run fdb
    • for github actions job: add the label run_fdb
  • for a compile downstream build please add comment: Jenkins run cdb
  • for a full production downstream build please add comment: Jenkins execute product fdb
  • for an upstream build please add comment: Jenkins run upstream
  • for a Quarkus LTS check please add comment: Jenkins run LTS
  • for a specific Quarkus LTS check please add comment: Jenkins (re)run [optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] LTS
  • for a Native check please add comment: Jenkins run native
  • for a specific Native LTS check please add comment: Jenkins (re)run [optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

@kie-ci
Copy link
Contributor

kie-ci commented Jan 18, 2022

The (build) optaplanner check has failed. Please check the logs.

@triceo triceo merged commit 469f92c into apache:main Jan 18, 2022
@rsynek rsynek deleted the disableMetricsTest branch August 25, 2022 10:22
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