I have a job which I trigger with parameters from another job using wget
. each time I give the job different parameter - which svn
revision to run with.
I don't want to allow concurrent runs of the same job, but I want to allow more than one pending build in the queue for the job.
From what I have tried it didn't work, I see in the queue only one build of the job pending, no matter how many builds I trigger.
Is it possible with any plugin?
相关问题
- Jenkins - cmd is not recognized
- How can I set the SVN password with Emacs 23.1 bui
- When using Nokogiri, how do you suppress the inser
- Where Jenkins stores plugin configuration
- If statements in .htaccess files, to enable passwo
相关文章
- dotnet restore还原nuget包时无法加载 https://api.nuget.org/
- jenkins在window集群环境中如何部署自动化发布?
- jenkins + Publish over FTP 自动部署前端React项目
- jenkins自定打包部署React前端项目遇到的问题。
- Best way to manage docker containers with supervis
- Access BitBucket payload data in Jenkins pipeline
- Build errors of missing packages in Visual Studio
- Is there a version control system abstraction for
I needed to do the same, and discovered the Random String Parameter Plugin. This adds a random string to each build as a parameter, which is enough to make each build unique and for Jenkins to queue them independently rather than coalesce them.
Jenkins doesn't place a build in the queue if it already contains one with the same param values.
To trick it, you could add an additional, unused param, and set it to a random value when calling
wget
.