December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23302: ------------------------------- Attachment: stage-http.png stage.png > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Fix For: 4.4.3.AM1 > > Attachments: image.png, stage-http.png, stage.png > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23302: ------------------------------------ Things are better but still having font resolution issues: http: !stage-http.png|thumbnail! vs. https: !stage.png|thumbnail! > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Fix For: 4.4.3.AM1 > > Attachments: image.png, stage-http.png, stage.png > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22774) Create integration tests PR check job for aerogar-hybrid

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22774?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-22774. -------------------------------- Resolution: Done pr check job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Create integration tests PR check job for aerogar-hybrid > -------------------------------------------------------- > > Key: JBIDE-22774 > URL: https://issues.jboss.org/browse/JBIDE-22774 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, build, qa > Reporter: Rastislav Wagner > Assignee: Pavol Srna > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23640) Integration tests: Once PushImageTest starts to fail, it will always fail if no image cleanup happens in the test suite

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23640?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23640: ------------------------------------------ [~jkopriva] thx! I fixed the missing pieces and pushed. > Integration tests: Once PushImageTest starts to fail, it will always fail if no image cleanup happens in the test suite > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23640 > URL: https://issues.jboss.org/browse/JBIDE-23640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > > PushImageTest is add a tag to an image. When looking at the images, it is comparing all of the decoration with the tag. This works fine as long as the image only has 1 tag, once it gets more, the lookup for the image starts to fail. The image is deleted later in the test, so if the image with the tag is not found, the delete wont happen and subsequent lookups will fail. This most likely wont happen if you run the complete suite because the suite is cleaning up, but it will happen if you run a single test. > Another problem is that PushImageTest wont wait until the freshly tagged image was successfully pushed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1003?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1003: ------------------------------------------ The reason for this task is that we would like to specify mirrors for such site but it is not possible without the id. For example {code:title=settings.xml} <mirror> <id>eclipse-neon-mirror</id> <name>eclipse-neon-mirror</name> <layout>p2</layout> <url>http://localhost:8081/nexus/content/repositories/jbt-neon/</url> <mirrorOf>jbt-neon</mirrorOf> <mirrorOfLayouts>p2</mirrorOfLayouts> </mirror> {code} > Add id to all repositories defined in target platform > ----------------------------------------------------- > > Key: JBTIS-1003 > URL: https://issues.jboss.org/browse/JBTIS-1003 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > > Currently, the definition looks as follows > {code:title=src/targets/integration-stack-base.target} > <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> > ... > <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> > </location> > {code} > Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. > {code} > http://download.jboss.org/jbosstools/updates/requirements/neon/ > {code} > I think that the composite site should work without any problem since all needed versions are specified in each unit. > Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1003: ---------------------------------------- Summary: Add id to all repositories defined in target platform Key: JBTIS-1003 URL: https://issues.jboss.org/browse/JBTIS-1003 Project: JBoss Tools Integration Stack Issue Type: Task Components: target-platform Affects Versions: 4.4.0.CR1-TP Reporter: Andrej Podhradsky Currently, the definition looks as follows {code:title=src/targets/integration-stack-base.target} <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> ... <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> </location> {code} Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. {code} http://download.jboss.org/jbosstools/updates/requirements/neon/ {code} I think that the composite site should work without any problem since all needed versions are specified in each unit. Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1003?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1003: ------------------------------------- Description: Currently, the definition looks as follows {code:title=src/targets/integration-stack-base.target} <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> ... <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> </location> {code} Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. {code} http://download.jboss.org/jbosstools/updates/requirements/neon/ {code} I think that the composite site should work without any problem since all needed versions are specified in each unit. Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. was: Currently, the definition looks as follows {code:title=src/targets/integration-stack-base.target} <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> ... <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> </location> {code} Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. {code} http://download.jboss.org/jbosstools/updates/requirements/neon/ {code} I think that the composite site should work without any problem since all needed versions are specified in each unit. Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. > Add id to all repositories defined in target platform > ----------------------------------------------------- > > Key: JBTIS-1003 > URL: https://issues.jboss.org/browse/JBTIS-1003 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > > Currently, the definition looks as follows > {code:title=src/targets/integration-stack-base.target} > <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> > ... > <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> > </location> > {code} > Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. > {code} > http://download.jboss.org/jbosstools/updates/requirements/neon/ > {code} > I think that the composite site should work without any problem since all needed versions are specified in each unit. > Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23154) tests: should have sonar checking our pull requests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23154?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23154: ------------------------------------------ wohoo, great stuff! Happy we now have this in place. Thanks! > tests: should have sonar checking our pull requests > --------------------------------------------------- > > Key: JBIDE-23154 > URL: https://issues.jboss.org/browse/JBIDE-23154 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: pull_request, quality, test > Fix For: 4.4.3.AM1 > > > Sonar being run in the background tends to get forgotten. I'd therefore love to have sonar testing our pull requests. > Docs for the sonar github plugin are here: http://docs.sonarqube.org/display/PLUG/GitHub+Plugin -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23154) tests: should have sonar checking our pull requests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23154?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23154: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > tests: should have sonar checking our pull requests > --------------------------------------------------- > > Key: JBIDE-23154 > URL: https://issues.jboss.org/browse/JBIDE-23154 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: pull_request, quality, test > Fix For: 4.4.3.AM1 > > > Sonar being run in the background tends to get forgotten. I'd therefore love to have sonar testing our pull requests. > Docs for the sonar github plugin are here: http://docs.sonarqube.org/display/PLUG/GitHub+Plugin -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23154) tests: should have sonar checking our pull requests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23154?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23154: ------------------------------------- Labels: pull_request quality test (was: ) > tests: should have sonar checking our pull requests > --------------------------------------------------- > > Key: JBIDE-23154 > URL: https://issues.jboss.org/browse/JBIDE-23154 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: pull_request, quality, test > Fix For: 4.4.3.AM1 > > > Sonar being run in the background tends to get forgotten. I'd therefore love to have sonar testing our pull requests. > Docs for the sonar github plugin are here: http://docs.sonarqube.org/display/PLUG/GitHub+Plugin -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016