June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22586: ------------------------------- Fix Version/s: 4.4.0.Final > JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict. > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22586 > URL: https://issues.jboss.org/browse/JBIDE-22586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png > > > For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict. > {code} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json > [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585. > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.{code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22586: ------------------------------- Fix Version/s: (was: 4.4.x) > JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict. > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22586 > URL: https://issues.jboss.org/browse/JBIDE-22586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png > > > For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict. > {code} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json > [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585. > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.{code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Dmitry Bocharov reassigned JBIDE-22593: --------------------------------------- Assignee: Dmitry Bocharov > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22593: ----------------------------------------- [~adietish] yes, of course > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22594: ------------------------------------- Steps to Reproduce: # ASSERT: DONT have anything selected in OpenShift explorer # EXEC: in docker explorer: pick "Deploy to OpenShift" in context menu of your image # ASSERT: connection page shows up # EXEC: pick the connection that you unfolded Result: Connection wizard page shows up. But even after picking and authenticating, password/token is not prefilled in "Deploy an Image" page Expected result: I should always be able to select my OpenShift connection, I should always have the connection page presented. Ideally either the selected connection in explorer or the most recently used connection should be preselected. The password/token should always be prefilled accordingly. was: # ASSERT: DONT have anything selected in OpenShift explorer # EXEC: in docker explorer: pick "Deploy to OpenShift" in context menu of your image # ASSERT: connection page shows up # EXEC: pick the connection that you unfolded Result: Connection wizard page shows up. But even after picking and authenticating, password/token is not prefilled in "Deploy an Image" page > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22594: ------------------------------------- Labels: connection_wizard deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Labels: connection_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22594: ------------------------------------- Attachment: out-2.ogv > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.Alpha1 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22594: ------------------------------------- Attachment: (was: out.ogv) > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.Alpha1 > > Attachments: out-2.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22594: ------------------------------------- Steps to Reproduce: # ASSERT: DONT have anything selected in OpenShift explorer # EXEC: in docker explorer: pick "Deploy to OpenShift" in context menu of your image # ASSERT: connection page shows up # EXEC: pick the connection that you unfolded Result: Connection wizard page shows up. But even after picking and authenticating, password/token is not prefilled in "Deploy an Image" page was: # EXEC: restart eclipse # EXEC: in openshift explorer: unfold connection (confirm ssl cert, provide auth) # ASSERT: DONT have anything selected in OpenShift explorer # EXEC: in docker explorer: pick "Deploy to OpenShift" in context menu of your image # ASSERT: connection page shows up # EXEC: pick the connection that you unfolded Result: Connection wizard page shows up. But even after picking and authenticating, password/token is not prefilled in "Deploy an Image" page > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.Alpha1 > > Attachments: out.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22594) Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22594: ------------------------------------- Attachment: out.ogv > Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22594 > URL: https://issues.jboss.org/browse/JBIDE-22594 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.Alpha1 > > Attachments: out.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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