Skip to content

Release for Dotty 3.0.0-M2 #144

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

Closed
Sciss opened this issue Dec 4, 2020 · 8 comments
Closed

Release for Dotty 3.0.0-M2 #144

Sciss opened this issue Dec 4, 2020 · 8 comments

Comments

@Sciss
Copy link
Contributor

Sciss commented Dec 4, 2020

So I did this and it made Travis publish for all Scala versions - https://travis-ci.com/github/scala/scala-swing/jobs/454325285 - , not just 3.0.0-M2. Should we rectify the scripts, or can you, @SethTisue , just delete the duplicate artifacts and release what's already on Sonatype?

@Sciss
Copy link
Contributor Author

Sciss commented Dec 4, 2020

There used to be this

# For tags that define a Scala version, we pick the jobs of one Scala version (2.13.x) to do the releases
- but that only worked for new 2.13.x versions.

@Sciss
Copy link
Contributor Author

Sciss commented Dec 4, 2020

My attempt to fix the script: #145

@Sciss
Copy link
Contributor Author

Sciss commented Dec 4, 2020

I can't really test this, because travis-ci.org - non-paid service - has moved to throttle-ware, so it will take a day to build my fork. If you drop the current contents at sonatype, I will just merge this and keep fingers crossed.

@Sciss
Copy link
Contributor Author

Sciss commented Dec 5, 2020

I think it works as expected. "Normal build", running each matrix cell with publish-local:

https://travis-ci.org/github/Sciss/scala-swing/builds/747665806

Tagged build, exiting all matrix cells except 2.13.x on JDK 8 with 'set every scala version':

https://travis-ci.org/github/Sciss/scala-swing/builds/747667211

Here is the one that tries to publish - it just publishes internally to Travis, but that's probably just the difference to your Travis set-up, credentials etc.:

https://travis-ci.org/github/Sciss/scala-swing/jobs/747667216

@SethTisue
Copy link
Member

can you, @SethTisue , just delete the duplicate artifacts and release what's already on Sonatype?

done, a few minutes ago. (leaving the ticket open since the artifacts haven't actually reached Maven Central yet)

as for how to handle this going forward, see my remarks on #145

@SethTisue
Copy link
Member

I can't really test this, because travis-ci.org - non-paid service - has moved to throttle-ware, so it will take a day to build my fork

(as we discussed on Gitter, you can flip the switch to move your fork to travis-ci.com... though then your new problem will be running out of minutes)

@Sciss
Copy link
Contributor Author

Sciss commented Dec 5, 2020

Ok - new artifacts should be ready to be released - https://travis-ci.com/github/scala/scala-swing/builds/206816837

@SethTisue
Copy link
Member

SethTisue commented Dec 5, 2020

I already released the staged artifacts from yesterday, and they are on Maven Central: https://repo1.maven.org/maven2/org/scala-lang/modules/scala-swing_3.0.0-M2/3.0.0/

Your attempt today went fine, I see a new staging repo (and I dropped it). So now you know the drill for next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants