Correction: I could upgrade to LTS 1.509.2 and *all* the latest and
greatest versions of the plugins.
I also upgraded to VisualSvn 2.6.4.
But I still get the error.
The VisualSvn server is now reporting the following in the log
Could not access revision times. [500, #175002]
Re-stuck.
--
Yo
The problem has come back a couple of times since I last posted on this
thread.
It always went away on its own after a few hours, but this time it's
sticking around. It came back yesterday afternoon 5pm GMT, and it's still
there.
The same issue seems to be affecting Jenkins installations that
:
>
> Are the clocks on the Jenkins machine and the subversion server in sync
> (e.g. via ntp)? They need to be.
>
> Matthew
>
>
>
> *From:* jenkins...@googlegroups.com [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Masariello
> *Sent:* 0
I've been running a Jenkins 1.480.x + VisualSvn 2.5.x since Nov 2012.
A few days ago we started to experience the exception below ('500 Internal
Server Error'). For a few times the problem went away after a reboot. But
today everything started to fail ALWAYS.
This started to happen completely o
Hi there
The Promoted Builds Plugin puts the number of the build being promoted in
an environment variable called PROMOTED_NUMBER
How can the Copy Artifacts Plugin use it in a promotion process?
I tried several combinations without success.
Thanks in advance!
Another possibility I thought of after posting this topic:
To name all the builds in a matrix multi-config job (incl. the master) I'd
be happy to use an expression like
*last_level_of*(${SVN_URL}) + "." + ${SVN_REVISION}
Does anyone know if there's a way to manipulate strings before they are
Hi there
I'm using the Build Name Setter plugin with a Matrix project to pick up a
version string from a build.properties file.
The right value of the version string is generated by my build script.
This is because we keep the MAJOR and MINOR version numbers in svn. The
build scripts make sure
Hi there
a quick question: during a promotion, is it possible to copy
the artefacts of a specific build within a matrix project with the Publish
Over CIFS plugin?
Things like $BUILD_URL/ABI=net,CONFIG=release/path/to/deploy/**/* do not
seem to work.
At the moment I'm having to use the followi
