-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a probe for failing builds on the default branch #363
Comments
Hi, @NotMyFault @alecharp I want to take this issue. can you please assign to me ? |
There is a probe already written that is JenkinsfileProbe. I guess this is the extend probe. we need to check only the default branch is build status |
@NotMyFault @alecharp Do we have any specific documentation to understand the different libraries used in the plugin? I understand most of the, but I have not been able to find a way to interact with the default branch and fetch the build status.
The New probe seems like to similar just need to add the status of the check API in the return statement, but i cannot able to figure out what is check API ? Can you please guide me a little bit |
Hello @AayushSaini101.
Well no, each library we use have their own documentation, which we don't duplicate in this project. To get the default branch of a plugin, you can see that you can find that information in the GitHub API, more specifically in the GHRepository class. To interact with GitHub API, we use https://github.com/hub4j/github-api. Please see its documentation and maybe you need to browse its source code to have a better grasp at what you can do with it. |
hello, @NotMyFault @alecharp , i can fix this issue. can you please assign me. |
@Peakycode99 Hi I have already made a PR I will try to complete by this week. |
Description
If the project has as
Jenkinsfile
in the root directory, the probe should obtain the build status published through the checks API, whether it fails on ci.jenkins.io or not.Failing builds on the default branch are a good indicator, that the project is in a bad state and requires (maintainer) attention.
The text was updated successfully, but these errors were encountered: