[jbosstools-issues] [JBoss JIRA] (JBIDE-15483) generate content in staging/_composite_/core/{trunk, 4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1}

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12807419#comment-12807419 ] 

Nick Boldt edited comment on JBIDE-15483 at 9/25/13 11:28 PM:
--------------------------------------------------------------

I have bootstrapped the required content under staging/CI/JOB_NAME/BUILD_ID using this script; however, this is old content and the jobs still need to be updated to use publish_new.sh instead of publish.sh so that they push content into the correct path format.

{code}
# as hudson user
cd ~/STATIC/jbds/builds/staging
for d in `find . -maxdepth 1 -name jbosstools-\*_master | grep -v aggregate | sort`; do num=`echo $d/logs/201*`; num=${num/.txt/}; num=${num##*/}; \
echo "mkdir ${d##./}" | sftp $TOOLS/builds/staging/CI/; scpr $d/* $TOOLS/builds/staging/CI/${d##./}/${num}/; done
{code}
                
      was (Author: nickboldt):
    Bootstrapping the required content under staging/CI/JOB_NAME/BUILD_ID using this script:

{code}
# as hudson user
cd ~/STATIC/jbds/builds/staging
for d in `find . -maxdepth 1 -name jbosstools-\*_master | grep -v aggregate | sort`; do num=`echo $d/logs/201*`; num=${num/.txt/}; num=${num##*/}; \
echo "mkdir ${d##./}" | sftp $TOOLS/builds/staging/CI/; scpr $d/* $TOOLS/builds/staging/CI/${d##./}/${num}/; done
{code}
                  
> generate content in staging/_composite_/core/{trunk,4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1}
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15483
>                 URL: https://issues.jboss.org/browse/JBIDE-15483
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> Because the content in builds/staging/\{JOB_NAME}/all/repo/ and builds/staging.previous/\{JOB_NAME}/all/repo/ is moving to builds/staging/\{JOB_NAME}/\{BUILD_ID_N} and builds/staging/\{JOB_NAME}/\{BUILD_ID_N-1}, we need to generate a list of matching build URLs for inclusion in the composite*.xml files, perhaps based on a template that's stored in github (to define which projects to include).
> Parameters to the generation would need to be:
> a) template
> b) number of builds per project to include (1, for stable_branch or 2, for trunk)
> Constraints:
> * Need to ensure that the generated files are always fresher than anything pulled from github via rsync, so templates should not be called "compositeContent.xml" but rather "compositeContent.template.xml"
> * Need to be able to run this regeneration as a Jenkins job, perhaps as the first step in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_41/ and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/
> Worries:
> * What happens if the regen happens and then a jbosstools-cleanup.sh fires minutes later, wiping out that N-1 build? Does jbosstools-cleaup.sh need to regen these files too?
> Default operation of jbosstools-cleanup.sh as called from publish_new.sh and publish.sh is to keep the last 5 builds and anything newer than 5 days old; if there are no such builds, it will always keep the last build in a folder:
> {code}./jbosstools-cleanup.sh --keep 5 --age-to-delete 5 --childFolderSuffix /all/repo/{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira