[JBoss JIRA] Created: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
4:20 p.m.
improve publishing of component sites using composite metadata so that content doesn't
vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Boldt
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the same
folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of whack
w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm all
ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:20 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-8667:
------------------------------
Fix Version/s: 3.3.0.M1
Affects Version/s: 3.3.0.M1
Component/s: Build/Releng
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M1
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:33 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-8667:
---------------------------------------
Fix Version/s: 3.3.0.M2
(was: 3.3.0.M1)
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M2
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:22 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-8667:
------------------------------
Fix Version/s: 3.3.0.M3
(was: 3.3.0.M2)
Bump to M3
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-8667:
--------------------------------------------
JBIDE-9266 has example of how to do simple sftp symbolic link massaging. Similar could be
done for mv/rm operations.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:04 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
We now have two previous component builds available, stored outside the /staging/ dir [0]
to keep that folder less cluttered:
[0] http://download.jboss.org/jbosstools/builds/staging.previous/
Once these are populated, I can update the composite metadata here [1] to reference the
collection of 3 sites (current, previous, previous-previous) and be able to better resolve
& recover when builds are in progress.
(Note that the solution requires a mix of rsync --delete and sftp to clean out dirs and
remove them / rename them. See
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh and look for the lines
starting with JBIDE-8667.)
[1]
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/com...
----
We still have another related problem, which is that if the agg site for JBT or JBDS is
being built and upstream VPE or JSF or JST spin and finish while the downstream is
resolving, you can get into this situation:
{code}
[INFO] [Software being installed:
org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT,
Only one of the following can be installed at once: [
org.jboss.tools.xulrunner.initializer 3.1.0.v20110720-1516-H397-M3,
org.jboss.tools.xulrunner.initializer 3.1.0.v20110721-0807-H399-M3
],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110720-1633-H328-M3 depends on: org.jboss.tools.xulrunner.initializer
[3.1.0.v20110720-1516-H397-M3],
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.richfaces.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.xulrunner.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group
1.9.216.v20110721-0807-H399-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110721-0807-H399-M3]]
{code}
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:04 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-8667 at 7/21/11 6:03 PM:
------------------------------------------------------------
We now have two previous component builds available, stored outside the /staging/ dir [0]
to keep that folder less cluttered:
[0] http://download.jboss.org/jbosstools/builds/staging.previous/
Once these are populated, I can update the composite metadata here [1] to reference the
collection of 3 sites (current, previous, previous-previous) and be able to better resolve
& recover when builds are in progress.
(Note that the solution requires a mix of rsync --delete and sftp to clean out dirs and
remove them / rename them. See
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh and look for the lines
starting with JBIDE-8667.)
[1]
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/com...
----
We still have another related problem, which is that if the agg site for JBT or JBDS is
being built and upstream VPE or JSF or JST spin and finish while the downstream is
resolving, you can get into this situation:
{code}
[INFO] [Software being installed:
org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT,
Only one of the following can be installed at once: [
org.jboss.tools.xulrunner.initializer 3.1.0.v20110720-1516-H397-M3,
org.jboss.tools.xulrunner.initializer 3.1.0.v20110721-0807-H399-M3
],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110720-1633-H328-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110720-1516-H397-M3],
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.richfaces.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.xulrunner.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group
1.9.216.v20110721-0807-H399-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110721-0807-H399-M3]]
{code}
was (Author: nickboldt):
We now have two previous component builds available, stored outside the /staging/ dir
[0] to keep that folder less cluttered:
[0] http://download.jboss.org/jbosstools/builds/staging.previous/
Once these are populated, I can update the composite metadata here [1] to reference the
collection of 3 sites (current, previous, previous-previous) and be able to better resolve
& recover when builds are in progress.
(Note that the solution requires a mix of rsync --delete and sftp to clean out dirs and
remove them / rename them. See
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh and look for the lines
starting with JBIDE-8667.)
[1]
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/com...
----
We still have another related problem, which is that if the agg site for JBT or JBDS is
being built and upstream VPE or JSF or JST spin and finish while the downstream is
resolving, you can get into this situation:
{code}
[INFO] [Software being installed:
org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT,
Only one of the following can be installed at once: [
org.jboss.tools.xulrunner.initializer 3.1.0.v20110720-1516-H397-M3,
org.jboss.tools.xulrunner.initializer 3.1.0.v20110721-0807-H399-M3
],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110720-1633-H328-M3 depends on: org.jboss.tools.xulrunner.initializer
[3.1.0.v20110720-1516-H397-M3],
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.richfaces.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.xulrunner.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group
1.9.216.v20110721-0807-H399-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110721-0807-H399-M3]]
{code}
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:06 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-8667 at 7/21/11 6:06 PM:
------------------------------------------------------------
We now have two previous component builds available, stored outside the /staging/ dir [0]
to keep that folder less cluttered:
[0] http://download.jboss.org/jbosstools/builds/staging.previous/
Once these are populated, I can update the composite metadata here [1] to reference the
collection of 3 sites (current, previous, previous-previous) and be able to better resolve
& recover when builds are in progress.
(Note that the solution requires a mix of rsync --delete and sftp to clean out dirs and
remove them / rename them. See
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh and look for the lines
starting with JBIDE-8667.)
[1]
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/com...
----
We still have another related problem, which is that if the agg site for JBT or JBDS is
being built and upstream VPE or JSF or JST spin and finish while the downstream is
resolving, you can get into this situation:
{code}
[INFO] [Software being installed:
org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT,
Only one of the following can be installed at once: [
org.jboss.tools.xulrunner.initializer 3.1.0.v20110720-1516-H397-M3,
org.jboss.tools.xulrunner.initializer 3.1.0.v20110721-0807-H399-M3
],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110720-1633-H328-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110720-1516-H397-M3],
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.richfaces.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.xulrunner.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group
1.9.216.v20110721-0807-H399-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110721-0807-H399-M3]]
{code}
I could set select upstream components (vpe, jst, jsf) to block while their downstream are
running, but that will delay builds from starting if ANY downstream are running. Not sure
that's ideal since jbt agg, jbds update, and jbds product can take over an hour each
which would prevent CI builds of vpe/jst/jsf from spinning for upwards of 3-4hrs.
was (Author: nickboldt):
We now have two previous component builds available, stored outside the /staging/ dir
[0] to keep that folder less cluttered:
[0] http://download.jboss.org/jbosstools/builds/staging.previous/
Once these are populated, I can update the composite metadata here [1] to reference the
collection of 3 sites (current, previous, previous-previous) and be able to better resolve
& recover when builds are in progress.
(Note that the solution requires a mix of rsync --delete and sftp to clean out dirs and
remove them / rename them. See
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh and look for the lines
starting with JBIDE-8667.)
[1]
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/com...
----
We still have another related problem, which is that if the agg site for JBT or JBDS is
being built and upstream VPE or JSF or JST spin and finish while the downstream is
resolving, you can get into this situation:
{code}
[INFO] [Software being installed:
org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT,
Only one of the following can be installed at once: [
org.jboss.tools.xulrunner.initializer 3.1.0.v20110720-1516-H397-M3,
org.jboss.tools.xulrunner.initializer 3.1.0.v20110721-0807-H399-M3
],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110720-1633-H328-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110720-1516-H397-M3],
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.richfaces.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.xulrunner.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group
1.9.216.v20110721-0807-H399-M3 depends on:
org.jboss.tools.xulrunner.initializer [3.1.0.v20110721-0807-H399-M3]]
{code}
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:22 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
Awesome. adding support for sftp-borne symlinking/moves/renames/deletes has caused a
problem w/ publishing JBDS because that pushes over rsync to a LOCAL path, which sftp
doesn't like.
Working on a hackaround now that says if DESTINATION path (/path/to/put/files) doesn't
include user@server: prefix, use "hudson@`hostname -f`:/path/to/put/files"
instead.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:57 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-8667 at 7/27/11 4:56 PM:
------------------------------------------------------------
Awesome. adding support for sftp-borne symlinking/moves/renames/deletes has caused a
problem w/ publishing JBDS because that pushes over rsync to a LOCAL path, which sftp
doesn't like.
Working on a hackaround now that says if DESTINATION path (/path/to/put/files) doesn't
include user@server: prefix, use "hudson@`hostname -f`:/path/to/put/files"
instead.
Waiting on good 5.0 update site build... (see also JBIDE-9410)
was (Author: nickboldt):
Awesome. adding support for sftp-borne symlinking/moves/renames/deletes has caused a
problem w/ publishing JBDS because that pushes over rsync to a LOCAL path, which sftp
doesn't like.
Working on a hackaround now that says if DESTINATION path (/path/to/put/files) doesn't
include user@server: prefix, use "hudson@`hostname -f`:/path/to/put/files"
instead.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:30 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
trunk composite staging site [1] now includes BOTH current and previous versions of
components to help w/ intra- and inter-build stability
[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/
This might be a really bad idea - we shall see.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:11 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt resolved JBIDE-8667.
-------------------------------
Resolution: Done
Caused a few problems including JBIDE-9430, but otherwise this seems an OK approach.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
Max said:
I was wondering if we got a page somewhere (if not we should create
one) that just outlines the various sites there are in play and what triggers their update
and how often they get updated, what stays for how long.
Currently there's the cascade page [0], but I don't mention the staging.previous
[1] folder which now provides the "last build before the current one" alluded to
above.
Both the staging [2] and staging.previous [1] are now composited together here [3], so
that an aggregate site [4] can be built & published [5].
[0] http://download.jboss.org/jbosstools/builds/cascade/trunk.html
[1] http://download.jboss.org/jbosstools/builds/staging.previous/
[2] http://download.jboss.org/jbosstools/builds/staging/
[3] http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/
[4] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/
[5] http://download.jboss.org/jbosstools/updates/nightly/trunk/
Both staging and staging.previous are updated every time a new CI nightly spins and
publishes its results. Commit a change to SVN, a build will run, and the sites will be
updated.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
Problem w/ that approach is that resolving the sites is slower because you have more
levels of nesting.
But that said, I now do publish metadata which composites both staging and staging
previous into a single URL. For example:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
So, we could change the metadata in
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/ to point at these
new composites if we wanted.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:30 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8667:
--------------------------------------
And how do you create staging previous? By moving staging current?
BTW xompositeContent.xml you mentioned has problems
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:30 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin updated JBIDE-8667:
---------------------------------
Attachment: screenshot103.png
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:30 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin edited comment on JBIDE-8667 at 8/18/11 1:29 PM:
---------------------------------------------------------------
And how do you create staging previous? By moving staging current?
BTW xompositeContent.xml you mentioned has problems
!screenshot103.png!
was (Author: dgolovin):
And how do you create staging previous? By moving staging current?
BTW xompositeContent.xml you mentioned has problems
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
Yes, a move/rename is done. See
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh
Committed a fix to publish.sh so that we won't have "--" within a <!--
comment block --> (which is what was causing the XML to be unparseable).
When builds respin, this will be fixed.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8667:
--------------------------------------
As I said before this approach with move/rename is not going to work. If you want keep
current downloads alive new version should be added to composite update site without
*touching* previous one.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:50 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
Well, it's certainly better than the old approach of destructively rsynching ON TOP of
the previous one. Now at least the time required to move from x to x+1 is seconds instead
of minutes, and the old bits are still available so that if you ping the site during a
build you can still resolve both x and x-1 builds.
Why won't it work?
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:29 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8667:
--------------------------------------
because it is not only about hudson builds, which are probably fine because of having
locks.
If you build component locally you have all chances to get problems with dependnecies. If
local build is downloading dependencies from nightly composite it doesn't expect they
going to be moved to different location. It could happen now and if it is, build fails.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-8667 at 8/19/11 5:52 PM:
------------------------------------------------------------
OK, but the composite from which it pulls references BOTH the latest site (staging) and
the previous site (staging.previous) so at any time you can get access to both PROVIDED
that no more than 1 build happens while you're pulling bits.
Worst case, you respin and you get the newer metadata, which points at the same sites but
which resolves the x+1 and x versions instead of the x and x-1 versions.
--
Are you suggesting we need to have composite sites which point at SPECIFIC builds
(possibly more than 2) rather than just staging + staging.previous? Suspect we'll run
out of disk doing that...
was (Author: nickboldt):
OK, but the composite from which it pulls references BOTH the latest site (staging)
and the previous site (staging.previous) so at any time you can get access to both
PROVIDED that no more than 1 build happens while you're pulling bits.
Worst case, you respin and you get the newer metadata, which points at the same sites but
which resolves the x+1 and x versions instead of the x and x-1 versions.
--
Are you suggesting we need to have composite sites which point at SPECIFIC builds
(possibly more than 2) rather than just staging + staging.previous?
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
OK, but the composite from which it pulls references BOTH the latest site (staging) and
the previous site (staging.previous) so at any time you can get access to both PROVIDED
that no more than 1 build happens while you're pulling bits.
Worst case, you respin and you get the newer metadata, which points at the same sites but
which resolves the x+1 and x versions instead of the x and x-1 versions.
--
Are you suggesting we need to have composite sites which point at SPECIFIC builds
(possibly more than 2) rather than just staging + staging.previous?
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8667:
--------------------------------------
two builds are fine in most cases for now. The only problem now that previous build is
moving when new build is ready to publish.
Why don't do it like this.
Lets assume new build is ready for publishing and we have two/one/ziro builds published
already. name for build folder is a timestamp in any format that lets sort them.
# first scp or rsync new build next to old ones
# then get list of published folders and sort them in descending order.
# generate metadata for first two folders and publish it, replacing old one
# remove published builds except two oldest
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:07 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt resolved JBIDE-8667.
-------------------------------
Resolution: Done
That's exactly what I do now, but a couple minor adjustments to account for disk space
usage and simplified (no need for timestamps):
1. first rsync as <project>.new
2. don't need a list, there will never be more than <project> and
<project>.new
3. generate metadata (but it's always the same two folders, just with updated
timestamps
4. remove <project>.previous
move <project> to <project>.previous
move <project>.new to <project>
this keeps no more than current and previous on disk at any time, and guarantees that
there'll always be one that works.
Tested it last night during a replacement op and was able to install from the .previous
version no problem.
---
If you have a specific problem w/ my implementation (which is basically yours but tweaked
slightly) please report the problem you're seeing and we can reopen this for M4.
Closing for now.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:25 p.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Jiri Peterka closed JBIDE-8667.
-------------------------------
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M3
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:49 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin updated JBIDE-8667:
---------------------------------
Fix Version/s: 3.3.0.M4
(was: 3.3.0.M3)
Changed fix version from 3.3.0.M3 to 3.3.0.M4
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M4
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:10 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8667:
--------------------------------------
I'll verify it first on trunk builds when they're running again.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.M4
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin edited comment on JBIDE-8667 at 9/12/11 3:14 PM:
---------------------------------------------------------------
It is not going to work until you keep previous location untouched.
was (Author: dgolovin):
It is not going to work until, you keep previous location untouched.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.M4
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:54 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
They're running again. Symptoms persist?
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.M4
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:18 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-8667:
--------------------------------------
{code}[INFO] Adding repository (cached)
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/
[INFO] Adding repository (cached)
http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/l...
[INFO] Downloading org.jboss.tools.jst.web
[INFO] Downloading org.jboss.tools.jst.web
[INFO] o.h.m.e.h.MavenExecutionResultHandler - Build failed with exception(s)
[INFO] o.h.m.e.h.MavenExecutionResultHandler - [1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could
not download artifacts from any repository
osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
[DEBUG] Closing connection to remote
[ERROR] Internal error: java.lang.RuntimeException: Could not download artifacts from any
repository
[ERROR] osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
[ERROR] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could
not download artifacts from any repository
osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: Could not download artifacts from any repository
osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:360)
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:293)
at
org.eclipse.tycho.p2.facade.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:389)
at
org.eclipse.tycho.p2.facade.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:150)
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:90)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:91)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
... 11 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.{code}
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 3.3.0.M4
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 a.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
Was the above in Hudson or a local build? Which component? Could be a problem w/ sync lag
-- I forced a sleep at the end of publish.sh so that the check in (publish) would have
time to replicate/nfs copy before the check out (running tests).
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.M4
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:55 a.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-8667:
------------------------------
Fix Version/s: 3.3.x
(was: 3.3.0.M4)
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.x
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
Is this still an issue?
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.x
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:45 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin updated JBIDE-8667:
---------------------------------
Fix Version/s: 3.4.x
(was: 3.3.x)
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.4.x
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 a.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt closed JBIDE-8667.
-----------------------------
Resolution: Done
[~dgolovin] Going to assume this is no longer a problem as the last reported incident was
23/Sep/11.
If it's still an issue, please reopen.
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha1
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
6:25 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-8667 at 9/12/12 12:25 PM:
-------------------------------------------------------------
Reopening. New proposal is twofold:
a) to stick metadata in [0] to composite the various build snapshots posted there --
initially, let's just collect latest + previous so there's a buffer
b) the cleanup script [1] would have to regen the files every time it scrubs out the
folders.
[0] http://download.jboss.org/jbosstools/builds/nightly/trunk/ composite*.xml
[1]
https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse....
was (Author: nickboldt):
Reopening.
New proposal is twofold:
a) to stick composite metadata here to composite the various build snapshots posted
there.
b) the cleanup script [1] would have to regen the files every time it scrubs out the
folders.
[0] http://download.jboss.org/jbosstools/builds/nightly/trunk/
[1]
https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse....
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha1
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
6:35 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-8667 at 9/12/12 12:34 PM:
-------------------------------------------------------------
Reopening. New proposal is twofold:
a) to stick metadata in [0] to composite the various build snapshots posted there --
initially, let's just collect latest + previous so there's a buffer
b) the cleanup script [1] would have to regen the files every time it scrubs out the
folders.
[0] http://download.jboss.org/jbosstools/builds/nightly/trunk/ composite*.xml
[1]
https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse....
was (Author: nickboldt):
Reopening. New proposal is twofold:
a) to stick metadata in [0] to composite the various build snapshots posted there --
initially, let's just collect latest + previous so there's a buffer
b) the cleanup script [1] would have to regen the files every time it scrubs out the
folders.
[0] http://download.jboss.org/jbosstools/builds/nightly/trunk/ composite*.xml
[1]
https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse....
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha1
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
6:35 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-8667 at 9/12/12 12:34 PM:
-------------------------------------------------------------
Reopening. New proposal is twofold:
a) to stick metadata in [0] to composite the various build snapshots posted there --
initially, let's just collect latest + previous so there's a buffer
b) the cleanup script [1] would have to regen the files every time it scrubs out the
folders.
[0] http://download.jboss.org/jbosstools/builds/nightly/trunk/ composite*.xml
[1]
https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse....
was (Author: nickboldt):
Reopening. New proposal is twofold:
a) to stick metadata in [0] to composite the various build snapshots posted there --
initially, let's just collect latest + previous so there's a buffer
b) the cleanup script [1] would have to regen the files every time it scrubs out the
folders.
[0] http://download.jboss.org/jbosstools/builds/nightly/trunk/ composite*.xml
[1]
https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse....
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha1
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
9:49 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8667:
-----------------------------------
jbosstools-cleanup job will now deposit composite metadata into any folder with a build in
it, eg.,
http://download.jboss.org/jbosstools/builds/nightly/core/trunk/
So you can now point your local build at that folder and it will collate any existing
folders in there to a single site.
Next up - porting this to the publish.sh script so that it's updated every time a new
build is added
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha1
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
10:05 a.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-8667:
---------------------------------------
Fix Version/s: 4.0.0.Alpha2
(was: 4.0.0.Alpha1)
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
5:30 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt reassigned JBIDE-8667:
---------------------------------
Assignee: Denis Golovin (was: Nick Boldt)
http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ now contains metadata for
all the builds available. Metadata is updated every time a build is published to collect
the top 5 builds (which are 5 days old or less) into the composite*.xml files.
jbosstools-cleanup job will also update the metadata after it purges old jobs.
Let me know if that solves the problems you describe.
Should we be pointing downstream builds at this new URL instead of the
updates/nightly/core/trunk/ site?
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 4.0.0.Alpha2
Attachments: screenshot103.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
5:32 p.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-8667:
------------------------------
Attachment: trunk-site-contains-multiple-versions.png
Screenshot showing that the site
http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ as built by
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
contains two sets of build artifacts:
!trunk-site-contains-multiple-versions.png!
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 4.0.0.Alpha2
Attachments: screenshot103.png, trunk-site-contains-multiple-versions.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
10:13 a.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Denis Golovin resolved JBIDE-8667.
----------------------------------
Resolution: Done
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 4.0.0.Alpha2
Attachments: screenshot103.png, trunk-site-contains-multiple-versions.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
10:50 a.m.
New subject: [JBoss JIRA] (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
[
https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin...
]
Mickael Istria closed JBIDE-8667.
---------------------------------
improve publishing of component sites using composite metadata so
that content doesn't vanish and break downstream jobs
-----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8667
URL: https://issues.jboss.org/browse/JBIDE-8667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 4.0.0.Alpha2
Attachments: screenshot103.png, trunk-site-contains-multiple-versions.png
(2011-04-01 10:11:04) nickboldt: and while I'd love to do:
(2011-04-01 10:11:12) nickboldt: mkdir whatever-new
(2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
(2011-04-01 10:11:25) nickboldt: rm -fr whatever
(2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
(2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and
"it's there and updated" is less
(2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
(2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the
same folder on top
(2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of
whack w.r.t the site content
(2011-04-01 10:12:17) maxandersen: hmmm
(2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then
rename" instead of "push into existing and clean out cruft"
(2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm
all ears
(2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply
connect over ssh and run a script directly
(2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site
into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete
the existing one..
(2011-04-01 10:14:10) maxandersen: sftp rm should work?
(2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
(2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont
need to rename anything
(2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know
"locally"
(2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in
the composite*.xml files
(2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
(2011-04-01 10:15:17) nickboldt: and then delete the old one
1. generate composite metadata files on the fly
2. publish that into root dir, all/repo/
3. purge previous build's folder over scripted sftp?
--
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
4369
days inactive
4919
days old
jbosstools-issues@lists.jboss.org
44 comments
7 participants
participants (7)
-
Denis Golovin (JIRA) -
Jiri Peterka (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Mickael Istria (JIRA)
-
Nick Boldt (Commented) (JIRA)
-
Nick Boldt (JIRA)
-
Nick Boldt (Updated) (JIRA)