jenkinsci / jenkinsci/java-client-api
when running in multithreading separate thread triggers the build
- Lingua principale
- Java
- Stelle
- 913
- Fork
- 466
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Running this code in parallel only starts one build, since they all refere to the same queue item
I am creating new jenkins server for each thread but using the same credentials
` try {
MTJenkinsUtil mtJenkinsUtil = new MTJenkinsUtil();
JenkinsServer jenkinsServer = mtJenkinsUtil.getJenkinsServer();
Job myJob = jenkinsServer.getJob(job);
String queue = myJob.build(params, true).getQueueItemUrlPart();
LOGGER.info(queue);
//BuildWithDetails buildWithDetails = qaJenkinsServer.
`
10:57:59.219 [pool-1-thread-3] INFO TestMTJobild - https://qajenkins/queue/item/5160/
10:57:59.225 [pool-1-thread-2] INFO TestMTJobild - https://qajenkins/queue/item/5160/
10:57:59.227 [pool-1-thread-1] INFO TestMTJobild - https://qajenkins/queue/item/5160/
10:57:59.227 [pool-1-thread-4] INFO TestMTJobild - https://qajenkins/queue/item/5160/
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start with the multithreaded call to Job.build(params, true) shown in the report and inspect how queue item URLs are returned for concurrent requests. Reproduce the four parallel calls using MTJenkinsUtil and determine the expected distinct queue behavior; done should include a verified fix and regression coverage for concurrent builds.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- api
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100