later
than build 103, for example. We've used these scripts for years and there
will be quite a large number to update to now work with this new format.
On Wednesday, September 2, 2015 at 10:30:34 AM UTC-7, BeckyY wrote:
>
> I recently upgraded Jenkins and noticed build artifacts f
I'd like to make use of that shortcut in scripts on slave servers, but
since the shortcut uses local drive path info, the shortcut doesn't work
from remote servers.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this grou
I recently upgraded Jenkins and noticed build artifacts folder names have
switched to using job numbers instead of timestamps. Does anyone know if
it is possible to keep the upgrade but configure Jenkins to use timestamps
instead of job numbers for the artifacts folder names for each saved bui
Thank you, Daniel!Yes, it was as simple as that! P4_CHANGELIST is an
environment variable containing the latest changelist for the path
provided.
On Tuesday, July 21, 2015 at 3:49:38 PM UTC-7, BeckyY wrote:
>
> Question is about the P4 plugin by Perforce, not the Perforce plugi
Question is about the P4 plugin by Perforce, not the Perforce plugin by a
third party.
I didn't see in the documentation any info about exposed variables. In
particular, I need to know the changelist # that the plugin selects to
build against. I created a simple project in Jenkins, configure
