With the recent change that broke the existing configuration, we are looking at adding testing for the Jira plugin.
Our Jenkins is managed as part of an automated CI/CD workflow that will update Jenkins and any plugins on a regular basis. As part of this we have some tests that run to ensure things will work as expected.
The issue is that Jira will gracefully fail when we run jiraSendDeploymentInfo (or similar commands). Which is understandable and is useful for most use cases. But for this particular script we need a way to verify it actually fails. Ideally with another argument saying graceful exit=false or something like that.
Or if there is another alternative to test this. Otherwise we may need to lock the Jira plugin which is less than ideal.
What feature do you want to see added?
With the recent change that broke the existing configuration, we are looking at adding testing for the Jira plugin.
Our Jenkins is managed as part of an automated CI/CD workflow that will update Jenkins and any plugins on a regular basis. As part of this we have some tests that run to ensure things will work as expected.
The issue is that Jira will gracefully fail when we run jiraSendDeploymentInfo (or similar commands). Which is understandable and is useful for most use cases. But for this particular script we need a way to verify it actually fails. Ideally with another argument saying graceful exit=false or something like that.
Or if there is another alternative to test this. Otherwise we may need to lock the Jira plugin which is less than ideal.
Upstream changes
No response