gradle-semantic-build-versioning | Gradle plugin to generate version | Plugin library

 by   vivin Groovy Version: 3.0.0 License: MIT

kandi X-RAY | gradle-semantic-build-versioning Summary

kandi X-RAY | gradle-semantic-build-versioning Summary

gradle-semantic-build-versioning is a Groovy library typically used in Plugin applications. gradle-semantic-build-versioning has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This is a Gradle plugin that provides support for semantic versioning of builds. It is quite easy to use and extremely configurable. The plugin allows you to bump the major, minor, patch or pre-release version based on the latest version, which is identified from a git tag. It also allows you to bump pre-release versions based on a scheme that you define. The version can be bumped by using version-component-specific project properties or can be bumped automatically based on the contents of a commit message. If no manual bumping is done via commit message or project property, the plugin will increment the version-component with the lowest precedence; this is usually the patch version, but can be the pre-release version if the latest version is a pre-release one. The plugin does its best to ensure that you do not accidentally violate semver rules while generating your versions; in cases where this might happen the plugin forces you to be explicit about violating these rules. As this is a settings plugin, it is applied to settings.gradle and so version calculation is performed right at the start of the build, before any projects are configured. This means that the project version is immediately available (almost as if it was set explicitly -- which it effectively is), and will never change during the build (barring some other, external task that attempts to modify the version during the build). While the build is running, tagging or changing the project properties will not influence the version that was calculated at the start of the build. Note: The gradle documentation specifies that the version property is an Object instance. So to be absolutely safe, and especially if you might change versioning-plugins later, you should use the toString() method on project.version. However, this plugin does set the value of project.version to a String instance and hence you can treat it as such. While the version property is a string, it does expose some additional properties. These are snapshot, major, minor, patch and preRelease. snapshot is a boolean and can be used for release vs. snapshot project-configuration, instead of having to do an endsWith() check. major, minor, patch and preRelease bear the single version components for further usage in the build process. major, minor and patch are of type int and are always set, preRelease is a String and can be null if the current version is not a pre-release version.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              gradle-semantic-build-versioning has a low active ecosystem.
              It has 73 star(s) with 26 fork(s). There are 8 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 14 open issues and 51 have been closed. On average issues are closed in 52 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of gradle-semantic-build-versioning is 3.0.0

            kandi-Quality Quality

              gradle-semantic-build-versioning has 0 bugs and 0 code smells.

            kandi-Security Security

              gradle-semantic-build-versioning has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              gradle-semantic-build-versioning code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              gradle-semantic-build-versioning is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              gradle-semantic-build-versioning releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.
              It has 78 lines of code, 3 functions and 2 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gradle-semantic-build-versioning
            Get all kandi verified functions for this library.

            gradle-semantic-build-versioning Key Features

            No Key Features are available at this moment for gradle-semantic-build-versioning.

            gradle-semantic-build-versioning Examples and Code Snippets

            No Code Snippets are available at this moment for gradle-semantic-build-versioning.

            Community Discussions

            QUESTION

            Gradle settings groovy file to kts file
            Asked 2018-Oct-02 at 20:57

            I have this as settings.gradle

            ...

            ANSWER

            Answered 2018-Sep-29 at 16:37

            QUESTION

            com.jfrog.artifactory gradle plugin 401 Unauthorised
            Asked 2018-Jul-10 at 16:24

            I have previously successfully set up bintray and artifactory accounts to publish snapshot versions to the OSS JFrog Artifactory repository, but after setting up a GitHub/Bintray/Artifactory organisation under the same user, I am unable to publish snapshots.

            When attempting to run

            ...

            ANSWER

            Answered 2018-Jun-30 at 16:52

            This turned out to be a simple solution. When moving over to use the organisation from the personal account on CircleCI, the environment variables were lost.

            Source https://stackoverflow.com/questions/51107006

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install gradle-semantic-build-versioning

            You can download it from GitHub.

            Support

            Please make sure you add tests when fixing bugs or adding new features.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/vivin/gradle-semantic-build-versioning.git

          • CLI

            gh repo clone vivin/gradle-semantic-build-versioning

          • sshUrl

            git@github.com:vivin/gradle-semantic-build-versioning.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link