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
Combine publish and publish-experimental build scripts #872
Comments
|
Thanks for this Josh (@jmreicha). I too have tested AArch64 and it appears to be functioning correctly. It would be fantastic to pull the main repo and get AArch64 support. Does anyone have an idea on timelines? |
Depends on the number of contributions we get. Thanks for testing it BTW! |
Any idea how that translates roughly into time? 1 day, 3 weeks, 6 months? |
|
ETA for the new LTS baseline is Sep 25. I will not provide any ETA for the feature itself. It is open-source. It is done when it is done, any time commitments just put stress on contributors who often invest their personal time to maintain the project. Depending on contributions, it might happen before or after LTS (or it might never happen at all). |
|
Right. I understand the ethics of open source. The AArch64 image appears to be working. What contributions are left wanting? |
|
Some level of compatibility checking with plugins and so forth would be good. Also, there are two other architectures that need to be tested |
|
To add to the list, ongoing ci.jenkins.io instabilities do not help: https://groups.google.com/forum/#!topic/jenkinsci-dev/v9d-XosOp2s . It may delay it a bit |
|
You might consider doing multi-arch testing using Drone Cloud, which you can run tests on x86 and arm64 native |
|
Any news on the LTS date? |
|
Any update on this issue? |
|
Which tag should I be using with Raspberry Pi 4B? 2.214-alpine-arm64 Keeps crashing |
|
@willinger all of the non amd64 images are experimental, so any issues you run into would best be filed in Jira (https://issues.jenkins.io). |
|
Script has been combined / removed |
Now that multi-arch images are building and getting pushed to the jenkins4eval repo, it would be nice to wrap everything up into one build script so that build scripts are kept DRY and in sync.
Any suggestions for how to test and verify that all the various new multi-arch builds are working correctly? I have tested aarch64 manually and it seems to work fine but I haven't done any type of systematic testing.
/cc @slide @oleg-nenashev @imdurgadas @lag-linaro
The text was updated successfully, but these errors were encountered: