June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22506) Aeri web requires login to see submitted bug

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22506?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22506: -------------------------------------- Assignee: Marcel Bruch > Aeri web requires login to see submitted bug > -------------------------------------------- > > Key: JBIDE-22506 > URL: https://issues.jboss.org/browse/JBIDE-22506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Affects Versions: 4.4.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Marcel Bruch > Priority: Critical > Fix For: 4.4.x > > > I've submitted a bug via aeri and got this url in notification > https://redhat.ctrlflow.com/reporters/#!/submissions/2UAIQE4IlcQ0ctFOxLBX... which requires login to see the content. > If I remember correctly logging in was not needed in the past. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22473: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Environment Var Wizard: Cannot remove env vars > ---------------------------------------------- > > Key: JBIDE-22473 > URL: https://issues.jboss.org/browse/JBIDE-22473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22506) Aeri web requires login to see submitted bug

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22506?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22506: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Aeri web requires login to see submitted bug > -------------------------------------------- > > Key: JBIDE-22506 > URL: https://issues.jboss.org/browse/JBIDE-22506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Affects Versions: 4.4.0.Alpha2 > Reporter: Rastislav Wagner > Priority: Critical > Fix For: 4.4.x > > > I've submitted a bug via aeri and got this url in notification > https://redhat.ctrlflow.com/reporters/#!/submissions/2UAIQE4IlcQ0ctFOxLBX... which requires login to see the content. > If I remember correctly logging in was not needed in the past. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22281) Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22281?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22281: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS) > ---------------------------------------------------------------------------- > > Key: JBIDE-22281 > URL: https://issues.jboss.org/browse/JBIDE-22281 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.x > > > * JBT 4.4.0.Alpha1 loads too many update sites: > 1. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/ > 2. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/discovery.early... > 3. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > 4. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.0.Final > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Fix Version/s: 4.4.0.Final (was: 4.4.x) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.0.Final > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19730) Build Improvement

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19730: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Build Improvement > ----------------- > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > Epic to track issues related to improving how we release software. > This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22281) Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22281?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22281: ------------------------------------ As of Final, I only see: 1. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/ Enabled 2. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/discovery.early... Enabled 3. JBoss Tools Integration Stack Update Site http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... Enabled > Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS) > ---------------------------------------------------------------------------- > > Key: JBIDE-22281 > URL: https://issues.jboss.org/browse/JBIDE-22281 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Final > > > * JBT 4.4.0.Alpha1 loads too many update sites: > 1. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/ > 2. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/discovery.early... > 3. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > 4. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19729) Version Auditing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19729: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Version Auditing > ---------------- > > Key: JBIDE-19729 > URL: https://issues.jboss.org/browse/JBIDE-19729 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > Epic to track issues related to auditing and quality control. > This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Labels: releasework (was: ) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.0.Final > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016