November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25322) Jenkins Job Builder proof of concept

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25322?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25322: --------------------------------------- {quote} 2. Fix the mmalina-experiment job yaml to not include any "raw" xml if possible. {quote} This is done. Some unnecessary parts were removed altogether, others were replaced by yaml syntax as documented here: https://docs.openstack.org/infra/jenkins-job-builder/properties.html#prop... The job is now set up to poll scm every 5 minutes. So if you push changes to the repo, those changes should be applied to jenkins jobs within a few minutes. > Jenkins Job Builder proof of concept > ------------------------------------- > > Key: JBIDE-25322 > URL: https://issues.jboss.org/browse/JBIDE-25322 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.5.x > > > Jenkins Job Builder > https://docs.openstack.org/infra/jenkins-job-builder/ > Jenkins Job Wrecker > https://github.com/ktdreyer/jenkins-job-wrecker > - for converting existing jobs xml config to yaml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25434) Connection specific oc location taken even after override oc location is reset

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25434?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25434: ---------------------------------- Assignee: Rob Stryker > Connection specific oc location taken even after override oc location is reset > ------------------------------------------------------------------------------ > > Key: JBIDE-25434 > URL: https://issues.jboss.org/browse/JBIDE-25434 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: openshift, openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.5.x > > > ASSERT: have no oc binary configured at preferences > ASSERT: have an oc configured at the connection level and override set > EXEC: create a server adapter > ASSERT: no warning about oc version should be displayed > ASSERT: reset the oc override flag for the connection > EXEC: create a server adapter > ASSERT: a warning about oc should be set, but it is not -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25434) Connection specific oc location taken even after override oc location is reset

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-25434: ---------------------------------- Summary: Connection specific oc location taken even after override oc location is reset Key: JBIDE-25434 URL: https://issues.jboss.org/browse/JBIDE-25434 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.2.AM1 Reporter: Jeff MAURY Fix For: 4.5.x ASSERT: have no oc binary configured at preferences ASSERT: have an oc configured at the connection level and override set EXEC: create a server adapter ASSERT: no warning about oc version should be displayed ASSERT: reset the oc override flag for the connection EXEC: create a server adapter ASSERT: a warning about oc should be set, but it is not -- 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 Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4616?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-4616: ---------------------------------- [~nickboldt] changes are now applied on rhel7 slaves. Please give it a try and verify if it works for you. thx. > 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) [build] 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 resolved JBIDE-25300. -------------------------------- Resolution: Done > [build] 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-25300) [build] 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 edited comment on JBIDE-25300 at 11/22/17 12:07 PM: --------------------------------------------------------------- Jobs updated to use maven-3.5.2, rather than maven3-latest (so we don't get surprises when new versions are released): https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... https://github.com/jbdevstudio/jbdevstudio-ci/commit/b9ac8d0ade405e091091... and these 182 jobs too: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1e2a8da8565f105a11b8... was (Author: nickboldt): Jobs updated: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... https://github.com/jbdevstudio/jbdevstudio-ci/commit/b9ac8d0ade405e091091... and these 182 jobs too: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1e2a8da8565f105a11b8... > [build] 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-25300) [build] 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 commented on JBIDE-25300: ------------------------------------ Jobs updated: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... https://github.com/jbdevstudio/jbdevstudio-ci/commit/b9ac8d0ade405e091091... and these 182 jobs too: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1e2a8da8565f105a11b8... > [build] 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-25430) New Openshift Server should not allow changing connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25430?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25430: -------------------------------- Fix Version/s: 4.5.2.AM2 > New Openshift Server should not allow changing connection > --------------------------------------------------------- > > Key: JBIDE-25430 > URL: https://issues.jboss.org/browse/JBIDE-25430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.5.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.2.AM2 > > > The openshift 3 new server wizard page allows you to change the details of the connection you've selected. This already seems very wrong. It's inappropriate for you to be changing the details of a connection that already exists, at least if you're not making a duplicate connection and leaving the original untouched. > Other server adapters or other parts of code may refer to these connections. Changing them in the new server wizard should not be a primary usecase. If the user does need to change them, it should be done via an 'edit connection' button, so teh user changes the connection but is aware he is changing it and is not simply making a duplicate with slightly different details. > Some of the fields (in the advanced section) are even changed on the connection EVEN if you CANCEL out of the new server wizard. THis is a big problem, and probably has more to do with the openshift connection API than anything. However, limiting that from occurring in the new server wizard will remove half the ways this bug can occur, so that's still a benefit. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25430) New Openshift Server should not allow editing connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25430?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25430: -------------------------------- Summary: New Openshift Server should not allow editing connection (was: New Openshift Server should not allow changing connection) > New Openshift Server should not allow editing connection > -------------------------------------------------------- > > Key: JBIDE-25430 > URL: https://issues.jboss.org/browse/JBIDE-25430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.5.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.2.AM2 > > > The openshift 3 new server wizard page allows you to change the details of the connection you've selected. This already seems very wrong. It's inappropriate for you to be changing the details of a connection that already exists, at least if you're not making a duplicate connection and leaving the original untouched. > Other server adapters or other parts of code may refer to these connections. Changing them in the new server wizard should not be a primary usecase. If the user does need to change them, it should be done via an 'edit connection' button, so teh user changes the connection but is aware he is changing it and is not simply making a duplicate with slightly different details. > Some of the fields (in the advanced section) are even changed on the connection EVEN if you CANCEL out of the new server wizard. THis is a big problem, and probably has more to do with the openshift connection API than anything. However, limiting that from occurring in the new server wizard will remove half the ways this bug can occur, so that's still a benefit. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25430) New Openshift Server should not allow editing connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25430?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25430: -------------------------------- Sprint: devex #141 December 2017 > New Openshift Server should not allow editing connection > -------------------------------------------------------- > > Key: JBIDE-25430 > URL: https://issues.jboss.org/browse/JBIDE-25430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.5.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.2.AM2 > > > The openshift 3 new server wizard page allows you to change the details of the connection you've selected. This already seems very wrong. It's inappropriate for you to be changing the details of a connection that already exists, at least if you're not making a duplicate connection and leaving the original untouched. > Other server adapters or other parts of code may refer to these connections. Changing them in the new server wizard should not be a primary usecase. If the user does need to change them, it should be done via an 'edit connection' button, so teh user changes the connection but is aware he is changing it and is not simply making a duplicate with slightly different details. > Some of the fields (in the advanced section) are even changed on the connection EVEN if you CANCEL out of the new server wizard. THis is a big problem, and probably has more to do with the openshift connection API than anything. However, limiting that from occurring in the new server wizard will remove half the ways this bug can occur, so that's still a benefit. -- 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