Re: Subversion Exclusion revprop name - trying to use this to ignore certain svn commits, but can't seem to get this to work

2014-04-18 Thread Daniel Beck
(Re-sending to the list -- sorry Robert!)

On 17.04.2014, at 22:50, Robert Mackin robert.mac...@gmail.com wrote:

 Does that mean this feature doesn't really exist? 

No, it just means you didn't see the 'Advanced' button a few options down.

 Repository URL
 Credentials
 Local module directory
 Repository depth
 Ignore Externals

It's not a per-module option. Everything in the SCM section is related to the 
selected SCM, not just the indented part.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Subversion Exclusion revprop name - trying to use this to ignore certain svn commits, but can't seem to get this to work

2014-04-17 Thread Robert Mackin
Thanks for your reply. I can't find such an option anywhere in the per-job 
SCM configurarion for Subversion.
All I see is:
Repository URL
Credentials
Local module directory
Repository depth
Ignore Externals

Does that mean this feature doesn't really exist? I updated to the latest 
svn plugin to see if it would show up, and it's not there.

Bob

On Wednesday, April 16, 2014 5:09:35 PM UTC-4, Daniel Beck wrote:

 The global exclusion revprop configuration option has absolutely no 
 associated functionality. 

 You need to set the equivalent option in the per-job SCM configuration. 

 On 16.04.2014, at 21:41, Robert Mackin robert...@gmail.com javascript: 
 wrote: 

  I'm setting up Jenkins to replace our homegrown build system. 
  
  I want to set it up so that we poll for svn changes and build when a 
 change is detected. 
  Problem is our current build checks a file into the project's svn 
 repository after a build. That means polling will *always* find a change. I 
 only want to build if a developer checks something in. 
  
  I discovered that the Subversion plugin allows you to configure an 
 Exclusion revprop name, documented thus: 
  
  If set, and Jenkins is set to poll for changes, Jenkins will ignore any 
 revisions that are marked with the given revision property (revprop) when 
 determining if a build needs to be triggered. This can be used to exclude 
 commits done by the build itself from triggering another build, assuming 
 the build server commits the change with the correct revprop. 
  This type of exclusion only works with Subversion 1.5 servers and 
 newer. 
  
  My svn server is running 1.7.7, and I'm running Version 2.2 of the 
 Subversion Plugin on Jenkins 1.557. 
  
  I tried setting the Exclusion revprop name to jenkins, and then I 
 tested with this checkin: 
   svn commit -m test --with-revprop jenkins=jenkins Foo.java 
  
  But jenkins sees this change and triggers a build. I tried leaving out 
 the =jenkins part, to no avail. 
  
  Am I misunderstanding the documentation? Shouldn't jenkins ignore this 
 change? 
  Or am I doing something obviously wrong? 
  
  Is there another way to do this? 
  
  Thanks in advance 
  
  -- 
  You received this message because you are subscribed to the Google 
 Groups Jenkins Users group. 
  To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-use...@googlegroups.com javascript:. 
  For more options, visit https://groups.google.com/d/optout. 



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Subversion Exclusion revprop name - trying to use this to ignore certain svn commits, but can't seem to get this to work

2014-04-16 Thread Robert Mackin
I'm setting up Jenkins to replace our homegrown build system. 

I want to set it up so that we poll for svn changes and build when a change 
is detected. 
Problem is our current build checks a file into the project's svn 
repository after a build. That means polling will *always* find a change. I 
only want to build if a developer checks something in.

I discovered that the Subversion plugin allows you to configure an Exclusion 
revprop name, documented thus:

If set, and Jenkins is set to poll for changes, Jenkins will ignore any 
revisions that are marked with the given revision property (revprop) when 
determining if a build needs to be triggered. This can be used to exclude 
commits done by the build itself from triggering another build, assuming 
the build server commits the change with the correct revprop.
This type of exclusion only works with Subversion 1.5 servers and newer.

My svn server is running 1.7.7, and I'm running Version 2.2 of the 
Subversion Plugin on Jenkins 1.557.

I tried setting the Exclusion revprop name to jenkins, and then I 
tested with this checkin:
 svn commit -m test --with-revprop jenkins=jenkins Foo.java

But jenkins sees this change and triggers a build. I tried leaving out the 
=jenkins part, to no avail.

Am I misunderstanding the documentation? Shouldn't jenkins ignore this 
change? 
Or am I doing something obviously wrong?

Is there another way to do this?

Thanks in advance

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Subversion Exclusion revprop name - trying to use this to ignore certain svn commits, but can't seem to get this to work

2014-04-16 Thread Daniel Beck
The global exclusion revprop configuration option has absolutely no associated 
functionality.

You need to set the equivalent option in the per-job SCM configuration.

On 16.04.2014, at 21:41, Robert Mackin robert.mac...@gmail.com wrote:

 I'm setting up Jenkins to replace our homegrown build system. 
 
 I want to set it up so that we poll for svn changes and build when a change 
 is detected. 
 Problem is our current build checks a file into the project's svn repository 
 after a build. That means polling will *always* find a change. I only want to 
 build if a developer checks something in.
 
 I discovered that the Subversion plugin allows you to configure an Exclusion 
 revprop name, documented thus:
 
 If set, and Jenkins is set to poll for changes, Jenkins will ignore any 
 revisions that are marked with the given revision property (revprop) when 
 determining if a build needs to be triggered. This can be used to exclude 
 commits done by the build itself from triggering another build, assuming the 
 build server commits the change with the correct revprop.
 This type of exclusion only works with Subversion 1.5 servers and newer.
 
 My svn server is running 1.7.7, and I'm running Version 2.2 of the Subversion 
 Plugin on Jenkins 1.557.
 
 I tried setting the Exclusion revprop name to jenkins, and then I tested 
 with this checkin:
  svn commit -m test --with-revprop jenkins=jenkins Foo.java
 
 But jenkins sees this change and triggers a build. I tried leaving out the 
 =jenkins part, to no avail.
 
 Am I misunderstanding the documentation? Shouldn't jenkins ignore this 
 change? 
 Or am I doing something obviously wrong?
 
 Is there another way to do this?
 
 Thanks in advance
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.