Thanks a lot Mark. Your solution worked. I don't know why in many tutorials
the installed weekly version and it worked. Once again thanks for the
response, you made my day.
--Suya Dilip I
On Tuesday, April 21, 2020 at 6:54:07 PM UTC+5:30, Mark Waite wrote:
>
> Jenkins 2.232 is the f
Are you using a build-name-setter plugin in this job?
For us, we were using it. Having stopped that, we are not seeing this
problem. But I am not sure.
On Tuesday, 1 April 2014 23:12:15 UTC-4, Dilip M wrote:
>
>
>
> On Wed, Dec 18, 2013 at 2:43 PM, Søren Mollerup wrote:
>
>
On Wed, Dec 18, 2013 at 2:43 PM, Søren Mollerup wrote:
> We've run into a weird problem lately.
>
> A couple of our jobs are sometimes marked as failures in the build
> history, and the trend says it is finished after 0 ms.
> If I examine the console output the build is executed as normal and
> r
shot
On Friday, March 8, 2013 3:52:48 AM UTC-6, Varghese Renny wrote:
>
> Hi dilip,
>
> You can go with
> setacl to the directory(get inherit to subfolders automatically)
> umask to newly creating file
> chown change the owner to who is running the jenkins
>
&g
Hey guys,
Need to throw a quick question to this group.
Have been using Jenkins for a while, but am trying to configure Jenkins
(1.5 latest) on linux (CentOS) pull a project built using GradleW (version
1.0)
All's fine and the job works in windows where the permission structure is
different, bu
