[JBoss JIRA] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2741:
--------------------------------------
Fix Version/s: 7.1.0.Alpha2
(was: 7.1.0.Alpha1)
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2741
> URL: https://issues.jboss.org/browse/JBDS-2741
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Alpha2
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2741:
-------------------------------------------
Isn't this more a JBIDE thing ?
Got link to the scripts ?
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2741
> URL: https://issues.jboss.org/browse/JBDS-2741
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Alpha2
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBDS-2457) Mirror stable content on Akamai
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2457?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2457:
--------------------------------------
Is it fine to create a /static/ folder in JBDS download area and ask it to be Akamai-fied (same as we do for JBT) ? [~nickboldt] [~maxandersen] ?
> Mirror stable content on Akamai
> -------------------------------
>
> Key: JBDS-2457
> URL: https://issues.jboss.org/browse/JBDS-2457
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: updatesite
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> In order to improve installation time (for both end-users and internal build/test usage), we should use Akamai on the stable folders if devstudio downloas site.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-13898) Update ESB tests to support latest SOA-P 5.3.x
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13898?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky closed JBIDE-13898.
-------------------------------------
Closed ad this was done
> Update ESB tests to support latest SOA-P 5.3.x
> ----------------------------------------------
>
> Key: JBIDE-13898
> URL: https://issues.jboss.org/browse/JBIDE-13898
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb, qa
> Affects Versions: 4.0.0.Alpha1-SOA, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Andrej Podhradsky
> Fix For: 4.0.1.Final
>
>
> Found two test classes which refer to SOA-P 5. They should be updated to refer to the latest 5.3.x *AND* new 6.0.0.Alpha bits, so both are available for testing.
> {code:title=jbosstools-esb/tests/org.jboss.tools.esb.project.core.test/pom.xml}
> <configuration>
> <url>http://***********/soa-5.3.0.ER5/soa-p-5.3.0.ER5.zip</url>
> <md5>**********</md5>
> <unpack>true</unpack>
> {code}
> {code:title=jbosstools-integration-tests/tests/org.jboss.tools.esb.ui.bot.test/pom.xml}
> <configuration>
> <url>http://***********/soa-5.3.0.GA/soa-p-5.3.0.GA.zip</url>
> <md5>**********</md5>
> <unpack>true</unpack>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months