Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-5077

Inconsistent naming of branches in asset management

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • jBPM 6.4.0.Final
    • None
    • NEW
    • NEW
    • Please see added comment.
    • Hide

      1. Sign in to business-central with kiemgmt role.
      2. In project administration create managed repo with automatically configured branches.
      3. In project authoring open repository structure, click configure.
      4. Hit ok.

      Expected result: Nothing happens.
      Actual result: Two new branches dev-1.0.0-SNAPSHOT and release-1.0.0-SNAPSHOT are created.

      Show
      1. Sign in to business-central with kiemgmt role. 2. In project administration create managed repo with automatically configured branches. 3. In project authoring open repository structure, click configure. 4. Hit ok. Expected result: Nothing happens. Actual result: Two new branches dev-1.0.0-SNAPSHOT and release-1.0.0-SNAPSHOT are created.

      When creating managed repo with automatically configured branches, branches with names (master, dev-1.0.0 and release-1.0.0) are created. However when the same repo is being configured and no changes are made in the configuration, two new branches dev-1.0.0-SNAPSHOT and release-1.0.0-SNAPSHOT are created.

            wmedvede@redhat.com Walter Medvedeo
            jsoltes Juraj Soltes (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: