Can Hudson ignore properties when polling scm (svn)?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Can Hudson ignore properties when polling scm (svn)?

B B-8
Greetings,

I have Hudson configured to Poll SCM (SVN).  Once the build is triggered, part of the task commit properties back to the project, which will result in a new revision being detected by the poller (hence, a new build triggered).

Is there any way to configure Hudson to ignore these property updates, when polling the SCM?

Thanks!
B
Reply | Threaded
Open this post in threaded view
|

Re: Can Hudson ignore properties when polling scm (svn)?

Andrew Chandler
Our build had similar characteristics - we used to check back in an updated xml file that was used by our product that had the build number embedded in it.   Unfortunately due to the way subversion works when you check into a directory it updates the revision number for it and its parents.   The polling mechanism is so much faster on subversion because all it looks at is the revision number and triggers an update if its higher than it was before.   The easiest way I can think of at the moment to do what you want is to have a separate subversion module that contains your build modified files and cause the checkin or update of those directories to happen inside your maven pom or ant build script.   If the separate module isn't listed on the subversion directories for the project it won't be polled and won't trigger the build.



On a separate note a enhancement where we could specify when there are multiple directories to be checked out in a project whether each one was polled or just a single one was polled for build triggering might be helpful. 


On Sat, 2009-07-04 at 11:41 -0400, B B wrote:
Greetings,

I have Hudson configured to Poll SCM (SVN).  Once the build is triggered, part of the task commit properties back to the project, which will result in a new revision being detected by the poller (hence, a new build triggered).

Is there any way to configure Hudson to ignore these property updates, when polling the SCM?

Thanks!
B

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Reply | Threaded
Open this post in threaded view
|

Re: Can Hudson ignore properties when polling scm (svn)?

Michael Donohue
Doesn't the SVN exclusion feature implemented to fix issue 3124 solve this?  Use a regex to identify the xml file that gets changed, to ignore the checkin.

-Michael

On Sat, Jul 4, 2009 at 12:18 PM, Andrew Chandler <[hidden email]> wrote:
Our build had similar characteristics - we used to check back in an updated xml file that was used by our product that had the build number embedded in it.   Unfortunately due to the way subversion works when you check into a directory it updates the revision number for it and its parents.   The polling mechanism is so much faster on subversion because all it looks at is the revision number and triggers an update if its higher than it was before.   The easiest way I can think of at the moment to do what you want is to have a separate subversion module that contains your build modified files and cause the checkin or update of those directories to happen inside your maven pom or ant build script.   If the separate module isn't listed on the subversion directories for the project it won't be polled and won't trigger the build.



On a separate note a enhancement where we could specify when there are multiple directories to be checked out in a project whether each one was polled or just a single one was polled for build triggering might be helpful. 


On Sat, 2009-07-04 at 11:41 -0400, B B wrote:
Greetings,

I have Hudson configured to Poll SCM (SVN).  Once the build is triggered, part of the task commit properties back to the project, which will result in a new revision being detected by the poller (hence, a new build triggered).

Is there any way to configure Hudson to ignore these property updates, when polling the SCM?

Thanks!
B

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply | Threaded
Open this post in threaded view
|

Re: Can Hudson ignore properties when polling scm (svn)?

Andrew Chandler
No idea - that one is new by me, we dealt with our build process about a year and a half ago to convert it over to something that we could use with hudson.  However I'll follow your link, it would be nice to be able to do it as you describe.


On Sun, 2009-07-05 at 16:45 -0400, Michael Donohue wrote:
Doesn't the SVN exclusion feature implemented to fix issue 3124 solve this?  Use a regex to identify the xml file that gets changed, to ignore the checkin.

-Michael

On Sat, Jul 4, 2009 at 12:18 PM, Andrew Chandler <[hidden email]> wrote:
Our build had similar characteristics - we used to check back in an updated xml file that was used by our product that had the build number embedded in it.   Unfortunately due to the way subversion works when you check into a directory it updates the revision number for it and its parents.   The polling mechanism is so much faster on subversion because all it looks at is the revision number and triggers an update if its higher than it was before.   The easiest way I can think of at the moment to do what you want is to have a separate subversion module that contains your build modified files and cause the checkin or update of those directories to happen inside your maven pom or ant build script.   If the separate module isn't listed on the subversion directories for the project it won't be polled and won't trigger the build.



On a separate note a enhancement where we could specify when there are multiple directories to be checked out in a project whether each one was polled or just a single one was polled for build triggering might be helpful. 



On Sat, 2009-07-04 at 11:41 -0400, B B wrote:


Greetings,

I have Hudson configured to Poll SCM (SVN).  Once the build is triggered, part of the task commit properties back to the project, which will result in a new revision being detected by the poller (hence, a new build triggered).

Is there any way to configure Hudson to ignore these property updates, when polling the SCM?

Thanks!
B


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Reply | Threaded
Open this post in threaded view
|

Re: Can Hudson ignore properties when polling scm (svn)?

Qazwart-2
In reply to this post by B B-8
What type of property changes are you talking about?

If you're talking about revprop changes, that shouldn't trigger a new
build. If you're talking about adding properties to the files
themselves, you're talking about creating a new revision, thus
triggering a build.

Look at your process and see why you want to add or change a property
on a file. Is there a better way to handle this?

If you have to update a property on a file, you will have to write
your own Subversion polling system. This isn't as bad as it sounds,
but does add a level of complexity to your build process.

On Sat, Jul 4, 2009 at 11:41 AM, B B<[hidden email]> wrote:

> Greetings,
>
> I have Hudson configured to Poll SCM (SVN).  Once the build is triggered,
> part of the task commit properties back to the project, which will result in
> a new revision being detected by the poller (hence, a new build triggered).
>
> Is there any way to configure Hudson to ignore these property updates, when
> polling the SCM?
>
> Thanks!
> B
>



--
David Weintraub
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Can Hudson ignore properties when polling scm (svn)?

Andrew Chandler
In our case we reworked our process because we were actually commiting an updated xml file back to svn during each build - I didn't quite key in on his discussion of properties....I was speaking of an attribute in an xml file when I gave my advice to move the updated file into its own svn module that isn't polled.  

On Mon, 2009-07-06 at 10:04 -0400, David Weintraub wrote:
What type of property changes are you talking about?

If you're talking about revprop changes, that shouldn't trigger a new
build. If you're talking about adding properties to the files
themselves, you're talking about creating a new revision, thus
triggering a build.

Look at your process and see why you want to add or change a property
on a file. Is there a better way to handle this?

If you have to update a property on a file, you will have to write
your own Subversion polling system. This isn't as bad as it sounds,
but does add a level of complexity to your build process.

On Sat, Jul 4, 2009 at 11:41 AM, B B<[hidden email]> wrote:
> Greetings,
>
> I have Hudson configured to Poll SCM (SVN).  Once the build is triggered,
> part of the task commit properties back to the project, which will result in
> a new revision being detected by the poller (hence, a new build triggered).
>
> Is there any way to configure Hudson to ignore these property updates, when
> polling the SCM?
>
> Thanks!
> B
>



-- 
David Weintraub
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Reply | Threaded
Open this post in threaded view
|

RE: Can Hudson ignore properties when polling scm (svn)?

Dean Yu
In reply to this post by Andrew Chandler
I'm in the process of integrating some additional exclusion filters into
the Subversion plugin. One of these filters is the ability to ignore
commits with a configurable revision property name. I think this does
what you want. I hope to get this integration compelted this week.

  -- Dean

> -----Original Message-----
> From: Andrew Chandler [mailto:[hidden email]]
> Sent: Sunday, July 05, 2009 2:05 PM
> To: [hidden email]
> Subject: Re: Can Hudson ignore properties when polling scm (svn)?
>
> No idea - that one is new by me, we dealt with our build
> process about a year and a half ago to convert it over to
> something that we could use with hudson.  However I'll follow
> your link, it would be nice to be able to do it as you describe.
>
>
> On Sun, 2009-07-05 at 16:45 -0400, Michael Donohue wrote:
>
>
> Doesn't the SVN exclusion feature implemented to fix
> issue 3124
> <https://hudson.dev.java.net/issues/show_bug.cgi?id=3124>  
> solve this?  Use a regex to identify the xml file that gets
> changed, to ignore the checkin.
>
> -Michael
>
>
>
> On Sat, Jul 4, 2009 at 12:18 PM, Andrew Chandler
> <[hidden email]> wrote:
>
> Our build had similar characteristics - we used
> to check back in an updated xml file that was used by our
> product that had the build number embedded in it.  
> Unfortunately due to the way subversion works when you check
> into a directory it updates the revision number for it and
> its parents.   The polling mechanism is so much faster on
> subversion because all it looks at is the revision number and
> triggers an update if its higher than it was before.   The
> easiest way I can think of at the moment to do what you want
> is to have a separate subversion module that contains your
> build modified files and cause the checkin or update of those
> directories to happen inside your maven pom or ant build
> script.   If the separate module isn't listed on the
> subversion directories for the project it won't be polled and
> won't trigger the build.
>
>
>
> On a separate note a enhancement where we could
> specify when there are multiple directories to be checked out
> in a project whether each one was polled or just a single one
> was polled for build triggering might be helpful.  
>
>
>
>
> On Sat, 2009-07-04 at 11:41 -0400, B B wrote:
>
>
>
>
> Greetings,
>
> I have Hudson configured to Poll SCM
> (SVN).  Once the build is triggered, part of the task commit
> properties back to the project, which will result in a new
> revision being detected by the poller (hence, a new build triggered).
>
> Is there any way to configure Hudson to
> ignore these property updates, when polling the SCM?
>
> Thanks!
> B
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner
> <http://www.mailscanner.info/> , and is
> believed to be clean.
>
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner
> <http://www.mailscanner.info/> , and is
> believed to be clean.
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner
> <http://www.mailscanner.info/> , and is
> believed to be clean.
>
>
>
>
> --
> This message has been scanned for viruses and dangerous
> content by MailScanner <http://www.mailscanner.info/> , and
> is believed to be clean.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]