-
Notifications
You must be signed in to change notification settings - Fork 171
Provide an ability to enter build notes/parameters for a Manual step in the pipeline #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
derekxlu
wants to merge
423
commits into
geoffbullen:master
Choose a base branch
from
jenkinsci:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix checkstyle errors
better support for jobs within folders
…g pipelines with circular/diamond-shaped project dependencies.
…From with a version that isn't ambigiuous with respect to overloading
[FIXED JENKINS-22146] now preventing infinite recursions for circular project dependencies.
Upgrade to 1.554.2 to explicitly resolve an overload ambiguity
Handle missing permission to get first job.
Modifying PR #29 UI checkbox not necessary for marking a build as parametrized
This will fix the problem I described here: http://goo.gl/lYcNPa where it is not possible to manually trigger projects that are listed with spaces around the commas.
We have links broken in the pipeline view due to the links being relative instead of absolute (a '/' is missing)
Trim comma separated list of trigger projects
[JENKINS-24194] Update main.css - align build cards
Fix relative links on build pipeline
[FIXED Jenkins-23749] NPE when view contains no builds.
55bf26f
to
e256a81
Compare
c861995
to
f82592e
Compare
No need to declare an older matrix-auth version as a test dependency when matrix-auth is already declared as a compile time dependency with a later version.
No need to declare a depdendency on Jenkins test harness when the parent pom provides it already. Especially good to not include a compile time depdedency on Jenkins test harness. https://issues.jenkins.io/browse/JENKINS-72353 reports the issue
https://issues.jenkins.io/browse/JENKINS-72581 describes the failure with Jenkins 2.426.2. Does not fix the "Delete" button. That needs to be replaced with the modern version of delete that will use a modal dialog.
Bumps `selenium.version` from 4.25.0 to 4.26.0. Updates `org.seleniumhq.selenium:selenium-firefox-driver` from 4.25.0 to 4.26.0 - [Release notes](https://github.com/SeleniumHQ/selenium/releases) - [Commits](SeleniumHQ/selenium@selenium-4.25.0...selenium-4.26.0) Updates `org.seleniumhq.selenium:selenium-chrome-driver` from 4.25.0 to 4.26.0 - [Release notes](https://github.com/SeleniumHQ/selenium/releases) - [Commits](SeleniumHQ/selenium@selenium-4.25.0...selenium-4.26.0) Updates `org.seleniumhq.selenium:selenium-support` from 4.25.0 to 4.26.0 - [Release notes](https://github.com/SeleniumHQ/selenium/releases) - [Commits](SeleniumHQ/selenium@selenium-4.25.0...selenium-4.26.0) --- updated-dependencies: - dependency-name: org.seleniumhq.selenium:selenium-firefox-driver dependency-type: direct:development update-type: version-update:semver-minor - dependency-name: org.seleniumhq.selenium:selenium-chrome-driver dependency-type: direct:development update-type: version-update:semver-minor - dependency-name: org.seleniumhq.selenium:selenium-support dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…figure-entries.jelly` (#145)
…ildCardHelpers.jelly` (#146)
…n_dashboard.jelly` (#149)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of pull request, I created a new feature request at
https://issues.jenkins-ci.org/browse/JENKINS-38670