Jenkins auto build is not working - jenkins

This is ramesh,
I tried to build my .net application using jenkins, my source is reside at in github. I can get build, when using manual build option in jenkins. But auto build is not working, when i give commit on github.
Thanks

Your question is not clear. What are you Build triggers?
Here's what I use:
Jenkins uses something called corn expressions
MINUTES Minutes in one hour (0-59)
HOURS Hours in one day (0-23)
DAYMONTH Day in a month (1-31)
MONTH Month in a year (1-12)
DAYWEEK Day of the week (0-7) where 0 and 7 are Sunday
* */23 * * * == one day

Related

Cron that runs on first Sunday after the first Friday of the month has passed

We work on a product whose software development team applies patch on every 1st Friday of the month. We have written some tests that we run on the Sunday after the patch is applied. So to automate the same on Jenkins, we would need a cron that runs on 1st Sunday after the 1st Friday of the month has passed.
Right now we just update our Jenkins each month considering dates, but can we automate this?
Thanks
Naively, one would suppose that 0 3 1-7 * fri would be "3am on the Friday that falls inside the first week of each month", and then we could use the similar logic to construct 0 3 3-9 * sun, for the Sunday that follows two days after such a Friday.
Unfortunately, this does not work, because day of week and day of month are taken as a disjunction by the cron specification; which means, the above would trigger not on the Sunday following the first Friday in a month, but on every Sunday, and also every day from 3rd to 9th.
Due to this twist in cron spec, what you ask is not possible by cron alone. The easiest way to untangle this is to separate the two requirements, ask the cron to track one of them, and manually test the other: either use 0 3 3-9 * * and then manually test in your script whether the day is Sunday and exit without performing your task if it is not, or use 0 3 * * sun and manually make sure the date is between 3rd and 9th.

Is there anyway/plugin we can trigger a build only at particular time and should not be able to trigger any other time?

I have created my job and want to trigger build daily at 11am and in any other time I should not be able to trigger it.
You can Go to “Build Triggers” section in jenkins and under that Check “Poll SCM”, here you can create cron jon for your pipeline trigger.
For you query you can give somethind like below in the Poll SCM schedule box:
0 11 * * *
Jenkins used a cron expression, and the different fields are:
MINUTES Minutes in one hour (0-59)
HOURS Hours in one day (0-23)
DAYMONTH Day in a month (1-31)
MONTH Month in a year (1-12)
DAYWEEK Day of the week (0-7) where 0 and 7 are sunday
For more info please visit here
To add on the given answer , you can also add a simple bash script to check the time and exit or do the same in the jenkins pipeline

Schedule a Jenkins job for future date

I have to schedule a Jenkins job which runs every Day of the week, every Month in a year , every Day in a month but after a specific date.
I have used the below cron expression but it will trigger the job only on 1:00 pm for sept month only.
0 13 * 8 *
I need to schedule it from Sept,01,2018 onward everyday at 1:00pm.
If You want to trigger in future use: Schedule Build Plugin
0 0 13 1 1/1 ? *
For more information you can visit www.cronmaker.com
Thanks,
Sunny

Can I get a Jenkins trigger to run every first week day of every month?

My goal is to trigger a report every first weekday of the month at 7AM (7/1/15,8/3/15,9/1/15, etc.)
I am using the following cron expression: H 7 1-3/3 * 1-5
It runs on July 1, but it is not scheduled next to run on August 3, but on September 1. How can I get it to run on the first weekday of every month?
I am using the following help guide:
MINUTE Minutes within the hour (0–59)
HOUR The hour of the day (0–23)
DOM The day of the month (1–31)
MONTH The month (1–12)
DOW The day of the week (0–7) where 0 and 7 are Sunday.
To specify multiple values for one field, the following operators are available. In the order of precedence,
The * specifies all valid values
M-N specifies a range of values
M-N/X or */X steps by intervals of X through the specified range or whole valid range
A,B,...,Z enumerates multiple values
To allow periodically scheduled tasks to produce even load on the system, the symbol H (for “hash”) should be used wherever possible.
First weekday of the month rules:
If today is a Monday, then the job should be run if today is also the 1st, 2nd, or 3rd of the month
If today is a Tuesday, Wednesday, Thursday, or Friday, then the job should be run if today is also the 1st of the month
The following cron expressions should do the job:
H 7 1-3 * 1
H 7 1 * 2
H 7 1 * 3
H 7 1 * 4
H 7 1 * 5
# Would last have run at Wednesday, July 1, 2015 7:00:02 AM EEST; would next run at Monday, August 3, 2015 7:00:02 AM EEST.
Beware, because of this article, you can't just use:
H 7 1-3 * 1
H 7 1 * 2-5
The above doesn't work! Instead, the job is run on every weekday, twice on the 1st of the month, and maybe twice on the 2nd and 3rd of the month!
But I was not able to reproduce it.
This should work just fine:
H 7 1-3 * 1
H 7 1 * 2-5
The article to which the accepted answer is referred to is about crontab expressions. Jenkins cron expressions actually use AND for DOM and DOW (otherwise the solution from the accepted answer wouldn't work either)
Here is the answer to your question, seems it can work
http://www.switchplane.com/blog/how-to-run-a-cron-job-on-the-first-weekday-of-the-month/
All the best

Jenkins polled repository once then never again, though 1 minute interval is set

I've set up a Jenkins job and set the poll interval at 1 minute (I used this syntax 0 * * * *).
Looking in the Polling log I can see its reported that a poll call was made as soon as I saved the changes to the job.
But not over 10 minutes later it hasn't made any other polls.
Any suggestions how I can proceed determining the problem?
You're looking for "* * * * *".
Jenkins gives a warning since every minute can be a bit excessive, but your version control server shouldn't have any problems handling the load.
Your cron syntax is set to poll once per hour, at zero minutes past the hour. From the Jenkins help text:
This field follows the syntax of cron (with minor differences). Specifically, each line consists of 5 fields separated by TAB or whitespace:
MINUTE HOUR DOM MONTH DOW
MINUTE Minutes within the hour (0-59)
HOUR The hour of the day (0-23)
DOM The day of the month (1-31)
MONTH The month (1-12)
DOW The day of the week (0-7) where 0 and 7 are Sunday.

Resources