September 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4535) RPM should depend on tern rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4535?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4535: -------------------------------- Assignee: Nick Boldt > RPM should depend on tern rpm > ----------------------------- > > Key: JBDS-4535 > URL: https://issues.jboss.org/browse/JBDS-4535 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > RPM should depend on upstream tern.java rpm(s). Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4536) RPM should depend on tern rpmbuildship/gradle rpms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4536?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4536: ----------------------------- Fix Version/s: 11.x > RPM should depend on tern rpmbuildship/gradle rpms > -------------------------------------------------- > > Key: JBDS-4536 > URL: https://issues.jboss.org/browse/JBDS-4536 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Fix For: 11.x > > > RPM should depend on upstream buildship & grade tooling commons rpm(s). Depends on getting this done in Fedora and devtools channel first. > See https://github.com/gradle/tooling-commons > We probably want to contribute a maven-based build for this too, so that we can use it in the RPMs rather than needing to use gradle to build the rpms. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4536) RPM should depend on tern rpmbuildship/gradle rpms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4536?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4536: -------------------------------- Assignee: Nick Boldt > RPM should depend on tern rpmbuildship/gradle rpms > -------------------------------------------------- > > Key: JBDS-4536 > URL: https://issues.jboss.org/browse/JBDS-4536 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > RPM should depend on upstream buildship & grade tooling commons rpm(s). Depends on getting this done in Fedora and devtools channel first. > See https://github.com/gradle/tooling-commons > We probably want to contribute a maven-based build for this too, so that we can use it in the RPMs rather than needing to use gradle to build the rpms. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4535) RPM should depend on tern rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4535?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4535: ----------------------------- Fix Version/s: 11.x > RPM should depend on tern rpm > ----------------------------- > > Key: JBDS-4535 > URL: https://issues.jboss.org/browse/JBDS-4535 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Fix For: 11.x > > > RPM should depend on upstream tern.java rpm(s). Depends on getting this done in Fedora and devtools channel first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24485) Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24485?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24485: ------------------------------------ Shaved 10 mins off the elapsed time, compared to the 65 mins needed for 4.5.0.* milestone staging. {code} jbosstools-releng-push-to-staging-02-copy-builds-and-update-sites_jbt 5 (4.5.1.AM2) OVERALL TIME 26 MIN 1 core 25-30 mins 2 coretests 20-30 mins 3 ea central 2m25 4 browsersim 56s 5 itests 1m42 6 fuse extras 37s jbosstools-releng-push-to-staging-02-copy-builds-and-update-sites_ds 5 (11.1.0.AM2) OVERALL TIME 56 MIN 1 ds installer 55 min 2 ds tp 8m9 3 ea central zips 52s 4 ea central 3m29 5 rpm 4m46 6 fuse extras 30s{code} Will check publish times for milestone release next week > Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24485 > URL: https://issues.jboss.org/browse/JBIDE-24485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.1.AM2 > > > Should split release job [1] into two pieces so jbosstools and devstudio can run in parallel to save time. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24485) Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24485?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24485 at 9/14/17 4:26 PM: ------------------------------------------------------------- Shaved 10 mins off the elapsed time, compared to the 65 mins needed for 4.5.0.* milestone staging. {code} jbosstools-releng-push-to-staging-02-copy-builds-and-update-sites_jbt 5 (4.5.1.AM2) OVERALL TIME 26 MIN 1 core 25-30 mins 2 coretests 20-30 mins 3 ea central 2m25 4 browsersim 56s 5 itests 1m42 6 fuse extras 37s jbosstools-releng-push-to-staging-02-copy-builds-and-update-sites_ds 5 (11.1.0.AM2) OVERALL TIME 56 MIN 1 ds installer 55 min 2 ds tp 8m9 3 ea central zips 52s 4 ea central 3m29 5 rpm 4m46 6 fuse extras 30s{code} -- https://docs.google.com/spreadsheets/d/1T-QBqznq_0CySe4bDvIFYrws-FA1HhcS8... Will check publish times for milestone release next week was (Author: nickboldt): Shaved 10 mins off the elapsed time, compared to the 65 mins needed for 4.5.0.* milestone staging. {code} jbosstools-releng-push-to-staging-02-copy-builds-and-update-sites_jbt 5 (4.5.1.AM2) OVERALL TIME 26 MIN 1 core 25-30 mins 2 coretests 20-30 mins 3 ea central 2m25 4 browsersim 56s 5 itests 1m42 6 fuse extras 37s jbosstools-releng-push-to-staging-02-copy-builds-and-update-sites_ds 5 (11.1.0.AM2) OVERALL TIME 56 MIN 1 ds installer 55 min 2 ds tp 8m9 3 ea central zips 52s 4 ea central 3m29 5 rpm 4m46 6 fuse extras 30s{code} Will check publish times for milestone release next week > Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24485 > URL: https://issues.jboss.org/browse/JBIDE-24485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.1.AM2 > > > Should split release job [1] into two pieces so jbosstools and devstudio can run in parallel to save time. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24757) improve errata waiver check script - add waivers for desktop-file-sanity, xml-validity, patches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24757?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24757: ------------------------------------ [~mat.booth] let me know the next time we have errata for me to script autowaiving and I'll make sure to do so before you get to them manually. > improve errata waiver check script - add waivers for desktop-file-sanity, xml-validity, patches > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24757 > URL: https://issues.jboss.org/browse/JBIDE-24757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.AM3 > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * xml-validity (always waive?) > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24757) improve errata waiver check script - add waivers for desktop-file-sanity, xml-validity, patches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24757?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24757: ------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > improve errata waiver check script - add waivers for desktop-file-sanity, xml-validity, patches > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24757 > URL: https://issues.jboss.org/browse/JBIDE-24757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.AM3 > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * xml-validity (always waive?) > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24757) improve errata waiver check script - add waivers for desktop-file-sanity, xml-validity, patches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24757?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24757: ------------------------------- Sprint: devex #135 July 2017, devex #138 September 2017 (was: devex #135 July 2017) > improve errata waiver check script - add waivers for desktop-file-sanity, xml-validity, patches > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24757 > URL: https://issues.jboss.org/browse/JBIDE-24757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.AM3 > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * xml-validity (always waive?) > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24895) some smoke and weekly jobs are configured for multiple OSes but only run on rhel7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24895?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24895: ------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > some smoke and weekly jobs are configured for multiple OSes but only run on rhel7 > --------------------------------------------------------------------------------- > > Key: JBIDE-24895 > URL: https://issues.jboss.org/browse/JBIDE-24895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, build, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > > Just wondering why there's a chunk of shell script in the aerogear.it.smoke job that allows it to run on linux, rhel, or osx... but the job is only configured to run on rhel7 slaves. > Is the code boilerplate, or is the job supposed to run on more than one type of OS? > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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