<p>Oh, I figured it out. I just went to the job configuration, activated the "build is parameterized" checkbox, added a string parameter called BRANCH, and in the "branches to build" section added <code>${BRANCH}</code>. Pretty much what is explained here:</p>

<ul>
<li><a href="https://stackoverflow.com/questions/20359810/how-to-trigger-jenkins-builds-remotely-and-to-pass-parameters">https://stackoverflow.com/questions/20359810/how-to-trigger-jenkins-builds-remotely-and-to-pass-parameters</a></li>
<li><a href="https://stackoverflow.com/questions/32108380/jenkins-how-to-build-a-specific-branch">https://stackoverflow.com/questions/32108380/jenkins-how-to-build-a-specific-branch</a></li>
</ul>

CC BY-SA 4.0
2019-01-21T20:23:08.453Z
2019-01-21T20:23:08.453Z
JMFS
<p>I am wondering if anyone else has integrated before a parameterized Jenkins build with <a href="https://www.anystat.us/" rel="nofollow noreferrer">AnyStatus</a>.</p>

<p><a href="https://i.sstatic.net/qQHwi.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/qQHwi.png" alt="enter image description here"></a></p>

<p>When removing the parameter above, I am able to run builds using the branch specified previously from the browser, but that's not the idea. There is a <a href="https://devops.stackexchange.com/questions/457/how-to-not-fire-and-forget-when-doing-a-remote-trigger-of-a-jenkins-build">post</a> explaining that I can use a script, but that wouldn't be integrated with AnyStatus in the existing Jenkin's plugin.</p>

<jenkins><monitoring>
Specifying branch name for jenkins job through AnyStatus
JMFS
# Specifying branch name for jenkins job through AnyStatus

(Asked by: username_0 on 2019-01-21)

I am wondering if anyone else has integrated before a parameterized Jenkins build with [AnyStatus](https://www.anystat.us/).

[![enter image description here](https://i.sstatic.net/qQHwi.png)](https://i.sstatic.net/qQHwi.png)

When removing the parameter above, I am able to run builds using the branch specified previously from the browser, but that's not the idea. There is a [post](https://devops.stackexchange.com/questions/457/how-to-not-fire-and-forget-when-doing-a-remote-trigger-of-a-jenkins-build) explaining that I can use a script, but that wouldn't be integrated with AnyStatus in the existing Jenkin's plugin.

**Tags:** jenkins, monitoring


---

## 1 answers

### Answer by username_0 on 2019-01-21. Score: 0 | Accepted answer

Oh, I figured it out. I just went to the job configuration, activated the "build is parameterized" checkbox, added a string parameter called BRANCH, and in the "branches to build" section added `${BRANCH}`. Pretty much what is explained here:

* <https://stackoverflow.com/questions/20359810/how-to-trigger-jenkins-builds-remotely-and-to-pass-parameters>
* <https://stackoverflow.com/questions/32108380/jenkins-how-to-build-a-specific-branch>


---

