[
https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3163:
----------------------------------
Can
devstudio.redhat.com be whitelisted as a server from which
https://www.redhat.com/j/elqNow/elqRedir.htm can be used?
If so, we could hide a directory listing (403'd if browsed) then link to something
like
https://www.redhat.com/j/elqNow/elqRedir.htm?ref=https://devstudio.redhat...
(while using javascript to obscure the mouseover/hover text so the full URL isn't
visible)
That would allow us to enforce the T&C & also track downloads.
Today if I try the above I get this failure:
{code:title=https://www.redhat.com/j/elqNow/elqNoRedir.htm}
The link you clicked on would have sent you to a website that we have not explicitly
verified as being safe. This action has been canceled and you are still on our website.
Please hit the "Back" button on your browser to be returned to the previous
page.
{code}
Good idea? Bad idea? Is there a better way? Could we autopublish into the repo where the
goldengate links point
(
http://www.jboss.org/download-manager/content/origin/files/sha256/), for all CI builds
(and do automated cleanup, too) ?
change publishing process so that JBDS staging builds go to
devstudio.redhat.com instead of
www.qa server
---------------------------------------------------------------------------------------------------------
Key: JBDS-3163
URL:
https://issues.jboss.org/browse/JBDS-3163
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: build
Affects Versions: 8.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 8.0.1.GA, 9.0.0.Alpha1
To simplify release/publishing process, we ought to start publishing nightlies and builds
staged for QE onto
devstudio.redhat.com (filemgmt) instead of the internal
www.qa box.
This will also allow us to use nightly URLs in ide-config.properties.
See
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad
solution to this problem.
Better solution is to move that content onto the new filemgmt instance and update
promote.sh to push to the new location.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)