[jbosstools-issues] [JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns
Max Rydahl Andersen (JIRA)
issues at jboss.org
Tue May 17 05:04:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238443#comment-13238443 ]
Max Rydahl Andersen commented on JBIDE-21785:
---------------------------------------------
also, PR builds probably can benefit from skipping some build steps for some jobs and might even want to happen at a finer granularity that the full component build. Thus I think there are a lot of reasons to have separate jobs for it.
Is there a reason to why not having different jobs but with same configs ? (Besides we don't have templatized of jobs to easily manage this?)
> 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)
More information about the jbosstools-issues
mailing list