jenkinsci / jenkinsci/parameterized-trigger-plugin
[JENKINS-65711] Faced few issues in 2.277.2 LTS version
- Dominant language
- Java
- Stars
- 77
- Forks
- 174
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 1
Description
I recently upgraded Jenkins version 2.277.2 LTS which is upgraded successfully but during testing found below issues.
1) Not able to trigger another job from Test to Production environment using 'Parametrized Remote Trigger' plugin.(Attached)
2) Not receiving all the values in Email notification but receiving only format as like below.
*****************
Subject: $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!
$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS:
Check console output at $BUILD_URL to view the results.
*********************
after all these issues I regressed to previous version.
---
Originally reported by dganesan, imported from: Faced few issues in 2.277.2 LTS version
Raw content of original issue
I recently upgraded Jenkins version 2.277.2 LTS which is upgraded successfully but during testing found below issues.
1) Not able to trigger another job from Test to Production environment using 'Parametrized Remote Trigger' plugin.(Attached)
2) Not receiving all the values in Email notification but receiving only format as like below.
*****************
Subject: $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS:
Check console output at $BUILD_URL to view the results.
*********************after all these issues I regressed to previous version.
1 attachment
- [error.PNG](https://issues.jenkins.io/secure/attachment/54873/error.PNG)
> 
Contributor guide
Research direction
Start by reproducing the two reported problems in the parameterized-trigger-plugin with Jenkins 2.277.2 LTS, using the attached error.PNG and the described trigger and email configurations. No source files or tests are named; done would require isolating whether either regression belongs to this plugin and documenting or fixing both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100