jenkinsci / jenkinsci/incrementals-tools
consume-incrementals profile should be activated on demand not by default
- Dominant language
- Java
- Stars
- 21
- Forks
- 16
- Avg merge
- 1h 21m
- Merged PRs (30d)
- 3
Description
### Jenkins and plugins versions report
By activating the profile unconditionally things like dependabot or other tools should/will see it as active and can do things like propose PRs for incremental versions.
the profile should only be activated where developers explicity desire it,
for exanple by adding a marker file in CI, by activating the profile sporadically locally for testing (`-Pconsume-incrementals`) or activating the profile more sidely by setting MAVEN_ARGS or setting the profile to be active in their settings.xml
### What Operating System are you using (both controller, and any agents involved in the problem)?
All
### Reproduction steps
incrementalify a plugin
add an incremental dependency to the plugin
run mvn test
### Expected Results
the build should fail as the dependency can not be found (until the `consume-incrementals` is activated)
### Actual Results
the build passes, and the incremental revision is fixed.
### Anything else?
https://github.com/jenkinsci/bom/pull/6234#issuecomment-5283694324
https://github.com/jenkinsci/archetypes/pull/953
https://github.com/jenkins-infra/jenkins.io/pull/9339
### Are you interested in contributing a fix?
_No response_
Contributor guide
Research direction
Start with the Maven profile configuration responsible for consume-incrementals and reproduce the issue by incrementalifying a plugin, adding an incremental dependency, and running mvn test. Done means the build fails without explicit profile activation and works when consume-incrementals is enabled through the documented mechanisms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100