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

Plugin does not start build if there is only one change set

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • tfs-plugin
    • None
    • Hudson ver. 1.363, both released and current tfs plugin
      tfs 2008 server
      MS TEE Command line client 10.0.0

      After checking in changes, TFS log in Hudson shows them consistently (see below). However, no automatic builds are being triggered.

      The problem is the newly released TEE Command line client – it does not output the

      "-------------------------------"

      seperation lines that the parsing algorithm depends upon. We have reverted to using the Microsoft Team System Explorer command line utility and everything seems to be working fine now.

      However, wouldn't it still be possible to change the parser to starting a block with "Changeset:" instead of ending it with "-----------------"?

      If necessary, I could provide a diff...

       
      Started on 28.06.2010 18:18:38
      [workspace] $ C:\javabuildtools\TEE-CLC-10.0.0\tf.cmd history $/Services/Server/DEV/SP/MavenDefs -noprompt -version:D2010-06-28T12:52:47Z~D2010-06-28T16:18:38Z -recursive -format:detailed -server:http://s-tfs:8080/ ********
      
      Changeset: 364235
      User: GRP\ObendorfH
      Date: 28.06.2010 17:25:40
      
      Comment:
        Versionierung für EJB EAR
      
      Items:
        edit $/Services/Server/DEV/SP/MavenDefs/pom.xml
      
      Check-in Notes:
        Code Reviewer: 
      
        Performance Reviewer: 
        Security Reviewer: 
      
      Done. Took 8,6 Sekunden
      No changes
      

          [JENKINS-6870] Plugin does not start build if there is only one change set

          hartmut created issue -
          hartmut made changes -
          Attachment New: screenshot.5.png [ 19541 ]
          hartmut made changes -
          Description Original: After checking in changes, TFS log in Hudson shows them consistently (see below). However, no automatic builds are being triggered. Perhaps this bug is related to bug#4184 ?

          --

          Started on 28.06.2010 18:18:38
          [workspace] $ C:\javabuildtools\TEE-CLC-10.0.0\tf.cmd history $/Services/Server/DEV/SP/MavenDefs -noprompt -version:D2010-06-28T12:52:47Z~D2010-06-28T16:18:38Z -recursive -format:detailed -server:http://s-tfs:8080/ ********

          Changeset: 364235
          User: GRP\ObendorfH
          Date: 28.06.2010 17:25:40

          Comment:
            Versionierung für EJB EAR

          Items:
            edit $/Services/Server/DEV/SP/MavenDefs/pom.xml

          Check-in Notes:
            Code Reviewer:

            Performance Reviewer:
            Security Reviewer:

          Done. Took 8,6 Sekunden
          No changes

          New: After checking in changes, TFS log in Hudson shows them consistently (see below). However, no automatic builds are being triggered. Perhaps this bug is related to bug#4184 ?

          {noformat}
          Started on 28.06.2010 18:18:38
          [workspace] $ C:\javabuildtools\TEE-CLC-10.0.0\tf.cmd history $/Services/Server/DEV/SP/MavenDefs -noprompt -version:D2010-06-28T12:52:47Z~D2010-06-28T16:18:38Z -recursive -format:detailed -server:http://s-tfs:8080/ ********

          Changeset: 364235
          User: GRP\ObendorfH
          Date: 28.06.2010 17:25:40

          Comment:
            Versionierung für EJB EAR

          Items:
            edit $/Services/Server/DEV/SP/MavenDefs/pom.xml

          Check-in Notes:
            Code Reviewer:

            Performance Reviewer:
            Security Reviewer:

          Done. Took 8,6 Sekunden
          No changes
          {noformat}
          hartmut made changes -
          Description Original: After checking in changes, TFS log in Hudson shows them consistently (see below). However, no automatic builds are being triggered. Perhaps this bug is related to bug#4184 ?

          {noformat}
          Started on 28.06.2010 18:18:38
          [workspace] $ C:\javabuildtools\TEE-CLC-10.0.0\tf.cmd history $/Services/Server/DEV/SP/MavenDefs -noprompt -version:D2010-06-28T12:52:47Z~D2010-06-28T16:18:38Z -recursive -format:detailed -server:http://s-tfs:8080/ ********

          Changeset: 364235
          User: GRP\ObendorfH
          Date: 28.06.2010 17:25:40

          Comment:
            Versionierung für EJB EAR

          Items:
            edit $/Services/Server/DEV/SP/MavenDefs/pom.xml

          Check-in Notes:
            Code Reviewer:

            Performance Reviewer:
            Security Reviewer:

          Done. Took 8,6 Sekunden
          No changes
          {noformat}
          New: After checking in changes, TFS log in Hudson shows them consistently (see below). However, no automatic builds are being triggered.

          The problem is the newly released TEE Command line client -- it does not output the

          "-------------------------------"

          seperation lines that the parsing algorithm depends upon. We have reverted to using the Microsoft Team System Explorer command line utility and everything seems to be working fine now.

          However, wouldn't it still be possible to change the parser to _starting_ a block with "Changeset:" instead of _ending_ it with "-----------------"?

          If necessary, I could provide a diff...

          {noformat}
          Started on 28.06.2010 18:18:38
          [workspace] $ C:\javabuildtools\TEE-CLC-10.0.0\tf.cmd history $/Services/Server/DEV/SP/MavenDefs -noprompt -version:D2010-06-28T12:52:47Z~D2010-06-28T16:18:38Z -recursive -format:detailed -server:http://s-tfs:8080/ ********

          Changeset: 364235
          User: GRP\ObendorfH
          Date: 28.06.2010 17:25:40

          Comment:
            Versionierung für EJB EAR

          Items:
            edit $/Services/Server/DEV/SP/MavenDefs/pom.xml

          Check-in Notes:
            Code Reviewer:

            Performance Reviewer:
            Security Reviewer:

          Done. Took 8,6 Sekunden
          No changes
          {noformat}
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          hartmut made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          hartmut made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          redsolo made changes -
          Summary Original: http://jenkins-ci.org/ New: Plugin does not start build if there is only one change set
          redsolo made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          redsolo made changes -
          Attachment New: mylyn-context.zip [ 19759 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 136965 ] New: JNJira + In-Review [ 187331 ]

            redsolo redsolo
            hartmut hartmut
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: