[jbosstools-issues] [JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-19190:
---------------------------------------------

not sure why this is assigned to me since nothing except #0 is related to me.

lets move it as its own repo. it does not seem to fit anywhere else and its supposed to be completely independent anyway.

Can you fix the rest ?

 

> migrate VersionWatch to jbosstools-* repo
> -----------------------------------------
>
>                 Key: JBIDE-19190
>                 URL: https://issues.jboss.org/browse/JBIDE-19190
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: qa
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Jiri Peterka
>            Priority: Minor
>             Fix For: 4.3.0.Alpha2
>
>
> 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly.
> 1. remove all refs to QA Jenkins file paths to make this more generic
> 2. migrate those internal file paths into jenkins config.xml files 
> 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)