[jbosstools-issues] [JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201206#comment-13201206 ] 

Nick Boldt commented on JBIDE-21785:
------------------------------------

Latest experiment is here [1]. Result:

{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__pull-request_master/1/console}
17:29:11 GitHub pull request #412 of commit 6ef861a47026124596a20fa24bd80d22507e9665, no merge conflicts.
17:29:11 Setting status of 6ef861a47026124596a20fa24bd80d22507e9665 to PENDING with url http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__pull-request_master/1/ and message: Build started, sha1 is merged
17:29:11 FileNotFoundException means that the credentials Jenkins is using is probably wrong. Or the user account does not have write access to the repo.
17:29:11 java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}{code}

[1] https://github.com/jbosstools/jbosstools-build-ci/commit/a45ff3671b09b57743d834ba2e353f1966331ea6

So, still need to figure out what credentials to use to talk to github.

> 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-sites.aggregate.child-sites__pull-request_master/
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.child-sites__pull-request_4.3.mars/
> 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)