[JBoss JIRA] (JBIDE-11155) consider caching svn sources outside Jenkins workspaces
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-11155:
----------------------------------
Summary: consider caching svn sources outside Jenkins workspaces
Key: JBIDE-11155
URL: https://issues.jboss.org/browse/JBIDE-11155
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta2
>From JBIDE-10974:
> 9. Every change in build component triggers full rebuild for all components
9. This could be fixed by instead of watching the /build folder in SVN for changes, we simply fetch it using `svn co` or `svn up` as a prelim step in the job.
Perhaps taking this a step further, we could fetch the whole SVN tree and store it outside the workspaces so that jobs would simply re-use local shared space instead of clean-fetching everything every time they run on a new slave.
This would of course make jobs "more tied to infrastructure" and "harder to build the same way offline" but that's the price you pay for optimizing for speed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-10197) Deployment assembly missbehaves - workaround with fileset
by Dirk Dollar (Created) (JIRA)
Deployment assembly missbehaves - workaround with fileset
---------------------------------------------------------
Key: JBIDE-10197
URL: https://issues.jboss.org/browse/JBIDE-10197
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Eclipse helios 3.6.2
Reporter: Dirk Dollar
Assignee: Rob Stryker
Priority: Minor
This is my first bugreport... if I'm doing something wrong or chose the wrong component (something) - please be forgiving :-)
so I had a couple days to figure this one out - the deployment assembly is misbehaving similarly (but differnt) to older versions when it was used under a different name (J2EE module dependencies i think).
So when I add a folder e.g. WebContent and want it to deploy to / it will not work or more accurately - under certain circumstances it will stop working. E.g. I think after adding some additional libraries to deploy to webcontent/lib. I suspect the problem is that it gets deleted before deploying. The workaround for me was to use a fileset of the <projectname>/WebContent folder and to point it to an empty deploy path - and to scream in rage at everyone who dared to touch any settings in there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-12363) Commit new astools test suite and get it working in build
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12363:
-----------------------------------
Summary: Commit new astools test suite and get it working in build
Key: JBIDE-12363
URL: https://issues.jboss.org/browse/JBIDE-12363
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.4.0.M1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.4.0.M1
A new test sutie is under creation. Ensure it starts running in hudson and is committed to svn. Much of this plugin will eventually replace the as.test plugin, and eventually as.test will be phased out or stripped into bare minimum contents.
Initially the two plugins are independent, which creates some duplication. The new test suite should be a bit of an integration suite, testing astools and all integrations, such as with classpath, archives, zipped publishing, etc etc.
The new test suite should automatically fail tests (or run them as-is) if a new server type is added, to remind the module owner (me) to implement the tests or fix situations for the new server type.
This will require the build system to download ALL versions of AS that are relevent, including EAP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months