[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:
-----------------------------------
The linked PR creates an additional zip in the site project. The structure of the zip is as follows:
./aggregate/${project.version}/<jbds-is-repo>
./targetplatform/${project.version}/<jbds-is-tp-repo>
The root composite site includes children for ./aggregate and ./targetplatform. There are no repository references in the jbds-is-repo. The jbds-is-tp-repo is created by mirroring the jbtis tp from a url specified in the pom configuration.
The one drawback is that you cannot install directly using the zip; you need to expand it first (the relative paths don't seem to work).
When deploying to server, you should be good to simply expand the zip in the desired location for the initial site. For updates, you will have to expand all but the composite*.xml files and will have to add the new version(s) to the existing composite*.xml files on the server.
Let me know what you think of this.
> 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 Andy Goldstein (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15375?page=com.atlassian.jira.plugi... ]
Andy Goldstein commented on JBIDE-15375:
----------------------------------------
The workflow I think they've been using is:
1) Clone repository into the Git Repositories view
2) Import existing Maven project from the cloned repository (note: *not* OpenShift)
3) Work on the code locally and deploy to a local JBoss server (again, not OpenShift)
4) Eventually, create a new OpenShift app using Eclipse, and have it use the project from above instead of the template from the cartridge (force push)
When looking at the cloned repository in cygwin, the permissions appear to be 700 (rwx------). When looking at the cloned repository in the Windows "git shell", they appear to be 755 (rwxr-xr-x) I believe. So it could just be that cygwin is reporting incorrectly.
At this point we need step-by-step steps to be able to reproduce the issue 100% of the time.
> 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] (JBDS-2722) Include Kepler SR1 by default
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2722:
-----------------------------
Description:
Kepler SR1 has bugfixes - we should include it in upcoming release.
* Affects JBT TP, JBDS TP, and JBDS installer.
* Verification by comparing old TPs and installer contents to newer one, eg., using vwatch tool [1] or by scheduled job [2].
[1] https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
was:
Kepler SR1 has bugfixes - we should include it in upcoming release.
* Affects JBT TP, JBDS TP, and JBDS installer.
> Include Kepler SR1 by default
> ------------------------------
>
> Key: JBDS-2722
> URL: https://issues.jboss.org/browse/JBDS-2722
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
>
> Kepler SR1 has bugfixes - we should include it in upcoming release.
> * Affects JBT TP, JBDS TP, and JBDS installer.
> * Verification by comparing old TPs and installer contents to newer one, eg., using vwatch tool [1] or by scheduled job [2].
> [1] https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
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] (JBDS-2722) Include Kepler SR1 by default
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2722:
-----------------------------
Description:
Kepler SR1 has bugfixes - we should include it in upcoming release.
* Affects JBT TP, JBDS TP, and JBDS installer.
was:Kepler SR1 has bugfixes - we should include it in upcoming release.
> Include Kepler SR1 by default
> ------------------------------
>
> Key: JBDS-2722
> URL: https://issues.jboss.org/browse/JBDS-2722
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
>
> Kepler SR1 has bugfixes - we should include it in upcoming release.
> * Affects JBT TP, JBDS TP, and JBDS installer.
--
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