|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
No, it probably wont be. The second problem you described should be fixed in 2.2.8
the first problem you described is something else. The matrix coordinator job can do a merge, but has no way of sharing that new commit to the matrix jobs.
As a workaround I suggest you split this in 2 jobs:
1 job to do the merge and push in a temporary branch, optionally in a separate repository. This job can then trigger the matrix job and pass the git revision.
Configure the matrix job with the temporary branch, and it will pick up the merge.