[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20513:
---------------------------------------------
moving of 4.3 since not absolute blocker.
> tricky to login to openshift when token expires
> -----------------------------------------------
>
> Key: JBIDE-20513
> URL: https://issues.jboss.org/browse/JBIDE-20513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> I logged in with token.
> 24hrs later I start eclipse and expand the connection in explorer
> expecting to just login.
> Here is what happens instead:
> a) info message (not error) is logged to error log hiding the explorer view
> b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.).
> cancel the dialog since I'm trying to figure out what happened.
> c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again.
> Turns out Refresh does trigger login again.
> meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case:
> a) do a user really need to re-login every 24 hours ?
> b) the error handling/dialogs shown are not very informative
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21386) Create and use Neon M5 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21386?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21386:
------------------------------------
As there were no objections or feedback after 2 days, I've merged the changes to Central. See also JBIDE-21853 for the change to SpringIDE.
> Create and use Neon M5 target platform
> --------------------------------------
>
> Key: JBIDE-21386
> URL: https://issues.jboss.org/browse/JBIDE-21386
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbds-tp-p2diff-460-summary.txt, jbds-tp-p2diff-460.txt, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.txt, p2diff.JBIDE-21386.summary.txt, p2diff.JBIDE-21386.txt
>
>
> Prepare TP to use Neon M5 bits. Cloned from JBIDE-20976 so I can start a fresh issue.
> https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S...
> Story points: 21 (fibonacci)
> * jbt tp,
> * jbds tp,
> * central tp;
> * jbt-build-sites,
> * jbds site build;
> * update install/matrix jobs to use new Eclipse JEE/platform binary;
> * mailing list announcements
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21853) bump version of SpringIDE 3.7.3 from CI to RELEASE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21853?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21853:
-------------------------------
Description:
We're still using a pre-release version of Spring IDE 3.7.3 in Central in master. Time to move up to the release version.
was:
We're still using a pre-release version of Spring IDE 3.7.3 in Central. Since we've now moved up to the 3.7.3.RELEASE version in master, I'm going to make the same change in 4.3.x.
> bump version of SpringIDE 3.7.3 from CI to RELEASE
> --------------------------------------------------
>
> Key: JBIDE-21853
> URL: https://issues.jboss.org/browse/JBIDE-21853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> We're still using a pre-release version of Spring IDE 3.7.3 in Central in master. Time to move up to the release version.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21849:
---------------------------------------------
what is RHAP Puddle ?
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3
>
> -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
> -Issue did not repro if switch to OSE
> -Repro on Linux/Windows/Mac OS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ]
Fred Bricon resolved JBDS-3552.
-------------------------------
Resolution: Partially Completed
> Developer - be able to incrementally deploy changes to docker containers
> -------------------------------------------------------------------------
>
> Key: JBDS-3552
> URL: https://issues.jboss.org/browse/JBDS-3552
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker, openshift
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 9.1.0.CR1
>
>
> User Story:
> As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly.
> Acceptance Criteria:
> * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment.
> * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh.
> * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source)
> * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years