-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
Different webhooks for different branches? #1033
Comments
I'm working on a local branch that reworks how all of this works. Basically, instead of branches being the abstraction for jobs, it's now environments, which can be triggered by different events. If you want to help, let me know and I'll push it up so you can contribute. |
Sure I'd like to take a look |
If anyone else runs into this issue, here is how I am solving it until the environment update referred to above: Using the strider-metadata plugin I'm creating an environment variable called $STRIDER_TRIGGER_TYPE for which the value is the strider job's trigger.type, and then in the custom script I'm running an if / else based on whether $STRIDER_TRIGGER_TYPE is a commit or pull request |
@knownasilya any progress on that? sounds like something very useful 😃 |
It's currently on the backburner, but I should be able to pick it back up next month. |
*poke* 😄 |
😸 I'll try to push up my local branch this week (it's maybe half way there). |
Hey guys, out of curiosity. Are there any updates around this? |
I'm working on one repository, but I want the build of certain branches of that repository to be triggered by different events. Eg, I want the master branch to only be triggered by a pull request, whereas I want certain feature branches to be triggered by commits.
Is it possible within Strider to specify different webhooks for different branches? Or can anyone else imagine a solution to obtain this functionality?
The text was updated successfully, but these errors were encountered: