continuous integration - Jenkins Artifactory Release Plugin: A way to release without specifying a new dev version? -


background

I work for company, we develop trunk and store release in branches Generally, after we release some, we set the next development version as a increment in the small version with the Kinlick "-SNAPSHOT" suffix. So far it is very good.

The problem

Our problem occurs when we use "Patch Edition" - Z in XYZ for a release module According to our rules, releasing a patch version is a release version of the work. The Jenkins artificial illumination release plugin (we use for the continuation of artworks) requires "the next development version" but for us, it is often not of any meaning; There is no god version for artifacts released - it is continuing, we want to patch it. It is worth noting that our patch version, like our other releases, is also deposited in new branches. The picture below helps clarify the model that I have described so far.

  --- 0.1.0-SNAPSHOT --- 1.1.0-SNAPSHOT (development version; trunk) \ \ 1.0.0 (release version) \ \ --- 1.0.1 ( This screenshot of the release plugin fields can also be useful:  

It is enough to say that a new div branch specifies the results Trying not to make errors in error but am I putting an existing branch version, a new branch version or leave it blank I am always getting the same error message:

error log
  19:40: 48.188 [Issue] Pushing branch 'release-branch-dummy-1.7 0 'to' git@bitbucket.org: inc / dummy.git '19: 40: 48.694 Error: [Release] Building failed to complete 19:40: 48.695 java.io.IOException: failed to push: command "git Push git@bitbucket.org: inc / dummy.git refs / heads / release-branch-dummy-1.7.0 "Back Status Code 1: 19: 40: 48.695 Stdout: 19: 40: 48.695 Stadder: To git @bitbucket. org: inc / dummy.git 19: 40: 48.695! [Rejected] Release-Branch-Dummy-1.7.0 - & gt; Release-Branch-Dummy-1.7.0 (Non-Fast-Forward) 19: 40: 48.695 Error: Failed to push some referee on 'git@bitbucket.org: inc / dummy.git': 19: 40: 48.695 Hint: Update has been rejected because the tip of your current branch is behind 19: 40: 48.695: merge its remote equivalent remote change (eg 'Git pull') 19: 40: 48.695 Indication: by pushing again First 19: 40: 48.695 Indicators: See the note about 'fast-forward' in 'git push --help' for details.   

Appreciate a better way to assist our problem or handle this process.

Edit: Update

Slavic signals helped me to realize that the problem occurs when I try to designate a new development version of a release branch. The plugin tries to create a new branch, but, in the case given above, the branch already exists. In other cases, however, for the reasons listed in my post, I do not want a new development version. So it is a losing necklace

Modify the source code of the Artifactory release plugin and make it your own requirements To reconstruct with, your only option is to write a custom branch in the scripting language.

The problem with plugins is that they are generally restrictive for a certain flow.

BTW FWIW, "Patch" in our setup is committed to the release branch (no special "patch" branch is created) tags that keep track of the released volumes and branches.

Comments

Popular posts from this blog

Verilog Error: output or inout port "Q" must be connected to a structural net expression -

jasper reports - How to center align barcode using jasperreports and barcode4j -

c# - ASP.NET MVC - Attaching an entity of type 'MODELNAME' failed because another entity of the same type already has the same primary key value -