svn revision policy

[fiona]

I confused about svn revision policy in system configuratioin. my
understanding as follows:
queue time: if I set Poll CM to */10 * * * *,when ten minutes
arrive,i.e. 10:50:40,my WC will update to the revision at the
time ,even the build is waiting for long time in queue ?
build time: when ten minutes arrive, if the frontal build do not
finish, then the build will be in queue, so when it startup ,maybe it
is delayed for many miniutes, the revision will be at the time it
startup?
Head revision : whenever the build startup, the revision is the latest
at the time the build startup?
my understanding is right? my best confused is Head revision, if the
revision is the latest at the time the build startup, I find it update
to the revision after the startup time,why?

[Sami Tikka]

2012/2/22 fiona <[hidden email]>:
> I confused about svn revision policy in system configuratioin. my
> understanding as follows:
> queue time: if I set Poll CM to */10 * * * *,when ten minutes
> arrive,i.e. 10:50:40,my WC will update to the revision at the
> time ,even the build is waiting for long time in queue ?

WC? You mean workspace? No. Even if Jenkins checks your svn server, it
does not change the workspace of a build that is running.

> build time: when ten minutes arrive, if the frontal build do not
> finish, then the build will be in queue, so when it startup ,maybe it
> is delayed for many miniutes, the revision will be at the time it
> startup?

When a build actually starts, it will check out whatever is the latest
version at that moment in your version control.

> Head revision : whenever the build startup, the revision is the latest
> at the time the build startup?

Isn't this the same question as above? I'm sorry if I misunderstood.
English is not my native language.

> my understanding is right? my best confused is Head revision, if the
> revision is the latest at the time the build startup, I find it update
> to the revision after the startup time,why?

I'm sorry... I must still be misunderstanding. It makes sense to build
using the latest version. Otherwise you would need to make another
build to test the latest version.

If you want to implement continuous integration to build _every
commit_, you need to create an SVN hook script that triggers Jenkins
to build a specific commit.

Usually people do not want to build every commit, because
building+testing takes a long time.

-- Sami

[Les Mikesell]

On Wed, Feb 22, 2012 at 2:16 PM, Sami Tikka <[hidden email]> wrote:
>>
> When a build actually starts, it will check out whatever is the latest
> version at that moment in your version control.
>

I thought someone said this was different for parametrized builds but
I didn't understand it well enough to know it the parameter expansion
had to specify the revision, or if a job having any parameters would
stick in the queue with the revision of the time it was invoked.

--
   Les Mikesell
     [hidden email]

[Sami Tikka]

2012/2/22 Les Mikesell <[hidden email]>:

> On Wed, Feb 22, 2012 at 2:16 PM, Sami Tikka <[hidden email]> wrote:
>>>
>> When a build actually starts, it will check out whatever is the latest
>> version at that moment in your version control.
>>
>
> I thought someone said this was different for parametrized builds but
> I didn't understand it well enough to know it the parameter expansion
> had to specify the revision, or if a job having any parameters would
> stick in the queue with the revision of the time it was invoked.

Indeed, with some SCM plugins you can specify the version to be
checked out as a variable and then set this variable from build
parameter.

-- Sami

[Christoph Kutzinski]

AFAIK with the svn plugin it will checkout the revision from the date when the build was started (or queued - not sure). If you want the latest revision, you have to append @head to the repo url.



Am 22.02.2012 um 21:40 schrieb Sami Tikka <[hidden email]>:

> 2012/2/22 Les Mikesell <[hidden email]>:
>> On Wed, Feb 22, 2012 at 2:16 PM, Sami Tikka <[hidden email]> wrote:
>>>>
>>> When a build actually starts, it will check out whatever is the latest
>>> version at that moment in your version control.
>>>
>>
>> I thought someone said this was different for parametrized builds but
>> I didn't understand it well enough to know it the parameter expansion
>> had to specify the revision, or if a job having any parameters would
>> stick in the queue with the revision of the time it was invoked.
>
> Indeed, with some SCM plugins you can specify the version to be
> checked out as a variable and then set this variable from build
> parameter.
>
> -- Sami

[Les Mikesell]

On Wed, Feb 22, 2012 at 2:40 PM, Sami Tikka <[hidden email]> wrote:

> 2012/2/22 Les Mikesell <[hidden email]>:
>> On Wed, Feb 22, 2012 at 2:16 PM, Sami Tikka <[hidden email]> wrote:
>>>>
>>> When a build actually starts, it will check out whatever is the latest
>>> version at that moment in your version control.
>>>
>>
>> I thought someone said this was different for parametrized builds but
>> I didn't understand it well enough to know it the parameter expansion
>> had to specify the revision, or if a job having any parameters would
>> stick in the queue with the revision of the time it was invoked.
>
> Indeed, with some SCM plugins you can specify the version to be
> checked out as a variable and then set this variable from build
> parameter.

It is more complicated than that.  Here's a link to the long earlier thread:
http://jenkins.361315.n4.nabble.com/Queue-Concurrent-Builds-v1-431-td3849421.html

--
  Les Mikesell
    [hidden email]

[fiona]

thanks a lot for your support! in fact , I'm confused by 'build time'
and 'Head revision' in configuring 'subversion revision policy', I
don't know the difference between them. I think both of them check out
the revision at the build startup time.

On 2月23日, 上午5时14分, Les Mikesell <[hidden email]> wrote:

> On Wed, Feb 22, 2012 at 2:40 PM, Sami Tikka <[hidden email]> wrote:
> > 2012/2/22 Les Mikesell <[hidden email]>:
> >> On Wed, Feb 22, 2012 at 2:16 PM, Sami Tikka <[hidden email]> wrote:
>
> >>> When a build actually starts, it will check out whatever is the latest
> >>> version at that moment in your version control.
>
> >> I thought someone said this was different for parametrized builds but
> >> I didn't understand it well enough to know it the parameter expansion
> >> had to specify therevision, or if a job having any parameters would
> >> stick in the queue with therevisionof the time it was invoked.
>
> > Indeed, with some SCM plugins you can specify the version to be
> > checked out as a variable and then set this variable from build
> > parameter.
>
> It is more complicated than that.  Here's a link to the long earlier thread:http://jenkins.361315.n4.nabble.com/Queue-Concurrent-Builds-v1-431-td...
>
> --
>   Les Mikesell
>     [hidden email]- 隐藏被引用文字 -
>
> - 显示引用的文字 -

[Christoph Kutzinski]

Is it possible that you talk about the Hudson svn plugin and not about the Jenkins one?
I'm not aware about a revision policy in the Jenkins one.



Am 23.02.2012 um 02:43 schrieb fiona <[hidden email]>:

> thanks a lot for your support! in fact , I'm confused by 'build time'
> and 'Head revision' in configuring 'subversion revision policy', I
> don't know the difference between them. I think both of them check out
> the revision at the build startup time.
>
> On 2月23日, 上午5时14分, Les Mikesell <[hidden email]> wrote:
>> On Wed, Feb 22, 2012 at 2:40 PM, Sami Tikka <[hidden email]> wrote:
>>> 2012/2/22 Les Mikesell <[hidden email]>:
>>>> On Wed, Feb 22, 2012 at 2:16 PM, Sami Tikka <[hidden email]> wrote:
>>
>>>>> When a build actually starts, it will check out whatever is the latest
>>>>> version at that moment in your version control.
>>
>>>> I thought someone said this was different for parametrized builds but
>>>> I didn't understand it well enough to know it the parameter expansion
>>>> had to specify therevision, or if a job having any parameters would
>>>> stick in the queue with therevisionof the time it was invoked.
>>
>>> Indeed, with some SCM plugins you can specify the version to be
>>> checked out as a variable and then set this variable from build
>>> parameter.
>>
>> It is more complicated than that.  Here's a link to the long earlier thread:http://jenkins.361315.n4.nabble.com/Queue-Concurrent-Builds-v1-431-td...
>>
>> --
>>  Les Mikesell
>>    [hidden email]- 隐藏被引用文字 -
>>
>> - 显示引用的文字 -