search

jfrog / teamcity-artifactory-plugin

TeamCity plugin that enables traceable build artifacts with Artifactory
https://www.jfrog.com/confluence/display/JFROG/TeamCity+Artifactory+Plug-in
Apache License 2.0
43 stars 48 forks source link

Doesn't update master branch in git #13

Open engelkek opened 9 years ago

engelkek commented 9 years ago

The gitflow workflow states that releases should be merged into master. This does not happen when making a release through this plugin. I have to merge the release branch into master manually.

eyalbe4 commented 9 years ago

@engelkek , are you referring to the Artifactory Release Staging flow as described in the following link? https://www.jfrog.com/confluence/display/RTF/TeamCity+Artifactory+Plugin+-+Release+Management If so, can please clarify what you mean by "The gitflow workflow states..."?

engelkek commented 9 years ago

Sorry, I wrote my comment in a hurry and left out too much information.

I am following "gitflow" (http://nvie.com/posts/a-successful-git-branching-model/) which, in short, means all development happens in the develop branch and master is kept on the latest release. I was hoping that I could configure the TeamCity plugin to do most of the work for me. What it already does very nicely is creating a release branch and updating Maven version numbers. If I had an option to say "merge release branch into ${configurable branch}" I wouldn't have to do this manually. There is a Maven plugin for this (https://bitbucket.org/atlassian/jgit-flow/wiki/Home) but I would rather have TeamCity do the work if possible.

eyalbe4 commented 9 years ago

Thanks @engelkek . You are correct. The Artifactory Release Staging currently does not support that flow. We might consider adding this functionality in the future. You may open a feature request this in JFrog's Jira: https://www.jfrog.com/jira