FlexDeploy provides automation where users can build once and deploy to many environments. By default, users can submit deployment request to all available environments and can configure Scheduled Window or Approvals to control what deployments are moving to specific environments. FlexDeploy 4.0 provides additional capability where users can control who can submit deployments to specific environments allowing

FlexDeploy’s WebLogic plugin provides various operations to automate the management of domain configurations. Similar to build and deploy of J2EE applications, you can utilize SCM repositories like Subversion, Git, TFS, CVS etc. to maintain configuration files and setup Build and Deploy workflows in FlexDeploy. Let me show you show it works:   See a very

One of my favorite additions to FlexDeploy in the 4.0 release is the Plugin Software Development Kit(SDK). The FlexDeploy Plugin SDK is a collection of materials and Java code designed to support the development of plugins for FlexDeploy. FlexDeploy has always had a great selection of plugins that meet many use cases, and there is

This blog article is the second part of a two-part series which dives into the FlexDeploy integration with Atlassian Jira.  The first article in the series focused on updating Jira issues based on build and deploy operations in FlexDeploy.  The second part will focus on automatically approving FlexDeploy tasks based on Jira workflow transitions. Just

Atlassian Jira has grown in popularity over the past several years and is used by many IT teams to manage and release software.  Once known as a bug tracking tool, Jira has evolved into the de facto standard for teams implementing agile methodologies.  Many organizations are making Jira the center of their universe for managing