incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Van Den Heuvel <andy.vandenheu...@gmail.com>
Subject Re: Looking for a Champion
Date Thu, 06 Jun 2013 06:53:28 GMT
Jenkins is used to build software projects. It's a continuous integration
server.
Tashlin will be more generic, used to build any set of tasks. Also business
processes are possible.

Example: Let's say I want a job to do a HTTP GET call every 5 minutes and
show the results.
In Jenkins, I'll probably create a free-style project, but it asks me for a
SCM which makes no sense for this scenario.
I think a lot of people today hack around the fact that Jenkins is a
continuous integration server, because it is easy to use and to setup
scheduling tasks.

If we make a generic platform we can create a one stop shop for all
schedeling tasks.



On Thu, Jun 6, 2013 at 8:17 AM, Alexei Fedotov <alexei.fedotov@gmail.com>wrote:

> There is no requirement to be different to join, I just wonder
> 06.06.2013 9:36 пользователь "Andy Van Den Heuvel" <
> andy.vandenheuvel@gmail.com> написал:
>
> > My apologies for causing confusion. Hopefully this will clear things up:
> >
> > Abstract
> > Tashlin is a lightweight application for composing and executing batch
> jobs
> > via a web user interface.
> >
> > Brief Description
> > Tashlin allows you to create and run batch jobs in a standalone
> application
> > for use cases where you want to automate a set of tasks. It will provide
> a
> > simple workflow
> > which allows users to set up automation up in minutes with provided
> plugins
> > for common functionality. This differs from tools like Jenkins in that it
> > can be used in a
> > more generic way. Continuous integration is just one of the possibities.
> > (E.g. integration with SCM or build automation is not a requirement).
> > Other use cases are Monitoring, Backups, General Process Automation...
> >
> > The basic idea runs around these concepts:
> > Recipe: Users will compose recipes. This is a template that will be
> > executed by a Job
> > Flow: A recipe contains 2 flows: a buildflow (= will stop when an
> exception
> > is thrown) and a feedbackflow (will run, even when exceptions are thrown
> to
> > notify interested parties)
> > Step: A flow will execute a set of steps. Step logic will be provided
> > through the use of plugins. Step configuration can be configured.
> > Job: A job will be executed on a specific trigger. (on-demand,
> > cron-based...) and can contain parameters.
> > Parameter: A parameter is a value that can be used in a recipe so that
> > recipes can be reused
> >
> > Because it has come up on this thread, I'll give continuous integration
> as
> > an example.
> > Let's say I want to setup continuous integration for my maven project.
> > I create a recipe with 2 build steps ('CheckOut From Subversion', 'Build
> > With Maven') and 1 feedback step ('Email results').
> > I create a job using this recipe and providing a parameter 'Goals' with
> > value 'clean install'
> > The 'Build With Maven' step will have ${GOALS} as a placeholder, the
> value
> > will be provided when executing the recipe (via EL).
> > Now I can create a 2nd job providing a parameter 'Goals' with value
> 'clean
> > test -Dtest=*IntegrationTests' etc.
> >
> > Keep in mind that this is just a very basic example. The goal of the
> > project is to bridge the gap for people who simply want to automate stuff
> > and see the results of it.
> > I think that a lot of people could benefit from this.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Jun 5, 2013 at 4:36 PM, Mohammad Nour El-Din <
> > nour.mohammad@gmail.com> wrote:
> >
> > > @Ate Yes I noticed but not enough information here in the thread to
> make
> > > anyone think to help or not and I would suggest for Andy just to
> prepare
> > an
> > > abstract and brief description and share it here to see if someone is
> > > interested rather than keep coming and going with question just to know
> > > what the project is about rather than discussing whom will help and how
> > >
> > > @Andy: Would you please paste (or link) here an abstract and a brief
> > > description what the project is about ? I would say have a look at [1]
> > make
> > > a similar one fill it in with as much as you can share that here to see
> > if
> > > someone is interested to be a Champion and take it from there
> > >
> > > [1] https://wiki.apache.org/incubator/StratosProposal
> > >
> > >
> > > On Wed, Jun 5, 2013 at 4:29 PM, Ate Douma <ate@douma.nu> wrote:
> > >
> > > > On 06/05/2013 04:12 PM, Mohammad Nour El-Din wrote:
> > > >
> > > >> +1 @Marcel
> > > >>
> > > >> Any links for the draft proposal so people can assess if they can
> help
> > > or
> > > >> not ?
> > > >>
> > > >
> > > > He is asking for help (Champion) to create such a draft :)
> > > >
> > > >
> > > >
> > > >>
> > > >> On Wed, Jun 5, 2013 at 4:07 PM, Marcel Offermans <
> > > >> marcel.offermans@luminis.nl> wrote:
> > > >>
> > > >>  I would never search for a generic job scheduling application in
> the
> > > >>> Wicket project. I still don't know exactly what this new project
is
> > > >>> about,
> > > >>> but the fact that it happens to use Wicket in itself is not enough
> to
> > > >>> make
> > > >>> it a Wicket subproject if you ask me.
> > > >>>
> > > >>> Greetings, Marcel
> > > >>>
> > > >>> On Jun 5, 2013, at 16:01 PM, Alexei Fedotov <
> > alexei.fedotov@gmail.com>
> > > >>> wrote:
> > > >>>
> > > >>>  Could it be a part of Apache Wicket?
> > > >>>> --
> > > >>>> With best regards / с наилучшими пожеланиями,
> > > >>>> Alexei Fedotov / Алексей Федотов,
> > > >>>> http://dataved.ru/
> > > >>>> +7 916 562 8095
> > > >>>>
> > > >>>>
> > > >>>> On Wed, Jun 5, 2013 at 5:33 PM, Andy Van Den Heuvel
> > > >>>> <andy.vandenheuvel@gmail.com> wrote:
> > > >>>>
> > > >>>>> Hey Alexei,
> > > >>>>>
> > > >>>>> Yes, it does.
> > > >>>>>
> > > >>>>> On Wed, Jun 5, 2013 at 3:20 PM, Alexei Fedotov <
> > > >>>>>
> > > >>>> alexei.fedotov@gmail.com>**wrote:
> > > >>>
> > > >>>>
> > > >>>>>  Andy,
> > > >>>>>> It uses Apache Wicket, doesn't it?
> > > >>>>>> --
> > > >>>>>> With best regards / с наилучшими пожеланиями,
> > > >>>>>> Alexei Fedotov / Алексей Федотов,
> > > >>>>>> http://dataved.ru/
> > > >>>>>> +7 916 562 8095
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On Wed, Jun 5, 2013 at 4:42 PM, Andy Van Den Heuvel
> > > >>>>>> <andy.vandenheuvel@gmail.com> wrote:
> > > >>>>>>
> > > >>>>>>> Jenkins is a continuous integration server, it
provides
> > integration
> > > >>>>>>>
> > > >>>>>> with
> > > >>>
> > > >>>> SCM, Build Automation, Testing...
> > > >>>>>>> This proposal is for a multi-purpose tool, providing
support
> for
> > > >>>>>>> Monitoring, Backup's,Process Automation, (also
Continuous
> > > Integration
> > > >>>>>>> though)
> > > >>>>>>> The architecture is very different.
> > > >>>>>>>
> > > >>>>>>> The idea behind this has come up of using Hudson/Jenkins
for
> > > several
> > > >>>>>>>
> > > >>>>>> years.
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> On Wed, Jun 5, 2013 at 2:25 PM, Simon Lucy <
> simon.lucy@bbc.co.uk
> > >
> > > >>>>>>>
> > > >>>>>> wrote:
> > > >>>
> > > >>>>
> > > >>>>>>>  Andy Van Den Heuvel wrote:
> > > >>>>>>>>
> > > >>>>>>>> I'm looking for a Champion to help me setup
a proposal.
> > > >>>>>>>>
> > > >>>>>>>>> The project is a pluggable all-round job
scheduling
> > application.
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> Not to be a killjoy but how is it different
to Hudson/Jenkins?
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> S
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>  Can somebody help me?
> > > >>>>>>>>>
> > > >>>>>>>>> Thanks for your consideration.
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>
>  ------------------------------****----------------------------**
> > > >>> --**---------
> > > >>>
> > > >>>> To unsubscribe, e-mail: general-unsubscribe@incubator.****
> > apache.org<
> > > >>>>>>>>
> > > >>>>>>> general-unsubscribe@incubator.**apache.org<
> > > general-unsubscribe@incubator.apache.org>
> > > >>>>>> >
> > > >>>>>>
> > > >>>>>>> For additional commands, e-mail: general-help@incubator.apache.
> > > >>>>>>>>
> > > >>>>>>> **org<
> > > >>>
> > > >>>> general-help@incubator.apache.**org <
> > > general-help@incubator.apache.org>
> > > >>>>>> >
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>> ------------------------------**------------------------------**
> > > >>>>>> ---------
> > > >>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.**
> > apache.org<
> > > general-unsubscribe@incubator.apache.org>
> > > >>>>>> For additional commands, e-mail: general-help@incubator.apache.
> > > **org<general-help@incubator.apache.org>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>> ------------------------------**------------------------------**
> > > >>>> ---------
> > > >>>> To unsubscribe, e-mail: general-unsubscribe@incubator.**
> apache.org<
> > > general-unsubscribe@incubator.apache.org>
> > > >>>> For additional commands, e-mail: general-help@incubator.apache.
> > **org<
> > > general-help@incubator.apache.org>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>> ------------------------------**------------------------------**
> > > >>> ---------
> > > >>> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org
> <
> > > general-unsubscribe@incubator.apache.org>
> > > >>> For additional commands, e-mail: general-help@incubator.apache.
> > **org<
> > > general-help@incubator.apache.org>
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > ------------------------------**------------------------------**---------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<
> > > general-unsubscribe@incubator.apache.org>
> > > > For additional commands, e-mail: general-help@incubator.apache.
> **org<
> > > general-help@incubator.apache.org>
> > > >
> > > >
> > >
> > >
> > > --
> > > Thanks
> > > - Mohammad Nour
> > > ----
> > > "Life is like riding a bicycle. To keep your balance you must keep
> > moving"
> > > - Albert Einstein
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message