[Anthill-pro] Getting changelog

Wed Nov 14 08:09:25 CST 2007

Hmmm, so just the changes since the last build regardles of status?

...isn't that in the output of every build already? ..and goes out with the email??  

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com [mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Uldis Karlovs-Karlovskis
Sent: Wednesday, November 14, 2007 9:03 AM
To: 'AnthillPro user and support list.'
Subject: RE: [Anthill-pro] Getting changelog

Hmm imo I understand this very well. I just don`t want to use this algorhythm. In our company failed builds are considered as normal build states when unit-tests are failing for weeks etc. When I`m getting only success changelist or any other I`m getting not what I wanted. If I have failing build for a week, that means that with every build I get longer changelist with all changes which are submitted after last success build. So every failed build is longer and longer.
Am I wrong?

What I want is to have retrieved changes from latest build to running one.

Uldis Karlovs-Karlovskis, C. T. Co
uldis.karlovs-karlovskis at ctco.lv

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko, Curtis
Sent: trešdiena, 2007. gada 14. novembrī 15:13
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] Getting changelog

I still feel like your not *getting it*

When you ask for a changelog from a previous status it will get all changes since that time regardless of any of the intermediate statuses. So when I ask for a change log since SUCCESS it gets all my FAILEDs and any other stuff. I'm pretty sure behind the scenes it is just doing a time/date based query. But it does roll up all changes since that time.

I use asomewhat simpler model of Archived, Failed, Success, Dev, QA and Prod

Every success collects all of the changes since the last success which in my case is just Failed.

Every Dev collects all of the faileds and Successes since the last Dev or all changes since the last Dev deploy

QA gets all of the Dev's, Successes and Faileds without any duplicates effectively rolling  up all changes since the last QA build.

If I actually collected all of the change logs themselve and merged them I would gets lots of duplicate entries since a change in a Failed would also be in a following Success and the following Dev  giving me three entries.

What AHP provides is an elegant solution to a very basic SCM function.

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Uldis Karlovs-Karlovskis
Sent: Wednesday, November 14, 2007 4:12 AM
To: 'AnthillPro user and support list.'
Subject: RE: [Anthill-pro] Getting changelog

That`s not true. Not every time my buildlife has success or success(warning) statuses. There may be cases when changlist is retrieved but only the "failed" state is assigned.

State "deployed" is only for specific buildlifes when deployment workflow is called.

"Success" and "success(warning)" are different build states so "Success" do not cover it.

Uldis Karlovs-Karlovskis, C. T. Co
uldis.karlovs-karlovskis at ctco.lv

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko, Curtis
Sent: otrdiena, 2007. gada 13. novembrī 17:44
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] Getting changelog

Even Success to Success should encompass any Success(warning) and failure logs. 

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Uldis Karlovs-Karlovskis
Sent: Tuesday, November 13, 2007 10:28 AM
To: 'AnthillPro user and support list.'
Subject: RE: [Anthill-pro] Getting changelog

No one from my statuses don`t fit. They are:
Success
success (Warning)
timed out
failure
not needed
Archived
deployed

So I need to browse at least through Success, success (Warning), failure

Uldis Karlovs-Karlovskis, C. T. Co
uldis.karlovs-karlovskis at ctco.lv

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko, Curtis
Sent: otrdiena, 2007. gada 13. novembrī 17:24
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] Getting changelog

Then you should already have what you need assuming one can be tracked back to the start time you're looking for. Seems like if you script thorough a bunch of changelogs you'dgetlotsof duplicate entries. 

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Uldis Karlovs-Karlovskis
Sent: Tuesday, November 13, 2007 8:22 AM
To: 'AnthillPro user and support list.'; 'AnthillPro user and support list.'
Subject: RE: [Anthill-pro] Getting changelog

I already have 6 statuses, I really don`t want to create one more. I need script which takes latest from all statuses.

Uldis Karlovs-Karlovskis, C. T. Co
uldis.karlovs-karlovskis at ctco.lv

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko, Curtis
Sent: otrdiena, 2007. gada 13. novembrī 15:20
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] Getting changelog

Perhaps I missunderstand but can't you make an additional status and use it for this roll up changelog? 

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Uldis Karlovs-Karlovskis
Sent: Tuesday, November 13, 2007 2:00 AM
To: 'AnthillPro user and support list.'
Subject: [Anthill-pro] Getting changelog

Hello!

Can You help me to write a "Change Log Status Selection Script" which takes latest changelog per all statuses for current originating workflow?

Uldis Karlovs-Karlovskis, C. T. Co
uldis.karlovs-karlovskis at ctco.lv

_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro

This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.

_______________________________________________
Anthill-pro mailing list
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

This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.

_______________________________________________
Anthill-pro mailing list
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

This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.

_______________________________________________
Anthill-pro mailing list
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

This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.

_______________________________________________
Anthill-pro mailing list
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

This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.