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.

Sign up for GitHub

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

Jump to bottom

Introduce CI #113

Closed
dmlloyd opened this issue Dec 17, 2021 · 2 comments
Closed

Introduce CI #113

dmlloyd opened this issue Dec 17, 2021 · 2 comments

Comments

@dmlloyd
Copy link
Member

dmlloyd commented Dec 17, 2021

While it's not easy to test a project such as this one directly, it should be possible to check out a couple of reference sub-projects and build & test them with the SNAPSHOT version of this project, perhaps with a few JDKs installed from the supported set.
@gastaldi gastaldi mentioned this issue Mar 14, 2022
Merged
@bstansberry
Copy link
Contributor

As @rhusar just suggested to me, using WIldFly as one of the reference subprojects could work, at least for SE 11. And sometime in the next few months SE 17 would be suitable too. (We currently don't compile with SE 17 and use complicated test jobs to test the runtime on 17, but I believe we could move to compiling on SE 17 now.)

@rhusar rhusar mentioned this issue Nov 11, 2022
Open
@dmlloyd
Copy link
Member Author

dmlloyd commented Sep 21, 2023

We have enabled CI with three projects for the time being. We can expand it out as needed.

@dmlloyd dmlloyd closed this as completed Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dmlloyd @bstansberry