[jbosstools-issues] [JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
[
https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-21657:
---------------------------------------
{quote}+1000 on this. I did templates for doing this but we never got the templatized jobs
and at the time the builds were too intermingle to publish reliably to a separate site. If
we can do it manually for the 40 odd or so jobs that is better than nothing.{quote}
I can help with this. Do you mean the same thing we have for oomph and
https://github.com/maxandersen/buildchow?
{quote}About posting the build result - then I would say that is a big plus if we can, but
there is more often than not more than 1 pr on our repos so I don't think having
autoclean happen that way is practical. Can we do keep a week instead ?{quote}
I think I have to agree with it because it would let someone verify it manually. BTW can
we also write SWT bot tests to run on build results.
Would be also good to have cleanup script included into PRs.
{quote}Also note that when some git pushes (with or without force) to the PR it should
just overwrite the old pr content.{quote}
Do you mean the case when PR gets updated by someone pushes in PR branch with force?
I think we should test how it works in this build first. Or we can just configure get to
always do new clone.
set up jobs to handle building from PRs
---------------------------------------
Key: JBIDE-21657
URL: https://issues.jboss.org/browse/JBIDE-21657
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.3.1.CR1, 4.4.0.Alpha1
First experimental build:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
Output:
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
{code}
"revision" : {
"HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
"currentBranch" : "HEAD",
"knownReferences" : [{
"name" : "origin",
"url" :
"git://github.com/jbosstools/jbosstools-build-sites.git",
"ref" : "pr/221/merge"
}]
},
{code}
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
{code}
#Fri Feb 05 16:42:42 EST 2016
null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
{code}
build log:
{code}
Started by upstream project
"jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number
1
originally caused by:
GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge
conflicts.
...
Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> git -c core.askpass=true fetch --tags --progress
git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/*
+refs/pull/*:refs/remotes/origin/pr/*
Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805
(refs/remotes/origin/pr/221/merge)
> git config core.sparsecheckout # timeout=10
> git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
{code}
vars:
{code}
-DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
-DghprbPullId=221
-Dsha1=origin/pr/221/merge
"-DghprbPullDescription=GitHub pull request #221 of commit
50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
-DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)