[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ]
Lukáš Valach commented on JBIDE-23489:
--------------------------------------
I have discused this problem with [~vkadlcik], he has test working against RPM. He doesn't use Tycho.
This way is less confortable, but I just letting you know about this option.
There is what he does:
# White SWTBot or Red Deer test and upload it to update site
# Install Devstudio RPM
# Install test as plugin
eclipse \
-application org.eclipse.equinox.p2.director \
-repository file://$UPDATE_SITE \
-i $FEATURE_WITH_OUR_PLUGIN
(Plugin will be installed in $HOME/.eclipse/)
# Start test
eclipse \
-application org.eclipse.swtbot.eclipse.junit.headless.swtbottestapplication \
-testPluginName $OUR_PLUGIN_ID \
-className $OUR_TEST_CLASS
> Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23489
> URL: https://issues.jboss.org/browse/JBIDE-23489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.2.AM3
> Reporter: Pavol Srna
> Fix For: 4.4.x
>
> Attachments: FreeMarket_rhscl_enabled.log, Freemarker_testRuntime_p2Installed.log
>
>
> We need to find a way how to run automated tests agains devstudio rpm.
> I've tried the following paths:
> 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
> 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-24112:
---------------------------------------------
normal users cannot assign issues, not on create or when being edited. So if you want that you need to find ways to get jiralint permissions across the projects.
As listed above I would please advise to use a different account for that. i.e. since these scripts would be run as part of manual steps (i assume) then just use your own accounts for that specific run.
Will also make it more explicit rather than some anonymous bot.
> document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-24112
> URL: https://issues.jboss.org/browse/JBIDE-24112
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
> Attachments: jiralint.user.no.perms.to.assign.txt
>
>
> Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24112:
------------------------------------
[~maxandersen] The idea is that is that N&N JIRAs then needs manually and boring setting to assign users as people tend to forget processing JIRAs. [~nickboldt] Can't we have the user assigned when creating the JIRA ?
> document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-24112
> URL: https://issues.jboss.org/browse/JBIDE-24112
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
> Attachments: jiralint.user.no.perms.to.assign.txt
>
>
> Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years