[JIRA] (JENKINS-59487) Startup Trigger doesnt execute jobs in master

2020-02-12 Thread treadston...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Emory Penney commented on  JENKINS-59487  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Startup Trigger doesnt execute jobs in master   
 

  
 
 
 
 

 
 I just installed job-dsl 1.76 on my box and am unable to reproduce this issue. Is this still a problem or has it resolved itself? If it's still a problem it may be a compatibility issue with jenknis-slim which I'm unfamiliar with.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202102.1569250479000.8383.1581547980604%40Atlassian.JIRA.

[JIRA] (JENKINS-59487) Startup Trigger doesnt execute jobs in master

2019-09-23 Thread blastik...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 blastik . created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59487  
 
 
  Startup Trigger doesnt execute jobs in master   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Emory Penney  
 
 
Components: 
 startup-trigger-plugin  
 
 
Created: 
 2019-09-23 14:54  
 
 
Environment: 
 docker jenkins/jenkins:2.194-slim  startup-trigger-plugin:2.9.3  configuration-as-code:1.30  configuration-as-code-support:1.18   saml:1.1.2  role-strategy:2.13  permissive-script-security:0.5   git:3.12.1  github:1.29.4  github-pullrequest:0.2.6   job-dsl:1.74  workflow-aggregator:2.6   uno-choice:2.1   groovy:2.2   ec2:1.45   
 
 
Priority: 
  Critical  
 
 
Reporter: 
 blastik .  
 

  
 
 
 
 

 
 similar to JENKINS-50681 i have this job groovy 

 

job('Startup') {
  triggers {
hudsonStartupTrigger {
  // By default, the build is triggered when Jenkins instance starts.
  label('')
  // Give the quiet period before scheduling the job.
  quietPeriod('0')
  runOnChoice('ON_CONNECT')
  // Pass node name as job parameter.
  nodeParameterName('')
}
  }
  steps {
systemGroovyScriptFile('/jobs/startup_script.groovy')
  }
}
 

  my master has 1 executor. the job triggers but remains on hold showing: (pending—‘Jenkins’ is reserved for jobs with matching label _expression_) I've tried to set a label but didnt help