]
Max Rydahl Andersen commented on JBIDE-21785:
---------------------------------------------
isn't this going to create a bottleneck where PR trigger builds prevents actually
running the main builds ?
I would assume having the main builds separate from PR builds (even if they have same
exact) configuration would be simpler/better. (reason why I wanted templatized jobs so it
was easy to create copies with same config but slightly different behaviorf for where
dependencies and deploys are from).
enable hybrid jobs which can handle both commits and PRs with
different publishing patterns
-------------------------------------------------------------------------------------------
Key: JBIDE-21785
URL:
https://issues.jboss.org/browse/JBIDE-21785
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Affects Versions: 4.3.1.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.4.0.Alpha2
Currently we have jobs which handle building from commits, then publishing to a builds/
folder.
And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then
publishing to a pulls/ folder.
[1]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site...
[2]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site...
Now we need to combine the jobs so that we can do both deployments from the same job,
eg.,
{code}
if [[ ! ${ghprbPullId} ]]; then
mvnStep1="clean install -DskipTests" # build without tests
mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows
difference into /builds/ folder
mvnStep3="verify" # run tests & fail job if problems found
else
mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/
folder if successful or fail if tests fail
mvnStep2="NONE"
mvnStep3="NONE"
fi
{code}