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

Allen Wittenauer updated YETUS-1005:
------------------------------------
    Description: 

Problem 1: CIRRUS_BUILD_ID goes missing

According to my read of 
https://cirrus-ci.org/guide/writing-tasks/#environment-variables, 
CIRRUS_BUILD_ID should be getting defined but clearly it is not in some 
instances.  This may be an intermittent but in Cirrus or something else going 
wrong.  In any case, we should provide a value if one is missing. It might also 
be worthwhile to look at all of the vars and see what else has changed/added.

Problem 2:  junit

Looks like junit artifacting has changed a bit and our sample isn't quite 
getting the junit results back.

  was:According to my read of 
https://cirrus-ci.org/guide/writing-tasks/#environment-variables, 
CIRRUS_BUILD_ID should be getting defined but clearly it is not in some 
instances.  This may be an intermittent but in Cirrus or something else going 
wrong.  In any case, we should provide a value if one is missing. It might also 
be worthwhile to look at all of the vars and see what else has changed/added.


> Update Cirrus CI Support
> ------------------------
>
>                 Key: YETUS-1005
>                 URL: https://issues.apache.org/jira/browse/YETUS-1005
>             Project: Yetus
>          Issue Type: Bug
>            Reporter: Allen Wittenauer
>            Priority: Minor
>
> Problem 1: CIRRUS_BUILD_ID goes missing
> According to my read of 
> https://cirrus-ci.org/guide/writing-tasks/#environment-variables, 
> CIRRUS_BUILD_ID should be getting defined but clearly it is not in some 
> instances.  This may be an intermittent but in Cirrus or something else going 
> wrong.  In any case, we should provide a value if one is missing. It might 
> also be worthwhile to look at all of the vars and see what else has 
> changed/added.
> Problem 2:  junit
> Looks like junit artifacting has changed a bit and our sample isn't quite 
> getting the junit results back.



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

Reply via email to