[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=13060851#comment-13060851 ] 

Max Rydahl Andersen edited comment on JBIDE-19190 at 4/27/15 3:59 AM:
----------------------------------------------------------------------

but that is not what https://github.com/jpeterka/jbosstools-vwatch/commits/master shows. so this was moved without retaining git history and attributions ;/

Jiri - I've created https://github.com/jbosstools/jbosstools-versionwatch which *retains* the proper git history as it is in https://github.com/jbdevstudio/jbdevstudio-qa.

This was created by running:

{code}
git filter-branch --prune-empty --subdirectory-filter vwatch -- --all
git remote add vwatch https://github.com/jbosstools/jbosstools-versionwatch
git push vwatch master jbosstools-4.2.x
{code}

That means jbosstools-versionwatch now have the proper history *but* missing whatever changes you made in jpeterka.
It looks like this can just be cherry-picked over but I think it is best you do it rather than me doing it blindly.

Can you make that and submit a PR for it ? 



was (Author: maxandersen):
but that is not what https://github.com/jpeterka/jbosstools-vwatch/commits/master shows. so this was moved without retaining git history and attributions ;/

Jiri - I've created https://github.com/jbosstools/jbosstools-versionwatch which *retains* the proper git history as it is in https://github.com/jbdevstudio/jbdevstudio-qa.

This was created by running:

{{{
git filter-branch --prune-empty --subdirectory-filter vwatch -- --all
git remote add vwatch https://github.com/jbosstools/jbosstools-versionwatch
git push vwatch master jbosstools-4.2.x
}}}

That means jbosstools-versionwatch now have the proper history *but* missing whatever changes you made in jpeterka.
It looks like this can just be cherry-picked over but I think it is best you do it rather than me doing it blindly.

Can you make that and submit a PR for it ? 


> 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.15#6346)