Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-4128

When pushing sources and dsc tarballs, use a unique CR folder each time

    XMLWordPrintable

Details

    • False
    • None
    • False

    Description

      Spoke with Christopher today about the way the mw stage command works, and it looks like to allow RC respins, we have to have a UNIQUE folder each time

      So instead of a stage-mw-release devspaces-3.5.0 command using a devspaces-3.5.0 folder, we need either sequential CR1, CR2, folders like devspaces-3.5.0.CR1 etc. or else datestamped suffixes like devspaces-3.5.0.2023-03-20, which are easier to generate as that's what we use for communicating with QE.

      Jobs impacted:

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. CRW-4049 Create jenkins build for vsix plugins, publishing to download.devel

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          mentioned on

          GitLab Merge request - chore: CRW-4128 use unique datestamped folders when staging on spmm-util

          Activity

            People

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: