[jbosstools-issues] [JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
Mickael Istria (JIRA)
issues at jboss.org
Mon May 9 04:12:01 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202459#comment-13202459 ]
Mickael Istria commented on JBIDE-21657:
----------------------------------------
As far as I understand, there is no point in creating a different job for master and branch, as long as they build the same way. The necessary parameter for a check build are/should be already in there respective pom, so the job config would be exactly the same and as we do not deploy to branch specific location, a single job can handle both.
So, unless I get some objection when [~nickboldt] is back, here are my plans:
* Rename https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__pull-request_master/ to https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__pull-request/
* Rename https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.child-sites__pull-request_master/ to https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.child-sites__pull-request/
* Remove https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.child-sites__pull-request_4.3.mars/
> 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
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
>
> 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