I have a FREESTYLE Jenkins job (i.e. not a pipeline job) that is leveraging the Office 365 Connector to notify events.
In the Advanced Configuration there is a section to only trigger using Macros (token macro).
I am trying to figure out how I can use this to only trigger notifications during a certain time period of the day? Say 9am to 5pm.
Or any other way to do this?
Related
I am looking to trigger Jenkins's job from the Microsoft team's channel. Can anyone provide step by step implementation of this?
There are two nice options you can use:
Outgoing Webhook - Will scan for words in the chats and send a notification to your Jenkins server.
Commander - Second and more customizable option is using the Commander add on for teams, which in addition to builtin commands provides the ability to Create your own Custom Commands.
With both options you will be able to tigger Jenkins jobs via the Remote Access API, see the This Question for additional info on remote execution.
Is there a way to set an alerts on com.google.cloud.dataflow.sdk.transforms.Aggregator? We can view current counter on Dataflow UI but there is no way to get current value from the aggregator instance or read current value from the stackdrive.
Not at the moment, but we are working on better integrating Dataflow with Stackdriver, and future enhancements to alerting in Dataflow will be made via Stackdriver
I am wonderding if there is a way to find out (through API preferably) when projects on a tfs server was created in psudo-real time (Specifically, tfs paths and git repositories). The closest I've gotten is to find the earliest push of every project, but any code I can think of would take too long. Here's my thought process:
Get Tfs API for list of all jobs
Go to the url of every job
Substring search for earliest commit
is there any way I can send only one api request and get the dates from the response? Thanks.
There is a tool for TFS Administrators which can monitor job status through
http://your-server:8080/tfs/_oi/
Built-in to TFS is the TFS Background Job Agent. This job agent is responsible for the scheduling and queuing of maintenance jobs and other jobs within TFS. More detailed info you can refer this blog from MSDN: How to see activity and job history in TFS 2012
I'm working on a POC to automate downstream processes in external systems based on JIRA processes and have hit a wall with the API. It appears to have great integration for pulling data about tickets out of JIRA and for the ability to externally generate tickets into JIRA.
However I don't see how to trigger external calls as a part of my workflows. For example if a ticket should be prevented from being routed to the next stage of a workflow without accessing a database to ensure availability of inventory first how could I do that in JIRA?
Based on attributes in the JIRA ticket upon final completion of the workflow we'd like to send a JMS or REST message or possibly update an external database. Is this possible?
Thanks all in advance for the help!
If you want to do a "before" check, use a Validator on the Workflow Transition.
I strongly suggest deploying the (free) Script Runner add-on. There you can implement a ton of things. For example, you'll get a new validator option "Script Validator", where you can specify a Groovy script that decides if it lets through the transition or aborts it.
I am doing a Grails project. And here are some requirements about the system monitoring as below:
1. Email notify team when system goes down
2. Email notify team system log daily
3. Email notify team when app is deployed
So I don't know what to meet my requirements.
Could someone help me？
Use any monitoring software or service. I use New Relic, but there are plenty to choose from. If you only need ping, use a ping monitoring service. I use a free Google script I found on the Internet, but it has had some false alerts.
Use the Quartz plugin to send the log at a daily basis, or a cron job or similar.
Maybe use a shell script that does the employment and sends an email as well, or it might exist a Grails event for deployment.