On 10/1/15, 4:40 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Well I want SNAPSHOTS to be published every day ... in order to do that I >need to setup a Jenkins Job on builds.apache.org ... or someone else >configures his private machine to do that manually using his credentials. I expect to have my private machine up and building today, but I’m not sure what you exactly you need from these machines. Just jars and swcs or are you trying to create full source release packages? > >We need more than 3-4 people testing this. In order to get them we need >to make it easy for them to do so. There's no use in writing READMEs with: > >1. First you have to download 10 different thing >2. Then you need to Set 20 Environment Variables >3. Then Run task A ... this will fail, but just ignore >4. After that run task Y on project B ... >5. Now you can run Task A again ... this time it will succeed :-) > >Like this I predict the number of people will not grow as fast as it >simply has to. That's why I think we should concentrate a little more on >making the build easier. I tried. The ‘ant all’ in flex-asjs eliminates many of the downloads, repo fetches and environment variables because it assumes where the other repos will be and what their folder names are. I asked folks to try it out and provide feedback on it. I also provided a way so the ant target in an installed FlexJS SDK will pull everything and build it, and do everything in your list. But no, I have not tried to make it easier for Jenkins builds to work they way they are currently set up on my VM or builds.a.o. I just don’t see that as our target customer’s needs. It might be more interesting for you to create a whole new job that runs the flex-asjs ‘ant all’ and see if you can work with its results. Again, I don’t know exactly what you are trying to do, so it is difficult to know how I can help. -Alex
