Skip to content
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

chore(deps-dev): bump jenkins-pipeline-unit from 1.3 to 1.8 #5

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jan 18, 2021

Bumps jenkins-pipeline-unit from 1.3 to 1.8.

Release notes

Sourced from jenkins-pipeline-unit's releases.

Release 1.8

Release 1.7

Release 1.6

🚀 New features and improvements

Release 1.5

Release 1.4

... (truncated)

Changelog

Sourced from jenkins-pipeline-unit's changelog.

Release Procedure

pre-requirements

In order to release new version you need jenkins.io account, push rights to this repository and access to jenkins jfrog artifactory. See jenkins plugin adoption procedure

Overview

In short release procedure could described in following steps:

  1. Update version in gradle.properties and create new commit
  2. Place a new tag
  3. Build and publish artifacts to repo.jenkins.io/releases maven repository (jar, src, docs)
  4. Update version in gradle.properties for next development cycle
  5. Add new release notes to github

NOTE: repo.jenkins.io/releases has a delay (1-2d) in publishing artifacts to public so mark new release notes as pre-release once artifacts are avalible pre-release label could be removed.

Tools

To automate steps abobe JPU uses a vary of gradle plugins and github actions scitps

Gradle plugins

net.researchgate.release

JPU uses it to prepare new release. This gralde plugin automativally cretaes new commit with updated release version, places new release tag, and then prepare repository for the next development cycle.

com.jfrog.artifactory

Is needed to publish artifacts to repo.jenkins.io/releases maven repository.

Github Actions

There is release-drafter github actions script to prepare release notes based on Issues and PR which were integrated with the mainline since previous release.

Example

Let's say current version is 1.6, new version is 1.7, next development version is 1.8-SNAPSHOT

  • checkout release branch
git fetch
git checkout -B master origin/master
  • run release:
./gradlew release
# You will be asked for new version, and new snapsot version 
# (just press enter to use default values)

  • checkout new tag
</tr></table> 

... (truncated)

Commits
  • a8359d3 [Gradle Release Plugin] - pre tag commit: 'v1.8'.
  • c58d0a5 Merge pull request #289 from Willem1987/update-delegate-handling
  • a17b36d Merge pull request #286 from Willem1987/add-container-allowed-method
  • 5f5559e Merge pull request #290 from asysgroupe/master
  • b9a7132 Update README.md
  • f437687 Add container method with Map Param (name, shell)
  • ae8ce5a Merge pull request #288 from Willem1987/with-credentials-multi
  • 03861af Add container as allowed method for pipelines using kubernetes
  • da966b6 Add case for userpasswordmulti credentials
  • 0893a20 Revisit groovy delegates and property/method lookup
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Jan 18, 2021
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Mar 15, 2021

Superseded by #17.

@dependabot dependabot bot closed this Mar 15, 2021
@dependabot dependabot bot deleted the dependabot/maven/com.lesfurets-jenkins-pipeline-unit-1.8 branch March 15, 2021 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants