jenkinsci / jenkinsci/workflow-cps-plugin

[JENKINS-47028] Replaying a job loads Jenkinsfile from Github but is replaced by custom input

Open
#1,365 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:workflow-cps-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
186
Forks
212
Avg merge
12h 12m
Merged PRs (30d)
8

Description

Hello together!

I've noticed that when you replay a build and make changes to the Jenkinsfile in the text area in the browser (and therefor basically replace it), it still tries to load the Jenkinsfile from source, which is unnecessary. I only noticed because we're already running tight with the Github API rate limit (which is of course unrelated).

Example:

Replayed #21
14:55:40 Connecting to https://api.github.com using some-user/****** (checkout)
14:55:40 GitHub API Usage: Current quota has 2147 remaining (0 under budget). Next quota of 5000 in 30 min
Obtained Jenkinsfile from 8522ab599dbab8763d57475e2879e5fd8aca1fd1

 


Originally reported by sneils, imported from: Replaying a job loads Jenkinsfile from Github but is replaced by custom input
  • status: Open
  • priority: Minor
  • component(s): workflow-cps-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 2
  • imported: 2025-12-07
Raw content of original issue

Hello together!

I've noticed that when you replay a build and make changes to the Jenkinsfile in the text area in the browser (and therefor basically replace it), it still tries to load the Jenkinsfile from source, which is unnecessary. I only noticed because we're already running tight with the Github API rate limit (which is of course unrelated).

Example:

Replayed #21
14:55:40 Connecting to https://api.github.com using some-user/****** (checkout)
14:55:40 GitHub API Usage: Current quota has 2147 remaining (0 under budget). Next quota of 5000 in 30 min
Obtained Jenkinsfile from 8522ab599dbab8763d57475e2879e5fd8aca1fd1

 

environment
Jenkins v2.6.2<br/>
Pipeline v2.5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the workflow-cps-plugin replay flow and reproduce the reported behavior with a replayed build whose Jenkinsfile is edited in the browser. Trace why the replay still loads the Jenkinsfile from GitHub and verify that the unnecessary source lookup no longer occurs while the custom input is used.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.