[
https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-16140:
----------------------------------------
[~maxandersen]: We already have some ability to set up an alternative server.
https://github.com/jbdevstudio/jbdevstudio-ci contains the config.xml files for each job
that can be pushed to whatever Jenkins server we want (through Jenkins Rest API). File
https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/pom-sync.xml shows how we use
Nick's mojo to do that without much effot.
The coupling to JBoss infra is on the publication part which relies on FileSystem and
network assumptions that are only true on jenkins.mw.lab.
What I see as a big benefit of Folder over buildchow is that:
* It is not generative, and generation is always an additional complex step
* it makes the concept of hierarchy and factorization natural in Jenkins
I may miss something, but I don't see what are the benefits of buildchow over the
Folder plugin. I'd be glad to learn more.
Investigate usage of Jenkins folder plugin
------------------------------------------
Key: JBIDE-16140
URL:
https://issues.jboss.org/browse/JBIDE-16140
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Mickael Istria
Cloudbees released their folder plugin, which is about factorizing jobs configuration, as
an OSS plugin:
http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc...
We should investigate on whether it would help to use to manage JBT/JBDS jobs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira