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

Visualise change sets #211

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

tommikiviniemi-srs
Copy link

Added ability to visualise change sets. Four per-project options: Hidden, Last or Next Build, Last Build Only, Next Build Only.

@Tommigun1980
Copy link

Hi @jan-molak! Do you think this change could be merged in? I think it's quite useful as it allows you to see what the last build's changes were and/or what the upcoming changes will be.

Thanks.

@jan-molak
Copy link
Member

Hi @Tommigun1980 - we're currently in the process of migrating Jenkins Build Monitor Plugin to Jenkins Org on GitHub (see #656). Once this is complete, maintainers will go through the outstanding PRs.

@basil
Copy link
Member

basil commented Mar 9, 2023

@Tommigun1980 If the changes in this PR work, you can consider adopting the plugin to merge and release them. The "Contributing to Open Source" workshop from DevOps World 2021 is a useful starting point for new maintainers. That document includes links to a five part video series that illustrates many of the steps. If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants