scheduled-trigger | Trigger standard hooks when scheduled ExpressionEngine | Cron Utils library
kandi X-RAY | scheduled-trigger Summary
kandi X-RAY | scheduled-trigger Summary
Problem: ExpressionEngine currently has no system in place to trigger actions or hooks when an entry goes live or expires. Solution: Scheduled Trigger. This add-on provides an endpoint that can be executed with a scheduled cron job configured to run at your desired interval. It's extremely lightweight so setting it for every 5 minutes or so is no problem.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Setup settings form
- Install Scheduled Trigger
- Check for scheduled checks
- Initialize queue entries
- Uninstalls module
- Save settings .
- Queue the scheduled trigger
- List scheduled trigger actions
- Run the scheduled trigger .
scheduled-trigger Key Features
scheduled-trigger Examples and Code Snippets
Community Discussions
Trending Discussions on scheduled-trigger
QUESTION
I have setup an Azure pipeline to run GUI tests twice a day. According to the documentation it should only run if there have been code changes, but it always runs.
This is my cron schedule in "azure-pipelines-cypress.xml"
...ANSWER
Answered 2020-Jan-08 at 02:41Azure cron pipeline always runs
Update2:
I don't want it to run every time the master branch is updated. It should run when the master branch is updated AND only at a scheduled time.
But is that not the expected behavior of my current pipeline? The current behavior acts as if I had set "always: true"
First of all, thanks Mick for your patience in providing a lot of detailed information.
Now, I figure out the issue and I could reproduce this issue on my side. If we set the scheduled triggers, but the build result is failed. In this case, even if we do not any change, the scheduled triggers will still fire. That because the latest build failed, so the last commit record was not recorded by the pipeline. When the scheduled time is reached, the last commit/source code change still exists. It will trigger scheduled triggers.
So, that the reason why your pipeline still executed, even if you do not do any change in the code/yaml.
If I successfully build the pipeline, the scheduled triggers works as expected.
So, it should be said that the documentation is not clear enough, it should be:
always: boolean # whether to always run the pipeline or only if there have been source code changes since the last successful run. The default is false.
I submit this to MS, Thank you for helping us build a better Azure DevOps.
Hope this helps.
QUESTION
I am trying to set my nightly build to occur at 00:30 every day in my build pipeline YAML file. I get the following error when trying to build:
Improperly formed cron syntax: '00 30 00 * * *'
This is what I've tried:
...ANSWER
Answered 2019-Jun-28 at 14:47Two possibilities:
- Double-quotes instead of single-quotes (?)
- Five cron fields, not six
QUESTION
We have just recently upgraded from TFS 2015.2.1 to TFS 2017 and were hoping that we get the possibility to have multiple build definitions as a trigger for a release definition. This feature seems to be available for VSTS (according to https://www.visualstudio.com/en-us/docs/release/author-release-definition/more-release-definition#continuous-deploymentintegration-and-scheduled-triggers) but is still not available in TFS 2017 (see https://www.visualstudio.com/en-us/docs/release/getting-started/release-notes#update-nov16).
Does anyone know why and when this feature will be available in TFS?
...ANSWER
Answered 2017-Jan-11 at 01:44I've submitted a UserVoice at website below, you can vote it:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install scheduled-trigger
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page