Comments (2)
I am not the author of this plugin, but maybe my experience can help.
I tried to figure out how to use this plugin in a similar way to an older configuration we had using a different Git server, where we defined all of the webhooks and triggers and jobs and views manually. I was not able to figure out how to give the Gitea Checks plugin the proper credentials so that it could submit the job results back to the PR or commit which had triggered it.
But when I tried using it in combination with the Gitea plugin, this plugin just worked without any special configuration. All of the actual configuration was on the Gitea plugin side.
Here's how I set that up.
- I set up a
hello-world
org in gitea with ahello-world/hello-world
repo, and stuck a.jenkinsfile
pipeline in there which ranmake run
andmake test
. - I added a credential to Jenkins, of type
Gitea Personal Access Token
. - Then, in my Jenkins dashboard view, I created a view named
hello-world
, of typeGitea Organization
. - In the configuration of that view, I told it where to find the
hello-world
org and that the pipeline filename it should look for is.jenkinsfile
.
It automatically went and found the hello-world/hello-world
repo, registered a webhook on that repo, and set up a hierarchy of job views to represent the repo, branches, and PRs. It triggered the job to run when I pushed a commit or created a PR. With all of that in place, this Gitea Checks plugin submits results to the right place. I see green checkboxes on commits which passed tests, and I see latest build results and verified
tags on PRs. The result was very clean, this integration makes new setups quite easy.
The build log includes messages like this:
[Gitea] Notifying branch build status: SUCCESS This commit looks good
[Gitea] Notified
However, it's unclear how to migrate older sets of CICD jobs over to Gitea without rewriting everything all at once. If anyone knows a way to set it up to submit check results, specifying credentials and locations manually, without all of the auto discovery stuff, that would be helpful.
from gitea-checks-plugin.
There is no configuration, it will just work when you use gitea connection for your multibranch pipeline.
Your can publish custom checks, see checks-api
plugin
https://plugins.jenkins.io/checks-api/#plugin-content-pipeline-usage
from gitea-checks-plugin.
Related Issues (5)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gitea-checks-plugin.