[jbosstools-issues] [JBoss JIRA] (JBDS-3304) [unit test] versionwatch should run against latest builds, not hardcoded older Betas

Nick Boldt (JIRA) issues at jboss.org
Mon Jan 5 11:40:30 EST 2015


Nick Boldt created JBDS-3304:
--------------------------------

             Summary: [unit test] versionwatch should run against latest builds, not hardcoded older Betas
                 Key: JBDS-3304
                 URL: https://issues.jboss.org/browse/JBDS-3304
             Project: Developer Studio (JBoss Developer Studio)
          Issue Type: Bug
          Components: build
    Affects Versions: 8.0.1.GA
            Reporter: Nick Boldt
            Assignee: Nick Boldt


versionwatch should run against latest builds, not hardcoded older Betas.

Need a way to pull the latest builds from /staging/ so that instead of testing hardcoded Beta2 builds we use the latest. 

This might have broken as a result of a bug in install.jbds.sh - I thought this used to work:

{code}
++ TMPDIR=/tmp
/mnt/hudson_workspace/workspace/devstudio.versionwatch_8.0.luna/sources/vwatch/install.jbds.sh: command substitution: line 151: unexpected EOF while looking for matching `"'
/mnt/hudson_workspace/workspace/devstudio.versionwatch_8.0.luna/sources/vwatch/install.jbds.sh: command substitution: line 152: syntax error: unexpected end of file
{code}

Either way, we need a better unit test here to ensure that the versions diffed are NOT just the list of hardcoded ones, but instead include the hardcoded list + at least one more (latest build).





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


More information about the jbosstools-issues mailing list