> > > Custom Command SCM: > This plugin allows to use any program on as a SCM. For polling and > checkout two separate commands can be defined in the Jenkins system page. >
Sounds to be very relevant to https://wiki.jenkins-ci.org/display/JENKINS/Script+SCM+Plugin . Did you consider integrating the features there? > Node Cleanup Plugin: > This plugin allows to remove unused workspaces from slave nodes. It > lists all workspaces (subfolders in the configured root folder on the > slave) and displays if there is a job available with an according > workspace name and if the job is bound to the slave. > This feature will be definitely useful as a separate plugin. It would be great to see the code in order to check if it is possible to integrate the implementation with existing plugins in order to avoid the functionality duplications. - Probably the functionality overlaps with https://wiki.jenkins-ci.org/display/JENKINS/Hudson+Distributed+Workspace+Clean+plugin. - It could be a value-added feature for https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin or for https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin => integrations may be useful вторник, 15 сентября 2015 г., 21:25:20 UTC+3 пользователь Andreas K написал: > > Hi, > > I have created two plugins which I would like to host on jenkins-ci. > > > Custom Command SCM: > This plugin allows to use any program on as a SCM. For polling and > checkout two separate commands can be defined in the Jenkins system page. > > For each job additional parameters may be configured and are added to > both, polling and checkout command. > > The outcome of the poll step depends on the return code of the poll > command, intermediate revision states are feed to the command using > stdin and may be returned via stdout. > > The checkout command may write its change log to stdout. The required > xml format is described using a xsd schema. > > > Node Cleanup Plugin: > This plugin allows to remove unused workspaces from slave nodes. It > lists all workspaces (subfolders in the configured root folder on the > slave) and displays if there is a job available with an according > workspace name and if the job is bound to the slave. > > > My GitHub ID: anderl86 > My jenkins-ci.org ID: anderl86 > > Custom Command SCM ID: custom-command-scm > Node Cleanup ID: node-cleanup > > If possible I'd like to start with empty GitHub repositories. > > Thanks for your assistance! > > Bye, Andreas > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ec3aa211-0e9c-4f04-96dd-e7b3c1fe8146%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
