[JBoss JIRA] (JBIDE-24542) Improve intaller/central tests to be possible to start them automatically
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24542?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-24542.
--------------------------------
Verified, all the tests were started at the weekend, closing.
> Improve intaller/central tests to be possible to start them automatically
> -------------------------------------------------------------------------
>
> Key: JBIDE-24542
> URL: https://issues.jboss.org/browse/JBIDE-24542
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.5.0.AM1
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 4.5.0.AM2
>
>
> There are some tests which have to be started manually because they require path to installer package which varies for each build, so they can't be triggered by timer.
> We have to rework these tests to be able to find path to installer.jar by themselves and then setup jenkins jobs to be started weekly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24657) CDI 1.1 and above should ignore static and private final methods when checking for unproxyable beans
by Dos Moonen (JIRA)
Dos Moonen created JBIDE-24657:
----------------------------------
Summary: CDI 1.1 and above should ignore static and private final methods when checking for unproxyable beans
Key: JBIDE-24657
URL: https://issues.jboss.org/browse/JBIDE-24657
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi
Affects Versions: 4.4.4.Final
Reporter: Dos Moonen
CDI 1.0 prohibits "classes which are declared final or have final methods" being normal scoped beans.
CDI 1.1 relaxes it to "classes which have non-static, final methods with public, protected or default visibility"
JBoss Tools adds a warning for all finals methods, regardless of the project's CDI version.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4455) Bundled installer "File not found" error when filename changes
by Jan Richter (JIRA)
Jan Richter created JBDS-4455:
---------------------------------
Summary: Bundled installer "File not found" error when filename changes
Key: JBDS-4455
URL: https://issues.jboss.org/browse/JBDS-4455
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 11.0.0.AM1
Environment: windows
Reporter: Jan Richter
Priority: Critical
7zip cannot find the file to execute when the archive is extracted. This is due to the file being hardcoded in config-bundle.txt file. The config needs to be updated when the simple archive file name changes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24565) Prepare shell scripts for setup/install cdk 3 on jenkins
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24565?page=com.atlassian.jira.plugi... ]
Ondrej Dockal resolved JBIDE-24565.
-----------------------------------
Resolution: Done
Readme added. Resolving.
> Prepare shell scripts for setup/install cdk 3 on jenkins
> --------------------------------------------------------
>
> Key: JBIDE-24565
> URL: https://issues.jboss.org/browse/JBIDE-24565
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, qa
> Affects Versions: 4.5.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.5.0.AM2
>
>
> To avoid having job full of "execute shell" build steps that configures cdk3 for integration tests It would be cleaner solution to have some set of scripts that:
> * clean up old cdk/minishift instances
> * download and install/configure cdk/minishift
> * stop/delete existing cdk/minishift instance
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24569) Create CDK PR-check job in jenkins
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24569?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24569:
----------------------------------
Comment: was deleted
(was: I decided to divide quite time-consuming CDK server adapter integration tests into smaller test cases due to time that is needed to run all of these test cases in one test class. The one class with all server adapter test cases will be divide into 4 independent classes.
org.jboss.tools.cdk.ui.bot.test.server.adapter.CDK3IntegrationTest will be split into
* CDK3IntegrationStartTest
* CDK3IntegrationRestartTest
* CDK3IntegrationDockerTest
* CDK3IntegrationOpenshiftTest
It will be possible to run cdk pr-check job much faster, if it would contain only one complex test case, instead of 4 test cases that each requires to start cdk 3 server adapter. )
> Create CDK PR-check job in jenkins
> ----------------------------------
>
> Key: JBIDE-24569
> URL: https://issues.jboss.org/browse/JBIDE-24569
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Affects Versions: 4.5.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: cdk, jenkins
> Fix For: 4.5.0.AM2
>
>
> Configure PR-check jenkins job running CDK integration tests in openshift repo. Since we cannot trigger the job on changes in component in repo, job will be triggered to every PR in openshift repo.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months