Kills me that BUILD_ID=dontKillMe

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Kills me that BUILD_ID=dontKillMe

Ioannis Moutsatsos-2
I have recently upgraded to Jenkins v2.100 from v2.93 and all the security plugins that came along for the ride.
The upgrade broke all the jobs where in Groovy scripts and properties I was using the BUILD_ID environment variable to create unique names for folders and files. 

The BUILD_ID (which up to this point was equal to BUILD_NUMBER) is now set to 'dontKillMe'

Is there an option to disable this? I want BUILD_ID=BUILD_NUMBER

Best regards
Ioannis

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c76b2ce5-ee5d-4e7d-a440-4052d04f3b8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Kills me that BUILD_ID=dontKillMe

Simon Richter
Hi,

Am 17.01.2018 um 17:25 schrieb Ioannis Moutsatsos:

> The BUILD_ID (which up to this point was equal to BUILD_NUMBER) is now
> set to 'dontKillMe'

I dimly remember that this is a way to tell the cleanup code that kills
all processes after the build has finished to ignore certain processes.

On Windows with Visual Studio, this is often needed because pdbserv.exe
is shared between builds, so if the build that initially started it
finishes, all the other builds that are still running will fail.

Not sure why this is set now, but I'd suspect a plugin rather than
Jenkins core here.

   Simon

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5A5F9EF2.30901%40hogyros.de.
For more options, visit https://groups.google.com/d/optout.

signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Kills me that BUILD_ID=dontKillMe

Ioannis Moutsatsos-2
Simon your suspicion was correct! Thank you!

After downgrading several plugins, I was able to isolate the issue with the EnvInject Plugin v2.1.5
This version of the plugin seems to inject 'dontKillMe' as the BUILD_ID for a build. This behavior is not present in EnvInject Plugin v2.13
So, I have now settled to v2.1.3 as the latest version of the plugin to install.

Best regards
Ioannis

On Wednesday, January 17, 2018 at 2:07:58 PM UTC-5, Simon Richter wrote:
Hi,

Am 17.01.2018 um 17:25 schrieb Ioannis Moutsatsos:

> The BUILD_ID (which up to this point was equal to BUILD_NUMBER) is now
> set to 'dontKillMe'

I dimly remember that this is a way to tell the cleanup code that kills
all processes after the build has finished to ignore certain processes.

On Windows with Visual Studio, this is often needed because pdbserv.exe
is shared between builds, so if the build that initially started it
finishes, all the other builds that are still running will fail.

Not sure why this is set now, but I'd suspect a plugin rather than
Jenkins core here.

   Simon

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c378e0d5-9d7c-4bf7-938f-ac1a9ecf7f74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Kills me that BUILD_ID=dontKillMe

Abhishek Chordia
In reply to this post by Ioannis Moutsatsos-2
Hi,

Recently i have started working on jenkinsfile for pipeline purpose, where my job stop once jenkinsfile process complete, please help me got this corrected, below is sample file : 

=======================================================================================================================================
pipeline {
  agent {
label 'master'
  }
  
  tools { 
        maven 'APACHE_MAVEN' 
    }
  
  stages {
    
    stage('Kill Process') {
      steps {
sh 'lsof -ti :6001 | xargs --no-run-if-empty kill -9'
      }
    }
    
    stage('Build Stage') {
      steps {
        sh 'mvn clean package install -DskipTests -Dspring.profiles.active=uat'
      }
    }
    
    stage('Testing Stage') {
      steps {
        echo "Testing Stage"
      }
    }
    
    stage('Deployement Stage') {
      steps {
        sh 'cd ./sms-server && BUILD_ID=dontKillMe nohup mvn spring-boot:run -DskipTests -Dserver.port=6001 -Dspring.profiles.active=development &'
      }
    }
    
   stage('URL Response') {
      steps {
sleep 10
        sh 'curl http://localhost:8085/healthcheck'
      }
    }

  }
}


=======================================================================================================================================

On Wednesday, January 17, 2018 at 9:55:41 PM UTC+5:30, Ioannis Moutsatsos wrote:
I have recently upgraded to Jenkins v2.100 from v2.93 and all the security plugins that came along for the ride.
The upgrade broke all the jobs where in Groovy scripts and properties I was using the BUILD_ID environment variable to create unique names for folders and files. 

The BUILD_ID (which up to this point was equal to BUILD_NUMBER) is now set to 'dontKillMe'

Is there an option to disable this? I want BUILD_ID=BUILD_NUMBER

Best regards
Ioannis

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8312cc46-5614-45cc-b479-e95be4ab19d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.