[
https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-15482:
---------------------------------------
Just follow the messages from Jenkins, especially during first attempt to build JBT after
code freeze.
There is no need to escalate it.
Sync issue can be fixed. We just need to do publishing step by step. Publish p2 repo and
wait until it accessible through http. There are examples of maven plugin to do such wait
(see
https://github.com/dgolovin/maven-wait-plugin) or it can be done in shell if you are
familiar with it. Then publish compositeArtifacts.xml and wait again until it is available
online, and then publish compositeContent.xml.
Replace staging & staging.previous (two builds w/ reused URLs)
with uniquely timestamped build URLs and auto-regenerated composite*.xml files
---------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-15482
URL:
https://issues.jboss.org/browse/JBIDE-15482
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build, updatesite
Affects Versions: 4.2.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.2.0.Beta3
Be it proposed:
{quote}
that instead of an in-place move which reuses
generic folder names like "staging" and "staging.previous", we
composite build output using unique names like
2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
{quote}
We therefore need:
a) to regenerate the composite site each time there's a new build
published, in order to remove the oldest and add the newest (keeping
only the Nth and N-1rst builds)
(I have a script that might already work for this, or would need
tweaking.)
b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
no longer needed, perhaps simply by assuming no one needs it after
24hrs?
24 hours should be more that enough.
c) a cleanup script which can purge all but the builds which are no
more than 1 day old, keeping at all times at least two builds (N and
N-1)
(I have a script that already does this for folders like
http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
might need to be tweaked to work for a new pattern of
staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
{quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)