[jbosstools-issues] [JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
Nick Boldt (JIRA)
issues at jboss.org
Fri Feb 5 16:55:00 EST 2016
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159449#comment-13159449 ]
Nick Boldt commented on JBIDE-21657:
------------------------------------
I'm thinking we should publish these to a separate URL from /builds/ since these are only PRs. Perhaps a /pulls/ folder?
http://download.jboss.org/jbosstools/neon/snapshots/pulls/jbosstools-build-sites.aggregate.earlyaccess-site_master/2016-02-05_16-20-04-B1854-PR221/
Then users can still roll up these builds with -Djbosstools-build-type=neon/snapshots/pulls !
> 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
> Reporter: Nick Boldt
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.child-sites__pull-request_master/
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-build-sites.aggregate.earlyaccess-site_master/2016-02-05_16-34-19-B1/all/repo/buildinfo.json
> {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-build-sites.aggregate.earlyaccess-site_master/2016-02-05_16-34-19-B1/logs/GIT_REVISION.txt
> {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)
More information about the jbosstools-issues
mailing list