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

Move settings to config page as default #119 #189

Closed
wants to merge 2 commits into from

Conversation

tcollignon
Copy link

This is PR2 of #119.

This is my first contribution of this plugin, so tell me all the problems with this PR, and I will fix it.

I have try to give tests, but I'm not sure it's ok for you.

Thanks

@jan-molak
Copy link
Member

Thanks @tcollignon! I'm currently working on addressing #124, #165 and #57 and will review your PR as soon as I'm done with those.

Best,
Jan

@tcollignon
Copy link
Author

Hi, any news here?

@erikhakansson
Copy link
Contributor

This would be very welcome

hughsaunders added a commit to hughsaunders/jenkins-build-monitor-plugin that referenced this pull request Jul 18, 2019
This commit allows Jenkins users to specify defaults for build monitor
views when creating the views from the Jenkins UI. End users can still
modify these settings using the widget within build monitor.

This is useful because the defaults do not scale to large numbers of builds
so if a user is creating a build monitor view that they anticipate will
contain a large number of builds they can increase the number of columns
and prevent each end user from having to do that individually.

This is essentially a rebase of @tcolligon's changes in pr jenkinsci#189
and is related to issue jenkinsci#119.
@hughsaunders
Copy link

Resolved the conflicts in a new PR: #413

hughsaunders added a commit to hughsaunders/jenkins-build-monitor-plugin that referenced this pull request Jul 18, 2019
This commit allows Jenkins users to specify defaults for build monitor
views when creating the views from the Jenkins UI. End users can still
modify these settings using the widget within build monitor.

This is useful because the defaults do not scale to large numbers of builds
so if a user is creating a build monitor view that they anticipate will
contain a large number of builds they can increase the number of columns
and prevent each end user from having to do that individually.

This is essentially a rebase of @tcolligon's changes in pr jenkinsci#189
and is related to issue jenkinsci#119.
@basil basil closed this in #573 Feb 15, 2022
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.

5 participants