Best practices on publishing packages to Atmosphere using Continuous Integration such as Codeship or Travis

packages
1

Hi everyone,

I just want to know how you guys publish your meteor package after it has already passed the build from a continuous integration app like Codeship or Travis. I’ve tried mimicking @arunoda and @aldeed’s travis.yml and adding tinytest to my packages so it also tests itself in Travis, and show a passing build icon in my github repo… but I got stumped on how to “auto-magically” publish it to atmosphere for my future projects.

Do you guys just publish it from your local console or am I missing something?

Thanks :slight_smile:

2

Check out @splendido’s awesome autopublish.meteor.com.

2 Likes
3

cool! I might try this. Thanks :smile:

4

I publish from local console

1 Like
5

I know topic is old but maybe it will be handy for someone: