[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25301:
-------------------------------
Fix Version/s: 4.6.0.AM1
(was: 4.6.x)
> [release] externalize common properties to parameterize jobs
> ------------------------------------------------------------
>
> Key: JBIDE-25301
> URL: https://issues.jboss.org/browse/JBIDE-25301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM1
>
>
> As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized.
> for example we could set these params in the jbosstools-jenkins.properties files:
> {code}TARGET_PLATFORM_VERSION_MIN=
> TARGET_PLATFORM_VERSION_MAX=
> TARGET_PLATFORM_CENTRAL_MAX=
> {code}
> Or we could simply remove them and source them from the parent pom.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-25301.
--------------------------------
Resolution: Done
Params removed from jobs where possible. Resolving.
> [release] externalize common properties to parameterize jobs
> ------------------------------------------------------------
>
> Key: JBIDE-25301
> URL: https://issues.jboss.org/browse/JBIDE-25301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM1
>
>
> As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized.
> for example we could set these params in the jbosstools-jenkins.properties files:
> {code}TARGET_PLATFORM_VERSION_MIN=
> TARGET_PLATFORM_VERSION_MAX=
> TARGET_PLATFORM_CENTRAL_MAX=
> {code}
> Or we could simply remove them and source them from the parent pom.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25700:
------------------------------------------
turns out that we need 3 additional flags to avoid this unnoticed error:
* --no-g
* --no-o
* --omit-dir-times
in a feature request for the oc client at https://github.com/openshift/origin/issues/19365 the openshift team is suggesting to include these by default.
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.6.0.AM1
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25597:
------------------------------------
Fix for RD 2.1 support: https://github.com/jbosstools/jbosstools-base/pull/616
However, I can't compile this because:
{code}
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.1.0:compile (default-compile) on project org.jboss.tools.common.model: Compilation failure: Compilation failure:
[ERROR] /home/nboldt/tru/jbosstools-base/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/meta/help/HelpUtil.java:[19]
[ERROR] import org.eclipse.ui.help.WorkbenchHelp;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.ui.help.WorkbenchHelp cannot be resolved
[ERROR] /home/nboldt/tru/jbosstools-base/common/plugins/org.jboss.tools.common.model/src/org/jboss/tools/common/meta/help/HelpUtil.java:[80]
[ERROR] WorkbenchHelp.displayHelpResource(path);
[ERROR] ^^^^^^^^^^^^^
[ERROR] WorkbenchHelp cannot be resolved
[ERROR] 2 problems (2 errors)
{code}
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM1, 4.6.0.AM2, 4.6.0.AM3, 4.6.0.Final
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25597:
------------------------------------
This TP updates the following projects/versions from the 4.73.1.Final TP:
{code}
docker;4.0.0.201804162200
dtp;1.14.100-201803020938
egit;4.11.0.201803080745-r
jetty;9.4.9.v20180320
orbit;I20180417184143
photon;201804161625-Photon.0.M6plus (from staging site)
reddeer;2.1.0.Final
tm;3.8.0.201803021406_4.4.0.201803141729
webtools;I-3.10.0-20180414044730
{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM1, 4.6.0.AM2, 4.6.0.AM3, 4.6.0.Final
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months