You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
It would be great if we could put a wildcard in branches, eg t[0-9]* which would match our feature branches (we name the branches tNNN_some_description_here where NN is the trac ticket number
This would match possibly multiple branches, with the latest version in each branch being tested.
What do people think?
The text was updated successfully, but these errors were encountered:
This doesn't seem like a bad idea even though I'm not sure I'd get much use out of it. I think I'd probably revert to manually entering the branch name to ensure it is testing the correct one and not an incorrectly labelled version.
I've never used that convention. My branches tend to be things like "integrated_cas" and then something like "integrate_cas_with_tdd" which I suppose it something like yours but would require a lot of additional customization.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if we could put a wildcard in branches, eg t[0-9]* which would match our feature branches (we name the branches tNNN_some_description_here where NN is the trac ticket number
This would match possibly multiple branches, with the latest version in each branch being tested.
What do people think?
The text was updated successfully, but these errors were encountered: