Ullrich Hafner
Ullrich Hafner
Can you please elaborate how and how often you invoke the step?
This is already tracked as https://issues.jenkins.io/browse/JENKINS-68677 The other new UI changes (tables, tooltips, etc.) need to be integrated there as well
From https://issues.jenkins-ci.org/browse/JENKINS-39203 it looks like that the new API has not been implemented here yet.
Interested in providing a PR? I think nobody has the time to look at new features right now.
This change was intentional so that we can better adjust the axis. Otherwise the axis would always start at zero.
> What is the reasoning to do this here? I think UI tests belong to a plugin like unit and integration tests (the idea is from @olivergondza, see https://github.com/jenkinsci/acceptance-test-harness/pull/556 for...
> Note that this will complicate infrastructure somewhat. [jenkinsci/plugin-compat-tester#249](https://github.com/jenkinsci/plugin-compat-tester/pull/249) I haven't looked in detail at those changes but I would assume that we would have two alternatives: a single module...
@NikolasFunction @Tjuri Are you still planning to update this PR? The longer you are waiting the more merge conflicts will occur...
> This is a serious bug impacting our consumption of 2.0.2, we have to rollback to 1.1.6 to see all the reports. That was actually the idea behind the 2.x...
> an example project or at least a pipeline would be helpful... I think it is easy to reproduce and to create a test case for that problem. Just the...