September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23212: ------------------------------------ I think you meant Mickael Istria, not Azuma. Also, https://maven.apache.org/guides/introduction/introduction-to-the-lifecycl... says that the maven lifecycle phase `install` INCLUDES `verify`. So... there's that. > Baseline check does not seem to work with features > -------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho, > Fix For: 4.4.2.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23212 at 9/22/16 9:46 AM: ------------------------------------------------------------- [~nickboldt] [~mickael_istria]] verify is required for the baseline check to run was (Author: jeffmaury): [~nickboldt] [~mazema] verify is required for the baseline check to run > Baseline check does not seem to work with features > -------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho, > Fix For: 4.4.2.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23206) build flag for always use current timestamp to assist QE in testing PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23206?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23206. ------------------------------ Release Notes Text: Remember though that if you use this -PR flag, you will likely have to UNINSTALL any current-date-versioned plugins/features in order to update to a new CI build, as your local build bits will look newer than bits with jgit timestamps. Fix Version/s: 4.4.2.AM1 Resolution: Done Merged to master and built. New parent pom 4.4.2.AM1-SNAPSHOT is live. Enjoy! Remember though that if you use this you will likely have to UNINSTALL any current-date-versioned plugins/features in order to update to a new CI build, as your local build bits will look newer than bits with jgit timestamps. > build flag for always use current timestamp to assist QE in testing PRs > ----------------------------------------------------------------------- > > Key: JBIDE-23206 > URL: https://issues.jboss.org/browse/JBIDE-23206 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > In the case where a PR is not rebased against master constantly, QE is blocked from testing it under two situations: > 1) The PR job has produced a site. QE installs most recent jbt, then tries to install the PR site. This fails because the PR site is older than the nightly build. > 2) The QE rep checks out the PR and tries to build locally. The timestamps match the change date (ie the date the PR was last changed), which is still older than the nightly build. > In both situations, QE cannot install a locally-built or PR-built site on top of a more recent nightly build of JBT. We cannot expect QE to rebase and (if required) merge / change code. > The best bet here is to simply add a flag QE can use when building locally to always use current timestamp, to ensure locally built unit is always 'newest'. > We then document that flag in devdoc for QE and make it part of their standard workflow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23212: ------------------------------------ [~nickboldt] [~mazema] verify is required for the baseline check to run > Baseline check does not seem to work with features > -------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho, > Fix For: 4.4.2.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-911) Cannot install all features from the zip file in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-911?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-911: ------------------------------------ Description: Cannot install all features from the zip file, e.g. com.jboss.devstudio.integration-stack.bpr.feature.feature.group. Note that this feature is visible for users only if they uncheck 'Group items by category'. All features listed in categories (which are visible by default) can be installed without any problem. Here is the error if we try to install com.jboss.devstudio.integration-stack.bpr.feature.feature.group in offline mode {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) Missing requirement: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) requires 'org.eclipse.rse.feature.group 0.0.0' but it could not be found {code} was: Cannot install all features from the zip file, e.g. com.jboss.devstudio.integration-stack.bpr.feature.feature.group. Note that this feature is visible for users only if they uncheck 'Group items by category'. All features listed in categories can be installed without any problem. Here is the error if we try to install com.jboss.devstudio.integration-stack.bpr.feature.feature.group in offline mode {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) Missing requirement: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) requires 'org.eclipse.rse.feature.group 0.0.0' but it could not be found {code} > Cannot install all features from the zip file in offline mode > ------------------------------------------------------------- > > Key: JBTIS-911 > URL: https://issues.jboss.org/browse/JBTIS-911 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.Alpha1 > Environment: RHDS 10.0.0.GA-v20160615-1853-B33 > RHDS-IS 10.0.0.Alpha1 EA zip file > Reporter: Andrej Podhradsky > > Cannot install all features from the zip file, e.g. com.jboss.devstudio.integration-stack.bpr.feature.feature.group. > Note that this feature is visible for users only if they uncheck 'Group items by category'. All features listed in categories (which are visible by default) can be installed without any problem. > Here is the error if we try to install com.jboss.devstudio.integration-stack.bpr.feature.feature.group in offline mode > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) > Missing requirement: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) requires 'org.eclipse.rse.feature.group 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-911) Cannot install all features from the zip file in offline mode

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-911: --------------------------------------- Summary: Cannot install all features from the zip file in offline mode Key: JBTIS-911 URL: https://issues.jboss.org/browse/JBTIS-911 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 10.0.0.Alpha1 Environment: RHDS 10.0.0.GA-v20160615-1853-B33 RHDS-IS 10.0.0.Alpha1 EA zip file Reporter: Andrej Podhradsky Cannot install all features from the zip file, e.g. com.jboss.devstudio.integration-stack.bpr.feature.feature.group. Note that this feature is visible for users only if they uncheck 'Group items by category'. All features listed in categories can be installed without any problem. Here is the error if we try to install com.jboss.devstudio.integration-stack.bpr.feature.feature.group in offline mode {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) Missing requirement: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) requires 'org.eclipse.rse.feature.group 0.0.0' but it could not be found {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23153) Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23153?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23153: ------------------------------------------ merged into jbosstools-integration-tests/master > Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23153 > URL: https://issues.jboss.org/browse/JBIDE-23153 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test, openshift_v3 > Fix For: 4.4.2.AM1 > > > OpenShiftCommandLineToolsRequirement will redownload the oc binary on each invocation. This is time consuming, it should check if it exists and not re-download it in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23212 at 9/22/16 9:39 AM: ------------------------------------------------------------- Cannot reproduce locally: {code} cd ~/tru/jbosstools-central/ hub checkout https://github.com/jbosstools/jbosstools-central/pull/387 mvn clean install -DskipTests {code} {code} [INFO] Reactor Summary: [INFO] [INFO] jbosstools-central ................................. SUCCESS [ 1.413 s] [INFO] discovery.all ...................................... SUCCESS [ 0.019 s] [INFO] discovery.plugins .................................. SUCCESS [ 0.017 s] [INFO] org.jboss.tools.discovery.core ..................... SUCCESS [ 9.697 s] [INFO] discovery.tests .................................... SUCCESS [ 0.017 s] [INFO] maven.all .......................................... SUCCESS [ 0.021 s] [INFO] maven.features ..................................... SUCCESS [ 0.013 s] [INFO] maven.plugins ...................................... SUCCESS [ 0.017 s] [INFO] org.jboss.tools.maven.core ......................... SUCCESS [ 3.517 s] [INFO] org.jboss.tools.maven.ui ........................... SUCCESS [ 3.350 s] [INFO] org.jboss.tools.maven.conversion.ui ................ SUCCESS [ 2.961 s] [INFO] org.jboss.tools.maven.feature ...................... SUCCESS [ 1.552 s] [INFO] org.jboss.tools.maven.seam ......................... SUCCESS [ 2.501 s] [INFO] org.jboss.tools.maven.seam.feature ................. SUCCESS [ 1.466 s] ... [INFO] central.maven.examples.site ........................ SUCCESS [ 12.125 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 05:19 min [INFO] Finished at: 2016-09-22T09:35:26-04:00 [INFO] Final Memory: 227M/831M {code} So... I've wiped the job's workspace and re-kicked the PR build... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... was (Author: nickboldt): Cannot reproduce locally: {code} cd ~/tru/jbosstools-central/ hub checkout https://github.com/jbosstools/jbosstools-central/pull/387 mvn clean install -DskipTests {code} {code} [INFO] Reactor Summary: [INFO] [INFO] jbosstools-central ................................. SUCCESS [ 1.413 s] [INFO] discovery.all ...................................... SUCCESS [ 0.019 s] [INFO] discovery.plugins .................................. SUCCESS [ 0.017 s] [INFO] org.jboss.tools.discovery.core ..................... SUCCESS [ 9.697 s] [INFO] discovery.tests .................................... SUCCESS [ 0.017 s] [INFO] maven.all .......................................... SUCCESS [ 0.021 s] [INFO] maven.features ..................................... SUCCESS [ 0.013 s] [INFO] maven.plugins ...................................... SUCCESS [ 0.017 s] [INFO] org.jboss.tools.maven.core ......................... SUCCESS [ 3.517 s] [INFO] org.jboss.tools.maven.ui ........................... SUCCESS [ 3.350 s] [INFO] org.jboss.tools.maven.conversion.ui ................ SUCCESS [ 2.961 s] [INFO] org.jboss.tools.maven.feature ...................... SUCCESS [ 1.552 s] [INFO] org.jboss.tools.maven.seam ......................... SUCCESS [ 2.501 s] [INFO] org.jboss.tools.maven.seam.feature ................. SUCCESS [ 1.466 s] [INFO] org.jboss.tools.maven.cdi .......................... SUCCESS [ 2.130 s] [INFO] org.jboss.tools.maven.cdi.feature .................. SUCCESS [ 1.362 s] [INFO] org.jboss.tools.maven.hibernate .................... SUCCESS [ 1.998 s] [INFO] org.jboss.tools.maven.hibernate.feature ............ SUCCESS [ 1.330 s] [INFO] org.jboss.tools.maven.portlet ...................... SUCCESS [ 1.958 s] [INFO] org.jboss.tools.maven.portlet.feature .............. SUCCESS [ 1.382 s] [INFO] maven.tests ........................................ SUCCESS [ 0.016 s] [INFO] org.jboss.tools.maven.common.test .................. SUCCESS [ 0.926 s] [INFO] org.jboss.tools.maven.jbosspackaging ............... SUCCESS [ 2.190 s] [INFO] org.jboss.tools.maven.jdt .......................... SUCCESS [ 2.031 s] [INFO] org.jboss.tools.maven.configurators.tests .......... SUCCESS [ 4.061 s] [INFO] org.jboss.tools.maven.conversion.test .............. SUCCESS [ 0.642 s] [INFO] org.jboss.tools.maven.sourcelookup.core ............ SUCCESS [ 2.390 s] [INFO] org.jboss.tools.maven.sourcelookup.ui .............. SUCCESS [ 3.356 s] [INFO] org.jboss.tools.maven.sourcelookup.test ............ SUCCESS [ 1.885 s] [INFO] org.jboss.tools.maven.test.feature ................. SUCCESS [ 0.359 s] [INFO] org.jboss.tools.maven.jbosspackaging.feature ....... SUCCESS [ 1.512 s] [INFO] org.jboss.tools.maven.sourcelookup.feature ......... SUCCESS [ 1.337 s] [INFO] org.jboss.tools.maven.jdt.feature .................. SUCCESS [ 1.176 s] [INFO] examples.all ....................................... SUCCESS [ 0.026 s] [INFO] examples.features .................................. SUCCESS [ 0.015 s] [INFO] examples.plugins ................................... SUCCESS [ 0.024 s] [INFO] org.jboss.tools.project.examples ................... SUCCESS [ 3.838 s] [INFO] org.jboss.tools.community.project.examples ......... SUCCESS [ 1.593 s] [INFO] org.jboss.tools.community.project.examples.feature . SUCCESS [ 1.242 s] [INFO] org.jboss.tools.project.examples.cheatsheet ........ SUCCESS [ 2.260 s] [INFO] org.jboss.tools.project.examples.feature ........... SUCCESS [ 1.032 s] [INFO] org.jboss.tools.maven.project.examples ............. SUCCESS [ 3.225 s] [INFO] org.jboss.tools.maven.project.examples.feature ..... SUCCESS [ 1.424 s] [INFO] org.jboss.tools.project.examples.seam .............. SUCCESS [ 2.031 s] [INFO] org.jboss.tools.project.examples.seam.feature ...... SUCCESS [ 1.248 s] [INFO] examples.tests ..................................... SUCCESS [ 0.012 s] [INFO] org.jboss.tools.maven.examples.test ................ SUCCESS [ 0.881 s] [INFO] org.jboss.tools.project.examples.test .............. SUCCESS [ 1.850 s] [INFO] org.jboss.tools.project.examples.test.feature ...... SUCCESS [ 0.751 s] [INFO] central.all ........................................ SUCCESS [ 0.180 s] [INFO] central.plugins .................................... SUCCESS [ 0.014 s] [INFO] org.jboss.tools.central ............................ SUCCESS [ 6.996 s] [INFO] org.jboss.tools.community.central .................. SUCCESS [ 1.879 s] [INFO] org.jboss.tools.central.themes ..................... SUCCESS [ 1.824 s] [INFO] central.features ................................... SUCCESS [ 0.014 s] [INFO] org.jboss.tools.central.feature .................... SUCCESS [ 1.118 s] [INFO] org.jboss.tools.community.central.feature .......... SUCCESS [ 1.520 s] [INFO] org.jboss.tools.central.themes.feature ............. SUCCESS [ 1.277 s] [INFO] central.tests ...................................... SUCCESS [ 0.014 s] [INFO] org.jboss.tools.central.test ....................... SUCCESS [ 1.150 s] [INFO] org.jboss.tools.central.test.feature ............... SUCCESS [ 0.244 s] [INFO] org.jboss.tools.central.easymport.feature .......... SUCCESS [ 0.862 s] [INFO] central.maven.examples.site ........................ SUCCESS [ 12.125 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 05:19 min [INFO] Finished at: 2016-09-22T09:35:26-04:00 [INFO] Final Memory: 227M/831M {code} So... I've wiped the job's workspace and re-kicked the PR build... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Baseline check does not seem to work with features > -------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho, > Fix For: 4.4.2.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) Baseline check does not seem to work with features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23212: ------------------------------------ Cannot reproduce locally: {code} cd ~/tru/jbosstools-central/ hub checkout https://github.com/jbosstools/jbosstools-central/pull/387 mvn clean install -DskipTests {code} {code} [INFO] Reactor Summary: [INFO] [INFO] jbosstools-central ................................. SUCCESS [ 1.413 s] [INFO] discovery.all ...................................... SUCCESS [ 0.019 s] [INFO] discovery.plugins .................................. SUCCESS [ 0.017 s] [INFO] org.jboss.tools.discovery.core ..................... SUCCESS [ 9.697 s] [INFO] discovery.tests .................................... SUCCESS [ 0.017 s] [INFO] maven.all .......................................... SUCCESS [ 0.021 s] [INFO] maven.features ..................................... SUCCESS [ 0.013 s] [INFO] maven.plugins ...................................... SUCCESS [ 0.017 s] [INFO] org.jboss.tools.maven.core ......................... SUCCESS [ 3.517 s] [INFO] org.jboss.tools.maven.ui ........................... SUCCESS [ 3.350 s] [INFO] org.jboss.tools.maven.conversion.ui ................ SUCCESS [ 2.961 s] [INFO] org.jboss.tools.maven.feature ...................... SUCCESS [ 1.552 s] [INFO] org.jboss.tools.maven.seam ......................... SUCCESS [ 2.501 s] [INFO] org.jboss.tools.maven.seam.feature ................. SUCCESS [ 1.466 s] [INFO] org.jboss.tools.maven.cdi .......................... SUCCESS [ 2.130 s] [INFO] org.jboss.tools.maven.cdi.feature .................. SUCCESS [ 1.362 s] [INFO] org.jboss.tools.maven.hibernate .................... SUCCESS [ 1.998 s] [INFO] org.jboss.tools.maven.hibernate.feature ............ SUCCESS [ 1.330 s] [INFO] org.jboss.tools.maven.portlet ...................... SUCCESS [ 1.958 s] [INFO] org.jboss.tools.maven.portlet.feature .............. SUCCESS [ 1.382 s] [INFO] maven.tests ........................................ SUCCESS [ 0.016 s] [INFO] org.jboss.tools.maven.common.test .................. SUCCESS [ 0.926 s] [INFO] org.jboss.tools.maven.jbosspackaging ............... SUCCESS [ 2.190 s] [INFO] org.jboss.tools.maven.jdt .......................... SUCCESS [ 2.031 s] [INFO] org.jboss.tools.maven.configurators.tests .......... SUCCESS [ 4.061 s] [INFO] org.jboss.tools.maven.conversion.test .............. SUCCESS [ 0.642 s] [INFO] org.jboss.tools.maven.sourcelookup.core ............ SUCCESS [ 2.390 s] [INFO] org.jboss.tools.maven.sourcelookup.ui .............. SUCCESS [ 3.356 s] [INFO] org.jboss.tools.maven.sourcelookup.test ............ SUCCESS [ 1.885 s] [INFO] org.jboss.tools.maven.test.feature ................. SUCCESS [ 0.359 s] [INFO] org.jboss.tools.maven.jbosspackaging.feature ....... SUCCESS [ 1.512 s] [INFO] org.jboss.tools.maven.sourcelookup.feature ......... SUCCESS [ 1.337 s] [INFO] org.jboss.tools.maven.jdt.feature .................. SUCCESS [ 1.176 s] [INFO] examples.all ....................................... SUCCESS [ 0.026 s] [INFO] examples.features .................................. SUCCESS [ 0.015 s] [INFO] examples.plugins ................................... SUCCESS [ 0.024 s] [INFO] org.jboss.tools.project.examples ................... SUCCESS [ 3.838 s] [INFO] org.jboss.tools.community.project.examples ......... SUCCESS [ 1.593 s] [INFO] org.jboss.tools.community.project.examples.feature . SUCCESS [ 1.242 s] [INFO] org.jboss.tools.project.examples.cheatsheet ........ SUCCESS [ 2.260 s] [INFO] org.jboss.tools.project.examples.feature ........... SUCCESS [ 1.032 s] [INFO] org.jboss.tools.maven.project.examples ............. SUCCESS [ 3.225 s] [INFO] org.jboss.tools.maven.project.examples.feature ..... SUCCESS [ 1.424 s] [INFO] org.jboss.tools.project.examples.seam .............. SUCCESS [ 2.031 s] [INFO] org.jboss.tools.project.examples.seam.feature ...... SUCCESS [ 1.248 s] [INFO] examples.tests ..................................... SUCCESS [ 0.012 s] [INFO] org.jboss.tools.maven.examples.test ................ SUCCESS [ 0.881 s] [INFO] org.jboss.tools.project.examples.test .............. SUCCESS [ 1.850 s] [INFO] org.jboss.tools.project.examples.test.feature ...... SUCCESS [ 0.751 s] [INFO] central.all ........................................ SUCCESS [ 0.180 s] [INFO] central.plugins .................................... SUCCESS [ 0.014 s] [INFO] org.jboss.tools.central ............................ SUCCESS [ 6.996 s] [INFO] org.jboss.tools.community.central .................. SUCCESS [ 1.879 s] [INFO] org.jboss.tools.central.themes ..................... SUCCESS [ 1.824 s] [INFO] central.features ................................... SUCCESS [ 0.014 s] [INFO] org.jboss.tools.central.feature .................... SUCCESS [ 1.118 s] [INFO] org.jboss.tools.community.central.feature .......... SUCCESS [ 1.520 s] [INFO] org.jboss.tools.central.themes.feature ............. SUCCESS [ 1.277 s] [INFO] central.tests ...................................... SUCCESS [ 0.014 s] [INFO] org.jboss.tools.central.test ....................... SUCCESS [ 1.150 s] [INFO] org.jboss.tools.central.test.feature ............... SUCCESS [ 0.244 s] [INFO] org.jboss.tools.central.easymport.feature .......... SUCCESS [ 0.862 s] [INFO] central.maven.examples.site ........................ SUCCESS [ 12.125 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 05:19 min [INFO] Finished at: 2016-09-22T09:35:26-04:00 [INFO] Final Memory: 227M/831M {code} So... I've wiped the job's workspace and re-kicked the PR build... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Baseline check does not seem to work with features > -------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho, > Fix For: 4.4.2.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-910) SwitchYard publish job does not promote to the correct directory

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-910: -------------------------------- Summary: SwitchYard publish job does not promote to the correct directory Key: JBTIS-910 URL: https://issues.jboss.org/browse/JBTIS-910 Project: JBoss Tools Integration Stack Issue Type: Bug Components: switchyard Reporter: Paul Leacu Assignee: Paul Leacu The SY build Jenkins job correctly creates 2.1.0.CR1 but the publish job promotes it to 2.1.0 ref: http://download.jboss.org/jbosstools/mars/integration/updates/integration... should be http://download.jboss.org/jbosstools/mars/integration/updates/integration... https://10.8.63.16/job/SwitchYard-Tools-2.1.x-Update-Site/34/ https://10.8.63.16/job/SwitchYard-Tools-2.1.x-Update-Site-Publish/22/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2016