March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13286) jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13286?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13286. ------------------------------ Fix Version/s: 4.5.3.AM3 (was: LATER) Resolution: Partially Completed We moved to CCI a while ago and now have pull request builds running. Don't have those jobs posting updates to JIRA, but the PRs DO have links to the builds. So... I think this is good enough. > jobs should generate comment in JIRA recording job URL, BUILD#, and more detailed commit info (committer + comments) > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13286 > URL: https://issues.jboss.org/browse/JBIDE-13286 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.5.3.AM3 > > > Is it possible to pull the git hash value used for a given build, look into github for the matching JIRA #, and drop a comment into the JIRA to the tune of: > "Spinning in <buildURL> >= BUILD_NUMBER" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13407. -------------------------------- Fix Version/s: 4.5.3.AM3 (was: LATER) Resolution: Rejected I suspect we'll never the resources to get this set up for CI builds, so I'm marking this Rejected. > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.5.3.AM3 > > Attachments: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25509?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-25509: ---------------------------------------- Assignee: Dmitrii Bocharov > Properties: one can not select multiple resources > ------------------------------------------------- > > Key: JBIDE-25509 > URL: https://issues.jboss.org/browse/JBIDE-25509 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: properties > Fix For: 4.5.x > > > steps: > # ASSERT: have an OpenShift app running > # EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods" > # ASSERT: there are multiple pods listed > # EXEC: try to select several ones (ex. in order to delete them) > Result: > You can only select a single entry, you cannot select several ones and ex. delete them at once. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25509?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-25509: ------------------------------------- Sprint: devex #146 March 2018 > Properties: one can not select multiple resources > ------------------------------------------------- > > Key: JBIDE-25509 > URL: https://issues.jboss.org/browse/JBIDE-25509 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: properties > Fix For: 4.5.x > > > steps: > # ASSERT: have an OpenShift app running > # EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods" > # ASSERT: there are multiple pods listed > # EXEC: try to select several ones (ex. in order to delete them) > Result: > You can only select a single entry, you cannot select several ones and ex. delete them at once. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23503) Target platform PR check fails to use p2diff correctly, so build fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23503?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23503. ------------------------------ Fix Version/s: 4.5.3.AM3 (was: LATER) Resolution: Won't Do Won't do. > Target platform PR check fails to use p2diff correctly, so build fails > ---------------------------------------------------------------------- > > Key: JBIDE-23503 > URL: https://issues.jboss.org/browse/JBIDE-23503 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM3 > > Attachments: dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com.log.txt > > > Recently, it was noticed that the TP PR checks are failing. And have been for a long time. > So, I'm opening this to track the work needed to make them work again. > There are two different TP PR jobs: > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... (which seems to have never worked) > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... (which has been blue in the past) > Recent failure: > {code} > [INFO] Command line: > [/qa/tools/opt/x86_64/jdk1.8.0_101/jre/bin/java, -jar, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.100.v20150511-1540/org.eclipse.equinox.launcher-1.3.100.v20150511-1540.jar, -install, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work, -configuration, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration, -application, org.eclipse.equinox.p2.example.p2diff.application, -outputFile=/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple-ignoreVersions.p2diff, -mode=ignoreVersions, file:/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple.target.repo, http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...] > An error has occurred. See the log file > /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration/1479683354475.log.{code} > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25581) Missing labels when creating an app from a builder image

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25581?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-25581: ------------------------------------- Sprint: devex #146 March 2018 > Missing labels when creating an app from a builder image > -------------------------------------------------------- > > Key: JBIDE-25581 > URL: https://issues.jboss.org/browse/JBIDE-25581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > > When an application is created from a builder image, some created resources (BuildConfig, Service, Route) are created without labels. The web console add app=name for all created resources -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25581) Missing labels when creating an app from a builder image

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25581?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-25581: ---------------------------------------- Assignee: Dmitrii Bocharov > Missing labels when creating an app from a builder image > -------------------------------------------------------- > > Key: JBIDE-25581 > URL: https://issues.jboss.org/browse/JBIDE-25581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > > When an application is created from a builder image, some created resources (BuildConfig, Service, Route) are created without labels. The web console add app=name for all created resources -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24182) wrap staging/release process with pipeline job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24182: ------------------------------- Fix Version/s: 4.5.3.AM3 (was: 4.5.x) > wrap staging/release process with pipeline job > ---------------------------------------------- > > Key: JBIDE-24182 > URL: https://issues.jboss.org/browse/JBIDE-24182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM3 > > > In JBIDE-22819 I created a buildflow job to orchestrate the steps involved in staging or release of jbt/ds. > However, on CCI we can now write a pipeline job [1] in groovy, which can trigger downstream builds [2] and wait for approval/input [3] before continuing. This might be an ever better visualization & control for these stages/releases. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/vscode-j... -> https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile > [2] https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job > [3] https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile#L68 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24182) wrap staging/release process with pipeline job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24182: ------------------------------- Sprint: devex #132 May 2017, devex #146 March 2018 (was: devex #132 May 2017) > wrap staging/release process with pipeline job > ---------------------------------------------- > > Key: JBIDE-24182 > URL: https://issues.jboss.org/browse/JBIDE-24182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > In JBIDE-22819 I created a buildflow job to orchestrate the steps involved in staging or release of jbt/ds. > However, on CCI we can now write a pipeline job [1] in groovy, which can trigger downstream builds [2] and wait for approval/input [3] before continuing. This might be an ever better visualization & control for these stages/releases. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/vscode-j... -> https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile > [2] https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job > [3] https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile#L68 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25276: ------------------------------- Sprint: devex #139 October 2017, devex #143 January 2018, devex #146 March 2018 (was: devex #139 October 2017, devex #143 January 2018) > intermittent test failures in webservices > ----------------------------------------- > > Key: JBIDE-25276 > URL: https://issues.jboss.org/browse/JBIDE-25276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.x > > Attachments: ws-intermittent-test-failures.png, ws-intermittent.png > > > Various tests are failing intermittently. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2 > Can these be fixed or if not, disabled, so that we can consistently get green builds? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 March 2018