[
https://issues.jboss.org/browse/JBIDE-10312?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10312:
------------------------------------
I've simplified the publish.sh script so it uses the target platform folder name as
the flag -- thus jbosstools-JunoSR1 or jbdevstudio-JunoSR0b.
Updated jobs now spinning:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl...
>=1
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_stable...
>=1
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk...
>=33
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_trunk....
>=15
Next... once the stable_branch TPs are built, we can link to them from trunk builds
(parent pom, associate.properties)
We could further simplify the jobs if we had a pom in each target-platforms/*/ folder
which ran a build of multiple, local, unified, and jenkins subfolders.
WDYT?
Define a minimal target platform as opposed to the recommend one we
have now for builds
---------------------------------------------------------------------------------------
Key: JBIDE-10312
URL:
https://issues.jboss.org/browse/JBIDE-10312
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 4.0.0.Alpha2
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.0.0.Beta1
Seeing JBIDE-10311 made me realize that we actually could catch these by having a
*minimal* target platform to either build or test against.
The problem here is that a plugin got a plugin dependency based on the target platform -
but the target platform have the latest 3.7.1 version meaning those users running 3.7.0
would have problems installing it.
If we had a minimal target platform (.target) we could actually install/verify these
issues against it.
Not necessarily every night - but like once a week run the build or install the
updatesite against the minimal target platform would
reveal these dependency issues.
WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira