jenkinsci / jenkinsci/workflow-aggregator-plugin
[JENKINS-51980] Missing Build Trigger Section after Upgrade of Jenkins
- Dominant language
- No language data
- Stars
- 225
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
I've upgraded Jenkins (to 2.127) and now the Build Triggers section is not showing up any more on the job configuration page. I also had to upgrade some Plugins but afaik the Build Triggers section is directly integrated into Jenkins, right? So I would at least expect to be able to schedule builds periodically which is not the case.
The downgrade does not work again below 2.121 because the format of some plugins changed and when doing so the jobs don't appear any more.
I can't find anything on the changelog nor the documentation about that. I've tested a bunch of different security settings with no success.
---
Originally reported by techradar, imported from: Missing Build Trigger Section after Upgrade of Jenkins
mjdetullio
Raw content of original issue
I've upgraded Jenkins (to 2.127) and now the Build Triggers section is not showing up any more on the job configuration page. I also had to upgrade some Plugins but afaik the Build Triggers section is directly integrated into Jenkins, right? So I would at least expect to be able to schedule builds periodically which is not the case.
The downgrade does not work again below 2.121 because the format of some plugins changed and when doing so the jobs don't appear any more.
I can't find anything on the changelog nor the documentation about that. I've tested a bunch of different security settings with no success.
Contributor guide
Research direction
No source files or tests are named. Start by reproducing the missing Build Triggers section on the Jenkins 2.127 job configuration page, comparing the upgraded plugins and security settings described in the report. Done means identifying why the section disappeared and restoring or clearly documenting the expected trigger behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100