So the issue that led to this is that a contrib tool of mine couldn't find 12-SNAPSHOT master pom anyway unless it was built already and available locally or available in a central repo. And this is constantly failing on Travis as it doesn't have 12-SNSPSHOT locally. Previously the contrib tool was building ok because it was on a stable 11.4 master, which is in central.

I think adding the repo to the contrib tool is ok if the tools needs to depend on a snapshot. At least then snapshots can be pushed up without mucking up core projects that are building against 12-SNAPSHOT as well.

What can I do to help get snapshots pushed up? I want to turn my automated tests back on via Travis

Yeah, I think the only thing we could do about 's issue is to have a parent above master that just defined repositories, similar to what oss-parent (https://github.com/sonatype/oss-parents/blob/master/oss-parent/pom.xml) used to be. This would be released VERY infrequently and be extremely minimal. \

Back a few releases ago when oss-parent was deprecated I rolled it all into master, but maybe it made more sense to have it separate still?

Though that probably wouldn't help contrib projects or this problem right? The contrib projects couldn't parent off of sakai-parent . . . Maybe we could change the parent but just have master be imported? http://stackoverflow.com/a/39160571/3708872 . . . I don't know, maybe easier just to have a repositories section in the few contrib tools using this.

I just did this as well:
https://jira.sakaiproject.org/browse/SAK-32540

A bit of analysis there. Will close as duplicate.

Actually, don't we just want to add this repository to the deployment (https://maven.apache.org/pom.html#Repository) part. All contrib tools will need to add this repo to their pom otherwise they won't be able to find the master POM (org.sakaiproject:master:12-SNAPSHOT) so it doesn't help having this in our master POM. What we do want is the ability to deploy the SNAPSHOTs to this repository though.