Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Publish snapshots to Sonatype #71
First step is, you will need to encrypt your credentials via Travis, and put them into a Travis file:
See those SECURE entries for instance.
Your credentials need to match a settings.xml file that is used by the sonatype deployment task:
So when you encrypt, you need to provide SONATYPE_USER=username and SONATYPE_PWD=password to the Travis command.
You'll need to have Travis installed locally of course. See instructions at the top of the yml file.
Then you instruct Travis to call a shell script to push changes to sonatype:
That, and sonatype auto publishes to central. This allows me to auto switch a GA to a SNAPSHOT without any further changes in the poms, which is much easier to teach. If a bug is fixed and the snapshot is made available automatically, I can just go back to my pom, switch the version and rebuild the same exact way without any additional changes.
The "releases" bit arguably can be removed.
So, I apologize for being this demanding but this still is not solved.
If I let travis pull the repository above and run through the tests, it fails miserable.
So, this sort of indicates to me that snapshots are not auto-published, right? State of the codebase is not the same of the repo. I don't know if you can call this a snapshot.
If you are manually publishing artifacts every once in a while, you're really releasing milestones. Which doesn't solve the problem stated in the original issue description.
Are there processes in place that publish snapshots to the github repo automatically?