[JBoss JIRA] (JBDS-3593) Enable continuous delivery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3593?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3593:
----------------------------------
Woo, CD! +100 for this idea.
So right now, the job you created is just a wrapper for jbosstools-install-grinder.install-tests.matrix_master. Could you add more jobs to it?
Note too that sometimes one of the many configs in that job (or the p2director one) fails while all the rest are fine. I'm not sure I would hold back a release if 1 out of 6 child jobs failed due to a network glitch. So... we would still need to manually review when a job in the buildflow was red to determine if it was 6/6 failures or 1/6 failures, like http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-gr... (which was fired again via Naginator and was then 6/6 success.
Or else we'd need to enable a naginator-like approach to this build flow job... but do we want to have to rebuild ALL the test install jobs for ALL the platform configs, just because ONE child config failed? Seems like a total waste of cycles and time.
Anyway, if it sounds like I'm crapping on this idea, I'm NOT. I do like this idea. :D
I'm just trying to flesh out how we can use it given the current constraints we have for jobs that SOMETIMES fail for a non-reproduceable reason, which fix themselves when they respin.
How would you handle that case? And what other verification steps can we add here to ensure a build is "ready to stage" or "ready to exit stage into prod" ?
> Enable continuous delivery
> --------------------------
>
> Key: JBDS-3593
> URL: https://issues.jboss.org/browse/JBDS-3593
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 10.0.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 10.x
>
>
> A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective).
> If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt.
> I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22275) oc version is not recognized
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-22275 at 4/29/16 10:50 AM:
-------------------------------------------------------------------------
OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2
It can be replaced with
{code}
"oc v([0-9\\.-\\.]*)(?:-(?:([0-9]+)-)?(.*))?"
{code}
So, two hyphens are valid in oc v1.2.0-1-rc2, one hyphen in oc v1.2.0-rc2
was (Author: scabanovich):
OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2
It can be replaced with
{code}
"oc v([0-9\\.-\\.]*)(?:-(?:([0-9]+)-)?(.*))?"
{code}
> oc version is not recognized
> ----------------------------
>
> Key: JBIDE-22275
> URL: https://issues.jboss.org/browse/JBIDE-22275
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: oc_warning.png
>
>
> Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0.
> !oc_warning.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-495) Support graphiti milestone version 0.13
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-495?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-495.
-----------------------------------
Closed as obsolete. Current JBTIS-TP 4.3.1.Final uses graphiti of version 0.13.0.v20160203-1129
> Support graphiti milestone version 0.13
> ----------------------------------------
>
> Key: JBTIS-495
> URL: https://issues.jboss.org/browse/JBTIS-495
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.0.Final-TP
>
>
> *Reason:* Replace the older 0.13 graphiti reference and m2e 1.6.1 reference in JBTIS TP with an actual milestone version from Eclipse Mars SR1.RC3
> *Project page/sources:*
> *Version:* 4.3.0.Beta1f-SNAPSHOT
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBDSIS
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> < org.eclipse.m2e.model.edit [1.6.2.20150819-1555]
> < org.eclipse.graphiti.feature.feature.jar [0.13.0.v20150720-0642]
> < org.eclipse.emf.compare.ide.ui.feature.jar [3.1.0.201506080833]
> < org.eclipse.ocl.uml [5.0.100.v20150519-0914]
> < org.eclipse.graphiti.ui [0.13.0.v20150720-0642]
> < org.eclipse.m2e.profiles.ui [1.6.2.20150819-1555]
> < org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20150720-0642]
> < org.eclipse.graphiti.doc [0.13.0.v20150720-0642]
> < org.eclipse.m2e.maven.indexer [1.6.2.20150819-1553]
> < org.eclipse.ocl.uml.feature.jar [5.1.0.v20150521-1211]
> < org.eclipse.m2e.scm [1.6.2.20150819-1555]
> < org.eclipse.m2e.editor.xml [1.6.2.20150819-1555]
> < org.eclipse.emf.compare.rcp [2.3.0.201506080833]
> < org.eclipse.m2e.feature.feature.group [1.6.2.20150819-1555]
> < org.eclipse.emf.compare.ide [3.2.0.201506080833]
> < org.eclipse.ocl.uml.feature.group [5.1.0.v20150521-1211]
> < org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20150720-0642]
> < org.eclipse.ocl.common [1.3.0.v20150519-0914]
> < org.eclipse.m2e.lifecyclemapping.defaults [1.6.2.20150819-1555]
> < org.eclipse.m2e.profiles.core [1.6.2.20150819-1555]
> < org.eclipse.graphiti.ui.capabilities [0.13.0.v20150720-0642]
> < org.eclipse.emf.compare.rcp.ui [4.1.0.201506080833]
> < org.eclipse.graphiti.pattern [0.13.0.v20150720-0642]
> < org.eclipse.ocl.jdt.annotation7 [1.0.0.v20150519-0914]
> < org.eclipse.graphiti.mm [0.13.0.v20150720-0642]
> < org.eclipse.m2e.jdt.ui [1.6.2.20150819-1555]
> < org.eclipse.m2e.core [1.6.2.20150819-1555]
> < org.eclipse.ocl.all.feature.group [5.1.0.v20150525-1635]
> < org.eclipse.emf.ecore.feature.jar [2.11.0.v20150512-0501]
> < org.eclipse.emf.compare.feature.jar [3.1.0.201506080833]
> < org.eclipse.m2e.core.ui [1.6.2.20150819-1555]
> < org.eclipse.emf.ecore.feature.group [2.11.0.v20150512-0501]
> < org.eclipse.emf.codegen.ecore.ui [2.11.0.v20150601-0402]
> < org.eclipse.m2e.launching [1.6.2.20150819-1555]
> < org.eclipse.ocl.all.feature.jar [5.1.0.v20150525-1635]
> < org.eclipse.emf.compare.feature.group [3.1.0.201506080833]
> < org.eclipse.m2e.feature.feature.jar [1.6.2.20150819-1555]
> < org.eclipse.m2e.discovery [1.6.2.20150819-1555]
> < org.eclipse.m2e.archetype.common [1.6.2.20150819-1553]
> < org.eclipse.draw2d [3.10.0.201506010206]
> < org.eclipse.graphiti [0.13.0.v20150720-0642]
> < org.eclipse.emf.ecore [2.11.0.v20150512-0501]
> < org.eclipse.emf.compare.doc [3.2.0.201506080833]
> < org.eclipse.emf.ecore.change [2.11.0.v20150512-0501]
> < org.eclipse.emf.compare.ide.ui [4.1.0.201506080833]
> < org.eclipse.ocl.feature.jar [3.5.0.v20150525-1635]
> < org.eclipse.emf.compare.ide.ui.feature.group [3.1.0.201506080833]
> < org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20150720-0642]
> < org.eclipse.emf.codegen.ecore.ui.feature.jar [2.11.0.v20150601-0402]
> < org.eclipse.m2e.editor [1.6.2.20150819-1555]
> < org.eclipse.emf.compare.edit [4.1.0.201506080833]
> < org.eclipse.m2e.tests.common [1.6.2.20150819-1555]
> < org.eclipse.ocl [3.5.0.v20150521-1211]
> < org.eclipse.emf.ecore.xmi [2.11.0.v20150512-0501]
> < org.eclipse.ocl.feature.group [3.5.0.v20150525-1635]
> < org.eclipse.emf.codegen.ecore.ui.feature.group [2.11.0.v20150601-0402]
> < org.eclipse.m2e.jdt [1.6.2.20150819-1555]
> < org.eclipse.graphiti.feature.feature.group [0.13.0.v20150720-0642]
> < org.eclipse.m2e.workspace.cli [0.3.1]
> < org.eclipse.m2e.maven.runtime.slf4j.simple [1.6.2.20150819-1553]
> < org.eclipse.ocl.ecore [3.5.0.v20150525-1635]
> < org.eclipse.m2e.maven.runtime [1.6.2.20150819-1553]
> < org.eclipse.graphiti.export.batik [0.13.0.v20150720-0642]
> < org.eclipse.m2e.refactoring [1.6.2.20150819-1555]
> < org.eclipse.emf.compare [3.2.0.201506080833]
> < org.maven.ide.eclipse [1.6.2.20150819-1555]
> > org.eclipse.emf.codegen.ecore.ui.feature.group [2.12.0.v20150817-0432]
> > org.eclipse.graphiti.feature.feature.group [0.13.0.v20150818-1354]
> > org.eclipse.emf.ecore [2.12.0.v20150805-0624]
> > org.eclipse.ocl.jdt.annotation7 [1.0.100.v20150611-1921]
> > org.eclipse.emf.compare.feature.group [3.2.0.201508181443]
> > org.eclipse.graphiti.mm [0.13.0.v20150818-1354]
> > org.eclipse.emf.ecore.xmi [2.12.0.v20150805-0624]
> > org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20150818-1354]
> > org.eclipse.draw2d [3.10.1.201508170204]
> > org.eclipse.emf.compare.ide.ui.feature.group [3.2.0.201508181443]
> > org.eclipse.emf.compare.ide.ui [4.2.0.201508181443]
> > org.eclipse.emf.compare.doc [3.2.0.201508181443]
> > org.eclipse.ocl.ecore [3.5.100.v20150611-1921]
> > org.eclipse.graphiti.ui [0.13.0.v20150818-1354]
> > org.eclipse.emf.compare.rcp [2.4.0.201508181443]
> > org.eclipse.emf.compare.rcp.ui [4.2.0.201508181443]
> > org.eclipse.ocl [3.5.100.v20150611-1921]
> > org.eclipse.graphiti.ui.capabilities [0.13.0.v20150818-1354]
> > org.eclipse.ocl.all.feature.group [5.1.100.v20150611-1921]
> > org.eclipse.graphiti [0.13.0.v20150818-1354]
> > org.eclipse.emf.compare.ide [3.3.0.201508181443]
> > org.eclipse.emf.codegen.ecore.ui [2.12.0.v20150817-0432]
> > org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20150818-1354]
> > org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20150818-1354]
> > org.eclipse.emf.compare.feature.jar [3.2.0.201508181443]
> > org.eclipse.ocl.feature.jar [3.5.100.v20150611-1921]
> > org.eclipse.graphiti.doc [0.13.0.v20150818-1354]
> > org.eclipse.graphiti.pattern [0.13.0.v20150818-1354]
> > org.eclipse.emf.compare.ide.ui.feature.jar [3.2.0.201508181443]
> > org.eclipse.ocl.all.feature.jar [5.1.100.v20150611-1921]
> > org.eclipse.graphiti.feature.feature.jar [0.13.0.v20150818-1354]
> > org.eclipse.emf.ecore.change [2.11.0.v20150805-0624]
> > org.eclipse.ocl.common [1.3.100.v20150611-1921]
> > org.eclipse.emf.compare.edit [4.2.0.201508181443]
> > org.eclipse.emf.ecore.feature.jar [2.12.0.v20150805-0624]
> > org.eclipse.ocl.feature.group [3.5.100.v20150611-1921]
> > org.eclipse.ocl.uml.feature.jar [5.1.100.v20150611-1921]
> > org.eclipse.graphiti.export.batik [0.13.0.v20150818-1354]
> > org.eclipse.ocl.uml.feature.group [5.1.100.v20150611-1921]
> > org.eclipse.emf.ecore.feature.group [2.12.0.v20150805-0624]
> > org.eclipse.emf.codegen.ecore.ui.feature.jar [2.12.0.v20150817-0432]
> > org.eclipse.emf.compare [3.3.0.201508181443]
> > org.eclipse.ocl.uml [5.0.200.v20150611-1921]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 66 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 43 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20850:
-------------------------------
Sprint: devex #114 May 2017 (was: devex #113 April 2016)
> target platform matrix job's install test step fails silently when using incompatible Eclipse version
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20850
> URL: https://issues.jboss.org/browse/JBIDE-20850
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
>
> For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform:
> {code}
> [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554)
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158)
>
> BUILD FAILED
> /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> {code}
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034)
> [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859)
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> And yet the build is successful here:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> This is most likely because all three configs are set to use the same Eclipse JEE bundle:
> {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz
> {code}
> So... I guess there are two things we need here:
> a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1
> b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20850) target platform matrix job's install test step fails silently when using incompatible Eclipse version
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20850?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20850:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> target platform matrix job's install test step fails silently when using incompatible Eclipse version
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20850
> URL: https://issues.jboss.org/browse/JBIDE-20850
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
>
> For some reason, the targetplatforms-matrix job is ignoring this, and still getting blue balls when it can't install the built target platform:
> {code}
> [p2.dir] !MESSAGE Software being installed: Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.5.1.20150910-0554 (epp.package.jee 4.5.1.20150910-0554)
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.100.v20150808-0755 (org.eclipse.ui.ide 3.11.100.v20150808-0755)
> [p2.dir] !MESSAGE Eclipse IDE UI 3.11.0.v20150825-2158 (org.eclipse.ui.ide 3.11.0.v20150825-2158)
>
> BUILD FAILED
> /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/85031d6f/director.xml:62: exec returned: 13
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> {code}
> [p2.dir] !MESSAGE Only one of the following can be installed at once:
> [p2.dir] !MESSAGE Refactoring Core 3.6.201.v20150819-1034 (org.eclipse.ltk.core.refactoring 3.6.201.v20150819-1034)
> [p2.dir] !MESSAGE Refactoring Core 3.6.200.v20140826-0859 (org.eclipse.ltk.core.refactoring 3.6.200.v20140826-0859)
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> And yet the build is successful here:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf...
> This is most likely because all three configs are set to use the same Eclipse JEE bundle:
> {code}downloadURL=http://www.eclipse.org/downloads/download.php?r=1&file=/technology/epp/downloads/release/mars/1/eclipse-jee-mars-1-linux-gtk.tar.gz
> {code}
> So... I guess there are two things we need here:
> a) ensure that the TP and Eclipse versions are compatible (4.50 == mars-R, 4.51 == mars-1, 4.60 == neon-M1) in the job config, rather than trying to install the 4.50 or 4.60 TPs onto Eclipse Mars.1
> b) ensure that the log is checked for the string "BUILD FAILED" or "director.xml .* exec returned: 13" and if found, fail the build
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years