-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
match release branch pattern with conditions #112
Labels
enhancement
New feature or request
Comments
dmfs
added a commit
that referenced
this issue
May 11, 2024
dmfs
added a commit
that referenced
this issue
May 11, 2024
dmfs
added a commit
that referenced
this issue
May 11, 2024
dmfs
added a commit
that referenced
this issue
May 13, 2024
dmfs
added a commit
that referenced
this issue
May 13, 2024
dmfs
added a commit
that referenced
this issue
May 13, 2024
dmfs
added a commit
that referenced
this issue
May 13, 2024
dmfs
added a commit
that referenced
this issue
May 25, 2024
dmfs
added a commit
that referenced
this issue
May 25, 2024
dmfs
added a commit
that referenced
this issue
May 25, 2024
dmfs
added a commit
that referenced
this issue
May 25, 2024
dmfs
added a commit
that referenced
this issue
May 25, 2024
dmfs
added a commit
that referenced
this issue
May 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Jenkins builds branch names are not available in git, only detached heads. Branch names are made available via environment variable. Currently we don't support matching release branches by environment variables. The idea is that we use the same conditions we use in the other elements.
The text was updated successfully, but these errors were encountered: