December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23151) script creation of PRs by generic user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23151?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23151: ------------------------------------ Note, job was renamed: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/view/devstudio/job/jbossto... > script creation of PRs by generic user > -------------------------------------- > > Key: JBIDE-23151 > URL: https://issues.jboss.org/browse/JBIDE-23151 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > Need the ability to create, submit, and merge PRs automatically as a generic user, so that changes to filesystem on download.jboss.org & devstudio.redhat.com (filemgmt) can be done automatically. > Spoke with [~akazakov] today to discuss how to proceed: > * new user "devstudio-release" for: jbdevstudio-website and jbosstools-downloads.jboss.org repos > * in future might also fork jbosstools-website repo so that changes to products.yaml can be automated too > * ideally, this would be a non-password (plaintext in config.xml = bad) authentication. github auth token? ssh key? > * maybe run this in isolation on wonka? that way less people have access to the config.xml of the job > * @Nick to explore getting more ssh keys for pushing to filemgmt.jboss.org > * @Nick to create user & start generating PRs for changes to dl.jb.o and ds.rh.c -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23475) split ide-config.properties into multiple files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23475?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23475: ------------------------------------ I've updated the python script so that changes are applied to the fragment files, then merged to ide-config.properties. Also added support for commenting/uncommenting blocks when required, so that we don't get conflicts between staging and released content. Added doc on how to run in the three modes: {code} # 1. release a dev milestone: git checkout src/main/ide-config.*properties ide-config.properties mvn clean install -DbuildType=development # 2. release a stable GA: mvn clean install -DbuildType=stable # 3. stage a milestone: mvn clean install -DbuildType=staging \ -Dversion_jbt_PREV=4.4.2.Final -Dversion_jbt=4.4.3.AM1 -Dversion_jbt_NEXT=4.4.3.AM2 \ -Dversion_ds_PREV=10.2.0.GA -Dversion_ds=10.3.0.AM1 -Dversion_ds_NEXT=10.3.0.AM2 {code} > split ide-config.properties into multiple files > ------------------------------------------------- > > Key: JBIDE-23475 > URL: https://issues.jboss.org/browse/JBIDE-23475 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, central-update > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > I'd like to split the contents of the current ide-config.properties file into multiple files so the content is easier to maintain via code generation. > So, rather than 1 big file [1] we could split this into 5 files: > * ide-config_4.4.snapshots.properties - contains the properties needed for jbosstools and devstudio CI builds (currently 4.4.2.Final and 10.2.0.GA) > * ide-config_4.4.staging.properties - contains the properties needed for the latest jbosstools and devstudio staging build (currently 4.4.2.AM3 and 10.2.0.AM3) > * ide-config_4.4.development.properties - contains the properties needed for the latest jbosstools and devstudio development build (currently 4.4.2.AM2 and 10.1.0.GA) > * ide-config_4.4.stable.properties - contains the properties needed for the latest jbosstools and devstudio stable build (currently 4.4.1.Final and 10.1.0.GA) > * ide-config.properties - contains all the other properties for 4.3.x and earlier releases > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > By splitting this into smaller files, the contents that need to be changed every 3 weeks when we stage or release a build could be generated destructively, rather than having to worry about making changes w/ sed and not accidentally pushing in an invalid URL or value. > From the central side of things, we would just want to treat all ide-config*.properties files as if they were pieces of a single file, and load them all into the same hash of properties we currently have from the single file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23629) integration tests: AddConnectionTest looks up connections by name, should by host

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23629?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23629: ------------------------------------- Fix Version/s: 4.4.3.AM1 > integration tests: AddConnectionTest looks up connections by name, should by host > --------------------------------------------------------------------------------- > > Key: JBIDE-23629 > URL: https://issues.jboss.org/browse/JBIDE-23629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Fix For: 4.4.3.AM1 > > > Connections in the Docker explorer must be unique in name and unique in host. AddConnectionTest thus can fail if there already is a connection using the same host with a different name. > This should be fixed by looking up connections by their host. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23629) integration tests: AddConnectionTest looks up connections by name, should by host

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23629?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23629: ---------------------------------------- Assignee: Andre Dietisheim > integration tests: AddConnectionTest looks up connections by name, should by host > --------------------------------------------------------------------------------- > > Key: JBIDE-23629 > URL: https://issues.jboss.org/browse/JBIDE-23629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > > Connections in the Docker explorer must be unique in name and unique in host. AddConnectionTest thus can fail if there already is a connection using the same host with a different name. > This should be fixed by looking up connections by their host. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23629) integration tests: AddConnectionTest looks up connections by name, should by host

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23629: ---------------------------------------- Summary: integration tests: AddConnectionTest looks up connections by name, should by host Key: JBIDE-23629 URL: https://issues.jboss.org/browse/JBIDE-23629 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Affects Versions: 4.4.2.Final Reporter: Andre Dietisheim Connections in the Docker explorer must be unique in name and unique in host. AddConnectionTest thus can fail if there already is a connection using the same host with a different name. This should be fixed by looking up connections by their host. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-473) Don't try to browse a container that isn't using TTY [EBZ#508705]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-473?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-473. ------------------------------- Resolution: Done > Don't try to browse a container that isn't using TTY [EBZ#508705] > ----------------------------------------------------------------- > > Key: ERT-473 > URL: https://issues.jboss.org/browse/ERT-473 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > The browse Container features of Copy from Container and Copy to Container features rely on using exec to run ls and gather info from the Container. This does not work reliably when the Container is not created with the tty option. Instead, treat the Container as if it was stopped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-471) Update Docker documentation for Neon.2 [EBZ#508552]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-471?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-471. ------------------------------- Resolution: Done > Update Docker documentation for Neon.2 [EBZ#508552] > --------------------------------------------------- > > Key: ERT-471 > URL: https://issues.jboss.org/browse/ERT-471 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > Documentation for Docker Tooling needs to be updated for Neon.2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-473) Don't try to browse a container that isn't using TTY [EBZ#508705]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-473?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-473: --------------------------------- Assignee: Jeff Johnston > Don't try to browse a container that isn't using TTY [EBZ#508705] > ----------------------------------------------------------------- > > Key: ERT-473 > URL: https://issues.jboss.org/browse/ERT-473 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > The browse Container features of Copy from Container and Copy to Container features rely on using exec to run ls and gather info from the Container. This does not work reliably when the Container is not created with the tty option. Instead, treat the Container as if it was stopped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-473) Don't try to browse a container that isn't using TTY [EBZ#508705]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-473?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-473: ------------------------------ Sprint: devex #124 December 2017 > Don't try to browse a container that isn't using TTY [EBZ#508705] > ----------------------------------------------------------------- > > Key: ERT-473 > URL: https://issues.jboss.org/browse/ERT-473 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > The browse Container features of Copy from Container and Copy to Container features rely on using exec to run ls and gather info from the Container. This does not work reliably when the Container is not created with the tty option. Instead, treat the Container as if it was stopped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-471) Update Docker documentation for Neon.2 [EBZ#508552]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-471?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-471: --------------------------------- Assignee: Jeff Johnston > Update Docker documentation for Neon.2 [EBZ#508552] > --------------------------------------------------- > > Key: ERT-471 > URL: https://issues.jboss.org/browse/ERT-471 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > Documentation for Docker Tooling needs to be updated for Neon.2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 December 2016