Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use gradle-git for version and tagging #8

Merged
merged 1 commit into from
Dec 2, 2014

Conversation

mikezx6r
Copy link
Contributor

@mikezx6r mikezx6r commented Dec 2, 2014

This leverages gradle-git plugin and its release-base plugin. Removes git command-line dependency from build as well as tasks for tagging and pushing changes.

Current config will build a SNAPSHOT if nothing is passed for release.stage.

As per notes below, -Prelease.stage= controls version. Based on the stage, it will increment the build number and possibly add rc.#, mileston.# to end.

The release tag does the tagging and push of tag. Just passing the release.stage property will affect the version used to perform the gradle actions, so can preview version numbering before executing.

Build would be gradle bintrayUpload release -Prelease.stage=final

If you like this approach, I'll also add it to the other repos.

=== If local repository is dirty
-Always builds a SNAPSHOT version.
-Will complain that 'Stage {} is not one of [SNAPSHOT] allowed for strategy snapshot.'

=== If local repository is not dirty
    Set release type using property release.stage. Valid values are:
        -milestone
        -rc
        -final
    milestone creates a tag with the next version from tag + -milestone.#
    rc similar, but uses rc. Cannot create a milestone after an rc
    final creates a version with no endings

If want to use ssh authorization, must ensure ssh-agent contains correct key for repository being worked on.
If you experience issues, try ssh-add -D to clear identities and add the one identity for the repo in question.

The release tags the current commit, and pushes to the remote repository. It does not check if there's a new commit, so only use it if you really need to.

gradle bintrayUpload release -Prelease.stage={milestone|rc|final}

    === If local repository is dirty
        -Always builds a SNAPSHOT version.
        -Will complain that 'Stage {} is not one of [SNAPSHOT] allowed for strategy snapshot.'

    === If local repository is not dirty
        Set release type using property release.stage. Valid values are:
            -milestone
            -rc
            -final
        milestone creates a tag with the next version from tag + -milestone.#
        rc similar, but uses rc. Cannot create a milestone after an rc
        final creates a version with no endings

    If want to use ssh authorization, must ensure ssh-agent contains correct key for repository being worked on.
    If you experience issues, try ssh-add -D to clear identities and add the one identity for the repo in question.

    The release tags the current commit, and pushes to the remote repository. It does not check if there's a new commit, so only use it if you really need to.

    gradle bintrayUpload release -Prelease.stage={milestone|rc|final}
wakaleo added a commit that referenced this pull request Dec 2, 2014
Use gradle-git for version and tagging
@wakaleo wakaleo merged commit 499604d into serenity-bdd:master Dec 2, 2014
@mikezx6r mikezx6r deleted the grgit branch December 8, 2014 02:05
nbarrett pushed a commit to nbarrett/serenity-core that referenced this pull request Dec 19, 2017
…t_for_junit_webtests

Pull requst to add gradle script to junit-webtests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants