search

git-commit-id / git-commit-id-maven-plugin

Maven plugin which includes build-time git repository information into an POJO / *.properties). Make your apps tell you which version exactly they were built from! Priceless in large distributed deployments... :-)
http://www.kto.so
GNU Lesser General Public License v3.0
1.61k stars 298 forks source link

Snapshot repository doesn't include the newer versions #344

Closed games647 closed 5 years ago

games647 commented 6 years ago

The snapshot repository only contains versions for 2.0.5, but I want to use a feature from 2.2.4. Could you update the builds on that repository or is there another way to use the unreleased 2.2.4 version (except building it manually)?

TheSnoozer commented 6 years ago

Even though its on the readme it doesn't seem to be used. It seems that it was exactly used for one snapshot deploy back in 2012 (https://oss.sonatype.org/content/repositories/snapshots/pl/project13/maven/git-commit-id-plugin).

I get your point why you might want to have this as convenient way...I'll see if there is anything automatic that could be used to always deploy the latest and greatest.

If there is no such automatic process I feel it would be too tedious to always deploy the latest snapshot....or just when being asked doesn't sound right as well.....debating this with myself since it seems this might even be an option too since the last ask was back in 2012...so one deploy every 5 years sounds reasonable for doing it manually. However manually would then not always deliver the latest and greatest. Honestly not sure if something automated would be way over the top for the ask here, but it feels like this would be the most accurate and the right solution for this.

Edit: Quick research on automated process:

TODO: verify that PRs do not deploy a snapshot and get the travis publication working.

TheSnoozer commented 6 years ago

Why did you close this? It is not fixed properly (yet)....

TheSnoozer commented 5 years ago

The snapshot versions are now finally being deployed by travis (https://travis-ci.org/git-commit-id/maven-git-commit-id-plugin/jobs/473237719). I quite frankly don't know why the initial commit I did with the automatic deployment failed, but in general it's pretty much the still the same concept....I guess I needed to hit the regenerate credentials thing within Nexus to get this working. Not sure why.

Nevertheless, the snapshot versions are now permanently available via:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
        <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Travis will deploy from the master branch after all tests passed.

Additional inspiring configurations: https://alexn.org/blog/2017/08/16/automatic-releases-sbt-travis.html https://coderwall.com/p/9b_lfq/deploying-maven-artifacts-from-travis https://github.com/kumuluz/kumuluzee/blob/master/.travis.yml https://github.com/chaijs/type-detect/blob/master/.travis.yml