Where may I find snapshot version numbers for Kote...
# kotest
j
Where may I find snapshot version numbers for Kotest?
s
there's a badge on teh github index page
j
Thanks. I'm not sure what the badge is on there. Is it the last commit number? It's not
v5.5.5
that I need. I need a build of the unreleased master.
j
Awesome. Thank you!
s
np 🙂
j
I'm trying to use the Kotest snapshot in the Arrow project. But I get this error when I build:
Copy code
Could not find io.kotest:kotest-framework-engine-iosx64:5.6.0.1131-SNAPSHOT.
Required by:
    project :arrow-continuations > io.kotest:kotest-framework-engine:5.6.0.1131-SNAPSHOT:20221009.182649-1
Any ideas about this? I thought updating this line in the Arrow
.toml
to the snapshot version would be sufficient to set the version for all Kotest dependencies. https://github.com/lgtout/arrow/blob/bacd9042f5d7c9bbba2dc8244ddd277f6995d874/gradle/libs.versions.toml#L11-L11
s
Did you add the maven snapshots repo
j
I thought that's already present in the Arrow library here, so I didn't need to: https://github.com/lgtout/arrow/blob/bacd9042f5d7c9bbba2dc8244ddd277f6995d874/build.gradle.kts#L17-L17
s
Yeah that looks right
j
But I also found this: https://github.com/lgtout/arrow/blob/bacd9042f5d7c9bbba2dc8244ddd277f6995d874/settings.gradle.kts#L17-L17 I'm gonna try adding the snapshots repo there too. I don't know Gradle well, so I'm just kinda firing in the dark. Maybe I'll hit something 😂
No joy. Even more errors.
s
No something is missing
j
Ah, okay. So then, not a problem with the way Arrow is configured, right?
j
Doesn't return a 404. I'll update Arrow to try that snapshot. Thank you!
With snapshot
5.6.0.1129-SNAPSHOT
the build reports missing io.kotestkotest framework engine tvossimulatorarm645.6.0.1129-SNAPSHOT io.kotestkotest assertions core tvossimulatorarm645.6.0.1129-SNAPSHOT io.kotestkotest property tvossimulatorarm645.6.0.1129-SNAPSHOT
s
I'm afk atm but will try to figure it out later.
We could release 5.6 tomorrow too
j
Yeah, releasing 5.6 tomorrow, or sometime this week, would be great. Re the issues with the snapshots - no rush. That can wait till after the weekend, too. Thank you so much!
e
Snapshots dont include all targets for some reason. compare regular publish with snapshot publish
j
You're right!
tvossimulatorarm64
is missing from snapshot publish.
And that's the one that keeps breaking my build.
e
I can try adding them.. if it works we'll get a snapshot you can actually use.. and if it doesn't we can just revert it.
j
🕺
Yes please.
j
Awesome! So that will trigger a build, right? And I just need to wait till the next snapshot appears on sonatype?
e
yes 🙂
j
Thank you!
@Emil Kantis Do builds + publish get triggered when there's a commit to master? Or on a fixed schedule? Or neither?
e
Commit to master
For snapshots
j
So how come I'm not seeing a new snapshot on sonatype, after your commit?
The repo Sam linked to has been replaced with s01 as far as I know.. I'm guessing 1129 is the last snapshot that will exist there 🙂
j
Aah. Okay. Maybe that's why the old repos timestamps all seem wrong.
@Emil Kantis How come the
-js
s aren't being updated on s01.oss.sonatype.org? See how the dates at that link are older than the others. This is causing my build to fail with
5.6.0.1189-SNAPSHOT
.
e
On mobile. But it looks like master build failed
j
Ah, ok. Thanks. Is it possible for me to determine which commit kicked off a specific build that created a snapshot?
e
The snapshot suffix is the same number as the build that creates it
Shit. Mobile. Let me know if you got it otherwise I can try again when I’m back
j
The snapshot suffix is the same number as the build that creates it
Ah, excellent! Thank you!
I didn't need
1189
, after all.
1188
snapshot build succeeded, and has what I need, so used that instead. All good. Thanks again!