September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23153) Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23153?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23153: ------------------------------------- Labels: integration-test (was: ) > Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23153 > URL: https://issues.jboss.org/browse/JBIDE-23153 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test, openshift_v3 > Fix For: 4.4.2.AM1 > > > OpenShiftCommandLineToolsRequirement will redownload the oc binary on each invocation. This is time consuming, it should check if it exists and not re-download it in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23153) Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23153?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23153: ---------------------------------------- Assignee: Andre Dietisheim > Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23153 > URL: https://issues.jboss.org/browse/JBIDE-23153 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test, openshift_v3 > Fix For: 4.4.2.AM1 > > > OpenShiftCommandLineToolsRequirement will redownload the oc binary on each invocation. This is time consuming, it should check if it exists and not re-download it in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23153) Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23153?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23153: ------------------------------------- Labels: integration-test openshift_v3 (was: integration-test) > Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23153 > URL: https://issues.jboss.org/browse/JBIDE-23153 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test, openshift_v3 > Fix For: 4.4.2.AM1 > > > OpenShiftCommandLineToolsRequirement will redownload the oc binary on each invocation. This is time consuming, it should check if it exists and not re-download it in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23153) Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23153: ---------------------------------------- Summary: Integration tests: OpenShiftCommandLineToolsRequirement should only download oc binary once Key: JBIDE-23153 URL: https://issues.jboss.org/browse/JBIDE-23153 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.1.Final Reporter: Andre Dietisheim OpenShiftCommandLineToolsRequirement will redownload the oc binary on each invocation. This is time consuming, it should check if it exists and not re-download it in this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22968. --------------------------------- I guess time will tell if this works as intended in all cases. Closing for now. > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23098) Create New and Noteworthy for 4.4.1.Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23098?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23098. --------------------------------- > Create New and Noteworthy for 4.4.1.Final > ----------------------------------------- > > Key: JBIDE-23098 > URL: https://issues.jboss.org/browse/JBIDE-23098 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.4.1.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23092: --------------------------------------- [~nickboldt], I wanted to verify that the list is now correct, but I can't find where it is. Can you advice? I checked https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... and also the ci repo if it's pulled from there: https://github.com/jbosstools/jbosstools-build-ci > add more projects to the list of projects to branch and/or update root pom > -------------------------------------------------------------------------- > > Key: JBIDE-23092 > URL: https://issues.jboss.org/browse/JBIDE-23092 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > MIssing projects we could have included in the automated branching: > * jbosstools-integration-tests [root pom in ./] > Need to also branch these, but there's no root pom to adjust, so the script should just fail silently: > * jbosstools-devdoc [no root pom] > * jbosstools-download.jboss.org [no root pom] > * jbosstools-maven-plugins no root pom] > * jbosstools-versionwatch [no root pom] > * jbdevstudio-ci [no root pom] > * jbdevstudio-qa [no root pom] > * jbdevstudio-website [no root pom] > * jbdevstudio-artwork [no root pom] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23121) server New and Noteworthy for 4.4.1.Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23121?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23121. --------------------------------- There is currently no staging website up to verify this, but the commit looks ok and it's just one small note about WildFly 10.1 anyway. Closing. > server New and Noteworthy for 4.4.1.Final > ----------------------------------------- > > Key: JBIDE-23121 > URL: https://issues.jboss.org/browse/JBIDE-23121 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23152?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23152: --------------------------------------- For CDK 2.2 it is happening because there are added following environment variables: {code}"HTTP_PROXY=", "HTTPS_PROXY=", "NO_PROXY=",{code} so we have to allow displaying environment variables with empty value. > NPE when deploying image with ENV with no value > ----------------------------------------------- > > Key: JBIDE-23152 > URL: https://issues.jboss.org/browse/JBIDE-23152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: Dockerfile > > > EXEC: first deploy jboss-eap64-openshift builder image > ASSERT: wait until deployment is finished > EXEC: delete the deployment > EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd) > ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=) > As this first scenario seems to be valid only if you're working with CDK2.2 and no proxy set, here is a scenario valid for all versions of CDK: > ASSERT: have a Docker file with an empty ENV value. You can use https://github.com/redhat-helloworld-msa/aloha and edit the Docker file and add the following statement: > {quote}ENV NOVALUE ""{quote} > EXEC: build the Docker image on the CDK Docker connection. If you use aloha (https://github.com/redhat-helloworld-msa/aloha), then you must beforehand run the "mvn package" command to get binary artifacts being produced. Select the Dockerfile, click *_Run As -> Docker Image Build_*, select the CDK Docker connection and give *_msa/aloha:1_* as image name > ASSERT: your Docker image has been generated > EXEC: from the Openshift explorer, select the *_Deploy Docker Image_*, then select the CDK Docker Connection, then click on *_Browse_* and select the *_msa/aloha:1_* image, then click on the Next button > ASSERT: you should get an error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23152?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23152: ------------------------------- Attachment: Dockerfile > NPE when deploying image with ENV with no value > ----------------------------------------------- > > Key: JBIDE-23152 > URL: https://issues.jboss.org/browse/JBIDE-23152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: Dockerfile > > > EXEC: first deploy jboss-eap64-openshift builder image > ASSERT: wait until deployment is finished > EXEC: delete the deployment > EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd) > ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=) > As this first scenario seems to be valid only if you're working with CDK2.2 and no proxy set, here is a scenario valid for all versions of CDK: > ASSERT: have a Docker file with an empty ENV value. You can use https://github.com/redhat-helloworld-msa/aloha and edit the Docker file and add the following statement: > {quote}ENV NOVALUE ""{quote} > EXEC: build the Docker image on the CDK Docker connection. If you use aloha (https://github.com/redhat-helloworld-msa/aloha), then you must beforehand run the "mvn package" command to get binary artifacts being produced. Select the Dockerfile, click *_Run As -> Docker Image Build_*, select the CDK Docker connection and give *_msa/aloha:1_* as image name > ASSERT: your Docker image has been generated > EXEC: from the Openshift explorer, select the *_Deploy Docker Image_*, then select the CDK Docker Connection, then click on *_Browse_* and select the *_msa/aloha:1_* image, then click on the Next button > ASSERT: you should get an error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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