Cirrus-ci-docs: Badge is reporting 'not found' when actually passing

Created on 27 Mar 2019  路  17Comments  路  Source: cirruslabs/cirrus-ci-docs

image
... as seen in:
https://github.com/brianegan/flutter_architecture_samples
This is the currently passing build:
https://cirrus-ci.com/build/6482870825648128
May have something to do with being a first build,... or manual reruns on a task, for example:
https://cirrus-ci.com/task/5753077868003328

bug question

All 17 comments

Weird since the link points to the right badge: https://api.cirrus-ci.com/github/brianegan/flutter_architecture_samples.svg

I see a green badge in your comment...

Could it be that GitHub cached the redirect when it was failing?

Some mystery of GitHub rendering... Let me poke around... 馃

Seems GH pre-renders Markdown and caches it. Not sure how to avoid it.

Screen Shot 2019-03-27 at 4 45 17 PM

Right, I'm seeing
image
now.
Maybe it rebuilds cache periodically. (I was doing a bunch of re-runs due to transient flutter timeouts about an hour or so ago). Will report back if I see a change.

BTW: I am currently seeing:
image
in
https://github.com/niieani/bash-oo-framework
which is a first build as of about 20 minutes ago:
https://github.com/niieani/bash-oo-framework/pull/83

@mmcc007 I've switched away from redirecting to cacheble shields to proxying them with no-cache. Should fix the issue but will need to wait for GitHub to invalidate the cache.

FYI:
https://github.com/brianegan/flutter_architecture_samples
is showing the passing badge correctly.

https://github.com/niieani/bash-oo-framework
is still showing the 'not found' badge when actually passing

Seems bash-oo-framework still cached:

image

brianegan/flutter_architecture_samples also seems to be still cached (if I'm reading this correctly)

Screen Shot 2019-03-28 at 1 20 45 PM
But anyway, it's bound to invalidate cache at some point... so I'm not going to worry about it 馃榾

This is happening with me for 5 (five) weeks.

https://api.cirrus-ci.com/github/<USER OR ORGANIZATION>/<REPOSITORY>.svg


image

@claudioandre-br it seems your default branch is not test so you need explicitly specify it in the URL:

https://api.cirrus-ci.com/github/claudioandre-br/JohnTheRipper.svg?branch=test

Or once there will be a build for the default bleeding-jumbo branch, then the badge will work. 馃憣

Should probably consider using a different image for branches with no builds yet. The image might be a bit non-intuitive for some (like first time users).
For example, travis shows:
Screen Shot 2019-06-08 at 8 48 14 AM
and suggests creating a build.
https://travis-ci.com/mmcc007/default_flutter_app

Cirrus provides no similar suggestions (other than a plus sign):
https://cirrus-ci.com/github/mmcc007/default_flutter_app
which may be a little non-intuitive for first time users.

Another option is to use overall the latest build if there is none for the default branch 馃

Or once there will be a build for the default bleeding-jumbo branch, then the badge will work. ok

Another option is to use overall the latest build if there is none for the default branch thinking

There is no "default branch thinking" or I'm still doing something wrong. The default-branch is bleeding-jumbo not master. So:

Build Status (no branch info)
Build Status (using ?branch=master)
Build Status (using ?branch=bleeding-jumbo)
Build Status (using ?branch=test)

@claudioandre-br It was still defaulting to master for your repo. Should be working now. Sorry for the inconvenience!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

plicease picture plicease  路  5Comments

iskakaushik picture iskakaushik  路  5Comments

cjdb picture cjdb  路  5Comments

pzahemszky picture pzahemszky  路  5Comments

hilbix picture hilbix  路  3Comments