[JIRA] (JENKINS-32308) NoSuchMethodError: hudson.scm.SubversionSCM.getLocations
Title: Message Title David Pärsson assigned an issue to Unassigned Jenkins / JENKINS-32308 NoSuchMethodError: hudson.scm.SubversionSCM.getLocations Change By: David Pärsson Assignee: David Pärsson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title David Pärsson commented on JENKINS-55460 Re: Cleaning of svn workspace broken in 2.157 I'm sorry to let you know that this plugin isn't under active development anymore. If you can provide a pull request that fixes this I'd be happy to review it though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title David Pärsson assigned an issue to Unassigned Jenkins / JENKINS-55460 Cleaning of svn workspace broken in 2.157 Change By: David Pärsson Assignee: David Pärsson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-50321 Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin Change By: David Pärsson Component/s: github-branch-source-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title David Pärsson commented on JENKINS-50321 Re: Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin All right, I'll watch that. Thanks for a very fast response! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-50321
Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Change By:
David Pärsson
In a job created by the GitHub Branch Source plugin, {{git lfs pull}} fails with {{Bad credentials}} when building pull requests merged with the target branch.It works fine when building any branch separately. Here's the build log:{code:java}Started by user AnonymousConnecting to https://api.github.com using github-user/** (GitHub username and password for github-user)Checking out git https://github.com/acme-inc/repo.git into /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script to read Jenkinsfile> git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository> git config remote.origin.url https://github.com/acme-inc/repo.git # timeout=10Cleaning workspace> git rev-parse --verify HEAD # timeout=10Resetting working tree> git reset --hard # timeout=10> git clean -fdx # timeout=10Fetching without tagsFetching upstream changes from https://github.com/acme-inc/repo.git> git --version # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git fetch --no-tags --progress https://github.com/acme-inc/repo.git +refs/pull/512/head:refs/remotes/origin/PR-512 +refs/heads/master:refs/remotes/origin/masterMerging remotes/origin/master commit ac1ba744ee37a24027fb05a662b8ad79a675a19f into PR head commit f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeafEnabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull origin> git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f # timeout=10Enabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull originGitHub has been notified of this commit’s build resulthudson.plugins.git.GitException: Command "git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f" returned status code 128:stdout: stderr: Downloading path/to/some_file.zip (292 KB)Error downloading object: path/to/some_file.zip (b7bf2ce): Smudge error: Error downloading path/to/some_file.zip (b7bf2ceb57d399cd89d339f2cddf5c355979b580861346d7e1251a60bc3fbfe9): batch response: Bad credentialsErrors logged to /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script/.git/lfs/logs/20180321T163523.475698065.logUse `git lfs logs last` to view the log.error: external filter 'git-lfs filter-process' failedfatal: path/to/some_file.zip: smudge filter lfs failedat org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1964)at
[JIRA] (JENKINS-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-50321
Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Change By:
David Pärsson
In a job created by the GitHub Branch Source plugin, {{git lfs pull}} fails with {{Bad credentials}} when building pull requests merged with the target branch.It works fine when building any branch separately. Here's the build log:{code:java}Started by user AnonymousConnecting to https://api.github.com using github-user/** (GitHub username and password for github-user)Checking out git https://github.com/acme-inc/repo.git into /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script to read Jenkinsfile> git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository> git config remote.origin.url https://github.com/acme-inc/repo.git # timeout=10Cleaning workspace> git rev-parse --verify HEAD # timeout=10Resetting working tree> git reset --hard # timeout=10> git clean -fdx # timeout=10Fetching without tagsFetching upstream changes from https://github.com/acme-inc/repo.git> git --version # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git fetch --no-tags --progress https://github.com/acme-inc/repo.git +refs/pull/512/head:refs/remotes/origin/PR-512 +refs/heads/master:refs/remotes/origin/masterMerging remotes/origin/master commit ac1ba744ee37a24027fb05a662b8ad79a675a19f into PR head commit f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeafEnabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull origin> git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f # timeout=10Enabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull originGitHub has been notified of this commit’s build resulthudson.plugins.git.GitException: Command "git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f" returned status code 128:stdout: stderr: Downloading path/to/some_file.zip (292 KB)Error downloading object: path/to/some_file.zip (b7bf2ce): Smudge error: Error downloading path/to/some_file.zip (b7bf2ceb57d399cd89d339f2cddf5c355979b580861346d7e1251a60bc3fbfe9): batch response: Bad credentialsErrors logged to /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script/.git/lfs/logs/20180321T163523.475698065.logUse `git lfs logs last` to view the log.error: external filter 'git-lfs filter-process' failedfatal: path/to/some_file.zip: smudge filter lfs failedat org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1964)at
[JIRA] (JENKINS-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title David Pärsson created an issue Jenkins / JENKINS-50321 Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin Issue Type: Bug Assignee: Mark Waite Attachments: 20180321T164155.656172294.log Components: git-plugin, github-branch-source-plugin Created: 2018-03-21 15:50 Environment: Jenkins 2.89.4 GitHub Branch Source Plugin 2.3.3 (latest) Git plugin 3.8.0 (latest) git 2.11.0 git-lfs 2.4.0 Priority: Major Reporter: David Pärsson In a job created by the GitHub Branch Source plugin, git lfs pull fails with Bad credentials when building pull requests merged with the target branch. It works fine when building any branch separately. Here's the build log: Started by user Anonymous Connecting to https://api.github.com using github-user/** (GitHub username and password for github-user) Checking out git https://github.com/acme-inc/repo.git into /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script to read Jenkinsfile > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/acme-inc/repo.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Fetching without tags Fetching upstream changes from
[JIRA] (JENKINS-42322) Docker rm/stop/... commands killed by the timeout, failing builds
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-42322
Docker rm/stop/... commands killed by the timeout, failing builds
Change By:
David Pärsson
Summary:
Fail to Docker rm a container started with inside {} /stop/... commands killed by the timeout, failing builds
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson commented on JENKINS-37144
Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
I just got this with 0.6 and everything else up to date:
> git fetch --tags --progress https://github.com//.git +refs/pull/*/head:refs/remotes/origin/pr/*
> git rev-parse origin/PR-216^{commit} # timeout=10
> git rev-parse origin1/PR-216^{commit} # timeout=10
> git rev-parse PR-216^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson reopened an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson commented on JENKINS-37144 Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build For me this is only an issue in multi-branch-project, and not in workflow-multibranch. Switching to the latter resolved my issues (and gave other benefits as well). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39247) Add support for concurrent builds in Jenkins
Title: Message Title David Pärsson commented on JENKINS-39247 Re: Add support for concurrent builds in Jenkins May be related to JENKINS-32715. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39247) Add support for concurrent builds in Jenkins
Title: Message Title David Pärsson created an issue Jenkins / JENKINS-39247 Add support for concurrent builds in Jenkins Issue Type: New Feature Assignee: Unassigned Components: shiningpanda-plugin Created: 2016/Oct/25 3:00 PM Priority: Major Reporter: David Pärsson How to (sometimes) reproduce: Create a Jenkins job with Execute concurrent builds if necessary checked, and a Virtualenv Builder running sleep 20 or something similar. Start two builds that will be running at the same time. Expected result: The two builds should be running with different virtualenvs. Actual result: The two builds are running using the same virtualenv. Add Comment
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials of the type _Username with password_ using my predefined user with username {{jenkins-37144}} and password {{37144-jenkins}}. That is a GitHub user which has a repository with an open pull request.# Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job# Run the job for the pull request and watch it fail with the error described below*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}*Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials of the type _Username with password_ using my predefined user with username {{jenkins-37144}} and password {{37144-jenkins}}. That user has a repository with an open pull request. # Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job# Run the job for the pull request and watch it fail with the error described below*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}*Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials of the type _Username with password_ using my predefined user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job# Run the job for the pull request and watch it fail with the error described below* Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat} *Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for of the type _Username with password_ using my test predefined user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job# Run the job for the pull request and watch it fail with the error described below*Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job# Run the branch job for the pull request and watch it fail with the error described below*Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson commented on JENKINS-37144 Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Jesse Glick, I've added a detailed description on how to reproduce this issue. It's easily reproducible from scratch. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job # Run the job for the pull request and watch it fail with the error described below *Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add Comment
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job# Run the branch job for the pull request and watch it fail with the error described below*Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project:## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click advanced _Advanced..._ and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job*Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add Comment
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a _Freestyle Freestyle multi-branch project_ project: ## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click advanced and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job*Good to know:*- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.*The build fails with this in the log:*{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add Comment
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for a user with access to a GitHub repo with pull requests, for example my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle _Freestyle multi-branch project project_ ## Under _Branch Sources_, add _GitHub_ as a source## Configure {{jenkins-37144}} as the owner## Select the credentials from above## Select {{jenkins-pr-test-repo}} as the repository## Click advanced and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job * Good to know: * - All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing. * The build fails with this in the log: * {noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below. *How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for a user with access to a GitHub repo with pull requests, for example my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project - Under _Branch Sources_, add _GitHub_ as a source - Configure {{jenkins-37144}} as the owner - Select the credentials from above - Select {{jenkins-pr-test-repo}} as the repository - Click advanced and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the job Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.The build fails with this in the log:{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add Comment
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.*How to reproduce:*# Start a clean Jenkins installation, possibly in a Docker container# Install the {{github-branch-source-plugin}} and the {{multi-branch-project-plugin}}, possibly using {{install-plugins.sh multi-branch-project-plugin github-branch-source}}# Add access credentials for a user with access to a GitHub repo with pull requests, for example my test user with username {{jenkins-37144}} and password {{37144-jenkins}}.# Create a Freestyle multi-branch project - ## Under _Branch Sources_, add _GitHub_ as a source - ## Configure {{jenkins-37144}} as the owner - ## Select the credentials from above - ## Select {{jenkins-pr-test-repo}} as the repository - ## Click advanced and make sure _Build origin PRs (merged with base branch)_ is checked.# Run the branch indexing for the jobGood to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.The build fails with this in the log:{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit}fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add Comment
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Component/s: multi-branch-project-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson edited a comment on JENKINS-37144
Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
I'm actually no longer so sure about my assumptions. Modifying the branch specifier in the Jenkins job for the PR from {{PR-27}} to {{PR/27}} does not solve anything. Changing it to{noformat}*/PR-27{noformat}or{noformat}*/PR/27{noformat}makes the build pass, but then the status on the GitHub pull request is not updated after the initial "This pull request is scheduled to be built" message.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson edited a comment on JENKINS-37144
Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
I'm actually no longer so sure about my assumptions. Modifying the branch specifier in the Jenkins job for the PR from {{PR-27}} to {{PR/27}} does not solve anything. Changing it to{noformat}*/PR-27{noformat}or{noformat}*/PR/27{noformat}makes the build pass, but then the status on GitHub is not updated after the initial "This pull request is scheduled to be built" message .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson edited a comment on JENKINS-37144
Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
I'm actually no longer so sure about my assumptions. Modifying the branch specifier in the Jenkins job for the PR from {{PR-27}} to {{PR/27}} does not solve anything. Changing it to { { noformat} */PR-27 {noformat } } or { { noformat} */PR/27 {noformat } } makes the build pass, but then the status on GitHub is not updated.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson edited a comment on JENKINS-37144
Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
I'm actually no longer so sure about my assumptions. Modifying the branch specifier in the Jenkins job for the PR from {{PR-27}} to {{PR/27}} does not solve anything. Changing it to {{*/PR-27}} or {{*/PR/27}} makes the build pass, but then the status on GitHub is not updated.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson commented on JENKINS-37144 Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build I'm actually no longer so sure about my assumptions. Modifying the branch specifier in the Jenkins job for the PR from PR-27 to PR/27 does not solve anything. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.The build fails with this in the log:{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat}> git rev-parse origin/PR-27^{commit} origin/PR-27^{commit} fatal: ambiguous argument 'origin/PR-27^{commit}': unknown revision or path not in the working tree.> git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.The build fails with this in the log:{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat} $ > git rev-parse origin/ PR-27^{commit} origin/ PR-27^{commit}fatal: ambiguous argument ' origin/ PR-27^{commit}': unknown revision or path not in the working tree. $ > git rev-parse origin/PR/27^{commit}0bbc328a72b6083d593c1ae746f80fdba75aa61a{noformat}
Add Comment
This message was sent by
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.The build fails with this in the log:{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{origin/PR/27}} instead of {{origin/PR-27}} works:{noformat} $ git rev-parse PR-27^{commit} PR-27^{commit}fatal: ambiguous argument 'PR-27^{commit}': unknown revision or path not in the working tree.$ git rev-parse origin/PR/27^{commit} 0bbc328a72b6083d593c1ae746f80fdba75aa61a {noformat}
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Attachment: consoleText Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Attachment: build.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Attachment: full_build_log.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Attachment: consoleText Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing. Build The build fails with this in the log:{noformat} Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspaceCloning the remote Git repositoryCloning repository https://github.com/private/repo.git > git init /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace # timeout=10Fetching upstream changes from https://github.com/private/repo.git > git --version # timeout=10using .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git4891900535821671503.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git571539317037453523.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin1.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git8818716521234454688.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/pull/*/head:refs/remotes/origin/pr/* > git config --local --remove-section credential # timeout=10 > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson commented on JENKINS-37144 Re: Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Jesse Glick, thanks for your comment! Is this confirmed to be working? I believe that nothing else is needed to reproduce this. My guess is that GitHub have renamed their pull request branches from PR-27 to PR/27. I have updated the issue accordingly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository.- Builds are triggered by branch indexing.The build fails with this in the log:{noformat} > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}When running the same git commands manually, they fail as well, but providing {{ origin /PR/27}} instead of {{ origin /PR-27}} works:{noformat}git rev-parse origin/PR/27^{commit}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Attachment: build.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22253) Problems Parsing
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-22253
Problems Parsing
Change By:
David Pärsson
{ quote noformat }23:45:17 GitHub pull request #11340 of commit 65a9359e86ae45224b8154957f5a81dcf743d305 automatically merged.23:45:17 [EnvInject] - Loading node environment variables.23:45:17 Building in workspace /var/lib/jenkins/jobs/salt-pr-build/workspace23:45:17 23:45:17 Deleting project workspace... done23:45:17 23:45:17 Cloning the remote Git repository23:45:17 Cloning repository https://github.com/saltstack/salt.git23:45:17 Fetching upstream changes from https://github.com/saltstack/salt.git23:45:44 Fetching upstream changes from https://github.com/saltstack/salt.git23:45:45 FATAL: Command "git rev-parse origin/pr/11340/merge^{commit}" returned status code 128:23:45:45 stdout: origin/pr/11340/merge^{commit}23:45:45 23:45:45 stderr: fatal: ambiguous argument 'origin/pr/11340/merge^{commit}': unknown revision or path not in the working tree.23:45:45 Use '--' to separate paths from revisions23:45:45 23:45:45 hudson.plugins.git.GitException: Command "git rev-parse origin/pr/11340/merge^{commit}" returned status code 128:23:45:45 stdout: origin/pr/11340/merge^{commit}23:45:45 23:45:45 stderr: fatal: ambiguous argument 'origin/pr/11340/merge^{commit}': unknown revision or path not in the working tree.23:45:45 Use '--' to separate paths from revisions23:45:45 23:45:45 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1183)23:45:45 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1160)23:45:45 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1156)23:45:45 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:972)23:45:45 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:982)23:45:45 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:416)23:45:45 at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)23:45:45 at hudson.plugins.git.RevisionParameterAction.toRevision(RevisionParameterAction.java:83)23:45:45 at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:787)23:45:45 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:879)23:45:45 at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)23:45:45 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)23:45:45 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)23:45:45 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)23:45:45 at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134)23:45:45 at hudson.model.Run.execute(Run.java:1676)23:45:45 at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73)23:45:45 at hudson.model.ResourceController.execute(ResourceController.java:88)23:45:45 at hudson.model.Executor.run(Executor.java:231){ quote noformat }
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository. - Builds are triggered by branch indexing. Build log:{noformat}Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspaceCloning the remote Git repositoryCloning repository https://github.com/private/repo.git > git init /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace # timeout=10Fetching upstream changes from https://github.com/private/repo.git > git --version # timeout=10using .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git4891900535821671503.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git571539317037453523.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin1.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git8818716521234454688.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/pull/*/head:refs/remotes/origin/pr/* > git config --local --remove-section credential # timeout=10 > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the message in the log below.Good to know:- All "non-PR" builds work fine.- Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository. Build log: {noformat}Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspaceCloning the remote Git repositoryCloning repository https://github.com/private/repo.git > git init /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace # timeout=10Fetching upstream changes from https://github.com/private/repo.git > git --version # timeout=10using .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git4891900535821671503.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git571539317037453523.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin1.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git8818716521234454688.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/pull/*/head:refs/remotes/origin/pr/* > git config --local --remove-section credential # timeout=10 > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished:
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo). All builds fail with the following message in the log below.Good to know : - All "non-PR" builds work fine. - Everything outside of the screenshot is configured according to the defaults.- The pull request exists and has no conflicts with the base branch.- The GitHub repository is my organization's private repository. {noformat}Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspaceCloning the remote Git repositoryCloning repository https://github.com/private/repo.git > git init /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace # timeout=10Fetching upstream changes from https://github.com/private/repo.git > git --version # timeout=10using .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git4891900535821671503.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git571539317037453523.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin1.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git8818716521234454688.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/pull/*/head:refs/remotes/origin/pr/* > git config --local --remove-section credential # timeout=10 > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished:
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I have created a freestyle multi-branch project, and I've configured it to use the GitHub branch source plugin as shown on the attached screenshot. With this I am unable to build origin pull requests (from the same repo) for my freestyle multi-branch project with the GitHub Branch Source plugin . All builds fail with the following message:{noformat}Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspaceCloning the remote Git repositoryCloning repository https://github.com/private/repo.git > git init /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace # timeout=10Fetching upstream changes from https://github.com/private/repo.git > git --version # timeout=10using .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git4891900535821671503.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git571539317037453523.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin1.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git8818716521234454688.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/pull/*/head:refs/remotes/origin/pr/* > git config --local --remove-section credential # timeout=10 > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat} I have configured Good to know:- All "non-PR" builds work fine.- Everything outside of the GitHub branch source plugin as shown on the attached screenshot , everything else is
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37144
Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Change By:
David Pärsson
I am unable to build origin pull requests (from the same repo) for my freestyle multi-branch project with the GitHub Branch Source plugin. All builds fail with the following message:{noformat}Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspaceCloning the remote Git repositoryCloning repository https://github.com/private/repo.git > git init /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace # timeout=10Fetching upstream changes from https://github.com/private/repo.git > git --version # timeout=10using .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git4891900535821671503.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git571539317037453523.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 > git config remote.origin1.url https://github.com/private/repo.git # timeout=10Fetching upstream changes from https://github.com/private/repo.gitusing .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git8818716521234454688.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/private/repo.git +refs/pull/*/head:refs/remotes/origin/pr/* > git config --local --remove-section credential # timeout=10 > git rev-parse origin/PR-27^{commit} # timeout=10 > git rev-parse origin1/PR-27^{commit} # timeout=10 > git rev-parse PR-27^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE{noformat}I have configured the GitHub branch source plugin as shown on the attached screenshot, everything else is according to the defaults. {{PR-27}} exists and has no conflicts with the base branch. The GitHub repository is my organization's private repository. All "non-PR" builds work fine.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Component/s: freestyle-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Change By: David Pärsson Component/s: freestyle-multibranch-plugin Environment: Jenkins LTS v2.7.1 (latest) GitHub Branch Source Plugin v1.8.1 (latest)GitHub API Plugin v1.76 (latest)GitHub Organization Folder Plugin v1.4 (latest)GitHub plugin v1.20.0 (latest)Git plugin v2.5.3 (latest) Multi-Branch Project Plugin v0.5.1 (latest)Branch API Plugin v1.10 (latest) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37144) Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build
Title: Message Title David Pärsson created an issue Jenkins / JENKINS-37144 Unable to build origin PRs with GitHub Branch Source Plugin: Couldn't find any revision to build Issue Type: Bug Assignee: Unassigned Attachments: jenkins-github-config.png Components: github-branch-source-plugin Created: 2016/Aug/03 11:40 AM Environment: Jenkins LTS v2.7.1 (latest) GitHub Branch Source Plugin v1.8.1 (latest) GitHub API Plugin v1.76 (latest) GitHub Organization Folder Plugin v1.4 (latest) GitHub plugin v1.20.0 (latest) Git plugin v2.5.3 (latest) Priority: Major Reporter: David Pärsson I am unable to build origin pull requests (from the same repo) for my freestyle multi-branch project with the GitHub Branch Source plugin. All builds fail with the following message: Started by user anonymous Building in workspace /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace Cloning the remote Git repository Cloning repository https://github.com/private/repo.git > git init /var/lib/jenkins/jobs/test-multi-branch/branches/PR-27/workspace # timeout=10 Fetching upstream changes from https://github.com/private/repo.git > git --version # timeout=10 using .gitcredentials to set credentials > git config --local credential.username my-user # timeout=10 > git config --local credential.helper store --file=/tmp/git4891900535821671503.credentials # timeout=10 > git -c core.askpass=true fetch
[JIRA] (JENKINS-37028) Github multibranch checkout
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-37028
Github multibranch checkout
Change By:
David Pärsson
Hi,I use github organisation plugin to build jobs inside my github orga.Now I ran into following problem:It seems that "checkout scm" does nothing for "non-master branches":it does not checkout the branch, the directory is stays empty. Only for the master branch it works.https://gist.github.com/Flow86/6b6570bc95c24d60fb06baec09103b7dthe part of my jenkinsfile already failing is this:{ { code} node('master') {stage name:"Checkout", concurrency:1checkout scmsh """set -x git submodule foreach "git reset --hard || true" || true git reset --hard || true git submodule update --init || true """stash includes: '**, .git/', excludes: 'ws/**', name: 'source', useDefaultExcludes: falsesh "env"wspwd = pwd()} {code } }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you
[JIRA] (JENKINS-37116) Add support for Jenkins Pipeline to the shiningpanda-plugin
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-37116 Add support for Jenkins Pipeline to the shiningpanda-plugin Change By: David Pärsson Summary: Jenkins pipeline Add support for Jenkins Pipeline to the shiningpanda-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37116) Jenkins pipeline support
Title: Message Title David Pärsson created an issue Jenkins / JENKINS-37116 Jenkins pipeline support Issue Type: New Feature Assignee: Unassigned Components: shiningpanda-plugin Created: 2016/Aug/02 10:48 AM Labels: pipeline Priority: Major Reporter: David Pärsson As a user of Jenkins and the ShiningPanda plugin I want to be able to define build steps from the ShiningPanda plugin in a Jenkinsfile So that builds in my pipelines can use virtualenv Add Comment
[JIRA] [svn-revert-plugin] (JENKINS-32308) NoSuchMethodError: hudson.scm.SubversionSCM.getLocations
Title: Message Title David Pärsson commented on JENKINS-32308 Re: NoSuchMethodError: hudson.scm.SubversionSCM.getLocations Yes, as far as I can see everything looks fine. Have you tried running this with as few other plugins enabled as possible? I'm not actively maintaining this plugin, so I have not tried this plugin on any recent Jenkins version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title
David Pärsson edited a comment on JENKINS-28578
Re: The NodeJS plugin breaks the Xvnc plugin
When modifying {{/usr/bin/vncserver}} the Xvnc Command line, in Jenkins' system configuration, to only print be {{ echo $PATH}} I get this result:{code}[TEST-nodejs-xvnc] $ /usr/bin/vncserver :88 -geometry 1920x1280 echo ${ PATH is: } /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.38/bin:null{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Pärsson commented on JENKINS-28578 Re: The NodeJS plugin breaks the Xvnc plugin When modifying /usr/bin/vncserver to only print $PATH I get this result: [TEST-nodejs-xvnc] $ /usr/bin/vncserver :88 -geometry 1920x1280 PATH is: /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.38/bin:null Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds
Title: Message Title David Pärsson commented on JENKINS-25242 Re: p4-plugin: Doesn't do concurrent builds Good job! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Pärsson commented on JENKINS-25249 Re: Post-commit hook for P4 plugin Great news! I'll give it a try as soon as I find the time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds
Title: Message Title David Pärsson commented on JENKINS-25242 Re: p4-plugin: Doesn't do concurrent builds Changing it required me to start Jenkins like this, as described in the comments for JENKINS-14354: java -Dhudson.slaves.WorkspaceList=- -jar jenkins.war As far as I know, there's no way for a plugin to override this during runtime. But how come the Perforce plugin works for workspaces with @ signs? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds
Title: Message Title
David Pärsson edited a comment on JENKINS-25242
Re: p4-plugin: Doesn't do concurrent builds
I've now verified that when changing the separator from {{@}} to {{-}} , concurrent builds work with the P4 Plugin.However, I've also verified that the [Perforce Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin] can do concurrent builds with {{@}} in the workspace names.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds
Title: Message Title David Pärsson commented on JENKINS-25242 Re: p4-plugin: Doesn't do concurrent builds I've now verified that when changing the separator from @ to - concurrent builds work with the P4 Plugin. However, I've also verified that the Perforce Plugin can do concurrent builds with @ in the workspace names. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds
Title: Message Title David Prsson commented on JENKINS-25242 Re: p4-plugin: Doesn't do concurrent builds For concurrent builds on the same node, Jenkins creates workspaces named workspace, workspace@2, workspace@3 and so on. For what reasons does this not work with Perforce? I just found out that it's possible to change the separator character using this system property: -Dhudson.slaves.WorkspaceList=SEPARATOR. I'll try this tomorrow and get back to you with the results. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25242) p4-plugin: Doesn't do concurrent builds
Title: Message Title
David Prsson commented on JENKINS-25242
Re: p4-plugin: Doesn't do concurrent builds
I tried to get around this by using Manual (custom view) together with a workspace name like this: Jenkins-${JOB_NAME}-${NODE_NAME}-${EXECUTOR_NUMBER}-workspace. I thought this should work since the executor number is unique for concurrent builds when running on a single node (as I did), which should make the workspace name unique.
When running one build at a time, everything works fine, but when running several concurrent builds, I only managed to get the first of the concurrent builds to fetch files from the repository. Any other concurrent build's workspaces were empty. This happens every time when I launch a build while another build is running, even when the other build is done running its P4 commands.
I'm using the P4 Plugin v1.1.4 on Jenkins 1.565.3 (LTS). This issue is a blocker for us and many other large companies, requiring fast feedback for frequent commits.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Prsson commented on JENKINS-25249 Re: Post-commit hook for P4 plugin Would this be a standalone web service, needing to be hosted outside Jenkins and Perforce? I'm no expert in the inner workings of Perforce so this might be the best solution, but requiring a third piece of software to be hosted is a drawback to me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Prsson commented on JENKINS-25249 Re: Post-commit hook for P4 plugin What are the chances of this getting implemented any time soon? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Prsson commented on JENKINS-25249 Re: Post-commit hook for P4 plugin Suggestion 1 is similar to what the Subversion plugin does. The Subversion server is configured with a post-commit hook that makes a request to Jenkins over HTTP. One significant difference is that the request however also includes the changed paths as POST data, removing the need for Jenkins to ask the Subversion server for changes. See the Subversion plugin's wiki page for more details. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Prsson edited a comment on JENKINS-25249 Re: Post-commit hook for P4 plugin Suggestion Design 1issimilartowhattheSubversionplugindoes. The Tousethiswith Subversion ,theSubversion serverisconfiguredwithapost-commithookthatmakesarequesttoJenkinsoverHTTP.Onesignificantdifference fromyourdesign isthattherequest however alsoincludesthechangedpathsasPOSTdata,removingtheneedforJenkinstoasktheSubversionserverforchanges.Seethe[Subversionplugin'swikipage|https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin#SubversionPlugin-Postcommithook]formoredetails. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-revert-plugin] (JENKINS-15082) svn-revert-plugin: revert for failed builds, too
Title: Message Title David Prsson commented on JENKINS-15082 Re: svn-revert-plugin: revert for failed builds, too This plugin is not under active development. Patches/pull requests are welcome. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-29747) Add fallback filters
Title: Message Title David Prsson edited a comment on JENKINS-29747 Re: Add fallback filters Theprovidedpatchwascommitted totheSubversionrepositoryinthecommit withrevision41369. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-24579) Filter based on Job Labels
Title: Message Title David Prsson edited a comment on JENKINS-24579 Re: Filter based on Job Labels Isn'tthisalreadyimplemented? ItispossibletousetheReglar_expression_JobFiltertofilteronaNodelabel_expression_ ,butthisrequiresthejobtoberestrictedtoexecuteoncertainjoblabels . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-29747) Add fallback filters
Title: Message Title David Prsson created an issue Jenkins / JENKINS-29747 Add fallback filters Issue Type: New Feature Assignee: Jacob Robertson Attachments: fallback-filter.patch Components: view-job-filters-plugin Created: 03/Aug/15 11:44 AM Labels: pull_request Priority: Major Reporter: David Prsson I'd like this plugin to support fallback filters, that can be used to do one of the following things: include all jobs in a view if no jobs have been included by previous filters exclude all jobs from a view if all jobs have been included by previous filters An unit tested implementation of this is provided in the attached
[JIRA] [view-job-filters-plugin] (JENKINS-24579) Filter based on Job Labels
Title: Message Title David Prsson commented on JENKINS-24579 Re: Filter based on Job Labels Isn't this already implemented? It is possible to use the Reglar _expression_ Job Filter to filter on a Node label _expression_. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-29747) Add fallback filters
Title: Message Title David Prsson resolved as Fixed Jenkins / JENKINS-29747 Add fallback filters Change By: David Prsson Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-29747) Add fallback filters
Title: Message Title David Prsson commented on JENKINS-29747 Re: Add fallback filters The provided patch was committed with revision 41369. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-29747) Add fallback filters
Title: Message Title David Prsson edited a comment on JENKINS-29747 Re: Add fallback filters TheprovidedpatchwascommittedtotheSubversionrepositoryinthecommitwithrevision41369. Thelatestreleaseofthispluginis1.26.Thiswillbeincludedin_thenextrelease_ifit'snotrevertedbeforethat. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29672) Auto-focused form elements causes page to scroll to the bottom
Title: Message Title David Prsson commented on JENKINS-29672 Re: Auto-focused form elements causes page to scroll to the bottom Sorry, I didn't find that one. Thanks for pointing me to it! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29672) Auto-focused form elements causes page to scroll to the bottom
Title: Message Title David Prsson updated an issue Jenkins / JENKINS-29672 Auto-focused form elements causes page to scroll to the bottom Change By: David Prsson *Howtoreproduce:*#MakesureJenkinsisconfiguredwithmanyexecutorsorslaves,ormakeyourbrowserwindowsmall,sothattheBuildExecutorStatuslistdoesnotfitonthescreen,makingeverypagehaveascrollbar#Visitapagewithautomaticformfocusing,forexampletheloginornewjobpage*Expected:*Thefirstinputelementshouldbefocusedandthepageshouldbescrolledtothetop*Actual:*Thefirstinputelementisfocused,butthepageisscrolledtothebottomThisseemstobebecausetheelementisfocusedwhilethepageisrenderedfordeviceswithsmallscreens,withtheBuildExecutorStatustakingupfullpagewithandtheloginform beingplaced belowit.Whilethereisnolossoffunction,thisissuecausesinconvenience. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29672) Auto-focused form elements causes page to scroll to the bottom
Title: Message Title David Prsson created an issue Jenkins / JENKINS-29672 Auto-focused form elements causes page to scroll to the bottom Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Jul/15 9:17 AM Environment: Jenkins 1.596.3 (LTS) and 1.609.1 (LTS), Chrome and Safari Labels: user-experience ui Priority: Minor Reporter: David Prsson How to reproduce: Make sure Jenkins is configured with many executors or slaves, or make your browser window small, so that the Build Executor Status list does not fit on the screen, making every page have a scrollbar Visit a page with automatic form focusing, for example the login or new job page
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson assigned an issue to cliffano Jenkins / JENKINS-28578 The NodeJS plugin breaks the Xvnc plugin Change By: David Prsson Assignee: LevonSaldamli cliffano Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson edited a comment on JENKINS-28578 Re: The NodeJS plugin breaks the Xvnc plugin Thecustom-toolspluginseemstohavehad,andresolved,theexactsameproblemin [JENKINS-20560|https://issues.jenkins-ci.org/browse/JENKINS-20560] seemstohavehad,andresolved,theexactsameproblem . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson created an issue Jenkins / JENKINS-28578 The NodeJS plugin breaks the Xvnc plugin Issue Type: Bug Assignee: Levon Saldamli Components: nodejs-plugin, xvnc-plugin Created: 26/May/15 2:04 PM Environment: Jenkins v1.596.3 (LTS), NodeJS plugin v0.2.1 (latest) and Xvnc plugin 1.21 (latest) on Ubuntu 14.10 with vnc4server v4.1.1+xorg4.3.0-37ubuntu5.2 Priority: Major Reporter: David Prsson Enabling the NodeJS plugin on a job that has the Xvnc plugin enabled results in a broken Xvnc plugin. The following log is from such a build: Starting xvnc [TEST-nodejs-xvnc] $ /usr/bin/vncserver :76 -geometry 1920x1280 /usr/bin/env: perl: No such file or directory Starting xvnc [TEST-nodejs-xvnc] $ /usr/bin/vncserver :46 -geometry 1920x1280 /usr/bin/env: perl: No such file or directory Starting xvnc ... FATAL: Failed to run '/usr/bin/vncserver :22 -geometry 1920x1280' (exit code 127), blacklisting display #22; consider checking the Clean up before start option java.io.IOException: Failed to run '/usr/bin/vncserver :22 -geometry 1920x1280' (exit code 127), blacklisting display #22; consider checking the Clean up before start option at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:119) at
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title
David Prsson updated an issue
Jenkins / JENKINS-28578
The NodeJS plugin breaks the Xvnc plugin
Change By:
David Prsson
EnablingtheNodeJSpluginonajobthathastheXvncpluginenabledresultsinabrokenXvncplugin.Thefollowinglogisfromsuchabuild:{code:java} ... Startingxvnc[TEST-nodejs-xvnc]$/usr/bin/vncserver:76-geometry1920x1280/usr/bin/env:perl:NosuchfileordirectoryStartingxvnc[TEST-nodejs-xvnc]$/usr/bin/vncserver:46-geometry1920x1280/usr/bin/env:perl:NosuchfileordirectoryStartingxvnc...FATAL:Failedtorun'/usr/bin/vncserver:22-geometry1920x1280'(exitcode127),blacklistingdisplay#22;considercheckingtheCleanupbeforestartoptionjava.io.IOException:Failedtorun'/usr/bin/vncserver:22-geometry1920x1280'(exitcode127),blacklistingdisplay#22;considercheckingtheCleanupbeforestartoptionathudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:119)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)athudson.plugins.xvnc.Xvnc.setUp(Xvnc.java:79)athudson.model.Build$BuildExecution.doRun(Build.java:154)athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)athudson.model.Run.execute(Run.java:1758)athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)athudson.model.ResourceController.execute(ResourceController.java:89)athudson.model.Executor.run(Executor.java:240){code}AtfirstIthoughtthatthiswasaPATHissue,buttheXvncpluginworksifIdisabletheNodeJSpluginandusetheEnvInjectplugintosetthePATHtowhattheNodeJSpluginwouldsetitto.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson assigned an issue to Unassigned Jenkins / JENKINS-28578 The NodeJS plugin breaks the Xvnc plugin Change By: David Prsson Assignee: LevonSaldamli Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson assigned an issue to Unassigned Jenkins / JENKINS-28578 The NodeJS plugin breaks the Xvnc plugin Change By: David Prsson Component/s: xvnc-plugin Assignee: cliffano Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson edited a comment on JENKINS-28578 Re: The NodeJS plugin breaks the Xvnc plugin [JENKINS-20560 ]( | https://issues.jenkins-ci.org/browse/JENKINS-20560 ) ] seemstohavehad,andresolved,theexactsameproblem Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson edited a comment on JENKINS-28578 Re: The NodeJS plugin breaks the Xvnc plugin [ JENKINS-20560]( https://issues.jenkins-ci.org/browse/JENKINS-20560 ] ) seemstohavehad,andresolved,theexactsameproblem Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson assigned an issue to Levon Saldamli Jenkins / JENKINS-28578 The NodeJS plugin breaks the Xvnc plugin Change By: David Prsson Component/s: xvnc-plugin Assignee: LevonSaldamli Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson commented on JENKINS-28578 Re: The NodeJS plugin breaks the Xvnc plugin https://issues.jenkins-ci.org/browse/JENKINS-20560 seems to have had, and resolved, the exact same problem Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-28578) The NodeJS plugin breaks the Xvnc plugin
Title: Message Title David Prsson updated an issue Jenkins / JENKINS-28578 The NodeJS plugin breaks the Xvnc plugin Change By: David Prsson Environment: Jenkinsv1.596.3(LTS), NodeJSpluginv0.2.1(latest)andXvncplugin1.21(latest)on Jenkinsv1.596.3(LTS), Ubuntu14.10withvnc4serverv4.1.1+xorg4.3.0-37ubuntu5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
David Pärsson commented on JENKINS-24432 SVN modules in sub directories are not removed by SVN Workspace Cleaner Thank you for reporting. To me this was a known bug/limitation. This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interested, and need any pointers on how to do it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
David Pärsson edited a comment on JENKINS-24432 SVN modules in sub directories are not removed by SVN Workspace Cleaner Thank you for reporting. To me this was a known bug/limitation. This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interested, and need any pointers on how to do it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
David Pärsson edited a comment on JENKINS-24432 SVN modules in sub directories are not removed by SVN Workspace Cleaner Thank you for reporting. This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interested, and need any pointers on how to do it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
David Pärsson edited a comment on JENKINS-24432 SVN modules in sub directories are not removed by SVN Workspace Cleaner Thank you for reporting. This plugin is not currently under that active development, but we're happy to accept pull requests. Please let me know if you're interestedand in need of any pointers on how to do it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
David Pärsson updated JENKINS-24432 SVN modules in sub directories are not removed by SVN Workspace Cleaner Change By: David Pärsson (26/Aug/14 11:44 AM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
David Pärsson commented on JENKINS-24432 SVN modules in sub directories are not removed by SVN Workspace Cleaner I changed my mind. A release with version 1.1 is published and should hopefully appear soon. It contains support for this feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-24432) SVN modules in sub directories are not removed by SVN Workspace Cleaner
David Pärsson resolved JENKINS-24432 as Fixed SVN modules in sub directories are not removed by SVN Workspace Cleaner Change By: David Pärsson (26/Aug/14 11:57 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-19100) Unable to wipe out workspace with file named: knäpplpåärtillvåraförlor.txt
David Pärsson commented on JENKINS-19100 Unable to wipe out workspace with file named: knäpplpåärtillvåraförlor.txt Are you really sure that this is related to the svn-workspace-cleaner plugin? P4 workspaces are not supported. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
