A modern programming language that makes developers happier.

kotlinlang

Screenshot 2022-04-05 at 11.35.34.png

Hi, we are using the M1 chips for our development and therefore using your `1.6.20-M1` release. When we run `./gradlew assemble` on our machines, everything works fine. However, when we run it on our CI we get the following log.
Our CI is using `gradle:jdk-11` docker image which is linux-aarc64 based. Does anyone know what's going on? It seems that `1.6.20-M1` can't be used on non macOS systems? If so, is there a way to use `1.6.20-M1` and `1.6.20` simultaneously?

M1 does not mean it is meant for the M1 chips, it means milestone 1 (milestones before release candidates before release). just use `1.6.20`.

in general, you cannot use multiple versions of the Kotlin compiler in the same project

M1  = milestone1 ? you are kidding :laughing:

I am using `1.6.20` but I am still not able to download the resource :thinking_face:

`&gt; Caused by: org.gradle.internal.resource.transport.http.HttpErrorStatusCodeException: Could not HEAD '<https://download-cdn.jetbrains.com/kotlin/native/builds/releases/1.6.20/linux-aarch64/kotlin-native-prebuilt-linux-aarch64-1.6.20.tar.gz>'. Received status code 403 from server: Forbidden`
`build                   &gt;       at org.gradle.internal.resource.transport.http.HttpClientHelper.processResponse(HttpClientHelper.java:215)`
`build                   &gt;       at org.gradle.internal.resource.transport.http.HttpClientHelper.performHead(HttpClientHelper.java:88)`
`build                   &gt;       at org.gradle.internal.resource.transport.http.HttpResourceAccessor.getMetaData(HttpResourceAccessor.java:66)`
`build                   &gt;       at org.gradle.internal.resource.transfer.DefaultExternalResourceConnector.getMetaData(DefaultExternalResourceConnector.java:63)`
`build                   &gt;       at org.gradle.internal.resource.transfer.AccessorBackedExternalResource.getMetaData(AccessorBackedExternalResource.java:201)`
`build                   &gt;       at org.gradle.internal.resource.BuildOperationFiringExternalResourceDecorator$1.call(BuildOperationFiringExternalResourceDecorator.java:61)`
`build                   &gt;       at org.gradle.internal.resource.BuildOperationFiringExternalResourceDecorator$1.call(BuildOperationFiringExternalResourceDecorator.java:58)`

<https://youtrack.jetbrains.com/issue/KT-36871>

I hadn't realized that linux-aarch64 just wasn't being supported as a host… even though `linuxArm64` is a supported target

Oh shoot! so then there is no way for me to run my CI pipeline locally using docker and my Apple M1, right? would you have any advice on how you'd go on testing a CI pipeline locally?

I don't have a M1 mac so I can't confirm but from a search it seems that Docker should support x86 containers still

Sorry, missed this! Thank you for your time :pray: