[JENKINS-67068] Fix regression for branch names with slashes #44
Conversation
This file contains 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
As a result of PR jenkinsci#29 it happens that some users cannot fetch branches with slashes in their names anymore. Regression from: JENKINS-65796
|
Waited for feedback in linked issue. Seems to fix it. Ready for review. |
lafriks
approved these changes
Nov 24, 2021
viceice
added a commit
to visualon/jenkins-gitea-plugin
that referenced
this pull request
Nov 24, 2021
* Enable cd workflow (#35) * Enable cd workflow Signed-off-by: Steven Kriegler <61625851+justusbunsi@users.noreply.github.com> * Add missing GitHub workflow Signed-off-by: Steven Kriegler <61625851+justusbunsi@users.noreply.github.com> * Update .github/workflows/cd.yaml Co-authored-by: Lauris BH <lauris@nix.lv> * Switch back to classic version syntax Co-authored-by: Lauris BH <lauris@nix.lv> * Bump version to 1.5.0 (jenkinsci#42) Additionally: Fix tag/release template to match previous releases * Fix release versioning + incremental builds (jenkinsci#43) * Add alt-texts to badges This is a commit for letting the status checks fail. * Lower the release version * Re-Add changelist to version * Opt-out incremental suffix during release See: jenkins-infra/jenkins-maven-cd-action#13 * Auto-incrementalify after release * Fix JENKINS-67068 (jenkinsci#44) As a result of PR #29 it happens that some users cannot fetch branches with slashes in their names anymore. Regression from: JENKINS-65796 Co-authored-by: Steven <61625851+justusbunsi@users.noreply.github.com> Co-authored-by: Lauris BH <lauris@nix.lv>
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.
As a result of PR #29 it happens that some users cannot fetch branches
with slashes in their names anymore.
Looks like it's an issue with manually triggering jobs.
Regression from: JENKINS-65796
Fixes: JENKINS-67068