[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 CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2741:
-----------------------------
CDW pm_ack: ?
> 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.Alpha1
>
>
> 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2741:
-----------------------------
CDW release: ?
Status: New (was: New)
Target Release: 7.1.0.GA
> 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.Alpha1
>
>
> 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2741:
-----------------------------
Summary: Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files (was: Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-regenerated composite*.xml files)
> 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.Alpha1
>
>
> 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 auo-regenerated composite*.xml files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2741:
-----------------------------
Docs QE Status: (was: NEW)
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-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.Alpha1
>
>
> 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-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2623:
-----------------------------
CDW pm_ack: ?
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Central, updatesite, Upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.x
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
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-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2623:
-----------------------------
CDW release: ?
Status: New (was: New)
Target Release: 7.1.0.GA
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Central, updatesite, Upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.x
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
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-2710) 3rd party certification for JBDS 7.0.x/7.1.x/8.0.x (next release TBD)
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2710:
-----------------------------
CDW pm_ack: ?
> 3rd party certification for JBDS 7.0.x/7.1.x/8.0.x (next release TBD)
> ---------------------------------------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: respin-a
> Fix For: 7.1.x, 8.0.x
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.2.1.v20130402 - JBIDE-13682
> * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486
> * pmd/4.0.0.v20130510-1000 - JBIDE-14902
> * SpringSource's Quick Search - JBDS-2686 *TBD*
> * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> * testng/6.8.1.20130330_0839/ - JBDS-2415
> * VJET 0.10 - JBIDE-14764
> These are currently unchanged since December when we released JBDS 6.0.0:
> * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799).
> * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21
> Additionally (Target Platform):
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues do not block the release of JBDS 7.0.1.GA.
--
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-2710) 3rd party certification for JBDS 7.0.x/7.1.x/8.0.x (next release TBD)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2710:
-----------------------------
CDW release: ?
Status: New (was: New)
Target Release: 7.1.0.GA
> 3rd party certification for JBDS 7.0.x/7.1.x/8.0.x (next release TBD)
> ---------------------------------------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: respin-a
> Fix For: 7.1.x, 8.0.x
>
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.2.1.v20130402 - JBIDE-13682
> * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486
> * pmd/4.0.0.v20130510-1000 - JBIDE-14902
> * SpringSource's Quick Search - JBDS-2686 *TBD*
> * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> * testng/6.8.1.20130330_0839/ - JBDS-2415
> * VJET 0.10 - JBIDE-14764
> These are currently unchanged since December when we released JBDS 6.0.0:
> * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799).
> * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21
> Additionally (Target Platform):
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues do not block the release of JBDS 7.0.1.GA.
--
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-2710) 3rd party certification for JBDS 7.0.x/7.1.x/8.0.x (next release TBD)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2710:
-----------------------------
Fix Version/s: (was: 8.0.x)
(was: 7.1.x)
> 3rd party certification for JBDS 7.0.x/7.1.x/8.0.x (next release TBD)
> ---------------------------------------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: respin-a
>
> For JBDS 7, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.2.1.v20130402 - JBIDE-13682
> * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486
> * pmd/4.0.0.v20130510-1000 - JBIDE-14902
> * SpringSource's Quick Search - JBDS-2686 *TBD*
> * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> * testng/6.8.1.20130330_0839/ - JBDS-2415
> * VJET 0.10 - JBIDE-14764
> These are currently unchanged since December when we released JBDS 6.0.0:
> * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799).
> * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21
> Additionally (Target Platform):
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues do not block the release of JBDS 7.0.1.GA.
--
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