Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51753

SCM-TeamConcert: outgoing change sets are discarded if running build against those workspaces with accept latest changes before build flag

    XMLWordPrintable

Details

    Description

      if you run a job which does a scm checkout on RTC repository workspace (which has outgoing change sets) and the "accept latest change before building" is enabled (by default -> see Job configuration 10.6 on wiki page) this outgoing change is discarded from repository workspace and can only be get back by searching for this change set in the complete repository

      Attachments

        Activity

          wreggyl Jan Bottek added a comment -

          lvaikunt i think the second option "only accept change sets without discarding outgoing" is the mandatory one which is needed, the other one with a snapshot creation even for unchanged workspace is nice to have

          wreggyl Jan Bottek added a comment - lvaikunt i think the second option "only accept change sets without discarding outgoing" is the mandatory one which is needed, the other one with a snapshot creation even for unchanged workspace is nice to have

          >>even create snapshots without the accepting change set option -> maybe optional flag

          >>only accept changes and leave outgoing change sets as it is => or if this is not possible die without discarding the change sets

          wreggyl Do you need both or just one of them?

           

          lvaikunt Lakshmi Narasimhan Vaikuntam added a comment - >>even create snapshots without the accepting change set option -> maybe optional flag >>only accept changes and leave outgoing change sets as it is => or if this is not possible die without discarding the change sets wreggyl Do you need both or just one of them?  
          wreggyl Jan Bottek added a comment - - edited

          Hi, my repo->stream configuration i standard. My repo has incoming/outgoing flow target to the stream.

          Normally i do not want to accept changes on my workspace, because i want to build against my specific change sets and do not want to get changes, but I still need a snapshot of the workspace with my outgoing change sets - to be able to reproduce the build

          So what i normally expect is to get a snapshot of a build against a workspace -> i know snapshots are only taken if accepting changes is enabled. But what i never expect is discarding change sets if i accept changes.

           

          So my proposal is:

          • even create snapshots without the accepting change set option -> maybe optional flag
          • only accept changes and leave outgoing change sets as it is => or if this is not possible die without discarding the change sets
          wreggyl Jan Bottek added a comment - - edited Hi, my repo->stream configuration i standard. My repo has incoming/outgoing flow target to the stream. Normally i do not want to accept changes on my workspace, because i want to build against my specific change sets and do not want to get changes, but I still need a snapshot of the workspace with my outgoing change sets - to be able to reproduce the build So what i normally expect is to get a snapshot of a build against a workspace -> i know snapshots are only taken if accepting changes is enabled. But what i never expect is discarding change sets if i accept changes.   So my proposal is: even create snapshots without the accepting change set option -> maybe optional flag only accept changes and leave outgoing change sets as it is => or if this is not possible die without discarding the change sets

          "Accept changes" options keeps the repository workspace at the same state as the flow target(s). This could also involve discarding change sets if they are not present in the stream.

          Perhaps we could scope the components such that these change sets don't have to be discarded.

          Could you describe your repository workspace->stream configuration? Do all components of the repository workspace flow to the same stream?

           

          lvaikunt Lakshmi Narasimhan Vaikuntam added a comment - "Accept changes" options keeps the repository workspace at the same state as the flow target(s). This could also involve discarding change sets if they are not present in the stream. Perhaps we could scope the components such that these change sets don't have to be discarded. Could you describe your repository workspace->stream configuration? Do all components of the repository workspace flow to the same stream?  

          People

            Unassigned Unassigned
            wreggyl Jan Bottek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: