svn checkout options

[Prajakta Joshi]

Hi, 

Is there a way in Jenkins to configure "svn checkout" options? I need to turn on the "use-commit-times flag"  option.

Thanks,

Prajakta

[David Carson]

Any response?  I would also like to know the answer to this question.  It seems like there must be more control over 'svn checkout' than the "Check-out Strategy" pull-down.

[Daniel Beck]

Should be possible by uncommenting the use-commit-times option in ~/.subversion/config on all nodes building the job. Subversion plugin (or rather SVNKit) appears to honor these options as defaults.

> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/794ea0b1-dc01-4cba-90ca-a804b4009725%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[David Carson]

The problem with setting the option in the user's config is that this option is not desirable for updates, only for checkouts.  If set in config, it applies to both.

Our problem is that certain parts of our code depend on the timestamps being correct to avoid triggering, for example, automake processing when we have already committed the Makefile output of automake.  Therefore, we need to have a definitive set of timestamps, which can be accomplished by using commit times when checking out.

For updates, however, it is always desirable to timestamp the updated files with 'now' rather than with the commit time of the file, so that the updates will always cause a rebuild where necessary.

In our developer environment, we created a wrapper script which provides the commit-times option.  We encourage developers not to set the option to yes in their config files.

Thanks.

[David Carson]

[Hmmm, I could have sworn I replied to this over the weekend, but it does not seem to be here....]

Anyway, there is a problem with setting commit-times to yes in the config file.  The problem is that, while this is desirable for checkouts, it is not desirable for updates.  Unfortunately, the option applies to both when set in the config file.

In our environment for developers, we suggest that they not set commit-times to yes in the config file, because updates should always set a newly updated file's timestamp to 'now' rather than the commit time of the file, thus forcing a rebuild.  Instead, we use a wrapper script for checkout only, where the commit times are used for timestamps -- necessary for us, because certain packages should not redo any automake step, and when the timestamps are random, this sometimes happens.

On Friday, January 9, 2015 at 6:41:41 PM UTC-5, Daniel Beck wrote: