I need to schedule a jenkins job to run every 90 minutes
I tried the following but it did not work
*/45 */1 * * *
But the job ran ever hour and then at every 45 minutes like
Sep 15, 2016 1:46:09 AM
Sep 15, 2016 1:01:09 AM
Sep 15, 2016 12:46:09 AM
Sep 15, 2016 12:01:09 AM
Sep 14, 2016 11:46:09 PM
Sep 14,2016 11:01:09 PM
and so on
Can any one please suggest me how this is done
You may have to specify two cron jobs for it in the scheduler like this in the same jenkins job - very similar to what one would do for a normal cron in Linux
0 0,3,6,9,12,15,18,21 * * * /path/to/script
45 1,4,7,10,13,16,19,22 * * * /path/to/script
Related
I'm trying to use highcharts-export-server in command-line/batch mode. I've installed the latest version (2.0.28). I'm running Windows 10 with Node 12.
I'm running it from the command line using the following command:
highcharts-export-server --nologo 1 --logLevel 4 --options chart.json --outfile chart.png --type png --width 500
The console output says:
starting highcharts export server v2.0.28...
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] attaching exit listeners to the process..
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] Pool started:
maxWorkers: 1
initialWorkers: 1
workLimit: 60
listening to process exit: true
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] phantom 1 - spawning worker
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] starting export
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] attempting to export from raw input
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] phantom - received work, finding available worker
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] phantom - found available worker
Fri Sep 25 2020 15:07:48 GMT+0100 (British Summer Time) [verbose] phantom 1 - starting work
Fri Sep 25 2020 15:07:52 GMT+0100 (British Summer Time) [notice] phantom worker 1 finished work ??? in 3562 ms
Fri Sep 25 2020 15:07:52 GMT+0100 (British Summer Time) [notice] phantom worker 1 - process was closed
Fri Sep 25 2020 15:07:52 GMT+0100 (British Summer Time) [notice] terminating, killing all running phantom processes
...but although a chart.png file is created and has the correct width, it's blank (transparent):
This is the content of the chart.json file, which I took from one of the examples on the Highcharts website:
{
chart: {
type: 'bar'
},
title: {
text: 'Fruit Consumption'
},
xAxis: {
categories: ['Apples', 'Bananas', 'Oranges']
},
yAxis: {
title: {
text: 'Fruit eaten'
}
},
series: [{
name: 'Jane',
data: [1, 0, 4]
}, {
name: 'John',
data: [5, 7, 3]
}]
}
Note: I'll mention that when I first tried to install highcharts-export-server I hit a different problem which was that I couldn't run it at all (it failed with uncaughtException: TypeError: "file" argument must be a non-empty string). After some googling I found some blog posts suggesting that I needed to install PhantomJS first, and to use the --unsafe-perm option. So, the commands I actually used to install it was:
npm install phantomjs --unsafe-perm
npm install highcharts-export-server --unsafe-perm
Oh, and it wasn't until some time later that I realised I might have to install Highcharts itself :-) So I did that too (npm install highcharts), but it didn't actually seem to make a difference.
In case this helps anyone else, here is the full conversation about this issue on the Highcharts Forum.
In summary, it turned out that the NPM package was improperly installed (due to a firewall issue).
This wasn't apparent from the installation logs, but the effect was that in the node_modules/highcharts/export-server/phantom/export.html file there was a script block that should have contained minified JavaScript but that actually contained only lines saying undefined;.
The fix in my case (to work around the firewall issue) was to specify an http URL for the CDN when installing Highcharts Export Server, rather than the default URL which uses https. Once I'd done that, the export.html did contain the minified JS code, and the tool worked correctly.
I had scheduled pulling in Jenkins every 5 minutes: */5 * * * *.
I committed changes to SVN, I can see them in SVN history (logs).
Jenkins starting the build, but it shows: Revision: x
No changes. And everything what was configured is running.
After 5 minutes Jenkins starts another run, with message: Revision: x+1
Changes
just for test Jenkins deploy (detail)
by UserName
After, for test purposes I have changed to * * * * * to run every minute, and the results were such:
Jenkins runs:
Success > Console Output#176 Nov 29, 2018 2:14 PM
Success > Console Output#175 Nov 29, 2018 2:13 PM
Success > Console Output#174 Nov 29, 2018 2:11 PM
Success > Console Output#173 Nov 29, 2018 2:10 PM
Success > Console Output#172 Nov 29, 2018 2:09 PM
Success > Console Output#171 Nov 29, 2018 2:08 PM
Success > Console Output#170 Nov 29, 2018 2:07 PM
Success > Console Output#169 Nov 29, 2018 2:06 PM
---Commit goes here
Success > Console Output#168 Nov 29, 2018 1:01 PM
from 2.06 he see that there is changes, he run job, but it really didn't see what changes was there, and only at 2:14 it wrote SVN commit message.
also in Recent Changes logs:
Changes
176 (Nov 29, 2018 2:14:19 PM)
just for test Jenkins deploy — UserName / detail
168 (Nov 29, 2018 1:01:36 PM)
It is strange behavior, could someone have idea, where could be the issue?
Based on the conversation, We have found out the culprit was the Time Difference of the 2 servers(Jenkins and SVN) approx 7-8 mins was the issue.
Why does this happen ?
Jenkins realized that a new version was available, but couldn't check it out
as long as its own time was smaller than the new versions time.
A similar issue is described here:
Why up-to-date files committed to SVN will not be immediately pulled out by Hudson to build
I would like to run job in Jenkins tool on every Wednesday morning at 7AM BST..
what's correct expression needs to use in Build Triggers?
Thanks for your help.. ..
Express mentioned as "0 6 * * 3"
Spread load evenly by using ‘H 6 * * 3’ rather than ‘0 6 * * 3’ Would last have run at Wednesday, November 14, 2018 6:00:00 AM CET; would next run at Wednesday, November 21, 2018 6:00:00 AM CET. ------------------------- – Girish B Nov 16 at 16:07
Dataflow job id: 2016-01-13_16_00_09-15016519893798477319
Pipeline was configured with the following worker/scaling config:
min 2 workers
max 50 workers
However, the job scaled to 55 workers. Why was the max worker value of 50 not honoured?
Jan 14, 2016, 11:00:10 AM
(77f7e53b4884ba02): Autoscaling: Enabled for job 2016-01-13_16_00_09-15016519893798477319 between 1 and 1000000 worker processes.
Jan 14, 2016, 11:00:17 AM
(374d4f69f65e2506): Worker configuration: n1-standard-1 in us-central1-a.
Jan 14, 2016, 11:00:18 AM
(28acda8454e90ad2): Starting 2 workers...
Jan 14, 2016, 11:01:49 AM
(cf611e5d4ce4784d): Autoscaling: Resizing worker pool from 2 to 50.
Jan 14, 2016, 11:06:20 AM
(36c68efd7f1743cf): Autoscaling: Resizing worker pool from 50 to 55.
This turned out to be a bug in our code. We were calling the wrong method. We need to call setMaxNumWorkers, and not setNumWorkers.
I'm not sure how to go about debugging this issue. Jenkins on restarts takes forever and from the logs I can see that its sitting trying to launch the slave
06/25/15 14:03:34] SSH Launch of Slave1 on dom-jenkins-sl1.cloud.dev.phx3.gdg failed in 179,907 ms
Jun 25, 2015 2:05:06 PM hudson.slaves.SlaveComputer tryReconnect
INFO: Attempting to reconnect Slave1
Jun 25, 2015 2:05:07 PM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 33090
Jun 25, 2015 2:05:07 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Jun 25, 2015 2:05:07 PM org.jenkinsci.plugins.skipcert.ItemListenerImpl onLoaded
INFO: Bypassing certificate check
Jun 25, 2015 2:05:08 PM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
[06/25/15 14:05:08] SSH Launch of Slave1 on dom-jenkins-sl1.cloud.dev.phx3.gdg completed in 1,923 ms
And yet on the second try 2 minutes later it works just fine. Any ideas?