workflow

Help me improve my continuous deployment workflow

陌路散爱 提交于 2019-12-02 13:51:40
I've been developing a workflow for practicing a mostly automated continuous deployment cycle for a PHP project. I'd like some feedback on possible process or technical bottlenecks in this workflow, suggestions for improvement, and ideas for how to better automate and increase the ease-of-use for my team. Core components : Hudson CI server Git and GitHub PHPUnit unit tests Selenium RC Sauce OnDemand for automated, cross-browser, cloud testing with Selenium RC Puppet for automating test server deployments Gerrit for Git code review Gerrit Trigger for Hudson EDIT : I've changed the workflow

Make: setting up build environment for multi-directory research workflows [closed]

柔情痞子 提交于 2019-12-02 13:14:48
This question grew out of my earlier question (and discussion in comments to it) on my use of make -based build environment for R -based scientific research software project (for my Ph.D. dissertation): make always rebuilds Makefile targets . Following recommendation of @MadScentist, I created this question to clarify the following aspect of the my build environment. Since I use Makefile files in almost all sub-directories of my project, I've experienced the problem of correct specification for my research workflow dependencies . While the workflow itself is pretty standard ( data collection =

WCF Workflow Service REST interface [duplicate]

╄→尐↘猪︶ㄣ 提交于 2019-12-02 11:18:50
问题 This question already has answers here : Closed 7 years ago . Possible Duplicate: RESTful Workflow Service Endpoints in WF4 / WCF I am trying to make Windows Workflow Services 4.0 work with a REST interface. I have a very simple workflow service called "Service1" with a receiveRequest and sendResponse activity. By default WF Services autogenerate the classes and interfaces implemented, however i would like to force the WF Service to use my own REST enabled interface instead of some internal

GitHub Actions 持续集成 - 0. 入门

亡梦爱人 提交于 2019-12-02 10:36:22
GitHub Actions 持续集成 - 0. 入门教程 本文地址:https://blog.lucien.ink/archives/468/ 0. 前言 之前挖了一个 坑 ,今天开始抽空来补上。 以前也写过一篇关于持续集成的文: GitHub 快速接入 Travis ,随后拿到了 GitHub Actions 的内测资格,鉴于使用 GitHub 自家的 CI 整合度会更高,而且 GitHub Actions 本身也足够好用,遂决定将所有项目逐渐从 travis 和 drone 迁移至 GitHub Actions。 经过几天的尝试,PasteMe 从提交 commits, pull request 时的自动测试,到自动 release,配合 webhook 实现自动 deploy,真正意义上实现了持续集成与持续交付,我将这一实战过程复现并记录下来,以备不时之需。 本文章旨在介绍 GitHub Actions 的基础操作,随后通过一个项目来演示 GitHub Actions 的实际效果。 本篇文章参考了阮一峰老师的 GitHub Actions 入门教程 ,感谢阮一峰老师 Orz。 1. 什么是 GitHub Actions 持续集成由很多操作组成,比如抓取代码、运行测试、登录远程服务器,发布到第三方服务等等。GitHub 把这些操作就称为 actions。 GitHub

JIRA Plugin: Where to start

回眸只為那壹抹淺笑 提交于 2019-12-02 08:01:53
I was asked to create a simple JIRA plugin that combines Workflow + Custom Fields + Conditional Steps I just started installing JIRA and finally managed to create a run a simple Hello World Plugin. I am already confused with how huge this interface is, and cannot seem to be able to grasp the big picture Could any of you send me to the right direction? An idea on what could include all these? It might be a good idea to start with the scriptrunner plugin. This enables you to write custom groovy scripts for workflow conditions, validators, post-functions, listeners and many more. The advantage is

Problem mixing OOTB SPD WFAs and Custom WFAs

百般思念 提交于 2019-12-02 07:09:20
问题 I'm using MOSS (SharePoint 2007 Enterprise), 32-bit, SP2. I've been noticing some odd problems with Custom Workflow Activities which I've developed and am using in SharePoint Designer (SPD) workflows. These actions seem to work correctly, but don't "play nice" with the rest of the workflow (specifically, the root issue was posted at: Timing concerns with Custom WF Activity changing permissions , since that hasn't gotten any responses I've been digging deeper...) To help pin down the problem,

advisor调优工具优化sql(基于sql_id)

▼魔方 西西 提交于 2019-12-02 06:06:15
advisor调优工具优化sql(基于sql_id) 问题背景: 客户反馈数据库迁移后cpu负载激增,帮忙查看原因 解决思路: 1> 查看问题系统发现有大量的latch: cache buffers chains 等待; latch:cache buffers chains出现的原因 1、不够优化的SQL。 大量逻辑读的SQL语句就有可能产生非常严重的latch:cache buffers chains等待,因为每次要访问一个block, 就需要获得该latch,由于有大量的逻辑读,那么就增加了latch:cache buffers chains争用的机率。 对于正在运行的SQL语句,产生非常严重的latch:cache buffers chains争用,可以利用下面SQL查看执行计划,并设法优化SQL语句。 select * from table(dbms_xplan.display_cursor('sql_id',sql_child_number)); 如果SQL已经运行完毕,我们就看AWR报表里面的SQL Statistics->SQL ordered by Gets->Gets per Exec,试图优化这些SQL。 2、热点块争用 查找数据库是否存在latch的争用 select sid,event,p1text,p1raw from v$session_wait

Problem mixing OOTB SPD WFAs and Custom WFAs

北战南征 提交于 2019-12-02 03:53:25
I'm using MOSS (SharePoint 2007 Enterprise), 32-bit, SP2. I've been noticing some odd problems with Custom Workflow Activities which I've developed and am using in SharePoint Designer (SPD) workflows. These actions seem to work correctly, but don't "play nice" with the rest of the workflow (specifically, the root issue was posted at: Timing concerns with Custom WF Activity changing permissions , since that hasn't gotten any responses I've been digging deeper...) To help pin down the problem, I've developed a very simple test, which I will outline in detail below, and am noticing even more odd

Pass a parameter to a CRM 2011 Workflow via the API

五迷三道 提交于 2019-12-01 23:18:53
问题 I have a workflow that has a 'Prompt and Response' dialogue. I can run the workflow from the API using ExecuteWorkflowRequest but how do I provide values for the prompt and response inputs? 回答1: Workflows don't take parameters. Dialogs take parameters, which are generally passed from other dialogs or queries. The only thing I managed to do is to pass a related entity from parent workflow as the primary entity to a child workflow. 回答2: I'm going to retract my earlier answer and upvote @Grigory

Pass a parameter to a CRM 2011 Workflow via the API

无人久伴 提交于 2019-12-01 21:24:52
I have a workflow that has a 'Prompt and Response' dialogue. I can run the workflow from the API using ExecuteWorkflowRequest but how do I provide values for the prompt and response inputs? Grigory Workflows don't take parameters. Dialogs take parameters, which are generally passed from other dialogs or queries. The only thing I managed to do is to pass a related entity from parent workflow as the primary entity to a child workflow. I'm going to retract my earlier answer and upvote @Grigory instead. See this page from the SDK Note Due to the interactive nature of the dialog process, you cannot