[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-158:
----------------------------------
Yes, but the TP is built *BEFORE* the rest of the aggregates, by necessity, as it's a prereq for the child projects themselves. So you can't very well build the TP and the aggregate in the same reactor, in order to produce some larger TP + aggregate zip.
I suppose you could fetch the latest TP site as a zip during the build (if in fact JBTIS' TP was being published that way, like we do for JBT), unpack it, create a zip containing that + the JBTIS aggregate site, and publish that uberzip.
In the interested of parallel dir trees, would this be better?
integration-stack/aggregate/<versions> (where ./<version> would go)
integration-stack/targetplatform/<versions> (where ./targetplatform/<version> would go)
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBIDE-15375) File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15375 at 8/27/13 10:59 AM:
--------------------------------------------------------------------
Git apparently only knows about 755 and 644 nothing else:
{quote}
(04:46:16 PM) agoldste: adietish: testing on the command line, git appears to only recognize 755 and 644. if i change the perms to/from rwx------ and rw------- it literally jumps between 755 and 644 on the server
{quote}
This was also reported in http://stackoverflow.com/questions/14557106/git-changes-my-file-permissio...
{quote}
Git supports two permission sets: 755 and 644. Nothing else. Ownership information is not stored at all.
{quote}
So it looks like that as long as we can preserve x-permissions for the owner when cloning via EGit we should be fine. Some operation in the user workflow seems to remove the x-permissions in this bug-report.
was (Author: adietish):
Git apparently only knows about 755 and 644 nothing else:
{quote}
(04:46:16 PM) agoldste: adietish: testing on the command line, git appears to only recognize 755 and 644. if i change the perms to/from rwx------ and rw------- it literally jumps between 755 and 644 on the server
{quote}
This was also reported in http://stackoverflow.com/questions/14557106/git-changes-my-file-permissio...
{quote}
Git supports two permission sets: 755 and 644. Nothing else. Ownership information is not stored at all.
{quote}
> File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-15375
> URL: https://issues.jboss.org/browse/JBIDE-15375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Environment: Windows, cygwin
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Attachments: resource-properties.png, set-x-permissions.png
>
>
> (filing on behalf of another user who is having login issues)
> When I clone a git repo (git@...:user/myapp.git) using the Eclipse plugins, the file permissions for my action_hooks are set as:
> {code}
> /cygdrive/c/Users/user/git/myapp/.openshift/action_hooks
> $ ls -l
> total 45
> -rwx------+ 1 Administrators Domain Users 265 Aug 22 14:38 build
> -rwx------+ 1 Administrators Domain Users 264 Aug 22 14:38 deploy
> -rwx------+ 1 Administrators Domain Users 186 Aug 22 14:38 post_deploy
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_start_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_stop_jbossas-7
> -rwx------+ 1 Administrators Domain Users 640 Aug 22 14:38 pre_build
> -rwx------+ 1 Administrators Domain Users 272 Aug 22 14:38 pre_build_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_start_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_stop_jbossas-7
> {code}
> When they are pushed to OpenShift, they can't be executed.
> {code}
> /var/lib/openshift/5216951d76c3b22b77000362/app-root/runtime/repo/.openshift/action_hooks/post_stop_jbossjsw-1.0: Permission denied
> remote: Failed to stop jbossjsw-1.0
> To
> ssh://5216951d76c3b22b77000362@ppon-tsujarit.qa02.shift.paypal.com/~/git/pp
> on.git/
> ! [remote rejected] master -> master (pre-receive hook declined)
> error: failed to push some refs to
> {code}
> On a different machine, when I clone using Eclipse, the file permission are set as expected:
> {code}
> -rwxr-xr-x 1 Administrators Domain Users 270 Aug 22 11:25 build
> -rwxr-xr-x 1 Administrators Domain Users 271 Aug 22 11:25 deploy
> -rwxr-xr-x 1 Administrators Domain Users 189 Aug 22 11:25 post_deploy
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_start_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_stop_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 650 Aug 22 11:25 pre_build
> -rwxr-xr-x 1 Administrators Domain Users 277 Aug 22 11:25 pre_build_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_start_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_stop_jbossas-7
> {code}
> Is it possible to set the file perms to +x on the action_hooks?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBIDE-15375) File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15375:
------------------------------------------
Git apparently only knows about 755 and 644 nothing else:
{quote}
(04:46:16 PM) agoldste: adietish: testing on the command line, git appears to only recognize 755 and 644. if i change the perms to/from rwx------ and rw------- it literally jumps between 755 and 644 on the server
{quote}
This was also reported in http://stackoverflow.com/questions/14557106/git-changes-my-file-permissio...
{quote}
Git supports two permission sets: 755 and 644. Nothing else. Ownership information is not stored at all.
{quote}
> File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-15375
> URL: https://issues.jboss.org/browse/JBIDE-15375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Environment: Windows, cygwin
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Attachments: resource-properties.png, set-x-permissions.png
>
>
> (filing on behalf of another user who is having login issues)
> When I clone a git repo (git@...:user/myapp.git) using the Eclipse plugins, the file permissions for my action_hooks are set as:
> {code}
> /cygdrive/c/Users/user/git/myapp/.openshift/action_hooks
> $ ls -l
> total 45
> -rwx------+ 1 Administrators Domain Users 265 Aug 22 14:38 build
> -rwx------+ 1 Administrators Domain Users 264 Aug 22 14:38 deploy
> -rwx------+ 1 Administrators Domain Users 186 Aug 22 14:38 post_deploy
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_start_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_stop_jbossas-7
> -rwx------+ 1 Administrators Domain Users 640 Aug 22 14:38 pre_build
> -rwx------+ 1 Administrators Domain Users 272 Aug 22 14:38 pre_build_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_start_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_stop_jbossas-7
> {code}
> When they are pushed to OpenShift, they can't be executed.
> {code}
> /var/lib/openshift/5216951d76c3b22b77000362/app-root/runtime/repo/.openshift/action_hooks/post_stop_jbossjsw-1.0: Permission denied
> remote: Failed to stop jbossjsw-1.0
> To
> ssh://5216951d76c3b22b77000362@ppon-tsujarit.qa02.shift.paypal.com/~/git/pp
> on.git/
> ! [remote rejected] master -> master (pre-receive hook declined)
> error: failed to push some refs to
> {code}
> On a different machine, when I clone using Eclipse, the file permission are set as expected:
> {code}
> -rwxr-xr-x 1 Administrators Domain Users 270 Aug 22 11:25 build
> -rwxr-xr-x 1 Administrators Domain Users 271 Aug 22 11:25 deploy
> -rwxr-xr-x 1 Administrators Domain Users 189 Aug 22 11:25 post_deploy
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_start_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_stop_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 650 Aug 22 11:25 pre_build
> -rwxr-xr-x 1 Administrators Domain Users 277 Aug 22 11:25 pre_build_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_start_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_stop_jbossas-7
> {code}
> Is it possible to set the file perms to +x on the action_hooks?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Rob Cernich commented on JBTIS-158:
-----------------------------------
Actually, a better structure might be:
compositeContent.xml (one child, ./<version>)
compositeArtifacts.xml (one child, ./<version>)
<version>/compositeContent.xml
<version>/compositeArtifacts.xml
<version>/<version>-jbds-is
targetplatform/compositeContent.xml (one child, ./<version>-jbds-is-tp)
targetplatform/compositeArtifacts.xml (one child, ./<version>-jbds-is-tp)
targetplatform/<version>-jbds-is-tp
That way you still have a self contained zip, but, if you want, when you deploy, you can separate things out.
That would work nicely with a site structure like:
7.0/integration-stack/<versions> (where ./<version> would go)
7.0/integration-stack/targetplatform/<versions> (where ./targetplatform/<version> would go
Anyway, you pick the root structure you want, but I think this bridges the gap. Obviously, you wouldn't move across the composite*.xml files in ./ or ./targetplatform.
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBIDE-15375) File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15375:
------------------------------------------
So apparently execute rights for the owner are absolutely sufficient.
{quote}
(04:41:17 PM) adietish: agoldste: yes, but owner-x is enough, right?
(04:41:37 PM) agoldste: adietish: yes
{quote}
This is good news in the first instance because there's an issue in EGit where it would NOT replicate the group permissions correctly: https://bugs.eclipse.org/bugs/show_bug.cgi?id=366366
{quote}
If I clone my Git respository using the git command line, one of the files has the execute bit set for everyone. That's what I expect.
If I clone my Git respository using Eclipse IDE (EGit), that file has the execute bit set for the owner only. That's wrong.
{quote}
> File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-15375
> URL: https://issues.jboss.org/browse/JBIDE-15375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Environment: Windows, cygwin
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Attachments: resource-properties.png, set-x-permissions.png
>
>
> (filing on behalf of another user who is having login issues)
> When I clone a git repo (git@...:user/myapp.git) using the Eclipse plugins, the file permissions for my action_hooks are set as:
> {code}
> /cygdrive/c/Users/user/git/myapp/.openshift/action_hooks
> $ ls -l
> total 45
> -rwx------+ 1 Administrators Domain Users 265 Aug 22 14:38 build
> -rwx------+ 1 Administrators Domain Users 264 Aug 22 14:38 deploy
> -rwx------+ 1 Administrators Domain Users 186 Aug 22 14:38 post_deploy
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_start_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_stop_jbossas-7
> -rwx------+ 1 Administrators Domain Users 640 Aug 22 14:38 pre_build
> -rwx------+ 1 Administrators Domain Users 272 Aug 22 14:38 pre_build_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_start_jbossas-7
> -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_stop_jbossas-7
> {code}
> When they are pushed to OpenShift, they can't be executed.
> {code}
> /var/lib/openshift/5216951d76c3b22b77000362/app-root/runtime/repo/.openshift/action_hooks/post_stop_jbossjsw-1.0: Permission denied
> remote: Failed to stop jbossjsw-1.0
> To
> ssh://5216951d76c3b22b77000362@ppon-tsujarit.qa02.shift.paypal.com/~/git/pp
> on.git/
> ! [remote rejected] master -> master (pre-receive hook declined)
> error: failed to push some refs to
> {code}
> On a different machine, when I clone using Eclipse, the file permission are set as expected:
> {code}
> -rwxr-xr-x 1 Administrators Domain Users 270 Aug 22 11:25 build
> -rwxr-xr-x 1 Administrators Domain Users 271 Aug 22 11:25 deploy
> -rwxr-xr-x 1 Administrators Domain Users 189 Aug 22 11:25 post_deploy
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_start_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_stop_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 650 Aug 22 11:25 pre_build
> -rwxr-xr-x 1 Administrators Domain Users 277 Aug 22 11:25 pre_build_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_start_jbossas-7
> -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_stop_jbossas-7
> {code}
> Is it possible to set the file perms to +x on the action_hooks?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months