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

!build command does not work for all builds

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      openfire 3.7.1
      jenkins 1.491
      im plugin 1.23
    • Similar Issues:

      Description

      the !build command only works for some builds, for others it says

      syntax is: 'build <job> [now|<delay>[s|m|h]] [<parameterkey>=<value>]*'

      I use exactly the name from jenkins view, and there are no blanks or special chars. The name is correct and i have all necesarry right. Btw. Please extend decription which rights (in job and global) are needed to execute !build commands from im.

        Attachments

          Activity

          Hide
          kutzi kutzi added a comment -

          Can you spot any pattern which jobs can be started and which not? Is there any relevant log info in Jenkins' log file?

          Show
          kutzi kutzi added a comment - Can you spot any pattern which jobs can be started and which not? Is there any relevant log info in Jenkins' log file?
          Hide
          cforce cforce added a comment -

          Ok, i found the cause.
          The user which is used to log in to im had'nt enough rights.

          I have found attached rights image possible to set. Can u please document which rights maps which xmpp chat (!help exluded) command, so that everybody knows that this user has to have thats right to be able to execute such commands.

          Tx.

          Show
          cforce cforce added a comment - Ok, i found the cause. The user which is used to log in to im had'nt enough rights. I have found attached rights image possible to set. Can u please document which rights maps which xmpp chat (!help exluded) command, so that everybody knows that this user has to have thats right to be able to execute such commands. Tx.
          Hide
          kutzi kutzi added a comment -

          I cannot see which rights you checked on the attached screenshot. Can you please attach a one showing that?

          Show
          kutzi kutzi added a comment - I cannot see which rights you checked on the attached screenshot. Can you please attach a one showing that?
          Hide
          cforce cforce added a comment - - edited

          Why should you, there is nothing to see then which right are available for jenkins. As you see above myquestion was how it is implemented. Which rights map which chat command, so that the command ca be executed! If you did the code you shall attach a description how this 't works. It wasn't my intension to reverse enginere and document the plugins manual by try and error.

          However i gave all rights (without admin), and then of course it works. I won't think that this is best practice.

          Again please write a manual how this chat commands map to jenkins user rights.
          This is a request for better documentation.

          Show
          cforce cforce added a comment - - edited Why should you, there is nothing to see then which right are available for jenkins. As you see above myquestion was how it is implemented. Which rights map which chat command, so that the command ca be executed! If you did the code you shall attach a description how this 't works. It wasn't my intension to reverse enginere and document the plugins manual by try and error. However i gave all rights (without admin), and then of course it works. I won't think that this is best practice. Again please write a manual how this chat commands map to jenkins user rights. This is a request for better documentation.
          Hide
          kutzi kutzi added a comment - - edited

          Okay, so I misunderstood your previous comment.
          AFAIR you need Job#Build rights to trigger a build (and I found this pretty obvious). However, I admit that documentation is missing in big parts.

          BTW: this is an open source project, so you're invited to amend the documentation in the Wiki if you find something missing.

          Show
          kutzi kutzi added a comment - - edited Okay, so I misunderstood your previous comment. AFAIR you need Job#Build rights to trigger a build (and I found this pretty obvious). However, I admit that documentation is missing in big parts. BTW: this is an open source project, so you're invited to amend the documentation in the Wiki if you find something missing.

            People

            Assignee:
            kutzi kutzi
            Reporter:
            cforce cforce
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: