June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22672) PR builds failing because undeployed dependency

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22672: -------------------------------- Summary: PR builds failing because undeployed dependency (was: PR bulds failing because undeployed dependency) > PR builds failing because undeployed dependency > ----------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR bulds failing because undeployed dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22672: ---------------------------------------- Ok, parent pom 4.4.0.Final-SNAPSHOT misses update to TP release. [~nickboldt] Was this intentional or just something forgotten? Any reason why not fixing it right now? > PR bulds failing because undeployed dependency > ---------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22603: ---------------------------------- Assignee: Jeff MAURY > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22592) Application wizard: Failed even though provided required value to parameters

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22592?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22592: ------------------------------- Fix Version/s: 4.4.1.M2 (was: 4.4.1.M1) > Application wizard: Failed even though provided required value to parameters > ---------------------------------------------------------------------------- > > Key: JBIDE-22592 > URL: https://issues.jboss.org/browse/JBIDE-22592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBoss OpenShift 3 Tools 3.3.0.Final-v20160610-1836-B1369 > JBoss OpenShift 3 Tools Developer Resources 3.3.0.Final-v20160610-1836-B1369 > Eclipse: Neon Milestone 7 (4.6.0M7) > Reporter: Xia Zhao > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.M2 > > Attachments: application-template-stibuild.json, fails-even-though-required-value-provided.png, Screenshot from 2016-06-12 01-59-02.png > > > Create app from the local template in attachment,give required value to parameter "xiazhao_checkfail" inside new-app wizard, get error message after clicking on the "Next>" button: > Template "ruby-helloworld-sample" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified > Could not create resource ruby-helloworld-sample in namespace 'xiazhao-1': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Template \"ruby-helloworld-sample\" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","reason":"Invalid","details":{"name":"ruby-helloworld-sample","kind":"Template","causes":[{"reason":"FieldValueRequired","message":"Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","field":"template.parameters[5]"}]},"code":422} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22653: ------------------------------- Fix Version/s: 4.4.1.M2 Story Points: 2 > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.4.1.M2 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR bulds failing because undeployed dependency

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22672: ------------------------------------ It's using 4.4.0.Final-SNAPSHOT as the parent POM and build reproducibility should make this build not failing > PR bulds failing because undeployed dependency > ---------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR bulds failing because undeployed dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22672: ---------------------------------------- Which version of the parent pom are you using? Current 4.4.1.Alpha1-SNAPSHOT on master and Nexus https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml / https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... seems to reference the right version of parent pom. So if you're using the right parent, you should get the right TP. > PR bulds failing because undeployed dependency > ---------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR bulds failing because undeployed dependency

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22672: ------------------------------------ Just got the same error (which is what I expected) because my work tree is refering to jbosstools-unified:4.60.0.Final-SNAPSHOT which is not deployed, which this issue tries to fix > PR bulds failing because undeployed dependency > ---------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR bulds failing because undeployed dependency

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22672: ------------------------------------ [~mickael_istria] managed to retrigger (add a testPR comment). > PR bulds failing because undeployed dependency > ---------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR bulds failing because undeployed dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22672: ---------------------------------------- The TP version is not overriden in PR jobs. So it's just using what's defined in referenced parent pom. I also didn't find a way to easily retrigger a PR build so far. > PR bulds failing because undeployed dependency > ---------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016