Finding Darin was a blessing. I was so nervous approaching Jenkins and watching his tutorials along with he Documentation helped me gain so much confidence. Thank you too much Darin!
I spent a lot of time watching and reading a lot of useless videos and articles, trying to accomplish deal with GitHub Pull Requests on Jenkins. It changes when I found your video! It is very clear and precise! It works very fine! You save my time! Thank you a lot! You got a new fan! : )
Thanks for your tuto Darin. But on question is: What is better to use when you manage a multi branches repo: the generic webhook trigger pluging or a multibranch pipeline?
Is it possible to programmatically prune the branches? For example, if I wanted just the branches with recent commits or only those with pull requests?
Finding Darin was a blessing. I was so nervous approaching Jenkins and watching his tutorials along with he Documentation helped me gain so much confidence. Thank you too much Darin!
I spent a lot of time watching and reading a lot of useless videos and articles, trying to accomplish deal with GitHub Pull Requests on Jenkins.
It changes when I found your video! It is very clear and precise! It works very fine!
You save my time!
Thank you a lot!
You got a new fan! : )
Great, thanks!
Very clear. Except that webhooks don't work when you have a running jenkins docker on a localhost.
Q: When will the Jenkins parameters evolve to allow users to create complex scenarios?
Thank you sir! :)
Thanks for your tuto Darin. But on question is:
What is better to use when you manage a multi branches repo: the generic webhook trigger pluging or a multibranch pipeline?
Thanks for the tutorial. Appreciate if you can also share Jenkins Job DSL syntax to create multibranch pipeline job.
Is it possible to programmatically prune the branches? For example, if I wanted just the branches with recent commits or only those with pull requests?