[Anthill-pro]
Recipientgenerator'CommittingDevelopers'delieversempty list.
Varban
vvv at urbancode.com
Thu Mar 27 09:20:32 CST 2008
Ronald,
the svn dates are converted from the local time zone to UTC in order to
send to the subversion server. If those dates are off by an hour I would
suspect that you are running AnthillPro with a JVM that does not account
correctly for the Daylight savings time, please verify that you are
using the latest JVM release of the series available and that the
timezone settings on the machine are correct.
Regards,
Varban
Ronald Barrett wrote:
> Hi Steve,
>
> I have found something that makes a difference. If I leave the Revision
> field blank in the Source Configuration, I get the change log as
> expected. The problem then is I am not getting the latest sources from
> the repository. The svn co uses a date and time stamp that is one hour
> earlier then the time zone that subversion and Anthillpro are located.
> Triggering the build maually makes no difference.
>
> How can I influence the time stamp used in the svn co?
>
> Ron
>
> ------------------------------------------------------------------------
> *From:* Ronald Barrett
> *Sent:* Donnerstag, 27. März 2008 11:40
> *To:* 'AnthillPro user and support list.'
> *Subject:* RE: [Anthill-pro]
> Recipientgenerator'CommittingDevelopers'delieversempty list.
>
> Hi Steve,
>
> I have already updated and am still having the problem. I have found
> that the svn log -r HEAD ... command always returns nothing on our
> system. I have tried a few different options for log and found that
> using svn log -limit 1 works.
>
> A few facts on our build cycle.
>
> We are running CI builds from the trunk of each component in the repositry.
> Builds are triggerd by Subversion through the post-commit hook or manually.
>
> svn --version
> svn, version 1.4.2 (r22196)
> compiled Nov 10 2006, 17:39:50
> The changelog output in AnthillPro.
>
> Subversion command line: svn log --non-interactive --verbose --username
> svn --password ***** --revision HEAD
> https://vm-venyonsvn.internal.venyon.com:6443/scm/scm-deploy/trunk/
> Subversion command working Directory: D:\development\anthill3\bin
> Subversion XML changelog file path:
> D:\development\anthill3\var\jobs\11557\changelog\change-log-0.xml
> Subversion command environment:
> command exit status: 0
> change-log-summary: com.urbancode.vcsdriver3.ChangeLogSummary {
> changeSetCount: 0
> changeCount: 0
> latestChangeSetUser: null
> latestChangeSetDate: 1970-01-01 01:00:00 +0100
> }
>
> Would it be possible to change the log command in AnthillPro? Can do
> this myself?
>
> Regards,
>
> Ron Barrett
>
>
>
>
>
>
> ------------------------------------------------------------------------
> *From:* anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Steve Boone
> *Sent:* Dienstag, 25. März 2008 16:19
> *To:* AnthillPro user and support list.
> *Subject:* Re: [Anthill-pro]
> Recipientgenerator'CommittingDevelopers'delieversempty list.
>
> Ronald,
>
> I am unable to reproduce this error, and I believe there were some
> notification issues that were fixed after 3.4.10.
>
> Can you try upgrading to 3.4.12, and let me know the User Generator
> script starts to pull some results for you.
>
> Cheers,
> Steve Boone
>
> On Tue, Mar 25, 2008 at 5:03 AM, Ronald Barrett
> <ronald.barrett at venyon.com <mailto:ronald.barrett at venyon.com>> wrote:
>
> I tried sending an email containing some bitmaps of the dashboard.
>
> Depending on where I look in the dashboard it shows something different.
>
> Under Most Recent Status Assignments: I see the latest successfull
> build as 'sucess' (Green).
> Under Recent Activity I see the latest successful build
> as 'Complete' (Green).
>
> Failed builds don't show up under Most Recent Status Assignments at
> all (red).
> Under Recent Activity I see them as 'failed' (red)
>
> In the Status History using -- Any Status --- I only see succesfull
> builds, although there have been failed builds.
>
>
> I am not sure if this makes any difference in the reason for this
> thread. I am still not able to get the Commiting Developers
> Recipient Generator to generate an email.
> I noticed in the doumentation that there was something mentioned
> about an User-Repository Alias being used. Presently we are using
> the same name for AnthillPro users as for the subversion users and
> there is no alias set in AnthillPro. The only other thing I can
> think of is we are using an 'ssh' connection to subversion for each
> developer but anthillpro uses https to connect.
>
> Regards,
>
> Ron Barrett
>
>
> ------------------------------------------------------------------------
> *From:* anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>
> [mailto:anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>] *On Behalf Of
> *Steve Boone
> *Sent:* Dienstag, 18. März 2008 15:35
>
> *To:* AnthillPro user and support list.
> *Subject:* Re: [Anthill-pro] Recipient
> generator'CommittingDevelopers'delieversempty list.
>
> Ronald,
>
> are you seeing builds getting correctly marked successful or failure?
>
>
>
> On 3/11/08, *Ronald Barrett* <ronald.barrett at venyon.com
> <mailto:ronald.barrett at venyon.com>> wrote:
>
> Hi Steve,
>
> I have configured the Lifecycle as you commented and re-added it
> to the job. This job is in the job library, if that makes any
> difference. I am attaching a bitmap with the 'Most Resent Status
> Assignments' and the 'Recent Activity' tables. I can only see
> the match of the 'success' status in the Status Assignments to
> the complete in the Recent Acitvities. I tried adding a few
> Statuses to see if that would make any difference but it hasn't
> changed.
>
> The only other thing I can think of is the scripts used to set
> the status at the end of the build. This is what we are using to
> set a failure.
>
>
> *return* Fail.unless(
> Logic.and(
> Logic.not(
> Logic.or(
> Output.contains("BUILD FAILURE"),
> Output.contains("BUILD ERROR")
>
>
>
> )
> ),
> ExitCode.is(0)
> )
> )
>
>
>
> Regards,
>
>
>
> Ron
>
>
>
>
>
> ------------------------------------------------------------------------
> *From:* anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>
> [mailto:anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>] *On Behalf Of
> *Steve Boone
> *Sent:* Montag, 10. März 2008 20:42
>
> *To:* AnthillPro user and support list.
> *Subject:* Re: [Anthill-pro] Recipient generator
> 'CommittingDevelopers'delieversempty list.
>
> Ronald,
>
> Did you change your changelog step, to use the "success"
> status? If you chose failure, then it will look back to the
> last failed build, and only look for changes from there.
>
> You should have
>
> -Added the lifecycle model to the job.
> -Selected "Success" for your Change Log Start Status.
>
> Maybe I misunderstood? Are you saying you have it configured
> this way and it is still erroring?
>
> On 3/10/08, *Ronald Barrett* <ronald.barrett at venyon.com
> <mailto:ronald.barrett at venyon.com>> wrote:
>
> Hi Eric,
>
> The life cycle had the stati success, failue, and archived.
> I addded the lifecycle to the job ( in the job library ) and
> am still getting this in the changelog setp:
>
>
> change-log-summary:
> com.urbancode.vcsdriver3.ChangeLogSummary {
> changeSetCount: 0
> changeCount: 0
> latestChangeSetUser: null
> latestChangeSetDate: 1970-01-01 01:00:00 +0100
> }
>
>
> If I change the 'change log start status' to 'failure' I get
> a message in the log to the effect that the change log step
> was skipped as this is the first build.
>
>
> Regards,
>
> Ron
>
>
>
>
>
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>
> [mailto:anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>] On Behalf
> Of Eric Minick
> Sent: Montag, 10. März 2008 17:45
> To: AnthillPro user and support list.
> Subject: Re: [Anthill-pro] Recipient generator 'Committing
> Developers'delieversempty list.
>
> Ron,
>
> It sounds like you might be missing statuses in your life
> cycle. Could you check to see if the lifecycle you have
> selected has any statuses in it? If it does, I would drop
> the existing changelog step and re-add it.
>
> If you are missing the statuses, you would need to add some
> (like "successful" for successful builds) and add an assign
> status step at the end of your builds that assigns the
> status of the build to successful if everything has passed.
>
> Regards,
>
> Eric
>
> Ronald Barrett wrote:
> > The Get changelog start status is set to 'Make Selection',
> as there is
> > no other selection to make and the Quiet period is set to
> 'Change Log
> > Quiet Period'
> >
> > Ron Barrett
> >
> >
> ----------------------------------------------------------------------
> > --
> > *From:* anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>
> > [mailto:anthill-pro-bounces at lists.urbancode.com
> <mailto:anthill-pro-bounces at lists.urbancode.com>] *On Behalf
> Of *Steve
> > Boone
> > *Sent:* Montag, 10. März 2008 17:13
> > *To:* AnthillPro user and support list.
> > *Subject:* Re: [Anthill-pro] Recipient generator 'Committing
> > Developers'delievers empty list.
> >
> > Ronald,
> >
> > On your get changelong step, there is a "Get changelog
> start status" ,
> > what do you have that set too?
> >
> > Also, how do you have your Quiet Period configured on the
> project?
> >
> > Regards,
> > Steve Boone
> >
> > On 3/10/08, *Ronald Barrett* <ronald.barrett at venyon.com
> <mailto:ronald.barrett at venyon.com>
> > <mailto:ronald.barrett at venyon.com
> <mailto:ronald.barrett at venyon.com>>> wrote:
> >
> > Hi,
> >
> > I am working on setting up notifications and am unable
> to get the
> > Committing Developers Recipient generator to deliever a
> list of
> > commiting developers.
> >
> > I am not sure if I missed something in the
> documentation or what
> > but I can't get this to work. I would like to use this for
> > notifying our Developers of new builds and there status
> but don't
> > want to spam everyone.
> >
> > I updated the script to use the
> > UserLookup.getAllContributors(workflow) as the
> > UserLookkup.getAllContributers has been depricated.
> >
> > We are using AnthillPro 3.4.10 and our repository is
> Subversion.
> > I have noticed that my Change Log step generally
> delivers the
> > following results.
> >
> > change-log-summary:
> com.urbancode.vcsdriver3.ChangeLogSummary {
> > changeSetCount: 0
> > changeCount: 0
> > latestChangeSetUser: null
> > latestChangeSetDate: 1970-01-01 01:00:00 +0100
> > }
> >
> > If use same command that is run by AnthillPro on the
> command line
> > I get the following:
> >
> > svn log ...
> >
> >
> ----------------------------------------------------------------------
> > --
> >
> >
> > If I run the svn info command I get something like this:
> >
> > Revision: 1234
> > Node Kind: directory
> > Last Changed Author: <username>
> > Last Changed Rev: 3456
> > Last Changed Date: 2008-03-10 10:26:52 +0100 (Mo, 10
> Mrz 2008)
> >
> >
> >
> > Have I missed something?
> >
> >
> > Ronald Barrett
> > Senior Software Engineer
> >
> >
> >
> > VENYON GmbH
> >
> >
> >
> > Email: ronald.barrett at venyon.de
> <mailto:ronald.barrett at venyon.de>
> <mailto:ronald.barrett at venyon.de
> <mailto:ronald.barrett at venyon.de>>
> > Willy-Brandt-Platz 2 Phone +49 89 45 21 33 102
> > 81829 Muenchen Fax +49 89 45 21 33 100
> > Germany
> >
> >
> >
> > Geschäftsführer: Oliver Pannke - Sitz der Gesellschaft:
> München -
> > HRB 163208
> > (Amtsgericht München)
> >
> >
> >
> > _______________________________________________
> > Anthill-pro mailing list
> > Anthill-pro at lists.urbancode.com
> <mailto:Anthill-pro at lists.urbancode.com>
> > <mailto:Anthill-pro at lists.urbancode.com
> <mailto:Anthill-pro at lists.urbancode.com>>
> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
> >
> >
> >
> ----------------------------------------------------------------------
> > --
> >
> > _______________________________________________
> > Anthill-pro mailing list
> > Anthill-pro at lists.urbancode.com
> <mailto:Anthill-pro at lists.urbancode.com>
> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
> >
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> <mailto:Anthill-pro at lists.urbancode.com>
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> <mailto:Anthill-pro at lists.urbancode.com>
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> <mailto:Anthill-pro at lists.urbancode.com>
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com <mailto:Anthill-pro at lists.urbancode.com>
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
More information about the Anthill-pro
mailing list