[JBoss JIRA] (JBIDE-12333) Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12333?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12333:
-------------------------------------
Priority: Minor (was: Major)
> Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-12333
> URL: https://issues.jboss.org/browse/JBIDE-12333
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: LATER
>
> Attachments: enable-jenkins-build-2.png, enable-jenkins-build.png
>
>
> If you want to switch to a jenkins based build you'd currently have to add the jenkins-client to your application. The OpenShift WebUI does this in a far more explicit and user friendly way:
> It explicilty features a button that "enable jenkins build"
> !enable-jenkins-build.png!
> !enable-jenkins-build-2.png!
> We should provide something equivalent.
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-12333) Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12333?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12333:
-------------------------------------
Fix Version/s: LATER
(was: 4.0.x)
> Explicitly provide "Enable jenkins build" (instead of adding jenkins-client cartridge)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-12333
> URL: https://issues.jboss.org/browse/JBIDE-12333
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: LATER
>
> Attachments: enable-jenkins-build-2.png, enable-jenkins-build.png
>
>
> If you want to switch to a jenkins based build you'd currently have to add the jenkins-client to your application. The OpenShift WebUI does this in a far more explicit and user friendly way:
> It explicilty features a button that "enable jenkins build"
> !enable-jenkins-build.png!
> !enable-jenkins-build-2.png!
> We should provide something equivalent.
--
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
13 years, 6 months
[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13348:
-------------------------------------
My method of testing this was as follows:
1) download indigo
2) update and install soa tools (which brings in jbosstools) from update site: http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling
3) run runtime workbench
4) create bpel project + server
5) publish, verify works (should work)
6) close runtime workbench
7) import 3.3.x source tree for org.jboss.ide.eclipse.as.core
8) run runtime workbench
9) publish, verify works (should work)
10) close runtime workbench
11) comment out newly-added method
12) run runtime workbench
13) publish, verify works (should work) FAIL
So, it seems that adding this method back does 100% fix the issue, at least as can be seen via runtime workbench without using a true update site.
All that's left now is to update the versions in 3.3.x for astools since the code has changed
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBIDE-13348
> URL: https://issues.jboss.org/browse/JBIDE-13348
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, SOA Tooling
> Affects Versions: 3.3.2
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Priority: Blocker
>
> After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server.
> See JBDS-2437
--
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
13 years, 6 months