-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Kotlin daily builds #10
Comments
I can look into this later. WDYT @pascalgrimaud |
new dedicated pipeline with Kotlin, similar to the config with 'official' or 'official openjdk8' pipelines With kotlin, you can use the same app/config (.yo-rc.json) |
It seems they have their own pipelines files for ci-cd that we can reuse (or supplement) for daily builds |
pinging @pvliss to ask what kind of config you would like to test. |
Thanks for looking into this @Hawkurane. Well, the pipeline is indeed identical with the exception of one or two samples to test some extra configurations as there is currently no daily build. In fact, the KHipster blueprint supports the exact same features as the Java main generator. We can re-use all the existing samples( I think I asked @pascalgrimaud before but would it be possible to have a separate repo for khipster daily builds in order to have all the pipelines of interest(instead of just 1-2) and re-use all samples( |
That is a very valid point @pvliss AFAICT, it would be great if we have separate repos for this. Because it will not be an overhead for anyone maintaining it. But if there are limitations, then we have to think about it. |
As far as I remember, each azure organization gets 10 parallel agents that can work at the same time. This means we can make another organization (e.g. khipster-daily-builds) which would be basically the fork from this repo and just changing the scripts to make sure the khipster blueprint is used. @pascalgrimaud should be the one making the org imo if there should ever be a new azure organization/account |
Opened for too long, let's close this |
Following this jhipster/jhipster-kotlin#138 (comment)
The text was updated successfully, but these errors were encountered: