Uploaded image for project: 'Nuxeo Studio'
  1. Nuxeo Studio
  2. NXS-3924

Same "next version" in multiple branches prevents from downloading the artifact

    Details

      Description

      • You have two branches, master and another one.
      • both of them have the same "next version"
      • you checkout master
      • you change to intermediate mode (it works in simple mode)
      • you cannot get the artifact
      • server logs are scarce:
        2017-03-30 16:36:32,498 WARN  [catalina-exec-988] [com.nuxeo.studio.servlet.StudioServlet] The version "0.0.1--wip--targuillere_72984b--master-SNAPSHOT" was not found for the project "coach-2017-04-nuxeo"
        

        Workaround: change the "next version" in master.

      Update: not sure, maybe the real issue is the following:

      • you create a project. It starts with a "next version", and generate everything it needs for that.
      • you use the import for a branch, it updates the "next version" in the corresponding `application.xml` file, but this is done outside of the normal workflow, which would update metadata/artifacts for the new version.
      • Thus when you update the "next version" through the regular way, you force an update, and artifact download recovers.
      • application.xml change in the 'import' commit:
        <application>
        - <version>0.0.1</version>
        + <version>0.0.1-TEMP_FOR_TEMPLATE</version>
        

      TODO
      Check if this issue happens

      • only after project copy (only happens to Nuxeo insiders and we have a workaround, lower priority)
      • in other cases too (higher priority)

      => Create the corresponding tickets

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.