Re: BitBucket Branch Source Plugin not triggering builds from Post Webhooks PR event

Thanx, That helps, I can see the PUSH event when I push a new branch git push --set-upstream origin webhook1 Push Event from webhook {"actor":{"username":"admin","displayName":"admin"},"repository":{"scmId":"git","project":{"key":"OP","name":"Open

Re: BitBucket Branch Source Plugin not triggering builds from Post Webhooks PR event

https://github.com/Eernie/bitbucket-webhooks-plugin/issues/72 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To

Re: BitBucket Branch Source Plugin not triggering builds from Post Webhooks PR event

have a looks at this issue, may help -D -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion

Re: "Jenkins is going to shut down" ad infinitum

If anyone can run any system groovy script then they might easily run the 'safe-restart'. can you confirm whether the script security is enabled? https://jenkins.io/doc/book/managing/script-approval/ -- You received this message because you are subscribed to the Google Groups "Jenkins

RE: "Jenkins is going to shut down" ad infinitum

Anything in the logs? Did anyone install https://wiki.jenkins.io/display/JENKINS/Post-initialization+script? Matthew -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the

Warning about PostBuildScript plugin 1.1.0

If you use the PostBuildScript plugin (https://plugins.jenkins.io/postbuildscript) and are considering upgrading to 1.1.0, can I suggest that you look at ticket https://issues.jenkins-ci.org/browse/JENKINS-48169 first. The upgrade caused us a lot of problems. -- This e-mail and any

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

@Cyril -- I am having the same issue as in your original post. I don't understand your solution though. I have webhooks defined for my RepoA and RepoB. In the "Build Triggers" section of the job config I have only "Github hook trigger" -- presumably this will only trigger a build on pushes to

Re: Git push to specific branch on multibranch pipelines builds all branches

On Wednesday, November 22, 2017 at 10:50:52 AM UTC-5, Stephen Connolly wrote: > > >>> * The Jenkinsfile for both branches is the same (v1.14 is a branch of >>> master) and has the following setup for triggering with a github push: >>> >>> properties([ >>>

"Jenkins is going to shut down" ad infinitum

Hello, We do have the ThinBackup and PeriodicBackup plugins in use, but there is nothing odd about either of their configurations. Moreover, the settings for ThinBackup and PeriodicBackup have not changed in several months. The "Jenkins is going to shut down. No further builds will be

Re: Problems with CSRF protection in Jenkins 2.85

Hello, ok, answer to my own mail... The rules seem to be: 1. Use “curl -s 'http://:@:/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)' && echo” to get the Crumb 2. The Crumb gets returned, ready to use: “Jenkins-Crumb:30….b” Exactly this need to be

Re: Git push to specific branch on multibranch pipelines builds all branches

On 22 November 2017 at 15:49, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > > On 22 November 2017 at 15:17, Harlan Barnes > wrote: > >> Hello Jenkins Friends, >> >> I'm having a problem getting the configuration correct for my >> multi-branch pipeline. Here

Re: Git push to specific branch on multibranch pipelines builds all branches

On 22 November 2017 at 15:17, Harlan Barnes wrote: > Hello Jenkins Friends, > > I'm having a problem getting the configuration correct for my multi-branch > pipeline. Here are the details > > * I have a Jenkins job configured with a simple Git Branch Source with the >

Git push to specific branch on multibranch pipelines builds all branches

Hello Jenkins Friends, I'm having a problem getting the configuration correct for my multi-branch pipeline. Here are the details * I have a Jenkins job configured with a simple Git Branch Source with the following options: * Discover All Sources * Filter by name (with regular expression):

Environment variables in docker agent args (pipeline)

Hi Jenkins experts, My first experiment with the Pipeline plugin was to execute a build step inside a Docker container, configured as agent, but I'm unable to use Jenkins' standard variables in my agent configuration. With the following code I'm trying to mount the current workspace to a