I'm attempting to add a badge to my GitHub repo showing the status of unit tests. I followed the guide, shown here, and produced the following change to my repo:
[](https://github.com/xefino/goutils/actions)
However, when I navigate to the repo's page on GitHub, I see that the action shows "No Status". I understand, from this question, that the name described in the workflow's YAML file has to match the URL, which mine does. So I'm having trouble understanding why I'm not seeing a status on the badge. Does anyone have any information on this?
I discovered the issue here. My URL was not actually correct, not because of some typo, but because the format had changed. So, doing this worked:
[](https://github.com/xefino/goutils/actions)
Related
I followed this link to add Github Actions.
I see the actions are getting executed without any error
But in coveralls.io dashboard, the badge is always unknown.
I tried many combinations in github actions still couldnt get the valid coverage badge.
https://coveralls.io/github/kubernetes-sigs/ibm-vpc-block-csi-driver
https://github.com/kubernetes-sigs/ibm-vpc-block-csi-driver
I got where I went wrong.
https://github.com/mattn/goveralls/issues/202
Working as expected when PR got merged
I've documented a function and I can see that the generator has captured the line number:
Is it possible to configure TypeDoc so that a user can click through to see the actual source code? The full repository is here.
There is a TypeDoc plugin that might address your problem:
https://github.com/gdelmas/typedoc-plugin-sourcefile-url
It doesn't work for my situation because for some reason the URLs to the GitHub source I'm connecting to must contain blob/master, which this plugin doesn't add. But I add it here in case it's useful to you.
I'm new to GitHub's template repositories. We've created a template repo for our course's code labs. Let's say it's on GitHub under myorg/labX. The students are using GitHub Classroom, which clones the template repo for each student under myorg/labX-studentlogin. We've got actions to run some tests against their code using GitHub's own CI, and I want to include badges in the repo's README.md to see the test results at a glance. So I know that
will include the badge, but this is the status of the template repo, not student repos. Is there a way to automate this so that when the students get their clone, it will contain a README with the URL that refers to the status of their own repo?
Turns out there is a simple solution, but only for GitHub's own Actions status badges. We've changed the image URL in our README.mds to relative.
The only minor thing is GitHub will insert /blob/<branch>/ into relative links when rendering the readmes.
For example, workflows/task1/badge.svg will become https://github.com/myorg/labX/blob/master/workflows/task1/badge.svg), which won't render. So we had to prepend '../../' to fool it.
TLDR: in repo's README.md, use
to get a badge for an Action status in this repo. This way, each student will get a badge referring to his own repo, not the template repo.
However, still looking for a way to use an external badge service like shields.io in a way relative to the repo.
I agree it would be a great feature to have.
It looks like at this point, GitHub Template Repositories do not support variable substitution, which is what would make it possible.
I see it is discussed briefly here:
Variable substitution for GitHub Template Repository Usage
Perhaps you should join the discussion and/or cast your Kudo.
I'm trying to publish https://bintray.com/mvysny/github/com.github.kaributesting onto JCenter, but the process fails with "Failed to send a message: The version control git returns 404.". Any tips on this please? Bintray, could you please make your error messages a bit more specific?
The reason was that I simply had "git" stated in the Version control field. The field's hint says it should be URL but the field is not validated, so git was accepted. I think it's supposed to point to the sources of the project. When I changed that to https://github.com/mvysny/karibu-testing it worked.
I'm having a heck of a time trying to publish any HTML report with htmlpublisher.
My input looks like this:
And the 404 looks like this:
The report is definitely generated in build/. I've visually compared my config.xml file to a known working example and it's apparently the same. The entry in jobs/ is there, with the correct name and documentation.
I can't figure out what I'm doing wrong. I've checked the "keep past HTML reports" box, unchecked it, played with the paths, read the (poor) documentation but I can't seem to get it working. Can anyone help?
What version of Jenkins are you running? I'm seeing this issue on all of my projects since updating to 1.529. The files are being copied to jobs/ correctly as you mentioned.
The answer you accepted is incorrect and contradicts the documentation at https://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin
EDIT: The issue has been resolved in 1.530: https://jenkins-ci.org/changelog
I've updated and I'm not seeing 404s anymore.
The developers of Jenkins has confirmed that this issue is related to the version 1.529 and it is solved in 1.530.