You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flagon.apache.org by "Joshua Poore (JIRA)" <ji...@apache.org> on 2019/05/12 02:26:00 UTC

[jira] [Resolved] (FLAGON-384) useralejs Jenkins build is failing (#32-33)

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

Joshua Poore resolved FLAGON-384.
---------------------------------
    Resolution: Not A Problem

action is to update configs or raise issue with builds.

> useralejs Jenkins build is failing (#32-33)
> -------------------------------------------
>
>                 Key: FLAGON-384
>                 URL: https://issues.apache.org/jira/browse/FLAGON-384
>             Project: Flagon
>          Issue Type: Bug
>          Components: UserALE.js
>    Affects Versions: UserALE.js 1.0.0
>            Reporter: Joshua Poore
>            Assignee: Joshua Poore
>            Priority: Trivial
>             Fix For: UserALE.js 1.0.0
>
>         Attachments: CIFail32useralejs, useralejsNODE4_6_0_replication.rtf
>
>
> [https://builds.apache.org/job/useralejs-ci/32/] [^CIFail32useralejs]
> Jenkins build failed after recent [commit|[https://github.com/apache/incubator-flagon-useralejs/commit/4bb5ebe8be228242861556c31ac6f4b78b929177]].
> This is weird because the commit exclusively incorporated changes to text referencing SensSoft, and links (Flagon–>SensSoft). This triggered a build test on Jenkins, which failed (see attachment). 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)