[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)
7 years, 10 months
[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)
7 years, 10 months
[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)
7 years, 10 months