On Thu, May 30, 2013 at 10:51:12AM -0400, David Nalley wrote: > Hi folks: > > I came across an interesting problem today, and think it's one that > deserves fixing. > > I looked at our jenkins config and found that we build packages in a > manner that is different from how our documentation tells users to > build those packages. IMO while there may be more than one way to skin > the cat, we should at least be testing the manner we tell others to > use. (or perhaps changing the method we tell users to use to match the > tests we are doing) > > Such disconnects between how our user base consumes ACS and how we > test it is bound to cause us problems. >
What was different? The package.sh script in our repo was modified to take options but performs the same steps as does the package job on jenkins. We only write the full complete `rpmbuild` command on our jenkins job. -- Prasanna., ------------------------ Powered by BigRock.com
