[jbosstools-issues] [JBoss JIRA] (JBIDE-12945) Migrate jbosstools-docs-nightly job to use git sources instead of svn
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Dec 3 15:16:22 EST 2012
[ https://issues.jboss.org/browse/JBIDE-12945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt closed JBIDE-12945.
------------------------------
Closing. Build is blue.
> Migrate jbosstools-docs-nightly job to use git sources instead of svn
> ---------------------------------------------------------------------
>
> Key: JBIDE-12945
> URL: https://issues.jboss.org/browse/JBIDE-12945
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Isaac Rooskov
> Labels: f2f2012, respin-c
> Fix For: 4.0.0.CR1
>
> Attachments: git-repo-filtering-jenkins.png, multiple-git-repos-jenkins.png
>
>
> This job needs to be tied to multiple git repos:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-docs-nightly/configure
> For an example of how to do a job w/ multiple git repos as source, see this one:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-4.0_trunk.tests/
> NOTE: You must set three advanced fields (each SCM entry has TWO *Advanced* buttons when configuring in the browser) for each repo to avoid collisions when fetching:
> !multiple-git-repos-jenkins.png!
> If you want to edit the config.xml file offline, the code looks like this, eg., for the jbosstools-base repo (which replaces common, tests, usage, and runtime):
> {code}
> <hudson.plugins.git.GitSCM>
> <configVersion>2</configVersion>
> <userRemoteConfigs>
> <hudson.plugins.git.UserRemoteConfig>
> <name/>
> <refspec/>
> <url>git://github.com/jbosstools/jbosstools-base.git</url>
> </hudson.plugins.git.UserRemoteConfig>
> </userRemoteConfigs>
> <branches>
> <hudson.plugins.git.BranchSpec>
> <name>origin/master</name>
> </hudson.plugins.git.BranchSpec>
> </branches>
> <disableSubmodules>false</disableSubmodules>
> <recursiveSubmodules>false</recursiveSubmodules>
> <doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations>
> <authorOrCommitter>false</authorOrCommitter>
> <clean>false</clean>
> <wipeOutWorkspace>false</wipeOutWorkspace>
> <pruneBranches>false</pruneBranches>
> <remotePoll>false</remotePoll>
> <ignoreNotifyCommit>false</ignoreNotifyCommit>
> <buildChooser class="hudson.plugins.git.util.DefaultBuildChooser"/>
> <gitTool>Default</gitTool>
> <submoduleCfg class="list"/>
> <relativeTargetDir>sources/base</relativeTargetDir>
> <reference/>
> <excludedRegions/>
> <excludedUsers/>
> <gitConfigName/>
> <gitConfigEmail/>
> <skipTag>false</skipTag>
> <includedRegions/>
> <scmName>base</scmName>
> </hudson.plugins.git.GitSCM>
> {code}
> You can also set filters to only watch the repo (when deciding when to build automatically) for specific paths instead of the whole repo:
> !git-repo-filtering-jenkins.png!
> For a complete list of the new merged repos, see:
> http://download.jboss.org/jbosstools/builds/cascade/swimlanes.html
> https://github.com/jbosstools/
--
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
More information about the jbosstools-issues
mailing list