Anders, you could spin up a Jenkins at CloudBees. That way at least the build slaves will be fedora based, and you can be up and running in <2 minutes (use a freestyle project not maven project)
On 21 August 2012 14:05, Anders Hammar <[email protected]> wrote: > > The trouble with rpm is that rpm is an application that largely works on > machines with a Redhat heritage, like RHEL, Fedora, etc. I also use MacOSX > as a development > > environment, however I just don't build the rpms on that platform. If > the rpm plugin can be made to work on MacOSX it would be really useful, but > it shouldn't stop an effort > > to get it working on Redhat based systems. > > Right, as I got the rpm tool installed on my Mac I was hoping it to > work. And the think is that lot does work, but there are issues with > target architecture. I kind of think that most of these are due to IT > (and maybe even the plugin code) taking different environments in > considerations. Very bad Java manners....:-) > > Not sure what the Codehaus Bamboo instance is running and if we could > at least get it setup there. > > > Maven best practice says that people should be pinning the version > number of their plugins, so releasing a new plugin should be a low risk > exercise - it won't break any properly configured maven projects. > > Right, but producing a new release with fixes for some tickets and > also including new issues is just something I hate. I hate being the > consumer of that and I don't want to be the producer. At a minimum, I > need to be able to see the ITs pass on at least one platform (RHEL?). > > /Anders > > > >>> If a release could be made, it would be a huge help. > >> > >> I appreciate this, but I don't like doing releases which I don't trust > myself. > >> > >>> Something else I picked up was that JIRA doesn't let an ordinary user > like me set the "path submitted" flag - I could post a patch, I just > couldn't mark the ticket as having a patch. (Or I am missing where in JIRA > you set that). > >> > >> I think you can set this when you initially create the ticket. I > >> marked a few of your tickets as patch included. > > > > The trouble was when I created the ticket, I didn't yet have the patch, > that came later. > > > > Regards, > > Graham > > -- > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
