[JIRA] (JENKINS-57484) Improve API Token "API" capability, esp. for scripting
Title: Message Title blastik . commented on JENKINS-57484 Re: Improve API Token "API" capability, esp. for scripting as requested in https://github.com/jenkinsci/jenkins/pull/4027#issuecomment-534558658 I'm deploying a new Jenkins from scratch on a single host using Docker all on top of AWS. Its authentication mode is set to SAML (using Okta) and we configure it using JCasC (Configuration as code). The deployment strategy we decided is to deploy a new instance each time a configuration change is made. However, in order to give a good experience to our end users, we want to make 2 steps before swapping between old and new release: Put the old instance in Quiet mode. Query running builds When running query builds = 0 then swap the instance. We have no problem on doing that with the API but... the problem is that we depend on one single thing: the API token! Ideally we would like to add a fix token into JCasC file to be able to connect to the API once Jenkins the host has been configured. jenkins saml 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
[JIRA] (JENKINS-59487) Startup Trigger doesnt execute jobs in master
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
