Adding build badge #71

Merged
merged 5 commits into from Feb 14, 2017

Conversation

Projects
None yet
3 participants
Member

ktsakalozos commented Feb 13, 2017

No description provided.

ktsakalozos and others added some commits Feb 13, 2017

Use dynamic badge template
The badge will now show the results for each individual controller,
rather than the total build pass / fail.

The URL of the badge was simplified as well.
Owner

johnsca commented Feb 14, 2017

Updated to use a dynamic badge template. Now, instead of getting a single pass / fail result, we will get info about each controller:

badge

One side-effect of this is that the Jenkins job names were changed so that they match up with the CWR name, both reported and on disk. I also removed the REST API prefix from the badge URL because it's more friendly and it's not truly an API endpoint.

Member

ktsakalozos commented Feb 14, 2017

I did not have much luck with testing this PR.

Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-cwr5-0/charm/scripts/bundlebuilder.py", line 13, in <module>
    from actions.cwrhelpers import get_fname
ImportError: No module named 'actions'

And then unit tests fail as well.

Member

kwmonroe commented Feb 14, 2017

Looks GREAT to me!

@kwmonroe kwmonroe merged commit c4c3506 into master Feb 14, 2017

0 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error
Details
continuous-integration/travis-ci/push The Travis CI build could not complete due to an error
Details

@kwmonroe kwmonroe deleted the feature/build-badge branch Feb 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment