[JIRA] [lockable-resources-plugin] (JENKINS-29206) Enhancement: put list of resources into logfile

[Philipp.Strobel@TQ-Logics.com (JIRA)]

Philipp Strobel created an issue

Jenkins / JENKINS-29206 Enhancement: put list of resources into logfile Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 03/Jul/15 7:39 AM Labels: configuration_file Priority: Minor Reporter: Philipp Strobel The configuration of available resources is located in the jenkins system configuration tab. In case of a high amount of resources to administrate, this is blowing up this tab. Gues a solution, where to save that resource informations in a configuration file and load that file on the jenkins system configuration tab would be a nice benifit. An further anhancement could be to load the resources configuration file along with the job configuration. This could provide the benefit to have different configurations for different projects on one jenkins instance. Having configurations in files also improves the possibility to make jobs reproduceable. The configuration files could be provided by an SCM-system along with the rather source code and gives an answer to the question, what external resources must be available to run that job... Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[Philipp.Strobel@TQ-Logics.com (JIRA)]

Philipp Strobel updated an issue

Jenkins / JENKINS-29206

Enhancement: put list of resources into a config-file Change By: Philipp Strobel Summary: Enhancement: put list of resources into  logfile  a config-file

Add Comment

[tobias-jenkins@23.gs (JIRA)]

Tobias Gruetzmacher closed an issue as Not A Defect

I don't consider this in scope for this plugin. See the Configuration-as-Code plugin (which lockable-resources supports since 2.6) for a different approach. If you disagree, please reopen with additional arguments.

Jenkins / JENKINS-29206 Enhancement: put list of resources into a config-file

Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Not A Defect

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)