AppControl Docs
  • Introduction
  • Overview
    • Features
    • Product architecture
      • AppControl Repository
      • Policy Checks
    • Initial set up
      • AppControl User
      • Install package
      • Configure system
      • Add apps
      • Add users
      • Give permissions
    • User Roles & Access
    • Getting Started
      • Platform Administrator
      • App Owner
      • App Administrator
      • Developer
  • Dashboards
    • Platform
    • Alerts
    • App
    • Policies
      • Compare Revisions
    • Releases
      • Create Release
    • Tasks
      • Task Assignment
      • Task Details
    • Insights
      • Components
      • Reports
      • Users
      • Logs
  • Administration
    • Policies
    • Pipelines
      • Approval
      • Backup
      • Build
      • Call API
      • Check Policy
      • Deploy
      • Deploy Configuration
      • Notification
      • Start / Stop
    • Tasks
    • App Groups
    • Access Groups
    • System
      • Accounts
      • Notifications
      • System Status
      • System Logs & Tools
      • System Configuration
      • Repository
      • Product License
      • Management API
      • Mendix Configuration
    • Feedback
  • Checks
    • APIs
      • Published APIs must use authentication
    • App
      • Project security level
      • Project security enabled
      • Demo users enabled
      • Anonymous users enabled
      • Strong password policy
      • Default admin username changed
      • Anonymous user access restricted
      • Default admin user restricted
      • Use strong hash algorithm
      • Check user role security for consistency
      • Restrict users to a single session
      • Perform strict page URL checks
      • Project naming standards
    • Components
      • Components with vulnerabilities
      • Mendix runtime version age
      • Mendix runtime support status
      • Non platform supported components
      • Max component age
      • Average age components
      • Use latest version of Marketplace module
      • Use latest version of Marketplace widget
      • Use latest version of Mendix
      • Limit number of Java libraries
      • Limit number of widgets
      • Use minimum Mendix runtime version
    • Constants
      • Do not expose constants to client
    • Development
      • Last commit to production
      • Last commit to project
      • Project documentation standards
      • Project organization standards
      • Project logging standards
    • Domain Model
      • Default member access rights restricted
      • Use read only attributes in XPath constraints
      • Anonymous users can only change own data
      • Anonymous users cannot change unlimited length strings
      • Domain model standards
      • Anonymous user access restricted
      • Naming standards - Domain Model
      • Documentation standards - Domain Model
    • Enumerations
      • Naming Standards - Enumerations
    • Microflows
      • Incorrect date format
      • Incorrect empty string check
      • Empty variable used
      • Apply entity access when generating documents
      • Use inherited entities from System module
      • Web service calls with templates should be escaped
      • Naming Standards - Microflows
      • Logging Standards - Microflows
      • Documentation Standards - Microflows
    • Pages
      • Attributes in data views should be editable
      • Naming Standards - Page Flows
      • Documentation Standards - Pages
  • Support
    • Docs
    • Feedback
    • Tickets
    • Releases
    • System Status
    • User Details
Powered by GitBook
On this page
  1. Dashboards
  2. Releases

Create Release

When you create a new release you first need to select the pipeline to use. Pipelines can be selected from one of the follolowing pipeline libraries. (Note: When creating a new release from the App page the 'App Pipelines' library is automatically selected):

  • Global Pipelines. All global pipelines.

  • Group Pipelines. All piplines that belong to the App Group that the selected app belongs to.

  • App Pipelines. All app-specific pipelines that have been created for the selected app.

After selecting the pipeline you want to use the manage release page appears.

Release Status

This tile shows status information about this pipeline:

  • Current status. The current status of the release. The following are the possible statuses:

    • Scheduled : The release is scheduled for execution.

    • Not started : The release has not yet been submitted to the release scheduler and can still be changed. This is the default status for a new release.

    • Waiting approval : The release is waiting for an approval before it begins execution.

    • Running : The release is currently running.

    • Successful : The release has successfully completed

    • Warning : The release completed but generated warnings.

    • Failed : The release failed to complete successfully.

    • Scheduled : The release is scheduled for execution but has not yet started.

  • Last message. The most recent output of the release.

Configuration

The pipeline configuration tile shows the configuration that is being used for the execution of this release. When you create a new release the following options are available:

  • Environment. The target environment for this release. Note: If this has been pre-configured in the pipeline it cannot be changed.

  • Configuration. If the selected pipeline has a 'Deploy Configuration' task, select the configuration to be used. Configurations are specific to the environment that you have selected. The list of configurations that are available can be managed from the Configurations tab for each environment in the App page.

  • Branch. The source branch for this release. Note: If this has been pre-configured in the pipeline it cannot be changed.

  • Revision. The source revision for this release. Note: If this has been pre-configured in the pipeline it cannot be changed.

  • Scheduled for. The date and time when this release is scheduled to be executed.

  • Scheduled for (after approvals). If the pipeline contains an approval task, and the 'Proceed on approvals' option is NOT checked, this pipeline will continue executing at this date and time. This option is used for delaying the execution of a pipeline after all approvals have been received.

  • Commit message. The last commit message for the source revision used by this release.

  • Mendix version. The version of Mendix used by the source revision used by this release.

  • Release version. The version number to be used for this release.

  • Release notes. The release notes to be used for this release.

Pipeline Tasks

This tile shows an overview of the pipeline tasks that have been configured for this release. For each task the current status is displayed as well as the last message that was output by the task.

PreviousReleasesNextTasks

Last updated 1 month ago