jenkinsci / jenkinsci/github-issues-plugin
Jenkins LTS having issue with prism-api and Timestamper plugin
- Lingua principale
- Java
- Stelle
- 5
- Fork
- 5
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
I am having issues with the latest n-1 Jenkins LTS version as well with the plugins Timestamper and Prisum APi Plugin. Both need antisamy-markup-formatter, but different versions. I do have 173 on the Docker image, but while loading, it is conflicting. Below is the error that I am getting during the initial loading.
```
Timestamper (1.30)
Plugin is missing: antisamy-markup-formatter (173.v680e3a_b_69ff3)
Prism API Plugin (1.30.0-1)
Plugin is missing: antisamy-markup-formatter (162.v0e6ec0fcfcf6)
Some of the above failures also result in additional indirectly dependent plugins not being able to load.
Indirectly dependent plugins:
Coverage Plugin (2.7.1)
Failed to load: Prism API Plugin (prism-api 1.30.0-1)
Cobertura Plugin (1.17)
Failed to load: Code Coverage Plugin (code-coverage-api 4.99.0)
Configuration as Code Plugin (1971.vf9280461ea_89)
Failed to load: Prism API Plugin (prism-api 1.30.0-1)
Code Coverage Plugin (4.99.0)
Failed to load: Coverage Plugin (coverage 2.7.1)
Warnings Plugin (12.7.0)
Failed to load: Prism API Plugin (prism-api 1.30.0-1)
```
Jenkins version: `2.504.2` and latest one
I am running the Jenkins process as a container in the VM. It's an air-gapped environment, so I can't download and install the plugin; the only way is to create the Docker image.
Any help will be much appreciated.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start with the Jenkins 2.504.2 startup log in the air-gapped Docker image and the listed Timestamper, Prism API, and antisamy-markup-formatter versions. Determine whether the image can load the declared plugin set without dependency conflicts; done means Jenkins starts with the affected dependent plugins loading successfully.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- docker, java
- Ambito
- ci-cd
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100