Merge pull request jenkinsci#225 from jenkinsci/chore/master/misc-modernization

Enable CD

Author: NotMyFault

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @jenkinsci/tikal-multijob-plugin-developers

.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+  - package-ecosystem: maven
+    directory: "/"
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 10
+    target-branch: master
+    labels:
+      - dependencies
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: daily

.github/release-drafter.yml

@@ -0,0 +1 @@
+_extends: .github

.github/worklfows/cd.yaml

@@ -0,0 +1,57 @@
+name: cd
+on:
+  workflow_dispatch:
+  check_run:
+    types:
+      - completed
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    outputs:
+      should_release: ${{ steps.verify-ci-status.outputs.result == 'success' && steps.interesting-categories.outputs.interesting == 'true' }}
+    steps:
+      - name: Verify CI status
+        uses: jenkins-infra/[email protected]
+        id: verify-ci-status
+        with:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          output_result: true
+
+      - name: Release Drafter
+        uses: release-drafter/release-drafter@v5
+        if: steps.verify-ci-status.outputs.result == 'success'
+        with:
+          name: next
+          tag: next
+          version: next
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Check interesting categories
+        uses: jenkins-infra/[email protected]
+        id: interesting-categories
+        if: steps.verify-ci-status.outputs.result == 'success'
+        with:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+  release:
+    runs-on: ubuntu-latest
+    needs: [validate]
+    if: needs.validate.outputs.should_release == 'true'
+    steps:
+      - name: Check out
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - name: Set up JDK 11
+        uses: actions/setup-java@v3
+        with:
+          distribution: temurin
+          java-version: 11
+      - name: Release
+        uses: jenkins-infra/[email protected]
+        with:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          MAVEN_USERNAME: ${{ secrets.MAVEN_USERNAME }}
+          MAVEN_TOKEN: ${{ secrets.MAVEN_TOKEN }}

.github/worklfows/jenkins-security-scan.yml

@@ -0,0 +1,15 @@
+name: Jenkins Security Scan
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    types: [ opened, synchronize, reopened ]
+  workflow_dispatch:
+
+jobs:
+  security-scan:
+    uses: jenkins-infra/jenkins-security-scan/.github/workflows/jenkins-security-scan.yaml@v2
+    with:
+      java-cache: '' # Optionally enable use of a build dependency cache. Specify 'maven' or 'gradle' as appropriate.
+      java-version: 11 # What version of Java to set up for the build.

.mvn/extensions.xml

@@ -0,0 +1,7 @@
+<extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd">
+    <extension>
+        <groupId>io.jenkins.tools.incrementals</groupId>
+        <artifactId>git-changelist-maven-extension</artifactId>
+        <version>1.3</version>
+    </extension>
+</extensions>

.mvn/maven.config

@@ -0,0 +1,3 @@
+-Pconsume-incrementals
+-Pmight-produce-incrementals
+-Dchangelist.format=%d.v%s

MIT-LICENSE.txt LICENSE.txtMIT-LICENSE.txt renamed to LICENSE.txt

@@ -1,17 +1,18 @@
+## Does anyone want to become a maintainer of this plugin?
+This plugin was very popular for many years, but since most of Jenkins usage now is based on Jenkins Pipeline, and the 'parallel' step along with 'BlueOcean' can basically do whatever this plugin does, it is no longer in [Tikal's radar](https://fullstackradar.tikalk.com/tikal/radar/index.html).
+Also, we published the [parallelPhase library class](https://github.com/TikalCI/tci-library/blob/master/src/tci/pipeline/parallelPhase.groovy) that can do in pipelines what the plugin does.
+Still, there are many users of the plugin that asked for fixes and new features, so we'll appreciate anyone willing to become a maintainer of the plugin.
+
 ## When to use MultiJob (tikal-multijob-plugin) plugin ?
 - If you'd like to stop the mess with downstream / upstream jobs chains definitions
 - When you want to add full hierarchy of Jenkins jobs that will be executed in sequence or in parallel
 - Add context to your buildflow implementing parameter inheritance from the MultiJob to all its Phases and Jobs, Phases are sequential whilst jobs inside each Phase are parallel
 
-### More info on wiki page @: https://wiki.jenkins.io/display/JENKINS/Multijob+Plugin
+### More info on wiki page @: https://plugins.jenkins.io/jenkins-multijob-plugin/
 
 ### Found a bug ? require a new feature ?
 #### Feel free to open an issue: https://github.com/jenkinsci/tikal-multijob-plugin/issues
 ****
-### Plugin CI job: https://jenkins.ci.cloudbees.com/job/plugins/job/tikal-multijob-plugin/
 
 ========
-## Does anyone want to become a maintainer of this plugin???
-This plugin was very popular for many years, but since most of Jenkins usage now is based on Jenkins Pipeline, and the 'parallel' step along with 'BlueOcean' can basically do whatever this plugin does, it is no longer in [Tikal's radar](https://fullstackradar.tikalk.com/tikal/radar/index.html).
-Also, we published the [parallelPhase library class](https://github.com/TikalCI/tci-library/blob/master/src/tci/pipeline/parallelPhase.groovy) that can do in pipelines what the plugin does.
-Still, there are many users of the plugin that asked for fixes and new features, so we'll appreciate anyone willing to become a maintainer of the plugin.
+