Yuriy Tymchuk wrote:
To summarise I’d like to propose adding startup scripts manager to pharo 
luncher. What’s more, usually we are working on our one “project”. And as it’s 
a good practice to start from a fresh image, we either have to load a 
configuration of it into fresh images or download pre-built image from CI. And 
we are too bound to CI because of image building. What I see as next step in 
the development workflow, is to say to the launcher: I want this Project is 
this Image (3.0, 4.0) with this prefs (experiences). The launcher builds the 
thing and you can work with it.

In general I like your idea a lot, but let’s have a little discussion to hear 
what the others have to say.

Uko

That would be a REALLY cool. Something like like a CI builder for home?
Doubly cool if the framework could be bent to do something like the following scenarios...

1. A menu item "Test A Slice" that asks for a case number, creates a new image from the latest "Local" template, named like...
     "Case12345-Build40230 The Case Description"
then on that image runs a script that
   a. Opens Inbox repository
   b. Adds slice number to filter
   c. For latest slice, clicks <Changes>. "as a reference after merge"
   d. For latest slice, clicks <Merge>, then waits for user interaction.

2. Allow user to define a test script to be run across multiple images, in a binary search pattern, to help isolate the first occurrence of a bug.

cheers -ben



On 27 Oct 2014, at 13:13, stepharo <[email protected]> wrote:

Dear experience makers (Martin, yuriy, tommaso, roberto and others,)

you would like to have many people doing your experience.... I know you would 
love that.
Here is my suggestion: ease the use of new images.
Each time I want to load the projects I'm hacking and I do not have a jenkins 
for it, it is painful (setting up
the repos.... loading....). So I do not change often images and I'm reluctant 
to load new stuff (like your experiments)


   - build a simple little tool that could be integrated in pharo and would do 
the following:
           - let the user (un)/select some packages or configurations
           - generate a script to reload these configurations really easily

This way I can load my project and then you provide a script for your 
experience.
and after I can reload my project with your material for experience in my new 
image.
Right now I do not like to hack the preference file because I have images where 
I do not want any interference

So is my proposal clear?

Stef







Reply via email to