November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25285) Declare "JAVA19" ENV vars in CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25285?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25285: ---------------------------------- Assignee: Pavol Srna > Declare "JAVA19" ENV vars in CCI > -------------------------------- > > Key: JBIDE-25285 > URL: https://issues.jboss.org/browse/JBIDE-25285 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVA19 env vars need to be declared: > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25285) Declare "JAVA19" ENV vars in CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25285?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25285: ------------------------------------ Did this get done in another JIRA already? > Declare "JAVA19" ENV vars in CCI > -------------------------------- > > Key: JBIDE-25285 > URL: https://issues.jboss.org/browse/JBIDE-25285 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVA19 env vars need to be declared: > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25285) Declare "JAVA19" ENV vars in CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25285?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25285: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > Declare "JAVA19" ENV vars in CCI > -------------------------------- > > Key: JBIDE-25285 > URL: https://issues.jboss.org/browse/JBIDE-25285 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVA19 env vars need to be declared: > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4616) signed rpm fetch job should verify the rpms are signed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4616?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4616: ---------------------------------- [~psrna] Once we're done with AM1 build, stage, and release, can we push this change (next week some time) ? > signed rpm fetch job should verify the rpms are signed > ------------------------------------------------------ > > Key: JBDS-4616 > URL: https://issues.jboss.org/browse/JBDS-4616 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 11.1.0.GA > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 11.2.0.AM2 > > > Currently, the job that fetches the signed devstudio rpms can't automatically verify the rpms are signed because the key is not installed on the slaves. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So, we need to fix that so that the job can verify signing has occurred and speed up the release process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25300) update jobs to use maven 3.5

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25300?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25300: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > update jobs to use maven 3.5 > ---------------------------- > > Key: JBIDE-25300 > URL: https://issues.jboss.org/browse/JBIDE-25300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM2 > > > Jobs currently use mvn 3.3.9, unless pointed as "mvn3-latest", which was recently updated to be a symlink to 3.5.0 instead of 3.3.9. > We should get 3.5.2 [1] installed and use that in the jobs as it supports JDK 9. > [1] https://maven.apache.org/docs/3.5.2/release-notes.html > cc: [~psrna] [~mmalina] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > externalize common properties to parameterize jobs > -------------------------------------------------- > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM2 > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4588) update installer to be able to use JDK 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4588?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4588: ----------------------------- Fix Version/s: 11.2.0.AM3 (was: 11.2.0.AM1) > update installer to be able to use JDK 9 > ---------------------------------------- > > Key: JBDS-4588 > URL: https://issues.jboss.org/browse/JBDS-4588 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.2.0.AM3 > > > Investigate what's needed to support running the installer w/ JDK 9. > May also need to add this to the devstudio.ini, after *-vmargs*: > {code}-Dosgi.requiredJavaVersion=1.8 > --add-modules=ALL-SYSTEM{code} -- https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_f... > cc: [~mmalina] [~jeffmaury] [~dgolovin] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25139) migrate PR build jobs on fusesource jenkins to dev-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25139?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25139: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > migrate PR build jobs on fusesource jenkins to dev-platform > ----------------------------------------------------------- > > Key: JBIDE-25139 > URL: https://issues.jboss.org/browse/JBIDE-25139 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fusetools > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM2 > > Attachments: all-three-PR-builders.png > > > I believe the current PR build job is this one: > https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > [~lhein] [~aurelien.pupier] is that correct? > Yes, it is correct -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19065) Versionwatch should check if found IUs fall in/out ranges defined in ignore.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19065?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19065: ------------------------------- Fix Version/s: 4.5.2.AM3 (was: 4.5.2.AM1) > Versionwatch should check if found IUs fall in/out ranges defined in ignore.properties > -------------------------------------------------------------------------------------- > > Key: JBIDE-19065 > URL: https://issues.jboss.org/browse/JBIDE-19065 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.2.Final > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > Improve report duplicate versions -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4618) remove dupe/older versions of glassfish and jersey so devstudio and docker-tools use the same versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4618?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4618: ----------------------------- Fix Version/s: 11.2.0.AM2 (was: 11.2.0.AM1) > remove dupe/older versions of glassfish and jersey so devstudio and docker-tools use the same versions > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-4618 > URL: https://issues.jboss.org/browse/JBDS-4618 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: rpm, target-platform > Affects Versions: 11.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.2.0.AM2 > > > Some bundles that appear in both docker tools and devstudio: > {code} > org.glassfish.hk2.osgi-resource-locator_2.4.0.jar -> ../../../../../java/glassfish-hk2/osgi-resource-locator.jar linuxtools-docker > org.glassfish.hk2.osgi-resource-locator_2.5.0.v20161103-1916 devstudio > org.glassfish.jersey.core.jersey-common_2.22.1.v20161103-1916 devstudio > org.glassfish.jersey.core.jersey-common_2.23.2.jar -> ../../../../../java/jersey/jersey-common.jar linuxtools-docker > org.glassfish.jersey.core.jersey-server_2.22.1.v20161103-1916 devstudio > org.glassfish.jersey.core.jersey-server_2.23.2.jar -> ../../../../../java/jersey/jersey-server.jar linuxtools-docker > {code} > Symlinks are to paths here (installed via rpm): > * /opt/rh/rh-eclipse47/root/usr/share/java/glassfish-hk2 --> rh-eclipse47-glassfish-hk2-osgi-resource-locator.noarch > * /opt/rh/rh-eclipse47/root/usr/share/java/jersey --> rh-eclipse47-jersey.noarch > Complete list via this script: > {code} > sudo su > cd /opt/rh/rh-eclipse47/root/usr/share/eclipse/ > rm -f /tmp/list.txt > for d in $(find . -mindepth 3 -name \*glassfish\* | egrep -v "META-INF|org/glas"); do ls -lad $d | sed -e "s#.\+droplets/$[^/]\+$/eclipse/plugins/$.\+$#\2 \1#" >> /tmp/list.txt; done > cat /tmp/list.txt | sort | egrep "jersey|glassfish" > rm -f /tmp/list.txt > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017