[
https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-21785 at 5/6/16 10:10 AM:
-------------------------------------------------------------
Seems as though PR jobs won't also build commits automatically:
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server__pull-request_master/5/}
GitHub pull request #412 of commit ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f, no merge
conflicts.
734e1c3a03355c0a57e21bb723241e98f2286751
refs/remotes/origin/pr/412/merge
Test Result (69 failures / ±0)
{code}
vs.
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/966/}
JBIDE-22157 - per-module zip settings (commit: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f)
Revision: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f
refs/remotes/origin/master
Test Result (3 failures / ±0)
{code}
So, perhaps the solution is to have a buildflow job triggered every 3 hours to poke the
projects into building anything they haven't already built.
was (Author: nickboldt):
Seems as though PR jobs won't also build commits:
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server__pull-request_master/5/}
GitHub pull request #412 of commit ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f, no merge
conflicts.
734e1c3a03355c0a57e21bb723241e98f2286751
refs/remotes/origin/pr/412/merge
Test Result (69 failures / ±0)
{code}
vs.
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/966/}
JBIDE-22157 - per-module zip settings (commit: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f)
Revision: ce964c7d9c30d8732a9627d8e3b37997eb9c6d5f
refs/remotes/origin/master
Test Result (3 failures / ±0)
{code}
So, perhaps the solution is to have a buildflow job triggered every 3 hours to poke the
projects into building anything they haven't already built.
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}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)