Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
* @jenkinsci/.-plugin-developers
* @jenkinsci/vigilnz-security-plugin-developers
4 changes: 0 additions & 4 deletions .github/release-drafter.yml

This file was deleted.

54 changes: 54 additions & 0 deletions .github/workflows/cd.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
# Note: additional setup is required, see https://www.jenkins.io/redirect/continuous-delivery-of-plugins
#
# Please find additional hints for individual trigger use case
# configuration options inline this script below.
#
---
name: cd
on:
workflow_dispatch:
inputs:
validate_only:
required: false
type: boolean
description: |
Run validation with release drafter only
→ Skip the release job
# Note: Change this default to true,
# if the checkbox should be checked by default.
default: false
# If you don't want any automatic trigger in general, then
# the following check_run trigger lines should all be commented.
# Note: Consider the use case #2 config for 'validate_only' below
# as an alternative option!
check_run:
types:
- completed

permissions:
checks: read
contents: write

jobs:
maven-cd:
uses: jenkins-infra/github-reusable-workflows/.github/workflows/maven-cd.yml@v1
with:
# Comment / uncomment the validate_only config appropriate to your preference:
#
# Use case #1 (automatic release):
# - Let any successful Jenkins build trigger another release,
# if there are merged pull requests of interest
# - Perform a validation only run with drafting a release note,
# if manually triggered AND inputs.validate_only has been checked.
#
validate_only: ${{ inputs.validate_only == true }}
#
# Alternative use case #2 (no automatic release):
# - Same as use case #1 - but:
# - Let any check_run trigger a validate_only run.
# => enforce the release job to be skipped.
#
#validate_only: ${{ inputs.validate_only == true || github.event_name == 'check_run' }}
secrets:
MAVEN_USERNAME: ${{ secrets.MAVEN_USERNAME }}
MAVEN_TOKEN: ${{ secrets.MAVEN_TOKEN }}
19 changes: 0 additions & 19 deletions .github/workflows/release-drafter.yml

This file was deleted.

1 change: 1 addition & 0 deletions .mvn/maven.config
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
-Pconsume-incrementals
-Pmight-produce-incrementals
-Dchangelist.format=%d.v%s
38 changes: 22 additions & 16 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,9 @@

<!-- Plugin Name -->
<name>Vigilnz Security</name>
<description>Vigilnz Security Plugin integrates security scanning capabilities into Jenkins. Run CVE, SAST, SBOM, and other security scans as part of your CI/CD pipeline.</description>
<description>Vigilnz Security Plugin integrates security scanning capabilities into Jenkins. Run CVE, SAST, SBOM,
and other security scans as part of your CI/CD pipeline.
</description>
<url>https://github.com/${gitHubRepo}</url>
<licenses>
<license>
Expand All @@ -32,18 +34,18 @@
<tag>${scmTag}</tag>
<url>https://github.com/${gitHubRepo}</url>
</scm>
<developers>
<developer>
<id>vigilnz</id>
<name>Vigilnz Team</name>
<email>[email protected]</email>
</developer>
</developers>

<!-- <developers>-->
<!-- <developer>-->
<!-- <id>vigilnz</id>-->
<!-- <name>Vigilnz Team</name>-->
<!-- <email>[email protected]</email>-->
<!-- </developer>-->
<!-- </developers>-->

<properties>
<revision>1.0</revision>
<changelist></changelist>
<changelist>999999-SNAPSHOT</changelist>
<!-- https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ -->
<jenkins.baseline>2.516</jenkins.baseline>
<jenkins.version>${jenkins.baseline}.3</jenkins.version>
Expand All @@ -52,15 +54,14 @@
<spotless.check.skip>false</spotless.check.skip>
<ban-junit4-imports.skip>false</ban-junit4-imports.skip>
<hpi.strictBundledArtifacts>true</hpi.strictBundledArtifacts>
<hpi.bundledArtifacts>jackson-annotations,jackson-core,jackson-databind</hpi.bundledArtifacts>
</properties>

<dependencyManagement>
<dependencies>
<dependency>
<groupId>io.jenkins.tools.bom</groupId>
<artifactId>bom-${jenkins.baseline}.x</artifactId>
<version>5659.vecf9e2dc5a_ed</version>
<version>5750.vec44cb_c78352</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Expand All @@ -87,7 +88,7 @@
<dependency>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>credentials</artifactId>
<version>1337.v60b_d7b_c7b_c9f</version>
<!-- <version>1337.v60b_d7b_c7b_c9f</version>-->
</dependency>

<!-- Pipeline Step API -->
Expand All @@ -112,10 +113,15 @@
<scope>provided</scope>
</dependency>

<!-- <dependency>-->
<!-- <groupId>com.fasterxml.jackson.core</groupId>-->
<!-- <artifactId>jackson-databind</artifactId>-->
<!-- <version>2.20.1</version>-->
<!-- </dependency>-->

<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.20.1</version>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>jackson2-api</artifactId>
</dependency>

</dependencies>
Expand Down
Loading