Tags: jenkinsci/gitea-plugin
Tags
Bump org.apache.maven.plugins:maven-checkstyle-plugin (#75) Bumps [org.apache.maven.plugins:maven-checkstyle-plugin](https://github.com/apache/maven-checkstyle-plugin) from 3.1.2 to 3.4.0. - [Commits](apache/maven-checkstyle-plugin@maven-checkstyle-plugin-3.1.2...maven-checkstyle-plugin-3.4.0) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-checkstyle-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Add gitea release handling (#60) This PR adds the ability to discover releases in gitea as "branches" to be build seperatly. It also adds an task for pipelines ("publishGiteaAssets") which works a little like copyArtifacts but uploads artifacts as an asset to the current building release. The PR also contains an (toggleable) feature to "map" artifacts originally created via copyArtifacts to gitea release assets. Relevant issues: - [JENKINS-67790 - Upload built artifacts](https://issues.jenkins.io/browse/JENKINS-67790)
Fix JENKINS-69719: Fetch PR data from target repo (#67) Jenkins token permissions potentially invalid to access source repo. This is the cause of issue [JENKINS-69719](https://issues.jenkins.io/browse/JENKINS-69719). All required Gitea Pull Request data can be accessed via target repo. Replace access to potentially inaccessible source repository by references in target repository Pull Request head. ### Testing done The change affects token/credential permission scope on the Gitea server. With the changed source for data access, the `MultiBranchPipeline` scan completes. Jenkins can pull/checkout (moving) head of pull request. Resolution to commit hash is done independently in body of `GiteaSCMFileSystem` constructor.
PreviousNext