November 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3209) Screencast for JBDS8/OpenShift - Quickstarts and links to custom cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3209?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-3209: ---------------------------------------- Part 1: https://www.youtube.com/watch?v=9FSFJVRh0f4 Part 2: https://www.youtube.com/watch?v=FZj0W60gtE8 > Screencast for JBDS8/OpenShift - Quickstarts and links to custom cartridges > --------------------------------------------------------------------------- > > Key: JBDS-3209 > URL: https://issues.jboss.org/browse/JBDS-3209 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.GA > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 8.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3209) Screencast for JBDS8/OpenShift - Quickstarts and links to custom cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3209?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3209: ----------------------------------- Fix Version/s: 8.0.0.GA > Screencast for JBDS8/OpenShift - Quickstarts and links to custom cartridges > --------------------------------------------------------------------------- > > Key: JBDS-3209 > URL: https://issues.jboss.org/browse/JBDS-3209 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.GA > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 8.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3209) Screencast for JBDS8/OpenShift - Quickstarts and links to custom cartridges

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBDS-3209: -------------------------------------- Summary: Screencast for JBDS8/OpenShift - Quickstarts and links to custom cartridges Key: JBDS-3209 URL: https://issues.jboss.org/browse/JBDS-3209 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: openshift Affects Versions: 8.0.0.GA Reporter: Andre Dietisheim Assignee: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-360: ---------------------------------- [~pleacu] https://github.com/jbdevstudio/jbdevstudio-website/pull/159 gets my +0.5; needs some tweaks to be a +1. > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18742) Decide whether to publish new aggregate by comparating it with last snapshot

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18742 at 11/12/14 12:34 PM: --------------------------------------------------------------- * schedule all 4 aggregate jobs [core, tests, hibernate, webtools] to check at 3 hr intervals (same as we do today for the composite install job) ** if we want, we can implement the "if you failed try again 30 mins later" logic currently in the master branch composite install job [1] * put p2diff executable (for both x86 and x86_64) in /home/hudson/static_build_env/jbds/ on dev01 server * store 4 p2diff logs in /logs/ folder [compare w/ previous snapshot, previous staging, previous milestone/development, previous stable/release] When the above is working, we can: * deprecate master branch composite install job [1] * delete master branch composite install site [2] [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... [2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/master/ Added bonus is that for any given published build (snapshot, staging, development, stable) we can see how it compared with its predecessor build. Helpful for QE, I hope. was (Author: nickboldt): * schedule all 4 aggregate jobs [core, tests, hibernate, webtools] to check at 3 hr intervals (same as we do today for the composite install job) ** if we want, we can implement the "if you failed try again 30 mins later" logic currently in the master branch composite install job [1] * put p2diff executable (for both x86 and x86_64) in /home/hudson/static_build_env/jbds/ on dev01 server * store 4 p2diff logs in /logs/ folder [compare w/ previous snapshot, previous staging, previous milestone/development, previous stable/release] When the above is working, we can: * deprecate master branch composite install job [1] * delete master branch composite install site [2] [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... [2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/master/ > Decide whether to publish new aggregate by comparating it with last snapshot > ---------------------------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18742) Decide whether to publish new aggregate by comparating it with last snapshot

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18742: ------------------------------------ * schedule all 4 aggregate jobs [core, tests, hibernate, webtools] to check at 3 hr intervals (same as we do today for the composite install job) ** if we want, we can implement the "if you failed try again 30 mins later" logic currently in the master branch composite install job [1] * put p2diff executable (for both x86 and x86_64) in /home/hudson/static_build_env/jbds/ on dev01 server * store 4 p2diff logs in /logs/ folder [compare w/ previous snapshot, previous staging, previous milestone/development, previous stable/release] When the above is working, we can: * deprecate master branch composite install job [1] * delete master branch composite install site [2] [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... [2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/master/ > Decide whether to publish new aggregate by comparating it with last snapshot > ---------------------------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Description: We need to write tests for download.jboss.org & devstudio.redhat.com: * xmlunit test cases ** validate composite*.xml ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) * other test cases ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) was: We need to write tests for download.jboss.org & devstudio.redhat.com: * xmlunit test cases ** validate composite*.xml * other test cases ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Description: We need to write tests for download.jboss.org & devstudio.redhat.com: * xmlunit test cases ** validate composite*.xml * other test cases ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) was: We need to write tests for download.jboss.org & devstudio.redhat.com: * xmlunit test cases ** validate composite*.xml * other test cases ** *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18743: ---------------------------------- Summary: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) Key: JBIDE-18743 URL: https://issues.jboss.org/browse/JBIDE-18743 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.2.0.Final Reporter: Nick Boldt We need to write tests for download.jboss.org & devstudio.redhat.com: * xmlunit test cases ** validate composite*.xml * other test cases ** *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3163 at 11/12/14 12:20 PM: ------------------------------------------------------------- Per minutes of [1], Max and Len are +1 on this idea. [1] http://ether-man.rhcloud.com/p/build.next.20141112 (lines 54-58) [~jpallich] [~burrsutter]]: Does this sound good to you? If yes, can you please propose for release and mark as PM ack? was (Author: mickael_istria): [~jpallich] [~maxandersen]: Does this sound good to you? If yes, can you please propose for release and mark as PM ack? > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 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 2014