October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25202) Remove the Eclipse related files from git

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25202?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-25202: ------------------------------ Fix Version/s: 4.5.2.AM1 (was: 4.5.1.Final) > Remove the Eclipse related files from git > ----------------------------------------- > > Key: JBIDE-25202 > URL: https://issues.jboss.org/browse/JBIDE-25202 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.5.1.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.2.AM1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 reassigned JBIDE-25301: ---------------------------------- Assignee: Nick Boldt > 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.AM1 > > > 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, 5 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: ------------------------------- Story Points: 3 Sprint: devex #140 November 2017 > 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.AM1 > > > 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, 5 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.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.AM1 > > > 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, 5 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25301: ---------------------------------- Summary: 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 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25137) externalize the Eclipse platform and JEE bundles used for running jbt builds/tests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25137?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25137. -------------------------------- Resolution: Done 7 jobs updated. Resolving. > externalize the Eclipse platform and JEE bundles used for running jbt builds/tests > ---------------------------------------------------------------------------------- > > Key: JBIDE-25137 > URL: https://issues.jboss.org/browse/JBIDE-25137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests, integration-tests > Affects Versions: 4.5.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.Final > > > Currently, we have a number of Eclipse URLs in jobs and they're inconsistently applied, plus are scattered across a lot of jobs / variations. > Instead, we should externalize these URLs as variables we can control from some other global properties file, perhaps located in https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/ and called *jbosstools-jenkins.properties*. This would make the jobs easier to maintain and I'd forget to update stuff less often. :D > Affected jobs: > * devstudio_master/job/jbosstools-composite-install_master/config.xml > * devstudio_master/job/jbosstools-install-p2director.install-tests.matrix_master/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatform-4.70.x/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatform-4.71.x/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatform-4.71.x-experimental/config.xml > * devstudio_target_platforms/job/jbosstoolstargetplatformrequirements-mirror-matrix/config.xml > * jbosstools-releng/job/jbosstools-cleanup/config.xml > * ...? > URL patterns: > * /eclipse/downloads/drops4/R-4.7.1-201709061700/eclipse-platform-4.7.1-linux-gtk.tar.gz > * /eclipse/downloads/drops4/M-4.7.1RC4-201709061700/eclipse-platform-4.7.1RC4-linux-gtk.tar.gz > * /eclipse/downloads/drops4/S-4.7RC4a-201706120950/eclipse-platform-4.7RC4a-linux-gtk.tar.gz > * http://www.eclipse.org/downloads/download.php?r=1&file=/eclipse/downl... > * http://download.eclipse.org/eclipse/downloads/drops4/S-4.7RC4a-2017061209... > * eclipse_downloads_drops4_R-4.7.1-201709061700_eclipse-platform-4.7.1-linux-gtk.tar.gz > * eclipse-platform-4.7.1-linux-gtk.tar.gz > * ... more? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24868: ------------------------------------------ [~jeffmaury] resetting the timeout is now done. But [~rob.stryker] sees the same as I did in https://issues.jboss.org/browse/JBIDE-24868?focusedCommentId=13471109&pag...: eap works while node still cuts the connection after 30 seconds. > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.Final > > Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 reassigned JBIDE-25300: ---------------------------------- Assignee: Nick Boldt > 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 is symlinked to 3.5.0. > We should get 3.5.2 installed and use that in the jobs as it supports JDK 9. > cc: [~psrna] [~mmalina] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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: ------------------------------- Description: 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] was: Jobs currently use mvn 3.3.9, unless pointed as "mvn3-latest", which is symlinked to 3.5.0. We should get 3.5.2 installed and use that in the jobs as it supports JDK 9. cc: [~psrna] [~mmalina] > 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, 5 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25300: ---------------------------------- Summary: 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 Jobs currently use mvn 3.3.9, unless pointed as "mvn3-latest", which is symlinked to 3.5.0. We should get 3.5.2 installed and use that in the jobs as it supports JDK 9. cc: [~psrna] [~mmalina] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017