On Wed, Jul 23, 2014 at 2:42 PM, John Chilton wrote:
> Problem with automation is I could create dozens of templates over the
> next several years and consume less time in aggregate than it would
> take me to automate this. Nonetheless, there is a documentation
> component here that is important s
Problem with automation is I could create dozens of templates over the
next several years and consume less time in aggregate than it would
take me to automate this. Nonetheless, there is a documentation
component here that is important so I did enough to document - if
someone wants to automate from
On Tue, Jul 22, 2014 at 7:41 PM, Eric Rasche wrote:
> John,
>
> How are those generated? Would you be amenable to scripting that
> portion and running it once a month? (...say in a cron job, with a
> passwordless ssh key so you never have to touch it again)
>
> Cheers,
> Eric
How to generate it w
John,
How are those generated? Would you be amenable to scripting that portion and
running it once a month? (...say in a cron job, with a passwordless ssh key so
you never have to touch it again)
Cheers,
Eric
22.07.2014, 19:08, "John Chilton" :
> On Tue, Jul 22, 2014 at 7:51 AM, Peter Cock wr
On Tue, Jul 22, 2014 at 7:51 AM, Peter Cock wrote:
> On Tue, Jul 22, 2014 at 1:15 PM, Eric Rasche wrote:
>> Hi Peter,
>>
>> On July 22, 2014 3:15:41 AM CDT, Peter Cock
>> wrote:
>>>
>>>Given how close you can get now for minimal effort,
>>>this seem unnecessary.
>>>
>>>http://blastedbio.blogspo
For my part:Script/infra to generate brancheshttps://cpt.tamu.edu/gitlab/rasche.eric/docker-branch-generator/tree/masterGenerated branches:https://cpt.tamu.edu/gitlab/rasche.eric/generated-docker-branches/branches/recentNeed to patch up a couple issues, but I'm pretty much done on my end. Whenever
That's awesome Björn and Eric. And, I'll also have to go through your
Travis CI document Peter. It looks really cool.
Aaron
On Tue, Jul 22, 2014 at 9:35 AM, Björn Grüning
wrote:
> :) great I like it!
> Will do it shortly!
>
> Am 22.07.2014 15:36, schrieb Eric Rasche:
>
> Hi Björn,
>>
>> 22.
:) great I like it!
Will do it shortly!
Am 22.07.2014 15:36, schrieb Eric Rasche:
Hi Björn,
22.07.2014, 14:26, "Björn Grüning" :
Hi Eric,
That sounds like a pretty good idea. If there was a pre-built image
available for whatever release I wanted to test against I could just
cache
Hi Björn,
22.07.2014, 14:26, "Björn Grüning" :
> Hi Eric,
That sounds like a pretty good idea. If there was a pre-built image
available for whatever release I wanted to test against I could just
>>> cache
it and (hopefully) get my tests running a bit faster. I'm not sure
Hi Eric,
That sounds like a pretty good idea. If there was a pre-built image
available for whatever release I wanted to test against I could just
cache
it and (hopefully) get my tests running a bit faster. I'm not sure
if
anyone else is already doing this?
Also, I remember there being men
On Tue, Jul 22, 2014 at 1:15 PM, Eric Rasche wrote:
> Hi Peter,
>
> On July 22, 2014 3:15:41 AM CDT, Peter Cock wrote:
>>
>>Given how close you can get now for minimal effort,
>>this seem unnecessary.
>>
>>http://blastedbio.blogspot.co.uk/2013/09/using-travis-ci-for-testing-galaxy-tools.html
>>
>
Hi Peter,
On July 22, 2014 3:15:41 AM CDT, Peter Cock wrote:
>On Mon, Jul 21, 2014 at 6:51 PM, Eric Rasche
>wrote:
>> Currently the checkout options consist of hg clones, and archives
>that
>> mercurial produces.
>>
>> Having pulled or cloned galaxy a few times lately, I'm wondering if
>anyone
>
Hi Björn,
On July 22, 2014 3:17:38 AM CDT, "Björn Grüning"
wrote:
>Hi Aaron and Eric,
>
>Am 21.07.2014 22:58, schrieb Aaron Petkau:
>> Hello Eric,
>>
>> That sounds like a pretty good idea. If there was a pre-built image
>> available for whatever release I wanted to test against I could just
>c
Hi Aaron and Eric,
Am 21.07.2014 22:58, schrieb Aaron Petkau:
Hello Eric,
That sounds like a pretty good idea. If there was a pre-built image
available for whatever release I wanted to test against I could just cache
it and (hopefully) get my tests running a bit faster. I'm not sure if
anyone
On Mon, Jul 21, 2014 at 6:51 PM, Eric Rasche wrote:
> Currently the checkout options consist of hg clones, and archives that
> mercurial produces.
>
> Having pulled or cloned galaxy a few times lately, I'm wondering if anyone
> would have a use for a once-run galaxy instance in an archive? I.e., I
Hello Eric,
That sounds like a pretty good idea. If there was a pre-built image
available for whatever release I wanted to test against I could just cache
it and (hopefully) get my tests running a bit faster. I'm not sure if
anyone else is already doing this?
Also, I remember there being mentio
Hi Aaron,
Yeah, absolutely understandable. I want my tools tested early and often.
I abuse my CI server for everything, especially for building and
packaging software. In this case I was imagining that I might have it
produce an archive on every tagged release, as well as producing a
"daily" arch
Hello Eric,
Your right about that, downloading the archive, installing all the eggs,
and then updating the database takes a bit of time (especially if you're
like me and like re-running tests on nearly every change you make :P). I
think it would be cool to have a pre-package Galaxy for integratio
Hi Aaron,Good points, I was considering using galaxy bootstrap. This is mostly for the CI folk who want to download an archive, unpack it, and be ready to install/test their tools. The hg clone and egg/db steps seem like unnecessary overhead for this specific use case.Cheers,Eric
__
Hello Eric,
I think that's a great idea. You may be interested in checking out Björn's
Galaxy Docker image
https://github.com/bgruening/docker-recipes/tree/master/galaxy which is
very similar to what you're describing. A few other testing frameworks,
like Galaxy bootstrap https://github.com/jmch
Currently the checkout options consist of hg clones, and archives that mercurial produces. Having pulled or cloned galaxy a few times lately, I'm wondering if anyone would have a use for a once-run galaxy instance in an archive? I.e., I'd clone, run once to grab eggs and do the db migration, then
21 matches
Mail list logo
