sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radu Cotescu (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-9047) The CIStatusValidator cannot verify multi-module releases
Date Wed, 05 Feb 2020 12:40:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Radu Cotescu resolved SLING-9047.
---------------------------------
    Resolution: Fixed

Fixed inĀ [commit 646b413|https://github.com/apache/sling-org-apache-sling-committer-cli/commit/646b413].

> The CIStatusValidator cannot verify multi-module releases
> ---------------------------------------------------------
>
>                 Key: SLING-9047
>                 URL: https://issues.apache.org/jira/browse/SLING-9047
>             Project: Sling
>          Issue Type: Bug
>          Components: Tooling
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Committer CLI 1.0.0
>
>
> The {{CIStatusValidator}} cannot verify multi-module releases, since the current algorithm
for detecting the GitHub endpoint for retrieving the build status [0] relies on the artifact
name + version for the reference. This works for regular single-module releases, since the
tag corresponds to the artifact name + version. However, in the case of multi-module releases
the validator fails. The reliable way of validating releases is by just using the tag name,
which in the case of a release available in the pom.
> [0] - https://developer.github.com/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message