[jbosstools-issues] [JBoss JIRA] (JBIDE-22877) Update RedDeer in TP for JBT 4.4.1.AM3
Martin Malina (JIRA)
issues at jboss.org
Thu Aug 4 16:38:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13275372#comment-13275372 ]
Martin Malina edited comment on JBIDE-22877 at 8/4/16 4:37 PM:
---------------------------------------------------------------
Wait a minute, I thought you copy the bits from a location one time to the TP and then it's there. So you're saying that the TP will always only point to the location that I give you? OK then, fair enough.
I tried to run jbosstools_rsync here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-rsync/13/
The build is red, but the update site still seems to be up at
http://download.jboss.org/jbosstools/neon/development/updates/reddeer/1.1.0.20160804/
The cleanup script could not be found.
{code}
16:17:02 /tmp/hudson38112553799167838.sh: line 26: jbosstools-cleanup.sh: command not found
{code}
It worked for me two weeks ago.
I noticed that while rsync is referenced correctly in the shell step:
{code}${WORKSPACE}/sources/publish/rsync.sh{code}
the cleanup script is called like this:
{code}jbosstools-cleanup.sh{code}
which doesn't seem right - shouldn't that be this instead?
{code}${WORKSPACE}/sources/util/cleanup/jbosstools-cleanup.sh{code}
So I fixed this and now the build is blue. But please check that I didn't screw it up.
Regarding a Final version - yes, 1.1.0.Final is planned in time for the TP freeze at the end of August. But I would like to point out that what we have in the TP right now is not a Final either, so I'm not sure what you'd want to roll back to ;)
was (Author: mmalina):
Wait a minute, I thought you copy the bits from a location one time to the TP and then it's there. So you're saying that the TP will always only point to the location that I give you? OK then, fair enough.
I tried to run jbosstools_rsync here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-rsync/13/
The build is red, but the update site still seems to be up at
http://download.jboss.org/jbosstools/neon/development/updates/reddeer/1.1.0.20160804/
The cleanup script could not be found.
{code}
16:17:02 /tmp/hudson38112553799167838.sh: line 26: jbosstools-cleanup.sh: command not found
{code}
It worked for me two weeks ago.
I noticed that while rsync is referenced correctly in the shell step:
${WORKSPACE}/sources/publish/rsync.sh
the cleanup script is called like this:
jbosstools-cleanup.sh
which doesn't seem right - shouldn't that be this instead?
${WORKSPACE}/sources/util/cleanup/jbosstools-cleanup.sh
So I fixed this and now the build is blue. But please check that I didn't screw it up.
Regarding a Final version - yes, 1.1.0.Final is planned in time for the TP freeze at the end of August. But I would like to point out that what we have in the TP right now is not a Final either, so I'm not sure what you'd want to roll back to ;)
> Update RedDeer in TP for JBT 4.4.1.AM3
> --------------------------------------
>
> Key: JBIDE-22877
> URL: https://issues.jboss.org/browse/JBIDE-22877
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
> You can simply take the latest from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ . Let me know if it's better for you if I copy it somewhere else using the rsync job or if this is sufficient.
> Please make sure to copy the RedDeer UI feature as well as it seems to have been missing last time: JBIDE-22857 (I'm not sure how that happened.)
> Once this is done, it should be available on the current TP within a day?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list