Signing a release bundle that includes artifacts from the build with the name or with a number larger than 64 chars fails. While generating a public key, clicking the eye icon and then clicking copy creates different spacing in the public key compared to the key spacing without clicking the icon. JIRA integration - the status code when trying to get all labels with an invalid integration name is 500 instead of 404. JIRA integration - the status code when trying to get all Jira projects with an invalid integration name is 500 instead of 404. ![]() JIRA integration - the status code when trying to get the issue types with an invalid integration name and ticketing project is 500 instead of 404 (when specifying which parameter is wrong). JIRA integration - the status code when using an invalid integration name is 200 instead of 404. JIRA integration - the status code when trying to delete a non-existent integration is shown as 200 instead of 404. JIRA integration - the validation of the auth type during creation and update is missing, which means that the user can create an integration with any authType. JIRA integration - the API allows the creation of an integration with empty values. Some oauth2 fields are missing when clicking edit for the first time after creation. JIRA integration - for the oauth2 auth integration, w hen mandatory keys are missing in the payload, the response should mention which exact keys are missing. JIRA integration - for the oauth1 auth integration, w hen mandatory keys are missing in the payload, the response should mention which exact keys are missing. JIRA integration - for the basic auth integration, w hen mandatory keys are missing in the payload, the response should mention which exact keys are missing. Updating a profile gives the wrong status code. To check whether a released version has a known issue detected in it, look for the version number. Affected Versionįor each product below, you will find the version in which a know issue (or issues) was detected in. ![]() When considering an upgrade to your system, we recommend that you review the Known Issues below (including the database schema issues that follow) to help you determine which is the right upgrade for your system. In this document, you will find the issues that met the criteria above and that were detected in a released version (only). Issues that have caused downtime and restarts.Known issues are based on the following criteria: For JFrog Artifactory issues, click the issue ID for the details in JIRA. The following document lists the set of known issues in the JFrog Platform, including the version in which they were discovered, and the version in which they were fixed (if relevant).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |