[jbosstools-dev] Build target platform for master

[Nick Boldt]

Less jobs = less maintenance.

In the past I've just updated the matrix to exclude the stuff we aren't 
actively building immediately before running the job (like the 4.3x 
stuff while building 4.4x).

So... I've done that now for the [1] job, by temporarily removing the 
4.41.x configuration so we only build the 4.5x stuff.

[1] 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstoolstargetplatforms-matrix/

--

When it's time to start up the 4.42.x builds for Luna SR2 (in February), 
we can just add that configuration back into the job, and voila.

N

On 01/20/2015 07:17 PM, Max Rydahl Andersen wrote:
> On 20 Jan 2015, at 11:21, Mickael Istria wrote:
>
>> On 01/20/2015 11:16 AM, Denis Golovin wrote:
>>> It there any better way to rebuild targetplatform for master?
>>> Now I can trigger only
>>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstoolstargetplatforms-matrix/
>>> which rebuilds luna branch and master.
>> There is currently no better way of doing that.
>> We find it more convenient to have a single job that does twice the
>> job, than to have multiple jobs (1 for each TP). Practically, it has
>> never caused any delay or issue...
>
> why would we want to trigger an update of the branch build if only
> master needs building ?
>
> why not have branched jobs for TP like we have for other components ?
>
> /max
> http://about.me/maxandersen
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com