• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • cvs-plugin
    • None
    • Linux redhat 2.6.18-164.15.1.el5
      Tomcat 7.0.2
      Hudson 1.381
      CVS plugin 1.2

      It is not possible to tag a build any more. In the past (issue JENKINS-4374) it was not possible to "Tag all upstream builds at once", but it was possible to tag one build per time.

      Whenever we try to tag a build it shows us a message saying "Marcação está em progresso:" (meaning Tagging is in progress) and a button saying "Limpar erro para tentar novamente" (meaning Clear errors and retry). Moreover we get no log errors neither tag in the source code.

      According to mindless, he is also having a similar issue in SVN. Mindless also said the following in an issue comment (JENKINS-4374).
      "From what I can tell in the src, the screen with "Tagging is in progress" should show output from the cvs tag command and several other status messages about what it's doing.. the "Clear error to retry" button is only there when the operation is done.. so the fact you see this right away and with no log output is quite odd."

      I set the log level to ALL to try to understand the problem. The log is attached.
      What is important to say is that hudson is trying to use the user 'anonymous' (and 'SYSTEM' in some cases), but I'm logged in with the 'admin' user.

      If it is not possible to provide a fix in a mean time, please, provide a work around. Since, right now, it is not possible to tag a build at all.

          [JENKINS-8128] Tagging a build is not working

          fernandor created issue -
          Alan Harder made changes -
          Component/s New: cvs [ 15486 ]
          Component/s Original: cvs-tag [ 15534 ]
          Assignee Original: Alan Harder [ mindless ]
          Description Original:
          It is not possible to tag a build any more. In the past (issue JENKINS-4374) it was not possible to "Tag all upstream builds at once", but it was possible to tag one build per time.

          Whenever we try to tag a build it shows us a message saying "Marcação está em progresso:" (meaning Tagging is in progress) and a button saying "Limpar erro para tentar novamente" (meaning Clear errors and retry). Moreover we get no log errors neither tag in the source code.

          According to mindless, he is also having a similar issue in SVN. Mindless also said the following in an issue comment (JENKINS-4374).
          "From what I can tell in the src, the screen with "Tagging is in progress" should show output from the cvs tag command and several other status messages about what it's doing.. the "Clear error to retry" button is only there when the operation is done.. so the fact you see this right away and with no log output is quite odd."

          I set the log level to ALL to try to understand the problem. The log is attached.
          What is important to say is that hudson is trying to use the user 'anonymous' (and 'SYSTEM' in some cases), but I'm logged in with the 'admin' user.

          If it is not possible to provide a fix in a mean time, please, provide a work around. Since, right now, it is not possible to tag a build at all.
          New: It is not possible to tag a build any more. In the past (issue JENKINS-4374) it was not possible to "Tag all upstream builds at once", but it was possible to tag one build per time.

          Whenever we try to tag a build it shows us a message saying "Marcação está em progresso:" (meaning Tagging is in progress) and a button saying "Limpar erro para tentar novamente" (meaning Clear errors and retry). Moreover we get no log errors neither tag in the source code.

          According to mindless, he is also having a similar issue in SVN. Mindless also said the following in an issue comment (JENKINS-4374).
          "From what I can tell in the src, the screen with "Tagging is in progress" should show output from the cvs tag command and several other status messages about what it's doing.. the "Clear error to retry" button is only there when the operation is done.. so the fact you see this right away and with no log output is quite odd."

          I set the log level to ALL to try to understand the problem. The log is attached.
          What is important to say is that hudson is trying to use the user 'anonymous' (and 'SYSTEM' in some cases), but I'm logged in with the 'admin' user.

          If it is not possible to provide a fix in a mean time, please, provide a work around. Since, right now, it is not possible to tag a build at all.
          Michael Clarke made changes -
          Assignee New: Michael Clarke [ mc1arke ]
          Michael Clarke made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Michael Clarke made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 138231 ] New: JNJira + In-Review [ 187906 ]

            mc1arke Michael Clarke
            fernandor fernandor
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: