Skip to main content
All CollectionsRelease Notes
Release 23.02.01--Checkmarx and Codescan integration, notification to JIRA when backing up changes to GIT
Release 23.02.01--Checkmarx and Codescan integration, notification to JIRA when backing up changes to GIT

Checkmarx and Codescan integration, new trial activation page, update UX for approval process.

S
Written by Shreya Reddy Kommidi
Updated over a month ago

Enable Checkmarx and Codescan for all Essentials Plus users

Users with Essentials Plus licenses now have access to Checkmarx and Codescan integration. For on-premise versions of these apps, you may need to add the Essentials application IPs to the Checkmarx or Codescan whitelists.

In Work Items, send notification to JIRA when backing up changes to GIT

Trial Activation Page

New page where Free Users can go to activate their Essentials+ trial

Changes under approval process

  • Have a filter on the approval column in the Work Item List view

  • If the Work Item is not being approved, do not show the deploy button, show the “Request Approval” button instead

Bugs fixed:

  • User able to trigger CI job via API with "View" only access to the job

  • Fix bug "checkRestrictedUrl" support -git specific URL

    This bug fix addresses an issue in Copado Essentials where the function that checks for restricted URLs (called checkRestrictedUrl) was not properly supporting URLs specific to Git repositories.

    Here's what might have been happening before the fix:

    • Restricted URL checks: Copado Essentials likely has a security or compliance feature to prevent users from accessing or deploying to certain restricted URLs. This might include repositories that are private, internal, or blacklisted for security reasons.

    • Git-specific URLs: Git repositories often have unique URL formats (e.g., https://github.com/user/repo.git or git@github.com:user/repo.git), and it seems that the checkRestrictedUrl function wasn’t handling these correctly.


    With this bug fix, Copado Essentials now properly recognizes and processes these Git-specific URLs during the restriction check, ensuring that any restricted Git repository URLs are correctly flagged or allowed, depending on their status.

    In essence, this makes the restricted URL check feature compatible with the URL formats typically used in Git repositories.

Did this answer your question?