-
Task
-
Resolution: Won't Do
-
Minor
-
-
Evergreen - Milestone 2
With JENKINS-50164, we are introducing system properties to better differentiate durable and less durable build data.
To test this, we must run a job. This is a bit less than trivial with the current setup, so I'm filing this as a separate task to better clarify the intent and the task being worked on.
I think it's time to introduce something like a test mode. A mode where where we will have data to help us test things that will be used in production, but that we obviously do not want to ship like a smoke testing job for instance.
- relates to
-
JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
-
- Closed
-
[JENKINS-50940] Introduce a way to have build data only during Evergreen testing
Assignee | Original: R. Tyler Croy [ rtyler ] | New: Baptiste Mathus [ batmat ] |
Link |
New:
This issue relates to |
Rank | New: Ranked higher |
Sprint | Original: Essentials - Milestone 1 [ 511 ] | New: Essentials - Milestone 2 [ 516 ] |
Labels | Original: essentials essentials-triggered | New: essentials essentials-triggered evergreen |
Labels | Original: essentials essentials-triggered evergreen | New: essentials essentials-triggered evergreen evergreen-triggered |
Labels | Original: essentials essentials-triggered evergreen evergreen-triggered | New: evergreen evergreen-triggered |
Assignee | Original: Baptiste Mathus [ batmat ] |
"bit less than trivial": just had another quick look when testing manually a build, so yes: confirmed.
The fact we have no executor on the master makes triggering a job non that trivial, since it then requires tackling for instance
JENKINS-49866so that we do have an agent to run a freestyle job on (FreeStyle, because pipeline would mean we need to install the plugin at startup, which is currently not done yet, and will be done through the update/upgrade lifecycle, which rtyler was working on the design on with JEP-307).