Re: [skalli-dev] Assessing Skalli for the requirements of the codecentric AG
some time ago a link to a compiled version of Skalli was posted on this mailing list (I believe by Simon). Since it included Jetty (or similar, not sure anymore), I tried it and was happy to see that it was easy to get started with it.
Unfortunately, the project is missing documentation and seems to be lacking mailing list activity. Given the limited time for my thesis, I had to discard the idea of extending Skalli and instead went with a Jenkins plug-in. With information for new contributors (or developers in general), e.g., design overview, I probably would have chosen Skalli.
As far as the existing functionality is concerned: being able to search and look up projects was not required and I therefore did not really try it out (except for clicking around).
On Thu, May 10, 2012 at 3:49 PM, Ochmann, Michael <michael.ochmann@xxxxxxx>
Thanks for the links! Especially the REST API looks quite promising.
I would also be interested to learn a bit more about what you liked or disliked about Skalli. It’s really high time for a first release of Skalli, and any input concerning missing features would be greatly appreciated.
Thanks and regards,
From: skalli-dev-bounces@xxxxxxxxxxx [mailto:skalli-dev-bounces@xxxxxxxxxxx] On Behalf Of Ben Ripkens
Sent: Montag, 7. Mai 2012 10:39
To: Skalli project developer mailing list
Subject: Re: [skalli-dev] Assessing Skalli for the requirements of the codecentric AG
several months ago I was evaluating Skalli for the codecentric AG as part of my thesis. At that time, I was thinking about using Skalli to improve the project bootstrap process, i.e., automatically configure server-side CASE tools like version control, issue trackers, continuous integration and source code generation. While I really liked where the Skalli project was going, the limited amount of time did not permit contributions. Nevertheless, I wanted to inform you about my findings. Maybe you can use it for the further evolution of Skalli.
Simon pointed out that you are struggling with JIRA configuration: I found that JIRA provides a SOAP and REST web service [1, 2]. For my use case, I had to use both to fulfil the requirements. While doing this I created a component that you may be able to use directly (Apache license) or as a starting point for Skalli .
To get an overview, you can take a look at the JiraClient (combines SOAP and REST interfaces) integration test .
On Tue, Nov 8, 2011 at 2:10 PM, Simon Kaufmann <simon.kfm@xxxxxxxxxxxxxx> wrote:
Great to hear you're interested in the Skalli project. Skalli indeed already covers the most important use-case with Git/Gerrit, i.e. setting up a new project. For that, there also is a group in Gerrit created, that will have the Project committers assigned initially. However, what we currently still missing is an update/sync of these groups of later on the project members change. This requires some extension of the Gerrit API, that have not been implemented yet.
With Jira, the API looks worse. There we are struggling with the project creation, still looking for a way to realize that.
For Skalli, we only recently got all our IP related stuff approved at Eclipse, so we now work on getting the build up and running and providing some "ready to use" download. While it's not available yet, there is a little tweaking required in order to run it from the IDE. You find the necessary steps in our contributor guide: http://wiki.eclipse.org/Skalli/Contributor_Guide. Also, we are happy to help you out anytime and get you up to speed - don't hesitate to ask in this mailing list or contact any of us directly.
Talking about contributions: As it's still a young project, there of course is not yet everything covered. We are happy of course to accept any contribution of stuff you think is missing.
2011/11/6 Ben Ripkens <bripkens.dev@xxxxxxxxxxxxxx>
my name is Ben Ripkens and I'm currently looking into the Skalli project as part of my bachelor thesis (actually preliminary research). I'll be writing my bachelor thesis with support of the codecentric AG which is interested in tool support for automatic setup and configuration of software development environments.
I have been in contact with Jochen Hiller from Deutsche Telekom AG who pointed me towards the Skalli project. So far it seems that Skalli supports some of the necessary functionality for the codecentric AG. I was hoping you could help me answer some of my questions regarding the Skalli project so that I can assess whether it would be a proper choice for the codecentric AG.
Jochen Hiller presented Git, Gerrit and Jenkins support during his talk on the "Technology meets Talent" day 2011 in Darmstadt (DE). What I didn't see though was in how far Skalli is able to control and configure these applications. For instance, when you create a new project in Skalli, does it also create a new Git repository and configure user access rights?
Does Skalli support JIRA and/or Confluence in any way? It would be nice if it could create a new project in JIRA and configure the users which require access to it.
I would greatly appreciate any help in assessing the Skalli project for the codecentric AG .
skalli-dev mailing list
skalli-dev mailing list
skalli-dev mailing list