August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Roland Grunberg commented on JBIDE-22966: ----------------------------------------- It would also be nice if there could be some mappings for the state of an issue (that synchronizes every fixed period of time). As discussed, even just VERIFIED => resolved, CLOSED => closed would be great. > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RH-ECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22965: ---------------------------------------- I have created an issue for OpenShift Tools - JBIDE-22969 [~dbocharov] is this something you can take care in the next sprint? [~mlabuda], Dmitry will probably need your help with creating integration tests for this. I mean Dmitry is supposed develop these tests but devs don't have experience in creating reddeer tests so your help is appreciated. > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.Final > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-22969: -------------------------------------- Summary: Make sure OpenShift Tools support proxies Key: JBIDE-22969 URL: https://issues.jboss.org/browse/JBIDE-22969 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Reporter: Alexey Kazakov Assignee: Dmitry Bocharov Fix For: 4.4.1.Final CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. This issue covers: - testing - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-819: ---------------------------------- Yup - I don't know where that one in coming from - I'll look for it... > Update fuse icons for 9.0.1.GA > ------------------------------ > > Key: JBTIS-819 > URL: https://issues.jboss.org/browse/JBTIS-819 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, Fuse IDE > Affects Versions: 9.0.1.CR3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > Attachments: jbdsis901ga_camel_icon1.png, jbdsis901ga_camel_icon2.png > > > Update the fuse icons - they are out of date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22968: ---------------------------------- Story Points: 5 Sprint: devex #118 July 2016 Assignee: Nick Boldt > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22968: ------------------------------- Fix Version/s: 4.4.1.Final > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22968 at 8/9/16 11:33 AM: ------------------------------------------------------------- What happened: * !openshift-failed-future-builds-did-not-publish.png! What should have happened: * build 1482 should have been published into http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ope... was (Author: nickboldt): What happened: * !openshift-failed-future-builds-did-not-publish.png! What should have happened: * build 1478 should have been published into http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ope... > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22968: ------------------------------- Attachment: openshift-failed-future-builds-did-not-publish.png What happened: * !openshift-failed-future-builds-did-not-publish.png! What should have happened: * build 1478 should have been published into http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ope... > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22968: ---------------------------------- Summary: if a build fails to publish, future builds may think there's nothing new and also not publish Key: JBIDE-22968 URL: https://issues.jboss.org/browse/JBIDE-22968 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Nick Boldt When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-819: -------------------------------------- that looks like the old icon > Update fuse icons for 9.0.1.GA > ------------------------------ > > Key: JBTIS-819 > URL: https://issues.jboss.org/browse/JBTIS-819 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, Fuse IDE > Affects Versions: 9.0.1.CR3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > Attachments: jbdsis901ga_camel_icon1.png, jbdsis901ga_camel_icon2.png > > > Update the fuse icons - they are out of date. -- 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 August 2016