Repository navigation
Configure Travis to automatically push new tags to Maven #51
Description
Activity
- added this to the milestone
on May 11, 2015 - modified the milestones: ,
on Jun 1, 2015 @jgeewax , I don't think this belongs in this milestone.
Maven pushes could be done manually until this issue is resolved.
I think for the this milestone we just want to make sure we have a push that corresponds to all changes associated with this milestone.What I'm worried about is too much reliance on manual pushes -- if we need to get something out quickly, it would be great to have "all our ducks in a row" with regard to process so a tag gets pushed to maven.
If having Travis handle publishing was an enormous undertaking (which I suspect it's not, but let's say it is) then I could see us pushing this back. Otherwise, I would really prefer to have this (and the other process-focused things) ready before announcing publicly.
Travis is now configured to push a SNAPSHOT to maven every successful build.
Non snapshot builds are still done manually and should include the following:
- Update pom files to reflect the build number
- manual
maven site deploy - Update README.md with latest build number
Cool - thanks @aozarov
I'm going to close this out for now, and open a separate issue focused on the non-snapshot builds, including a site update.
@stephenplusplus : Let me know if you notice anything off about what we're doing here?
- added a commit that references this issue
on Jun 21, 2022 - added a commit that references this issue
on Jun 29, 2022 5 remaining items
- added 2 commits that reference this issue
on Sep 15, 2022 - added a commit that references this issue
on Jan 6, 2026 - added a commit that references this issue
on Feb 24, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Jul 13, 2026
Logic here is that we wouldn't want Maven lagging behind the GH repository.
I don't know if it's standard to have a nightly (or master) type build available on Maven (other libraries like gcloud-node don't do that), but at the very least all git tagged versions should be automatically pushed to Maven...
/cc @jboynes