[
https://issues.jboss.org/browse/JBBUILD-720?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBBUILD-720:
------------------------------------
If the goal here is to drive the parameters into the job and thus into the script, you can
do so like this:
a) log into Jenkins, then configure the job.
b) check the box for "This build is parameterized".
c) set a String Parameter called TARGETPATHROOT.
d) set the default value to
"modeshape@filemgmt.jboss.org:/downloads_htdocs/modeshape/tools/updates/development/juno/3.3.0.Beta5/"
(You could drive it from multiple parameters like in your example, but since it's just
you running it, that seems unnecessary.)
Then to publish, just do this via an Execute shell block in the jobs:
{code}
cd ${WORKSPACE}/sources/
wget
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh -q
--no-check-certificate -N
DESTINATION=${TARGETPATHROOT} . publish.sh tools/tmp
{code}
Change modeshape-tools-continuous Jenkins Job Update-Site Output
Directory
--------------------------------------------------------------------------
Key: JBBUILD-720
URL:
https://issues.jboss.org/browse/JBBUILD-720
Project: JBoss Build System
Issue Type: Task
Components: Maven Builds
Affects Versions: Build Support 2011
Reporter: Dan Florian
Assignee: Dan Florian
The modeshape-tools-continuous job outputs the ModeShape Tools update-site to here:
/downloads_htdocs/modeshape/builds/staging/modeshape-tools-continuous/all/repo
We would like the path to be (something like) this:
/downloads_htdocs/modeshape/tools/update/{stable|develop}/{helios|indigo|juno|etc}
At a minimum, the path needs to have the "tools" segment as this identifies it
from the ModeShape project. What do other projects do as far as stable vs. develop build?
Do other project's put the Eclipse release in the path? Please see MODE-1506 for
additional questions/discussion.
I was told to get with you on this Nick. Please update this issue's project and
component as appropriate as I wasn't sure.
--
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