Retrieve Jenkins queue status [improvements]

[ddimitrioglo]

Since 1.24 data.triggerResults returns queue info - and it's great, but if my Jenkins job is already in progress it would be cool also get queue status pending, started otherwise.

[tomasbjerre]

I'm pretty sure that is asynchronous. I think it is always pending immediately after it is triggered. But perhaps 20ms after triggered it is started.

[ddimitrioglo]

If I'm not wrong there is blocked property in queueInfo object which is true when queued and false when started

[ghost]

is there a way to trigger the build in jenkins through webhook for particular branch commit in github ?

[ddimitrioglo]

Hi @forpix ,

I achieved it by adding a "post content variable" like:

and then just filtered all the requests like this:

Hope it will help you ;)

[ghost]

Thanks for the response I will try it and get back to you @ddimitrioglo

[ghost]

@ddimitrioglo ,
Im having a scenario like this,
I have a job in a Jenkins which configured to trigger with web-hook in GitHub. In GitHub I'm having 3 branches called 'working' , 'developed', and final one 'master', if I commit to develop branch the build got triggered and now I have merged the committed file to master from developed now again Jenkins triggered the job(which don't have any chages in files apart from merging) with merged commit.
so how to restrict this ....., I tried out solution but its not restrict the job only for developed branch.

[ddimitrioglo]

@forpix I'm a bit confused...
If you make some changes in working branch and open a PR from working => developed, then merge PR, how could happen that you are opening a PR from developed => master and there is no changes just merged commit?

What I'm missing here?

[ghost]

leave about the above scenario, Let me explain again here, A job in Jenkins is configured to trigger through web-hook. In GitHub, I have a repository with two branches 1. Master 2.Working, now I have committed/created a new file on *Working branch* and Job is triggered, which exactly I want to have.😊 Now the committed file in Working branch should have to be *merge* to Master so PR should be needed, which leads to trigger the job again. (Because of PR from Working to Master again new build is triggered which I don't want..😐)

…

On Tue, May 15, 2018 at 1:02 PM, Dmitri Dimitrioglo < ***@***.***> wrote: @forpix <https://github.com/forpix> I'm a bit confused... If you make some changes in working branch and open a PR from working => developed, then merge PR, how could happen that you are opening a PR from developed => master and there is no changes just merged commit? What I'm missing here? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfZr8f34zLGafC670HG3JRXlK7wogVLYks5tyoR3gaJpZM4R69CC> .

-- Kind Regards, MAHAMMAD ALI, +919632282787

[ddimitrioglo]

Ok, I see the flow now.
Have you configured as I've proposed you?

In your case you just have to change ^(dev|test|stage|master)$ => ^Working$ this will trigger ONLY PRs to Working branch, everything else will be skipped.