I have a pipeline setup in Spinnaker where it cuts and deploys a nightly build. I like this to start running at 2am everyday. But I couldn't find any option or documentation on how to do this.
Thanks.
When editing your pipeline, click "Add Trigger" and then choose "CRON" as the trigger type. There is a tooltip on the "CRON Expression" field that gives some help on how to construct the cron expression.
Thanks,
-Matt
Related
I'm new in using pentaho and I need your help to investigate a problem.
I have scheduled in crontab to run a job by kitchen command. I'm using pentaho release 6.0.1.0.386.
Sometimes (it's not a deterministic problem) one of the transformation stops after "Loading transformation from repository" and before "Dispatching started for transformation". The log interrupts. No errors. Nothing. And the job doesn't go on.
Any idea? Any check I can do ? Thanks
is so many bigger the quantity data in this transformation?
There are some files that can cause some errors, you can find them in this path:
enter image description here
my computer/users / your user / .kettle
If you delete the ones I marked in the image, they will be created automatically when you open the pentaho again.
I am currently trying to implement a pipeline using Gitlab ci. I defined my pipeline in a gitlab-ci.yml file to run my jobs. I am working on pipeline where jobs are triggered by opened merge request. more specifically , non WIP and draft merge request. One of the most important condition is also that I want the job to be triggered and running when merge request changes state from WIP/draft to "ready".
Below is the closest way I found to do such thing.
integrationtest:
stage: integrationtest
only:
- merge_requests
except:
variables:
- $CI_MERGE_REQUEST_TITLE =~ /^WIP:.*/
Unfortunately, Now the only thing missing is indeed the pipeline being triggered when WIP state changes.
Any idea to bypass this problem is more than welcome.
Thank you in advance :)
There is an open issue for you exact use case. There is a workaround with webhook integration mentioned in the last comment of this issue, maybe this will help you.
Can't find any documentation on the Bixby verbal command to invoke an existing SmartThings automation
I know how to speak a Bixby command to CREATE a SmartThings automation to run at a later time, but not to invoke one that is already created
none
I expect it should be able to do this. Also, is it possible for Bixby to create an automation that runs everyday, not just ONCE
...update... I found that this can be done by including the phrase "every day" in the command. e.g. :"Hi Bixby, turn off the entry light every day at 7:00AM"
I would recommend looking into the SmartThings documentation for help with integration (https://smartthings.developer.samsung.com/).
I have created my cron task to run every day at 00:00. However, I don't understand how this works.
I have if Time.now.hour == 0 in my cron.rake but I don't understand if I need to setup the cron:daily addon at midnight?
Anyone care to explain?
Thanks
Heroku's cron:daily addon will only run the cron rake task every day at the time you activate the addon. So the condition in your rake task won't do anything. Just deactivate the cron addon, wait until midnight and then turn it on (probably via command line would be easiest). It's a little annoying that you have to do it this way, but that's what their docs say.
http://devcenter.heroku.com/articles/cron#frequently-asked-questions - Scroll to the bottom.
I have scheduled a DTS to run from a scheduled job. The DTS has several steps in it. Now whenever the job is running and I take a look at the jobs section in Enterprise manager, then it always displays the following in the status: Executing Job Step 1'.... although its running all steps properly. How do I know at what step the DTS is running at?
Can I get the status maybe from sql analyzer?
You can add something which can show you where the dts currently running at. I prefer best way is to put alert using a script. There is no other direct way using which you can trace DTS task !
The display you get is a snap shot. you need to keep refreshing it.
There is only one step in the job, the command to run the DTS package.
If you want to see progress of steps within the package, you need to add something to the DTS package to record each step as it finishes in a logging table.
Since the DTS mostly executes against database tables, on the SQLServer side you can find what all sessions are currently active, the statement it is executing etc if you have administrative privileges. You can find this under Management as Activity monitor.