|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14329) Trigger paramete... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) Trigger par... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) Trigger par... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) SCM Sync Co... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) SCM Sync Co... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) SCM Sync Co... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) SCM Sync Co... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) SCM Sync Co... [email protected] (JIRA)
- [JIRA] (JENKINS-14329) SCM Sync Co... [email protected] (JIRA)

I have Jenkins 1.461, Parametrized Trigger Plugin 2.13, and SCM Sync 0.0.4. I Do not experience this issue.
In your A config I see the following line.
<triggerWithNoParameters>false</triggerWithNoParameters>
Looks like you should supply some parameters, but you actually don't. Don't know if that makes a difference.