[jbosstools-issues] [JBoss JIRA] (JBIDE-12220) create generic publishing job which takes as input three parameters

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723038#comment-12723038 ] 

Nick Boldt edited comment on JBIDE-12220 at 10/1/12 4:48 PM:
-------------------------------------------------------------

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/SwitchYard-Tools-publish/ and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/SwitchYard-Tools-publish/ are now essentially clones (w/ different default settings) of this new multi-purpose job:


{color:green}*>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ <<*{color}


---

This script can be used to push integration and stable (release) builds, but can also be used to push integration builds.

For example:

http://download.jboss.org/jbosstools/updates/integration/juno/core/freemarker/
http://download.jboss.org/jbosstools/updates/integration/juno/core/freemarker/4.0.juno/

And, until we get to github, it can be used to produce merged repos that will mirror the structure we'll have after the migration (see JBIDE-12475). For example, running the job 7 times I was able to produce these composite/aggregate repos:

http://download.jboss.org/jbosstools/updates/integration/juno/core/base/ (contains usage, tests, runtime, common)
http://download.jboss.org/jbosstools/updates/integration/juno/core/server/ (contains as, archives, jmx)


---

For the curious, the affected scripts are here:

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh (for publishing CI build into builds/staging/{JOB_NAME})

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish/promote.sh (for promoting from builds/staging to updates/{BUILD_TYPE})

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/util/cleanup/jbosstools-cleanup.sh (cleans out old builds or simply updates parent folder metadata to composite children into a single site. Probably deserves to be renamed... but now sure what to call it)
                
      was (Author: nickboldt):
    https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/SwitchYard-Tools-publish/ and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/SwitchYard-Tools-publish/ are now essentially clones (w/ different default settings) of this new multi-purpose job:

{blockquote}
{color:green}*>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ <<*{color}
{blockquote}

---

This script can be used to push integration and stable (release) builds, but can also be used to push integration builds.

For example:

http://download.jboss.org/jbosstools/updates/integration/juno/core/freemarker/
http://download.jboss.org/jbosstools/updates/integration/juno/core/freemarker/4.0.juno/

And, until we get to github, it can be used to produce merged repos that will mirror the structure we'll have after the migration (see JBIDE-12475). For example, running the job 7 times I was able to produce these composite/aggregate repos:

http://download.jboss.org/jbosstools/updates/integration/juno/core/base/ (contains usage, tests, runtime, common)
http://download.jboss.org/jbosstools/updates/integration/juno/core/server/ (contains as, archives, jmx)


---

For the curious, the affected scripts are here:

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh (for publishing CI build into builds/staging/{JOB_NAME})

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish/promote.sh (for promoting from builds/staging to updates/{BUILD_TYPE})

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/util/cleanup/jbosstools-cleanup.sh (cleans out old builds or simply updates parent folder metadata to composite children into a single site. Probably deserves to be renamed... but now sure what to call it)
                  
> create generic publishing job which takes as input three parameters
> -------------------------------------------------------------------
>
>                 Key: JBIDE-12220
>                 URL: https://issues.jboss.org/browse/JBIDE-12220
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: SOA Tooling
>    Affects Versions: 3.3.0.CR1-SOA
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.0.0.Alpha1-SOA, 4.0.0.Beta1
>
>
> TODO: new generic build job that can take as input a URL (staging nightly site folder or zip or nexus path); as output publishes content into a new folder using convention above; optional generation of composite*.xml to point to milestone from parent folder
> IN: http://download.jboss.org/jbosstools/builds/staging/SwitchYard-Tools/eclipse/ or http://download.jboss.org/drools/release/5.3.0.Final/droolsjbpm-tools-distribution-5.3.0.Final.zip
> OUT: http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/switchyard/<version>/
> OUT: http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/drools/<version>/
> OPTIONAL OUT: http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/*/compositeContent.xml updated to point at the URL above
> --> only problem here is that Jenkins can't commit changes to SVN, and that folder will be synched from SVN, overriding locally pushed changes.

--
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