| January 13, 2023 |
Git Enhancements:
- Git Credentials view/editor – Since a given Git Server will often contain many repositories that should be accessed with the same credentials, credentials are now distinctly defined using option Git Credentials from the settings panel. A credential ID can then be applied to all repositories requiring the same authentication, making it simpler to add repositories or change a password or key pair.
- no longer necessary to define a Git ID per repository branch. Instead, only the main branch needs to be defined, which is then used for cross-referencing, while any feature branches are managed at the Continuous Integration level
- if the Git server is of type Azure DevOps, Bitbucket, GitHub or GitLab, it can be tied to a pipeline server which defines the REST URL and credentials for the possibility of easily generating Webhooks on the server for triggering actions by MDCMS (using new Webhooks option for the Git Repository) and for automatically creating pull requests
- The SSH Key handler has been updated to support all current SSH encryption standards
- new Explore option on the Git Repository to view the working tree of the main branch of the Repo from the MDXREF IFS view (once cloned to MDCMS)
- new option Re-Clone Main Branch to easily refresh the contents of the branch in case the local copy is no longer in sync
|
|
Continuous Integration Enhancements:
- automated requests from Git can now be against the main branch, any branch except the main branch, or any other specific branch, which can be selected from the content-assist list
- files to be requested can be filtered by a file naming pattern, such as *.RPGLE
- Parameter Map to IFS Path added for when requesting source for IBM i objects. If a value is provided, it will aid MDCMS in ascertaining the correct MDCMS attribute for new source when the target source is stored in the IFS with the same structure as in the Git working tree
- *BRANCH can be used as a special value for the Project in order to map the Project/Task/Subtask based on the branch name
- Parameter Auto-Create in Dev Lib added to automatically attempt to create the objects in the developer library for the requested source, along with any auto-requested dependencies
- Pull-Request Location/Level parameters added to define at which point in the deployment process a pull request should be automatically generated for merging the changes in the feature branch back into the main branch.
|
|
Object Requests can now more easily be locked or unlocked by right-clicking on one or many Object Requests and then selecting the Lock Request or Unlock Request option. These options are also available as favorites. |
|
An RFP in the Send Listing can be closed directly from the Send RFP to Target Systems dialog |
|
When creating a new RFP while requesting objects, the default RFP description will by default be the summary of the Project, Task or Subtask, depending on what the object request will be assigned to. |
| February 19, 2023 |
If the Project mapping for a Continuous Integration definition is set to *BRANCH, the Webhook will first check if a custom Project/Task field is defined and assigned the wildcard value of ++BRANCH++.
If this is the case, the Webhook will use the newest task/subtask that has the custom field value set to the name of the feature branch.
If not found, the Webhook will check if the branch name = a Task Reference ID or MD Project/Task name just as it did in the past. |
| February 26, 2023 |
Git Webhook Deliveries view – every time that a Git Webhook to MDCMS is delivered, this can now be viewed/filtered directly within MDOpen.
If the delivery for the specific push needs to be repeated, option Repeat can be used for a delivery, which is very helpful when the configuration on the MDOpen side needed to be altered.
If Object Requests were attempted for the delivery, they can also be listed and filtered, providing comprehensive and easy-to-use auditing and troubleshooting for Continuous Integrations. |
|
When requesting to modify an object of MDCMS type *SQL…, the DDL code can be automatically generated based on the SQL or DDS object definition and the code will be placed in the selected target member or IFS file.
In MDOpen, use the button Generate DDL Source |
