[JIRA] (JENKINS-54371) Monitoring plugin not pushing slave metrics to InfluxDB
Title: Message Title Puneeth Nanjundaswamy created an issue Jenkins / JENKINS-54371 Monitoring plugin not pushing slave metrics to InfluxDB Issue Type: Bug Assignee: evernat Components: monitoring-plugin Created: 2018-10-31 15:28 Priority: Blocker Reporter: Puneeth Nanjundaswamy The javamelody monitoring plugin doesn't seem to send metrics of slaves to InfluxDB. I can only see metrics from the master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-49312) AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38
Title: Message Title Puneeth Nanjundaswamy edited a comment on JENKINS-49312 Re: AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38 This is till an issue. so reopening it 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-49312) AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38
Title: Message Title Puneeth Nanjundaswamy reopened an issue This is till an issue. Jenkins / JENKINS-49312 AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38 Change By: Puneeth Nanjundaswamy Resolution: Not A Defect Status: Closed Reopened 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
[JIRA] (JENKINS-49312) AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38
Title: Message Title Puneeth Nanjundaswamy edited a comment on JENKINS-49312 Re: AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38 are facing the same issue too. We are now at Jenkins 2.89.4 and EC2 plugin 1.38 . [~bekzot89] Why is it not a defect? 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-49312) AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-49312 Re: AWS EC2 Plugin is not able to launch instances automatically on 1.37, 1.38 are facing the same issue too. We are now at Jenkins 2.89.4 and EC2 plugin 1.38 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-38729) Jobs not dequeued when all executors are free
Title: Message Title Puneeth Nanjundaswamy created an issue Jenkins / JENKINS-38729 Jobs not dequeued when all executors are free Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 2016/Oct/05 9:48 AM Environment: Jenkins: 2.7.1 Build Blocker Plugin: 1.7.3 Priority: Minor Reporter: Puneeth Nanjundaswamy Problem: I have two jobs that should not run in parallel. Job A runs when Job B is not running and vice versa. When no jobs are running and Job A queued (say when someone opens a PR) this job is always in the queue and not dequeued even though all the executors are free and no other job is running. This issue occurs when only this is the only job queued for execution in Jenkins. When a second job is queued, the first job starts executing. Seems like an issue with probing the queue. Workaround: The only effective workaround I could find was to have a dummy "hello world" job that runs every minute so that no jobs are always queued even though all executors are available and no conflicting jobs are running. Stacktrace: Oct 05, 2016 8:37:21 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.Queue$MaintainTask@3d40ed96 failed java.lang.NullPointerException at hudson.plugins.buildblocker.BlockingJobsMonitor.checkNodeForQueueEntries(BlockingJobsMonitor.java:108) at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.checkAccordingToProperties(BuildBlockerQueueTaskDispatcher.java:171) at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.checkForBlock(BuildBlockerQueueTaskDispatcher.java:127) at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canTake(BuildBlockerQueueTaskDispatcher.java:110) at hudson.model.Queue$JobOffer.canTake(Queue.java:258) at hudson.model.Queue.maintain(Queue.java:1532) at
[JIRA] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock Any update on this? :/ Jenkins: 2.7.1 Build Blocker Plugin: 1.7.3 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-20427 Re: Build Parameter variable in branch name causes polling to detect false changes in GIT Mark Waite Thanks for the response. I have created a seperate JIRA ticket with all details. Here is the link: https://issues.jenkins-ci.org/browse/JENKINS-38406 Let me know in case of more info 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-38411) Multijob view fails to display content
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-38411 Re: Multijob view fails to display content I am facing this issue as well. In the build phase, adding a build step along with the Multijob phase causes this 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-20427 Re: Build Parameter variable in branch name causes polling to detect false changes in GIT @Nicolas De Loof Any updates on this? This is is a major issue for us as sometimes builds fail because of network issue and when we try to rerun, the job picks up some random branch! 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Puneeth Nanjundaswamy updated an issue Jenkins / JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT Change By: Puneeth Nanjundaswamy Priority: Minor Major 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-29896) git plugin chooses a wrong scheme for remote polling with passed variable with wildcards
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-29896 Re: git plugin chooses a wrong scheme for remote polling with passed variable with wildcards I'm facing the same issue. Reported by me here: https://issues.jenkins-ci.org/browse/JENKINS-38406 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-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1.**Job config**build parameters: sha1 (default value: origin/) so technically, the job should fail as there is no branch called `origin/`Branches to build -1 : origin/masterBranches to build - 2: origin/developBranches to build - 3: \ $\{sha1\}Refspec: +refs/heads/\*:refs/remotes/origin/\* +refs/pull/\*:refs/remotes/origin/pr/\*- [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1.**Job config**build parameters: sha1 (default value: origin/) so technically, the job should fail as there is no branch called `origin/`Branches to build -1 : origin/masterBranches to build - 2: origin/developBranches to build - 3: ${sha1}Refspec: ` +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* ` - [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1.**Job config**build parameters: sha1 (default value: origin/) so technically, the job should fail as there is no branch called `origin/`Branches to build -1 : origin/masterBranches to build - 2: origin/developBranches to build - 3: ${sha1}Refspec: +refs/heads/ \ *:refs/remotes/origin/ \ * +refs/pull/ \ *:refs/remotes/origin/pr/ \ *- [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1.**Job config**build parameters: sha1 (default value: origin/) so technically, the job should fail as there is no branch called `origin/`Branches to build -1 : origin/masterBranches to build - 2: origin/developBranches to build - 3: \ $ \ {sha1 \ }Refspec: +refs/heads/\*:refs/remotes/origin/\* +refs/pull/\*:refs/remotes/origin/pr/\*- [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1.**Job config**build parameters: sha1 (default value: origin/) so technically, the job should fail as there is no branch called `origin/`Branches to build -1 : origin/masterBranches to build - 2: origin/developBranches to build - 3: ${sha1}Refspec: ` +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* ` - [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1.**Job config**build parameters: sha1 (default value: origin/) so technically, the job should fail as there is no branch called `origin/`Branches to build -1 : origin/masterBranches to build - 2: origin/developBranches to build - 3: ${sha1} Refspec: +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* - [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1.**Job config**build parameters: sha1 (default value: origin/) so technically, the job should fail as there is no branch called `origin/` Branches to build -1 : origin/masterBranches to build - 2: origin/developBranches to build - 3: ${sha1}- [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38406) GIT_BRANCH wrongly set.
Title: Message Title
Puneeth Nanjundaswamy created an issue
Jenkins / JENKINS-38406
GIT_BRANCH wrongly set.
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Sep/21 10:04 AM
Priority:
Major
Reporter:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually. The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. The GIT_BRANCH environment variable is overwritten with some other branch and not sha1. *Job config* build parameters: sha1 (default value: origin/) Branches to build -1 : origin/master Branches to build - 2: origin/develop Branches to build - 3: $ {sha1}
[√ ] Build when a change is pushed to GitHub
[√ ] GitHub Pull Request Builder
*Jenkins and plugin versions* jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0 GitHub API Plugin: 1.77 GitHub plugin: 1.21.1 GitHub Pull Request Builder: 1.33.1
[JIRA] (JENKINS-38405) MultiJob Plugin: 1.22 - java.lang.InterruptedException: sleep interrupted
Title: Message Title Puneeth Nanjundaswamy created an issue Jenkins / JENKINS-38405 MultiJob Plugin: 1.22 - java.lang.InterruptedException: sleep interrupted Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 2016/Sep/21 9:17 AM Priority: Minor Reporter: Puneeth Nanjundaswamy Multijob plugin logs errors when a multijob is aborted. Jenkins: 2.7.1 MultiJob Plugin: 1.22 INFO: test_some_jenkins_job #423 aborted java.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:432) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:136) at hudson.model.Run.execute(Run.java:1741) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)
[JIRA] (JENKINS-30300) Unable to specify a branch to build when using parameterized job with multiple branches
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-30300 Re: Unable to specify a branch to build when using parameterized job with multiple branches I have the same issue. Any updates on this? 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-38382) Github and ghprb plugins don't seem to work in harmony
Title: Message Title
Puneeth Nanjundaswamy updated an issue
Jenkins / JENKINS-38382
Github and ghprb plugins don't seem to work in harmony
Change By:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually.The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`.**Job config**build parameters: sha1 (default value: origin/)Branches to build: origin/masterBranches to build: origin/developBranches to build: origin/ ${sha1}- [√ ] Build when a change is pushed to GitHub- [√ ] GitHub Pull Request Builder**Jenkins and plugin versions**jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0GitHub API Plugin: 1.77 GitHub plugin: 1.21.1GitHub Pull Request Builder: 1.33.1
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38382) Github and ghprb plugins don't seem to work in harmony
Title: Message Title
Puneeth Nanjundaswamy created an issue
Jenkins / JENKINS-38382
Github and ghprb plugins don't seem to work in harmony
Issue Type:
Bug
Assignee:
Honza Brázdil
Components:
ghprb-plugin, github-plugin
Created:
2016/Sep/20 4:34 PM
Priority:
Minor
Reporter:
Puneeth Nanjundaswamy
I have a jenkins job that runs when code is pushed to `master` and `develop` branch. This job also picks up PRs. This job also has `sha1` as a build parameter to trigger builds manually. The job picks up PRs and builds them. Same with pushes to `master` or `develop`. The issue is when The job is triggered manually. It seems to pickup a random branch. sometimes a PR, sometimes `origin/develop`. *Job config* build parameters: sha1 (default value: origin/) Branches to build: origin/master Branches to build: origin/develop Branches to build: origin/$ {sha1}
[√ ] Build when a change is pushed to GitHub
[√ ] GitHub Pull Request Builder
*Jenkins and plugin versions* jenkins version: 2.7.1 Git client plugin: 2.0.0 Git plugin: 3.0.0 GitHub API Plugin: 1.77 GitHub plugin: 1.21.1 GitHub Pull Request Builder: 1.33.1
[JIRA] (JENKINS-31707) manually trigger builds using ghprb don't add comments to the pull request
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-31707 Re: manually trigger builds using ghprb don't add comments to the pull request For manual triggers AFAIK no unless you use the "Rebuild" plugin for jenkins. With the "Rebuild" plugin, the status should be updated back on github. It works with jenkins 1.6xx and 1,29.x 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-33873) Unable to update GitHub PR status
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-33873 Re: Unable to update GitHub PR status Can you please also show the advanced settings of ghprb? 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] [rebuild-plugin] (JENKINS-29671) Latest version of Rebuild Plugin does not use all environment parameters while rebuilding.
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-29671 Re: Latest version of Rebuild Plugin does not use all environment parameters while rebuilding. We are facing the same issues with jenkins 1.634 and rebuilder plugin 1.25 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.
