[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23322.
---------------------------------
> create mojo that takes as input a list of URLs and a name, and generates a composite site
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23322
> URL: https://issues.jboss.org/browse/JBIDE-23322
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.Final
>
>
> In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs.
> So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files:
> {code}
> target/composite/compositeContent.xml
> target/composite/compositeArtifacts.xml
> target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index )
> {code}
> Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> So we could use this to create composite sites in folders like:
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date)
> But also to point to remote (/stable/) URLs from pointer sites, like:
> * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd)
> * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1)
> * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-20177) migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20177?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-20177.
---------------------------------
> migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20177
> URL: https://issues.jboss.org/browse/JBIDE-20177
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.Final
>
>
> If we can migrate this logic into the mojo...
> {code}
> if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then
> {code}
> ... we'll be able to remove this step in all jobs:
> {code}
> <hudson.tasks.Maven>
> <targets>-U -e org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack</targets>
> <mavenName>maven-3.2.5</mavenName>
> <properties>artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Beta2-SNAPSHOT:zip
> outputDirectory=${WORKSPACE}/sources
> trimVersion=true
> mdep.stripClassifier=true
> mdep.stripVersion=true</properties>
> <usePrivateRepository>false</usePrivateRepository>
> <settings class="jenkins.mvn.DefaultSettingsProvider"/>
> <globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
> </hudson.tasks.Maven>
> {code}
> ... and instead, just pass in those vars to maven:
> {code}
> -DskipRevisionCheckWhenPublishing=${skipRevisionCheckWhenPublishing}
> -DcheckLatestPublishedSHA_SOURCE_PATH=${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo
> -DcheckLatestPublishedSHA_TARGET_PATH=http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24225.
---------------------------------
> publish p2diff app to Nexus for easier use in jenkins jobs
> ----------------------------------------------------------
>
> Key: JBIDE-24225
> URL: https://issues.jboss.org/browse/JBIDE-24225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.Final
>
> Attachments: maven-releng-fetch.png
>
>
> Rather than bootstrapping by hand and having to reference p2diff like this:
> {code}
> p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
> {code}
> It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) ...
> !maven-releng-fetch.png|thumbnail!
> ... and automatically unpack it to the workspace.
--
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 edited comment on JBIDE-25700 at 4/16/18 9:54 AM:
-------------------------------------------------------------------
The error that we currently experience occurs when rsync tries to change the ownership of folders
(see [comment-13560988|https://issues.jboss.org/browse/JBIDE-25700?focusedComme...]):
{code}
rsync: chgrp "/deployments/BOOT-INF/classes/org" failed: Operation not permitted (1)
{code}
When running "oc rsync" we use the --no-perms flag which prevents rsync from setting permissions but wont affect file ownership. According to the [rsync man-page|https://linux.die.net/man/1/rsync] in order to have rsync not applying ownership one needs to add --no-o and --no-g. Unfortunately oc wont allow you to provide these. I'll there file an enhancement request to oc for that: https://github.com/openshift/origin/issues/19365
was (Author: adietish):
The error that we currently experience occurs when rsync tries to change the ownership of folders
(see [comment-13560988|https://issues.jboss.org/browse/JBIDE-25700?focusedComme...]):
{code}
rsync: chgrp "/deployments/BOOT-INF/classes/org" failed: Operation not permitted (1)
{code}
When running "oc rsync" we use the --no-perms flag which prevents rsync from setting permissions but wont affect file ownership. According to the [rsync man-page|https://linux.die.net/man/1/rsync] in order to have rsync not applying ownership one needs to add --no-o and --no-g. Unfortunately oc wont allow you to provide these. I'll there file an enhancement request to oc for that.
> 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.5.x
>
> 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-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 edited comment on JBIDE-25700 at 4/16/18 9:19 AM:
-------------------------------------------------------------------
The error that we currently experience occurs when rsync tries to change the ownership of folders
(see [comment-13560988|https://issues.jboss.org/browse/JBIDE-25700?focusedComme...]):
{code}
rsync: chgrp "/deployments/BOOT-INF/classes/org" failed: Operation not permitted (1)
{code}
When running "oc rsync" we use the --no-perms flag which prevents rsync from setting permissions but wont affect file ownership. According to the [rsync man-page|https://linux.die.net/man/1/rsync] in order to have rsync not applying ownership one needs to add --no-o and --no-g. Unfortunately oc wont allow you to provide these. I'll there file an enhancement request to oc for that.
was (Author: adietish):
The error that we currently experience occurs when rsync tries to change the ownership of folders:
https://issues.jboss.org/browse/JBIDE-25700?focusedCommentId=13560988&pag...
{code}
rsync: chgrp "/deployments/BOOT-INF/classes/org" failed: Operation not permitted (1)
{code}
When running "oc rsync" we use the *--no-perms* flag which prevents rsync from setting permissions but wont affect file ownership. According to the [rsync man-page|https://linux.die.net/man/1/rsync] in order to have rsync not applying ownership one needs to add *--no-o* and *--no-g*. Unfortunately oc wont allow you to provide these. I'll there file an enhancement request to oc for that.
> 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.5.x
>
> 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-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 edited comment on JBIDE-25700 at 4/16/18 9:18 AM:
-------------------------------------------------------------------
The error that we currently experience occurs when rsync tries to change the ownership of folders:
https://issues.jboss.org/browse/JBIDE-25700?focusedCommentId=13560988&pag...
{code}
rsync: chgrp "/deployments/BOOT-INF/classes/org" failed: Operation not permitted (1)
{code}
When running "oc rsync" we use the *--no-perms* flag which prevents rsync from setting permissions but wont affect file ownership. According to the [rsync man-page|https://linux.die.net/man/1/rsync] in order to have rsync not applying ownership one needs to add *--no-o* and *--no-g*. Unfortunately oc wont allow you to provide these. I'll there file an enhancement request to oc for that.
was (Author: adietish):
The error that we currently experience occurrs when rsync tries to change the owership of folders:
{code:title=https://issues.jboss.org/browse/JBIDE-25700?focusedCommentId=13560988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13560988}
rsync: chgrp "/deployments/BOOT-INF/classes/org" failed: Operation not permitted (1)
{code}
When running "oc rsync" we use the *--no-perms* flag which prevents rsync from setting permissions but wont affect file ownership. According to the [rsync man-page|https://linux.die.net/man/1/rsync] in order to have rsync not applying ownership one needs to add *--no-o* and *--no-g*. Unfortunately oc wont allow you to provide these. I'll there file an enhancement request to oc for that.
> 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.5.x
>
> 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-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:
------------------------------------------
The error that we currently experience occurrs when rsync tries to change the owership of folders:
{code:title=https://issues.jboss.org/browse/JBIDE-25700?focusedCommentId=13560988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13560988}
rsync: chgrp "/deployments/BOOT-INF/classes/org" failed: Operation not permitted (1)
{code}
When running "oc rsync" we use the *--no-perms* flag which prevents rsync from setting permissions but wont affect file ownership. According to the [rsync man-page|https://linux.die.net/man/1/rsync] in order to have rsync not applying ownership one needs to add *--no-o* and *--no-g*. Unfortunately oc wont allow you to provide these. I'll there file an enhancement request to oc for that.
> 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.5.x
>
> 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