[JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH - proxy requirements definition
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26452:
----------------------------------
Sprint: devex #157 November 2019, devex #159 December 2018 (was: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019)
> Explore existing proxy server set up solutions outside RH - proxy requirements definition
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-26452
> URL: https://issues.jboss.org/browse/JBIDE-26452
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Environment: Linux
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: quality
> Fix For: 4.11.0.AM1
>
>
> Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge.
> Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code?
> Requirements for proxy solution:
> * Supports HTTP and HTTPS protocols
> * Clear and configurable logging and other tools
> * runs on linux
> * Open Source solution
> * License usable "in house" (can be use for profit = in enterprise environment)
> * Project is alive/maintained - or we would must maintain our own fork?
> * Community
> * Code on github - preferably
> * uses issue tracking system
> Requirements for putting proxy into action:
> * easy to deploy solution
> * does not require user knowledge of proxy configuration - minimalist config
> * can be updated at place
> * RH certificate can be used
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBIDE-26455) Implement monitoring Tool for watching changes in jbt repositories and dependency changes in TP
by Pavol Srna (Jira)
[ https://issues.jboss.org/browse/JBIDE-26455?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-26455:
-------------------------------
Sprint: devex #157 November 2019, devex #161 January 2019 (was: devex #157 November 2019)
> Implement monitoring Tool for watching changes in jbt repositories and dependency changes in TP
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26455
> URL: https://issues.jboss.org/browse/JBIDE-26455
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.10.0.AM1
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Priority: Major
> Labels: quality
> Fix For: 4.11.x
>
>
> The tool is to support new test strategy for devstudio:
> {quote}
> In the current approach we do a full test cycle on all components with every milestone. This includes also manual steps, etc. and it is resource and time demanding. However some of the components have zero activity, or only a few commits per train. The idea is to limit the testing on low activity components and focus more on the new stuff - like adapters, where it has more value for the current product offering. We do not plan to stop the testing completely. We will monitor github repositories for significant changes. In case we find out there is a significant change on the repository, we will include the component in the milestone testing.{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBIDE-26520) Create automated RHDS Launcher Application tests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26520?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka commented on JBIDE-26520:
-----------------------------------------
One of the 2 Pull Requests (jbosstools-central) successfully merged.
> Create automated RHDS Launcher Application tests
> ------------------------------------------------
>
> Key: JBIDE-26520
> URL: https://issues.jboss.org/browse/JBIDE-26520
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Affects Versions: 4.10.0.AM1
> Environment: Same as central.itests on Jenkins (will be part of central.itests)
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> Create automated RHDS Launcher Application tests. Tests will be part of the central.itests and they will cover 4 test cases described in Polarion:
> -> JBDS-9886
> -> JBDS-9887
> -> JBDS-9888
> -> JBDS-9889
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBIDE-26455) Implement monitoring Tool for watching changes in jbt repositories and dependency changes in TP
by Pavol Srna (Jira)
[ https://issues.jboss.org/browse/JBIDE-26455?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-26455:
------------------------------------
Update on the progress.
* architecture of the tool has been evaluated:
* the tool will be written in JavaScript
* for github queries GraphQL will be used (githuv v4 api)
* small helper tool to work with sprint data has been implemented: https://github.com/psrna/sprint
* currently is being worked on POC graphql queries
> Implement monitoring Tool for watching changes in jbt repositories and dependency changes in TP
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26455
> URL: https://issues.jboss.org/browse/JBIDE-26455
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.10.0.AM1
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Priority: Major
> Labels: quality
> Fix For: 4.11.x
>
>
> The tool is to support new test strategy for devstudio:
> {quote}
> In the current approach we do a full test cycle on all components with every milestone. This includes also manual steps, etc. and it is resource and time demanding. However some of the components have zero activity, or only a few commits per train. The idea is to limit the testing on low activity components and focus more on the new stuff - like adapters, where it has more value for the current product offering. We do not plan to stop the testing completely. We will monitor github repositories for significant changes. In case we find out there is a significant change on the repository, we will include the component in the milestone testing.{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months