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

Question: Release & hotfix branches #144

Open
3 of 6 tasks
cubasuarez opened this issue Nov 9, 2020 · 1 comment
Open
3 of 6 tasks

Question: Release & hotfix branches #144

cubasuarez opened this issue Nov 9, 2020 · 1 comment

Comments

@cubasuarez
Copy link

Before submitting an issue I have first:

  • searched for similar already existing issue
  • read the documentation and wiki

(if you have performed all the above, remove the paragraph and continue describing the issue with template below)

Issue

We know that your time is precious, we are thankful that you take time to report us an issue, to make it easier for you please use the following prefilled paragraphs

version: 1.5.1
usage context:

  • maven command line: 3.6.3
  • eclipse: replace with version
  • netbeans: replace with version
  • Intellij IDEA: replace with version

Problem description:
Configuration:

<configuration xmlns="http://jgitver.github.io/maven/configuration/1.1.0"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xsi:schemaLocation="http://jgitver.github.io/maven/configuration/1.1.0 https://jgitver.github.io/maven/configuration/jgitver-configuration-v1_1_0.xsd">
    <strategy>MAVEN</strategy>
    <useDirty>true</useDirty>
    <useGitCommitId>true</useGitCommitId>
</configuration>

How do I change my configuration so that artefacts in release & hotfix branches (for example denounced by release/x.y.z and hotfix/x.y.z+n are built without -SNAPSHOT and branch in artefact name?

Background: Manual/external testing after artefact creation and need to promote an immutable artefact to production through test-environments. - e.g I don't have the luxury to test in release branch and then (ff) merge to master and then rebuild the artefact.

Or am I missing something?

@fjakop
Copy link

fjakop commented Dec 3, 2020

I have the same issue, tried setting

<nonQualifierBranches>master,releases/*</nonQualifierBranches>
<nonQualifierBranches>master,releases/</nonQualifierBranches>

does not work, there's always a qualifier when I try to build an annotated tag un a branch starting with release/, e.g. release/1.4

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

No branches or pull requests

2 participants