[JBoss JIRA] (JBIDE-26830) examples.wildfly.itests contains error ".Checkstyle execution failed due to an internal error. Please check the error log for details."
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26830?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26830:
------------------------------------
Description:
Several examples contains error ".Checkstyle execution failed due to an internal error. Please check the error log for details."
h2. *List of WildFly examples with this issue:*
* spring-greeter
* deltaspike-beanbuilder
* kitchensink
* kitchensink-angularjs
* kitchensink-ml
* kitchensink-ear
* tasks-jsf
* tasks-rs
* spring-kitchensink-basic
* spring-kitchensink-springmvctest
* contacts-jquerymobile
was:
Several examples contains error ".Checkstyle execution failed due to an internal error. Please check the error log for details."
> examples.wildfly.itests contains error ".Checkstyle execution failed due to an internal error. Please check the error log for details."
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26830
> URL: https://issues.jboss.org/browse/JBIDE-26830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.12.0.Final
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> Several examples contains error ".Checkstyle execution failed due to an internal error. Please check the error log for details."
> h2. *List of WildFly examples with this issue:*
> * spring-greeter
> * deltaspike-beanbuilder
> * kitchensink
> * kitchensink-angularjs
> * kitchensink-ml
> * kitchensink-ear
> * tasks-jsf
> * tasks-rs
> * spring-kitchensink-basic
> * spring-kitchensink-springmvctest
> * contacts-jquerymobile
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (JBIDE-26760) Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26760:
----------------------------------
Description:
As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
* [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
* [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
* [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
* [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
* [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
* [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
* [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
Some other are still in doing:
*[Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEoMwb13s1TH5v9p6lCyT8/edit]
* [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
* [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
job migration workflow:
* Check on best practices and migrate job according to them, use existing examples, already migrated jobs
* Verify that migration is successful by running it locally using jcasc [2].
* Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
was:
As a part of QE - CI initiative and its out coming best practicies, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]:
[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
> Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26760
> URL: https://issues.jboss.org/browse/JBIDE-26760
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.13.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: integration_tests, jenkins, jenkins_pipeline
> Fix For: 4.13.0.Final
>
>
> As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
> * [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
> * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
> * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
> * [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
> * [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
> * [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
> * [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
> Some other are still in doing:
> *[Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEoMwb13s1TH5v9p6lCyT8/edit]
> * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
> * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
> job migration workflow:
> * Check on best practices and migrate job according to them, use existing examples, already migrated jobs
> * Verify that migration is successful by running it locally using jcasc [2].
> * Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
> [1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
> [2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (JBIDE-26760) Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26760:
----------------------------------
Description:
As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
* [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
* [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
* [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
* [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
* [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
* [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
* [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
Some other are still in doing:
* [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEo...]
* [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
* [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
job migration workflow:
* Check on best practices and migrate job according to them, use existing examples, already migrated jobs
* Verify that migration is successful by running it locally using jcasc [2].
* Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
was:
As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
* [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
* [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
* [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
* [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
* [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
* [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
* [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
Some other are still in doing:
*[Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEoMwb13s1TH5v9p6lCyT8/edit]
* [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
* [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
job migration workflow:
* Check on best practices and migrate job according to them, use existing examples, already migrated jobs
* Verify that migration is successful by running it locally using jcasc [2].
* Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
> Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26760
> URL: https://issues.jboss.org/browse/JBIDE-26760
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.13.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: integration_tests, jenkins, jenkins_pipeline
> Fix For: 4.13.0.Final
>
>
> As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
> * [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
> * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
> * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
> * [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
> * [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
> * [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
> * [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
> Some other are still in doing:
> * [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEo...]
> * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
> * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
> job migration workflow:
> * Check on best practices and migrate job according to them, use existing examples, already migrated jobs
> * Verify that migration is successful by running it locally using jcasc [2].
> * Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
> [1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
> [2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (JBIDE-26760) Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26760:
----------------------------------
Description:
As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
* [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
* [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
* [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
* [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
* [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
* [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
* [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
Some other are still in doing:
* [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEo...]
* [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
* [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
job migration workflow:
* Check on best practices and migrate job according to them, use existing examples, already migrated jobs
* Verify that migration is successful by running it locally using jcasc [2].
* Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
was:
As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
* [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
* [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
* [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
* [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
* [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
* [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
* [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
Some other are still in doing:
* [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEo...]
* [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
* [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
job migration workflow:
* Check on best practices and migrate job according to them, use existing examples, already migrated jobs
* Verify that migration is successful by running it locally using jcasc [2].
* Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
[1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
[2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
> Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-26760
> URL: https://issues.jboss.org/browse/JBIDE-26760
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.13.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: integration_tests, jenkins, jenkins_pipeline
> Fix For: 4.13.0.Final
>
>
> As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices that can be found here:
> * [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...]
> * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts]
> * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...]
> * [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types]
> * [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers]
> * [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready]
> * [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM]
> Some other are still in doing:
> * [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEo...]
> * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters]
> * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...]
> job migration workflow:
> * Check on best practices and migrate job according to them, use existing examples, already migrated jobs
> * Verify that migration is successful by running it locally using jcasc [2].
> * Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira
> [1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config
> [2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years
[JBoss JIRA] (JBIDE-26829) Content.xml not found trying to install from Eclipse marketplace
by stephane bouchet (Jira)
[ https://issues.jboss.org/browse/JBIDE-26829?page=com.atlassian.jira.plugi... ]
stephane bouchet commented on JBIDE-26829:
------------------------------------------
Hi,
Tested today from scratch to install JBossTools 4.12.0.Final into an eclipse 2019-06 IDE for Enterprise Java Developers with no errors.
I installed JBossTools inside Red Hat org.
Can you provide us the full error log ? seems the messgaes ("Unable to read repository at ..." ) may be due to network connectivity. Did you try again the installation ?
> Content.xml not found trying to install from Eclipse marketplace
> ----------------------------------------------------------------
>
> Key: JBIDE-26829
> URL: https://issues.jboss.org/browse/JBIDE-26829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Environment: Eclipse Market place
> Reporter: Ariel Barboza
> Priority: Major
> Labels: new_and_noteworthy
> Attachments: ErrorLog.PNG, ErrorLog1.PNG
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When trying to install JBoss tools from eclipse marketplace, it finds the applications needed for installation, when installing, it fails with the following error:
> https://download.jboss.org/jbosstools/updates/webtools/oxygen/content.xml does not exist
> Attached are pictures of the errors
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years