search

quarkusio / quarkus

Quarkus: Supersonic Subatomic Java.
https://quarkus.io
Apache License 2.0
13.4k stars 2.57k forks source link

[CI] - Camel Quarkus extensions + Quarkus main #8646

Open ppalaga opened 4 years ago

ppalaga commented 4 years ago

This issue will be open and closed dependent on the state of https://github.com/apache/camel-quarkus building against Quarkus master snapshot.

If you have interest in being notified of this subscribe to the issue.

maxandersen commented 4 years ago

@ppalaga can we close this for now as its not currently being open/closed by camel testing ?

ppalaga commented 4 years ago

+1, let's close

maxandersen commented 3 years ago

going to reopen this as its better it shows up red than green in status.quarkus.io.

gsmet commented 3 years ago

@ppalaga is there a way for you to report the Camel Quarkus build status to status.quarkus.io? Because I don't really agree being red is better than green because I check things regularly.

So either we find a way to report your status to status.quarkus.io or we just remove it from there (and then you're on your own, we won't monitor things at all).

ppalaga commented 3 years ago

Could you please remind me of the docs or example how to set it up?

gsmet commented 3 years ago

@ppalaga so you either use the whole Ecosystem CI such as in https://github.com/quarkiverse/quarkus-github-app/blob/main/.github/workflows/quarkus-snapshot.yaml (so that's one more build) or you just use the report facility https://github.com/quarkusio/quarkus/blob/main/.github/workflows/jdk-early-access-build.yml#L108-L119 (you will have to tweak issueNumber and issueRepo, also there's a good chance we will need to provide you with a token so that you can close/open the issue).

gsmet commented 3 years ago

I'm removing the labels including this issue into status.quarkus.io. We can add them again later if the issue is properly synced.

ppalaga commented 3 years ago

We have a nightly build that we watch and we'd like to attach that one to your dashboard.

When it comes to the issue status.quarkus.io could watch, can it be an issue in Camel Quarkus? We already have something like that, but our ci job is opening a new issue for every new failure. I think we would not mind keeping the issue number constant over time and just switch the state.

ppalaga commented 2 years ago

@jamesnetherton adapted our nightly Quarkus Main job to always use the same issue. It is this one: https://github.com/apache/camel-quarkus/issues/2926

How can it now be wired with status.quarkus.io? I guess you need to watch it on your side?