[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Paul Murphy commented on JENKINS-12006 Branch specifier does not replace matrix build variables I would appreciate if this feature was considered for a future release. It would be very useful to parameterize the git branch from the matrix axis. It is possible to do this as a build parameter so it unfortunate that it is currently not possible to do this from a matrix axis. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Alec Henninger commented on JENKINS-12006 Branch specifier does not replace matrix build variables What's odd is the git branch field will respond to environment variables set through a parameterized build, but not via a matrix axis. Is this an issue with how the matrix axis sets environment variables? 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Marcus Klein reopened JENKINS-12006 Branch specifier does not replace matrix build variables See my previous comment Change By: Marcus Klein (14/Nov/13 10:27 AM) Resolution: WontFix Status: Resolved Reopened 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Florian Doersch commented on JENKINS-12006 Branch specifier does not replace matrix build variables @Marcus: thats exactly the branching model I'll use and thats why I definitly want that feature in jenkins 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Marcus Klein commented on JENKINS-12006 Branch specifier does not replace matrix build variables @Nicolas: Your assumption is not correct. git SCM can detect changes in multiple branches during a single detect run. In our case this happens quite often. We are using the following branching model: http://nvie.com/posts/a-successful-git-branching-model/. This results in continuous commits in branches develop, release-something and hotfixes-something. Open-Xchange does this to develop features for the next release in branch develop, to harden the upcoming release in the release-something branch (bugfixing) and to maintain old releases (fixing of security issues e.g.). This requires builds in different branches if those branches have changes. Additionally I want to view and monitor test results in all these branches without selecting a certain job run. To do this, we want to use the matrix feature. Is this an exotic way of using git and Jenkins matrix feature? 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12006) Branch specifier does not replace matrix build variables
Ian Hinder commented on JENKINS-12006 Branch specifier does not replace matrix build variables I think this would be achieved if the plugin expanded environment variables in the branch field. A matrix job sets environment variables. I would also like this feature. A use case would be to have a matrix job which built several different branches of the code, checking out the corresponding branch from the repository. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
