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

CI: Introduce nightly JDK EA/RC job (starting with JDK 16 RC) #15575

Closed
famod opened this issue Mar 9, 2021 · 5 comments · Fixed by #15711
Closed

CI: Introduce nightly JDK EA/RC job (starting with JDK 16 RC) #15575

famod opened this issue Mar 9, 2021 · 5 comments · Fixed by #15711
Labels
area/housekeeping Issue type for generalized tasks not related to bugs or enhancements area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure
Milestone
2.0.0.Alpha1

Comments

@famod
Copy link
Member

famod commented Mar 9, 2021

Description
There is no CI job/workflow that is testing the next upcoming JDK, e.g. JDK 16 as of 09.03.2021.

See discussion: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Quarkus.20tested.20on.20Java.2016

Implementation ideas

  • at least analogous to job "JVM Tests - JDK 11"
  • more jobs to be decided:
    • Windows?
    • Maven?
    • Devtools?
    • Gradle?
  • trigger: nightly and on-demand
  • include in status.quarkus.io
@famod famod added the area/housekeeping Issue type for generalized tasks not related to bugs or enhancements label Mar 9, 2021
@quarkus-bot quarkus-bot bot added the env/windows Impacts Windows machines label Mar 9, 2021
@famod famod added area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure and removed env/windows Impacts Windows machines labels Mar 9, 2021
@gsmet
Copy link
Member

gsmet commented Mar 9, 2021

Let's run a simple full build on Linux. We don't care if it takes time so I would keep it simple.

@famod
Copy link
Member Author

famod commented Mar 11, 2021

Ok, KISS it is. Do we care about that job possibly creating the monthly Maven repo cache instead of the JDK 11 job from the regular CI workflow?

@gsmet
Copy link
Member

gsmet commented Mar 11, 2021

I don't think it makes sense to rely on a non final JDK to do anything :)

@famod famod self-assigned this Mar 13, 2021
@famod
Copy link
Member Author

famod commented Mar 14, 2021 •
edited

FWIW, I'm testing a new workflow file in my fork: https://github.com/famod/quarkus/actions/workflows/jdk-early-access-build.yml
4 hours timeout were not sufficient, testing with 6 hours now.

AFAICS, we'll have to use the default setup-java action to get an EA build easily, which is a Zulu one (not AdoptOpenJDK) but better than nothing. 😉

@famod famod mentioned this issue Mar 14, 2021
Merged
@famod
Copy link
Member Author

famod commented Mar 14, 2021 •
edited

#15711 adds the respective job. After this is merged, someone else will have to do the status.quarkus.io part.

@famod famod removed their assignment Mar 14, 2021
@quarkus-bot quarkus-bot bot added this to the 1.14 - main milestone Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/housekeeping Issue type for generalized tasks not related to bugs or enhancements area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure
Projects
None yet
Milestone
2.0.0.Alpha1
Development

Successfully merging a pull request may close this issue.

Introduce nightly/manual Early Access JDK build
2 participants
@gsmet @famod