-
Notifications
You must be signed in to change notification settings - Fork 27
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
[JAVA-2745] Setup Quarkus Ecosystem CI #38
Comments
Imported from JAVA-2745, originally commented by @absurdfarce on Fri, 8 May 2020 06:33:01 GMT. There’s mention in the how-to description at https://github.com/quarkusio/quarkus-ecosystem-ci about adding your extension to Quarkus Platform (basically a set of known good inter-operating plugins… see https://github.com/quarkusio/quarkus-platform ) before pursuing the integration with their CI. It doesn’t look like this is strictly necessary as there appear to be a few other extensions which are either in the process of adding themselves to Quarkus Platform or just aren’t in there at all. But I figured the question might come up when we start down this path so I wanted to make sure we were on the same page re: adding ourselves to Quarkus Platform. cc @tomekl007 and @adutra |
Imported from JAVA-2745, originally commented by @tomekl007 on Fri, 8 May 2020 06:58:35 GMT. Regarding integration with their quarkus platform, I think that it is only necessary to add a couple of integration tests in this repo, see this Jira task that I’ve created some time ago: |
Imported from JAVA-2745, originally commented by @adutra on Fri, 8 May 2020 10:29:24 GMT. @absurdfarce Yes the intention is to eventually get ourselves added to Quarkus Platform. Some of the prerequisites for that seem to be: CI integration, documentation, and quick-starter. Which is why we are working on all these items. |
Imported from JAVA-2745, originally commented by @absurdfarce on Fri, 8 May 2020 15:33:59 GMT. To be clear: their README for the CI seems to indicate that joining the Quarkus Platform was required: “After your extension has been added to the Quarkus Platform, you will additionally need to do the following“ As I mentioned above it doesn’t look like this is exactly required as there are extensions in the CI repo which are not in Quarkus Platform. My goal in asking was to make sure we were clear on the goal in case it came up during this process. |
Imported from JAVA-2745, originally commented by @absurdfarce on Fri, 8 May 2020 16:30:46 GMT. Quarkus ticket: quarkusio/quarkus#9183 |
Imported from JAVA-2745, originally commented by @absurdfarce on Fri, 8 May 2020 16:31:13 GMT. PR against ecosystem-ci repo to add us: quarkusio/quarkus-ecosystem-ci#12 |
Imported from JAVA-2745, originally commented by @absurdfarce on Fri, 8 May 2020 16:36:23 GMT. ECOSYSTEM_CI_TOKEN has been added. I believe at this point all that needs to happen is for our PR against the ecosystem-ci repo to be merged + the PR for this ticket to be merged and we should be in business |
Imported from [JAVA-2745](https://datastax-oss.atlassian.net/browse/JAVA-2745), originally reported by tomekl007 on Mon, 20 Apr 2020 06:45:14 GMT.
According to a conversation with quarkus team:
So we should consider using this method for CI
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: