May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3859: -------------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3859: -------------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3859: ----------------------------------- Assignee: Denis Golovin (was: Nick Boldt) > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3859. --------------------------------- Resolution: Done > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3859: ----------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3859: -------------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3859: -------------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3859: ----------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3849. --------------------------------- Resolution: Done > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22270) [jiralint] Error in JQL Query: Expecting either a value, list or function but got ')'

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22270?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22270: --------------------------------------------- inflight wifi is too slow for me to run this locally nor access jenkins to see the actual failing query. Go look at the query that cause the failure and look for empty "()" like version in (), most likely version metadata in jira is missing expected versions. Like a next version for maintanence. > [jiralint] Error in JQL Query: Expecting either a value, list or function but got ')' > ------------------------------------------------------------------------------------- > > Key: JBIDE-22270 > URL: https://issues.jboss.org/browse/JBIDE-22270 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.4.0.Alpha2 > > > Somewhere in the last 8 days, a commit [1] broke jiralint: > [1] https://github.com/maxandersen/jiralint/commits/master > {code}HTTPError = 400 {"errorMessages":["Error in JQL Query: Expecting either a value, list or function but got ')'. You must surround ')' in quotation marks to use it as a value. (line 1, character 41)"],"errors":{}} > Build step 'Jenkins Text Finder' changed build result to FAILURE > {code} - http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... ... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > The last good build was #2066: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... (Apr 19, 2016 2:58:01 AM EST) > Since then all builds have been red. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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